🔥Limbo Tournaments🔥 pinned Deleted message

Channel
🔥Limbo Tournaments🔥
@b9boost
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,201subscribers
-3,592 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1004464403579 |
|---|---|
| Type | Channel |
| Username | @b9boost |
| Created | 22 June 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/b9boost |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 12 Oct 2026, 08:02 | 1,201 | -38 |
| 5 Oct 2026, 13:39 | 1,239 | -39 |
| 27 Sept 2026, 23:17 | 1,278 | -156 |
| 15 Sept 2026, 07:59 | 1,434 | -34 |
| 11 Sept 2026, 08:37 | 1,468 | -27 |
| 6 Sept 2026, 20:39 | 1,495 | -30 |
| 1 Sept 2026, 22:56 | 1,525 | -22 |
| 30 Aug 2026, 06:54 | 1,547 | -154 |
| 26 Aug 2026, 23:42 | 1,701 | -622 |
| 23 Aug 2026, 23:26 | 2,323 | -567 |
| 20 Aug 2026, 15:02 | 2,890 | -154 |
| 17 Aug 2026, 11:27 | 3,044 | -141 |
| 14 Aug 2026, 08:26 | 3,185 | -102 |
| 11 Aug 2026, 08:48 | 3,287 | -558 |
| 8 Aug 2026, 16:53 | 3,845 | -948 |
| 7 Aug 2026, 19:48 | 4,793 | no change |
| 7 Aug 2026, 19:39 | 4,793 | first reading |
Engagement
17 posts held, back to 22 June 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel name was changed to «🔥Limbo Tournaments🔥»
Channel name was changed to «Limbo Tournaments»
🔥Limbo Tournaments🔥 pinned Deleted message
Channel name was changed to «🩸 LIMBO X HEAD🩸»
🔥Limbo Tournaments🔥 pinned Deleted message
🔥Limbo Tournaments🔥 pinned Deleted message
🔥Limbo Tournaments🔥 pinned Deleted message
🔥Limbo Tournaments🔥 pinned Deleted message
🔥Limbo Tournaments🔥 pinned Deleted message
🔥Limbo Tournaments🔥 pinned Deleted message
🔥Limbo Tournaments🔥 pinned Deleted message
Showing the 12 most recent of 17 posts we hold for @b9boost. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“🔥Limbo Tournaments🔥” (@b9boost), 1,201 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/b9boost.
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.