Channel
Kubbet CasinO Online
@kubetgame
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
9,224subscribers
-334 since we began measuring on 4 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002060206608 |
|---|---|
| Type | Channel |
| Username | @kubetgame |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 26 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 26 October 2026 |
| On Telegram | t.me/kubetgame |
Topic
Gambling & betting — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 26 Oct 2026, 15:10 | 9,224 | -24 |
| 23 Oct 2026, 07:54 | 9,248 | -33 |
| 20 Oct 2026, 13:06 | 9,281 | -19 |
| 17 Oct 2026, 20:50 | 9,300 | -5 |
| 14 Oct 2026, 16:27 | 9,305 | -33 |
| 11 Oct 2026, 07:18 | 9,338 | -41 |
| 5 Oct 2026, 10:02 | 9,379 | -75 |
| 27 Sept 2026, 04:20 | 9,454 | -65 |
| 15 Sept 2026, 08:37 | 9,519 | -25 |
| 11 Sept 2026, 12:55 | 9,544 | -22 |
| 6 Sept 2026, 13:36 | 9,566 | +8 |
| 4 Sept 2026, 12:25 | 9,558 | no change |
| 4 Sept 2026, 05:47 | 9,558 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@brazil24h · 18,099
Telegram ranks this channel #8 of 49 here — alongside 48 others — read 4 October 2026
@yumgamethai · 54,760
Telegram ranks this channel #16 of 64 here — alongside 63 others — read 4 September 2026
@jinfuautobet · 22,121
Telegram ranks this channel #20 of 60 here — alongside 59 others — read 20 September 2026
@app438 · 60,650
Telegram ranks this channel #21 of 65 here — alongside 64 others — read 4 September 2026
@snookbet888 · 30,065
Telegram ranks this channel #25 of 51 here — alongside 50 others — read 10 September 2026
@pgslotsh · 29,125
Telegram ranks this channel #68 of 72 here — alongside 71 others — read 9 September 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“Kubbet CasinO Online” (@kubetgame), 9,224 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/kubetgame.
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.