Kitakyushu Nagamichi-gumi 初代長道 #34756799
RoleplayENJapanese CultureRoleplayClan
Description
𝐊𝐢𝐭𝐚𝐤𝐲𝐮𝐬𝐡𝐮, 𝐉𝐚𝐩𝐚𝐧 Clan Nagamichi-Gumi-初代長道 Founded 8/7/24 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 𝐉𝐮𝐧-𝐊𝐨𝐬𝐞𝐢-𝐈𝐧 𝐃𝐨𝐧𝐭 𝐑𝐞𝐩𝐫𝐞𝐬𝐞𝐧𝐭 𝐔𝐬
Written by the group; not a statement by this register.
Membership history
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 6 Sept 2026, 06:18 | 48 | -1 |
| 15 Aug 2026, 11:01 | 49 | first reading |
Ownership
Owned by @NagamichiKami 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
@NagamichiKami — 長道 (rank 255)
@OkumaMiyoshi — 会長・Kaicho (rank 254)
@gonetomb — 最高幹部・Saikō-Komon (rank 12) terminated
keitomb (@cathedricvae) — 総本部長・Sō-Honbunchō (rank 11)
excaliburtomb (@juzostomb) — 若頭・Wakagashira (rank 9) terminated
BewitchedCiao (@KandaKiyoshi) — 舎弟頭・Shateiigashira (rank 8)
aztektomb (@Coolkid668940) — 兄弟・Kyodai (rank 3) terminated
682Galleta (@cookiesgirltiti1) — 兄弟・Kyodai (rank 3)
KoRReee (@K0RIISH) — 舎弟・Shateii (rank 2)
ShinzenKagemaru (@Gurasshu) — 舎弟・Shateii (rank 2)
@spd — 準構成員・Jun-kōsei-in (rank 1)
ChoByoungJu (@Amondivo) — 準構成員・Jun-kōsei-in (rank 1) terminated
FrensoSpookyAlmeidas (@SpookyUGH) — 準構成員・Jun-kōsei-in (rank 1) terminated
OZSWPHILLY (@KingOZSWPhilly) — 準構成員・Jun-kōsei-in (rank 1)
mirrored (@cwngc) — 部屋住・Heyazumi (rank 1)
anni (@SunsetBreezez) — 準構成員・Jun-kōsei-in (rank 1)
@NaigusHazara — 部屋住・Heyazumi (rank 1)
Vade (@vadesieus) — 準構成員・Jun-kōsei-in (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.