飛山鉄道 #33402044
RoleplayJAroleplaytrainrecruitment
Description
こちらは、飛山鉄道のグループです。 アップデートはいつするかわかりません。 社員を希望の場合は面接や研修が必要となってきます、面接などの時刻はこの下に多分書くと思います。
Written by the group; not a statement by this register.
Membership history
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 24 Aug 2026, 09:44 | 153 | +1 |
| 11 Aug 2026, 10:52 | 152 | -1 |
| 11 Aug 2026, 07:16 | 153 | first reading |
Ownership
Owned by YuuyamaT (@JR_2166) as measured.
Groups seen changing owner — the largest ever handed over and the most recent — are on the ownership transfers board.
Experiences
Experiences this group owns, by lifetime visits. Live-player counts are from our last measurement.
Members we’ve seen
YuuyamaT (@JR_2166) — 社長 (rank 255)
zeru_JP (@ZERUKUN6627) — 副管理者 (rank 254)
Sanstetsudou233 (@mosbbnjjjj) — 副管理者 (rank 254)
syomario (@syo_0411) — 開発者 (rank 230)
tokyukaizi (@Robloxcraft852) — 開発者 (rank 230)
EVA01_3513 (@Asahi09268) — 開発者 (rank 230)
RUKU_arM10015 (@arM10015) — 開発者 (rank 230)
00Joban (@Trainboy0906) — 人事部 (rank 200)
AkahoshiChannel (@Hsds628) — 社員 (rank 150)
@qmqqmq12 — 社員 (rank 150)
aiueo (@hankyuriichn) — 社員 (rank 150)
@tj110010 — 運転手、車掌 (rank 50)
yamaneko620 (@kazuya09208) — 運転手、車掌 (rank 50)
Bananakuni (@banana81031) — 駅員 (rank 20)
mirumeikuv (@miruku7383) — 駅員 (rank 20)
UMI_JPN (@kaikai09138) — 乗客 (rank 1)
mutumi_623 (@DOAHO_623mutumi) — 乗客 (rank 1)
kai202 (@Kainosuke202) — 乗客 (rank 1)
munmun_39 (@munmun_30) — 乗客 (rank 1)
ohalu86 (@ohaluomalu) — 乗客 (rank 1)
sakamoto_meine (@saka_moto07) — 乗客 (rank 1)
@WestTanuki — 乗客 (rank 1)
Infinite_nicky (@NNSIBUYA) — 乗客 (rank 1)
Mitarashi_Miskyahu (@yahhhhhh2024) — 乗客 (rank 1)
@kobokiti — 乗客 (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.