Channel
Bruce Bet
@brucebetgames
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
17,336subscribers
+589 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001931061274 |
|---|---|
| Type | Channel |
| Username | @brucebetgames |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 22 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 22 October 2026 |
| On Telegram | t.me/brucebetgames |
Topic
Other / unclassifiable — 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 17 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Oct 2026, 00:30 | 17,336 | +105 |
| 20 Oct 2026, 17:47 | 17,231 | +68 |
| 19 Oct 2026, 20:40 | 17,163 | +87 |
| 18 Oct 2026, 19:57 | 17,076 | +86 |
| 17 Oct 2026, 20:06 | 16,990 | +171 |
| 16 Oct 2026, 22:00 | 16,819 | +29 |
| 15 Oct 2026, 22:16 | 16,790 | +1 |
| 14 Oct 2026, 21:48 | 16,789 | -67 |
| 13 Oct 2026, 11:10 | 16,856 | +28 |
| 9 Oct 2026, 12:00 | 16,828 | +20 |
| 5 Oct 2026, 03:01 | 16,808 | +17 |
| 28 Sept 2026, 11:20 | 16,791 | +8 |
| 17 Sept 2026, 18:40 | 16,783 | +10 |
| 15 Sept 2026, 15:41 | 16,773 | +5 |
| 14 Sept 2026, 02:42 | 16,768 | +4 |
| 12 Sept 2026, 09:38 | 16,764 | +14 |
| 10 Sept 2026, 04:57 | 16,750 | -12 |
| 6 Sept 2026, 23:02 | 16,762 | +14 |
| 4 Sept 2026, 07:37 | 16,748 | +1 |
| 3 Sept 2026, 12:02 | 16,747 | 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.
@mrbetitsme · 31,568
Telegram ranks this channel #3 of 53 here — alongside 52 others — read 6 September 2026
@ampmcasino · 44,349
Telegram ranks this channel #17 of 52 here — alongside 51 others — read 3 September 2026
@hotlinecasino · 31,117
Telegram ranks this channel #22 of 57 here — alongside 56 others — read 8 September 2026
@BonanzaGameChannel · 35,801
Telegram ranks this channel #31 of 47 here — alongside 46 others — read 6 September 2026
This channel appears in 4 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 22 October 2026 — this entry's latest reading, not the date you are reading this.
“Bruce Bet” (@brucebetgames), 17,336 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/brucebetgames.
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.