Roblox RegisterIndependent record of Roblox groups · not affiliated with Roblox Corporation
Ryu no Michi 戦

Ryu no Michi 戦 #8703293

14
members (measured 10 Nov 2026, 08:10 UTC)
22 December 2020
created (per Roblox API)
10 August 2026
first measured by this register

RoleplayJAroleplayyakuzafictional

Description

Ryu no Michi — the Dragon’s Path. A trail marked by blood, betrayal, and power. Those who follow it rise above men… or are consumed by their own fire.”

Written by the group; not a statement by this register.

Membership history

Growth

141514.521 September 2026 — 15 members10 November 2026 — 14 members21 September 202610 November 2026
2 measurements spanning 50 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 14–15 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
10 Nov 2026, 08:1014-1
21 Sept 2026, 15:1515first reading

Daily: the last measured count of each UTC day. Days with no new reading have no point. The full per-reading record is in the CSV and JSON downloads below.

Ownership

Owned by HumbleNado (@tornadomadman3000) as measured.

Groups seen changing owner — the largest ever handed over and the most recent — are on the ownership transfers board.

Members we’ve seen

HumbleNado (@tornadomadman3000) — Owner (rank 255)

Takayuki Yagami (@Hazama3223) — Member (rank 1)

Miguel (@jackpackmr99) — Member (rank 1)

lemmings (@AloneLemmings) — Member (rank 1)

A sample — only members this register has independently measured, highest rank first. Not the full roster.

Rank structure

Owner1
Admin2
Member15
Member12
Guest0

Roles and per-rank member counts as Roblox reports them (rank 0 = guest … 255 = owner).

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.