22. Armeekorps #457032603
Membership history
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 19 Nov 2026, 03:46 | 79 | +3 |
| 7 Nov 2026, 14:36 | 76 | -4 |
| 31 Oct 2026, 03:15 | 80 | +3 |
| 22 Oct 2026, 04:10 | 77 | +4 |
| 17 Oct 2026, 11:09 | 73 | +8 |
| 8 Oct 2026, 14:35 | 65 | +4 |
| 6 Oct 2026, 10:54 | 61 | +30 |
| 26 Sept 2026, 15:06 | 31 | first 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 ZedlitzDio (@Retroficial) as measured.
Changed hands 1 time
Transferred from user #5518385487 to user #376285347 — observed between sweeps, detected 29 Sept 2026, 22:56 UTC
Detection dates bound when a change was seen by this register, not when it happened.
Groups seen changing owner — the largest ever handed over and the most recent — are on the ownership transfers board.
Members we’ve seen
zuj4w (@JaakIvanov) — zuj4w (rank 254)
Prokuror (@dlyat_2) — OK (rank 252)
@LightMt07 — Königlich Bayerisches 1. Jägerbataillon „König“ (rank 6)
Yuri (@crispsontoast01) — Königlich Bayerisches 1. Jägerbataillon „König“ (rank 6)
obfs4 (@Iced_22) — Königlich Bayerisches 1. Jägerbataillon „König“ (rank 6)
EntityDan (@Danster2206) — Königlich Bayerisches 1. Jägerbataillon „König“ (rank 6)
Siba (@happydragon2014) — Königlich Bayerisches 1. Jägerbataillon „König“ (rank 6)
anchrd (@David_PJO) — Königlich Bayerisches 1. Jägerbataillon „König“ (rank 6)
A sample — only members this register has independently measured, highest rank first. Not the full roster.
Name history
22. Armeekorps — seen 26 September 2026 → current
Іnnеndіеnst — seen 6 September 2026 → 26 September 2026
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.