Telegram RegisterThe public register of Telegram
Telegram profile photo for King Koopa's Shellposting Kingdom

Channel

King Koopa's Shellposting Kingdom

@koopakingdom

Has discussion group

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
TypeChannel
Username@koopakingdom
Created27 May 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded21 September 2026
Last confirmed live3 November 2026
Measurements held22
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.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

1,9632,0021,982.56 August 2026 — 1,963 subscribers6 August 2026 — 1,965 subscribers9 August 2026 — 1,968 subscribers12 August 2026 — 1,969 subscribers16 August 2026 — 1,979 subscribers23 August 2026 — 1,981 subscribers25 August 2026 — 1,982 subscribers28 August 2026 — 1,984 subscribers31 August 2026 — 1,982 subscribers4 September 2026 — 1,983 subscribers9 September 2026 — 1,988 subscribers13 September 2026 — 1,986 subscribers17 September 2026 — 1,981 subscribers21 September 2026 — 1,981 subscribers26 September 2026 — 1,985 subscribers5 October 2026 — 1,986 subscribers14 October 2026 — 1,990 subscribers20 October 2026 — 1,992 subscribers23 October 2026 — 1,990 subscribers28 October 2026 — 1,994 subscribers31 October 2026 — 1,999 subscribers3 November 2026 — 2,002 subscribers6 August 20263 November 2026
22 measurements spanning 89 days, net +39. 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 1,957–2,008 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
3 Nov 2026, 18:092,002+3
31 Oct 2026, 12:361,999+5
28 Oct 2026, 09:561,994+4
23 Oct 2026, 01:471,990-2
20 Oct 2026, 06:341,992+2
14 Oct 2026, 16:501,990+4
5 Oct 2026, 07:561,986+1
26 Sept 2026, 15:181,985+4
21 Sept 2026, 01:541,981no change
17 Sept 2026, 11:361,981-5
13 Sept 2026, 10:191,986-2
9 Sept 2026, 20:191,988+5
4 Sept 2026, 15:401,983+1
31 Aug 2026, 17:241,982-2
28 Aug 2026, 14:241,984+2
25 Aug 2026, 22:171,982+1
23 Aug 2026, 05:171,981+2
16 Aug 2026, 16:481,979+10
12 Aug 2026, 16:141,969+1
9 Aug 2026, 23:371,968first 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.

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.