砂浜電気鉄道 #33909434
Community & socialJAcommunityroleplaymap_development
Description
このグループは廃業済みの砂浜電気鉄道公式グループです。ここでは、雑談などをするコミュニティです。また、せっかくなので砂浜電気鉄道探索マップの制作予定です。
Written by the group; not a statement by this register.
Membership history
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 24 Aug 2026, 23:10 | 510 | -1 |
| 10 Aug 2026, 23:16 | 511 | first reading |
Ownership
Owned by @memorrer as measured.
Experiences
Experiences this group owns, by lifetime visits. Live-player counts are from our last measurement.
Members we’ve seen
@memorrer — [OW]社長/最高責任者 (rank 255)
MASAHIROLOVE_Banana (@Bananamanfollower123) — [AD]荒らし対策部 (rank 252)
sakamoto_meine (@saka_moto07) — [DV]開発者 (rank 251)
@Dauaa2525 — [DV]開発者 (rank 251)
00_raivaru (@keitaakasaki) — [DV]開発者 (rank 251)
HARUMAKI7070_JPN (@HARUMAKI31315) — [DV]開発者 (rank 251)
Sanstetsudou233 (@mosbbnjjjj) — [DV]開発者 (rank 251)
Omaturidaisuki (@yusari2013) — [DV]開発者 (rank 251)
yoryu (@yoshi22911) — [DV]開発者 (rank 251)
SY5703F (@sorapon07) — [OM]運行管理者 (rank 250)
@no20ummt — [OM]運行管理者 (rank 250)
@qmqqmq12 — [EP]社員 (rank 249)
Mitarashi_Miskyahu (@yahhhhhh2024) — [EP]社員 (rank 249)
munmun_39 (@munmun_30) — [EP]社員 (rank 249)
AkahoshiChannel (@Hsds628) — [TN]研修生 (rank 2)
Yokosuga_take3 (@Rurito60101) — [MB]お客様 (rank 1)
sougennJP (@opa123417) — [MB]お客様 (rank 1)
e223_200 (@HANNKYU23005) — [MB]お客様 (rank 1)
@pokakinnw — [MB]お客様 (rank 1)
Aizu (@Sorapsann) — [MB]お客様 (rank 1)
tokyukaizi (@Robloxcraft852) — [MB]お客様 (rank 1)
Kurikyu_OM (@GameMasterof_Roblox4) — [MB]お客様 (rank 1)
あぉのだよん (@56748yuya) — [MB]お客様 (rank 1)
VGF_Meowl (@kazyo67) — [MB]お客様 (rank 1)
hamham2525 (@MochaMochaXO) — [MB]お客様 (rank 1)
A sample — only members this register has independently measured, highest rank first. Not the full roster.
Rank structure
Roles and per-rank member counts as Roblox reports them (rank 0 = guest … 255 = owner).
Related groups
Groups whose measured members overlap with this one — a sample from our membership graph.
Open data
Download this group’s measured record — free to reuse with attribution: membership history (CSV) · full record (JSON)
Each file carries its licence and retrieval time inside it, and is generated from the same measurements shown above.