Channel
APEX BETTING 🔐
@apex_betting_t
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,178subscribers
-65 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002241237862 |
|---|---|
| Type | Channel |
| Username | @apex_betting_t |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/apex_betting_t |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 15 Sept 2026, 13:36 | 6,178 | -25 |
| 12 Sept 2026, 01:01 | 6,203 | -34 |
| 7 Sept 2026, 07:19 | 6,237 | -29 |
| 2 Sept 2026, 09:13 | 6,266 | +32 |
| 30 Aug 2026, 18:58 | 6,234 | +24 |
| 28 Aug 2026, 22:46 | 6,210 | no change |
| 27 Aug 2026, 23:53 | 6,210 | -29 |
| 24 Aug 2026, 22:34 | 6,239 | -4 |
| 24 Aug 2026, 07:30 | 6,243 | 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.
@Davidinfo2002 · 56,922
Telegram ranks this channel #30 of 83 here — alongside 82 others — read 24 August 2026
@Jc_Smith_Score · 24,452
Telegram ranks this channel #33 of 77 here — alongside 76 others — read 15 September 2026
@royalzone1 · 21,332
Telegram ranks this channel #60 of 79 here — alongside 78 others — read 24 September 2026
@Sportyx · 20,500
Telegram ranks this channel #71 of 85 here — alongside 84 others — read 27 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“APEX BETTING 🔐” (@apex_betting_t), 6,178 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/apex_betting_t.
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.