Channel
PUNTAJES CORRECTOS GARANTIZADOS📍
@bet365baller
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,497subscribers
-894 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 | -1002104362699 |
|---|---|
| Type | Channel |
| Username | @bet365baller |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/bet365baller |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 3 Nov 2026, 00:49 | 2,497 | -46 |
| 31 Oct 2026, 09:56 | 2,543 | -14 |
| 28 Oct 2026, 14:26 | 2,557 | -10 |
| 25 Oct 2026, 13:27 | 2,567 | -28 |
| 22 Oct 2026, 04:50 | 2,595 | -39 |
| 18 Oct 2026, 23:35 | 2,634 | -40 |
| 15 Oct 2026, 16:51 | 2,674 | -49 |
| 12 Oct 2026, 12:51 | 2,723 | -50 |
| 6 Oct 2026, 03:42 | 2,773 | -44 |
| 28 Sept 2026, 18:40 | 2,817 | -115 |
| 15 Sept 2026, 23:41 | 2,932 | -30 |
| 12 Sept 2026, 14:18 | 2,962 | -41 |
| 11 Sept 2026, 14:10 | 3,003 | no change |
| 8 Sept 2026, 05:00 | 3,003 | -35 |
| 2 Sept 2026, 23:38 | 3,038 | -50 |
| 30 Aug 2026, 22:54 | 3,088 | -21 |
| 28 Aug 2026, 03:33 | 3,109 | -12 |
| 24 Aug 2026, 20:37 | 3,121 | -10 |
| 20 Aug 2026, 19:23 | 3,131 | -18 |
| 18 Aug 2026, 03:34 | 3,149 | 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.
@garricmateoEAFC365cs · 133,968
Telegram ranks this channel #1 of 68 here — alongside 67 others — read 2 September 2026
@daniel_vieda_inversiones · 10,418
Telegram ranks this channel #5 of 30 here — alongside 29 others — read 8 September 2026
@soyeltiotony · 26,150
Telegram ranks this channel #39 of 69 here — alongside 68 others — read 11 September 2026
@ivanteevka_live · 18,453
Telegram ranks this channel #48 of 51 here — alongside 50 others — read 4 October 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“PUNTAJES CORRECTOS GARANTIZADOS📍” (@bet365baller), 2,497 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/bet365baller.
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.