Channel
King Koopa's Shellposting Kingdom
@koopakingdom
On this record: Topic · Growth · Engagement · Citations · Cite this entry
2,002subscribers
+39 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001154150830 |
|---|---|
| Type | Channel |
| Username | @koopakingdom |
| Created | 27 May 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 21 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/koopakingdom |
Topic
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 73% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 18:09 | 2,002 | +3 |
| 31 Oct 2026, 12:36 | 1,999 | +5 |
| 28 Oct 2026, 09:56 | 1,994 | +4 |
| 23 Oct 2026, 01:47 | 1,990 | -2 |
| 20 Oct 2026, 06:34 | 1,992 | +2 |
| 14 Oct 2026, 16:50 | 1,990 | +4 |
| 5 Oct 2026, 07:56 | 1,986 | +1 |
| 26 Sept 2026, 15:18 | 1,985 | +4 |
| 21 Sept 2026, 01:54 | 1,981 | no change |
| 17 Sept 2026, 11:36 | 1,981 | -5 |
| 13 Sept 2026, 10:19 | 1,986 | -2 |
| 9 Sept 2026, 20:19 | 1,988 | +5 |
| 4 Sept 2026, 15:40 | 1,983 | +1 |
| 31 Aug 2026, 17:24 | 1,982 | -2 |
| 28 Aug 2026, 14:24 | 1,984 | +2 |
| 25 Aug 2026, 22:17 | 1,982 | +1 |
| 23 Aug 2026, 05:17 | 1,981 | +2 |
| 16 Aug 2026, 16:48 | 1,979 | +10 |
| 12 Aug 2026, 16:14 | 1,969 | +1 |
| 9 Aug 2026, 23:37 | 1,968 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@bullyingart2 · 54,3634 postsEnigmatic Ghost-cluster
@enigmaticmemes · 10,2492 postsGatinhos
@gatosestranhos · 3,8862 postsGeopolítica para Brasileiros Desinformados
@geopolmemes · 11,4162 posts/v/ do Brasil
@vdobrasil · 6,6062 postsAlt Skull's Charnel House
@AltSkull48 · 29,6961 post𝙼𝙰𝙽𝙳𝙰𝙻𝙾𝚁𝙸𝙰𝙽𝙾 𝙲𝙾𝙽𝚂𝙿𝙸𝚁𝙰𝙲𝚈
@MandalorianoConspiracy · 10,4511 postPontifex Maximunposting
@Maximiorandom · 481 postThe National Justice Party 🎉
@NationalJusticeParty · 6,1391 postCanal SEMNOME
@csemn0me · 2,5051 postesoteric vibrations theory 🌻✝️
@esotericvibes · 9,4261 postFaz o L
@fazuely · 14,3371 post/g/'s Tech Memes
@gentoomemes · 28,5391 postmindvomit
@mindvomit · 1071 post
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 3 November 2026 — this entry's latest reading, not the date you are reading this.
“King Koopa's Shellposting Kingdom” (@koopakingdom), 2,002 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/koopakingdom.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.