Channel
BET365
@fixedmatchserviceBet
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,532subscribers
-785 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001166187655 |
|---|---|
| Type | Channel |
| Username | @fixedmatchserviceBet |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/fixedmatchserviceBet |
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 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 |
|---|---|---|
| 18 Sept 2026, 22:19 | 2,532 | -10 |
| 14 Sept 2026, 11:59 | 2,542 | -144 |
| 14 Sept 2026, 00:30 | 2,686 | no change |
| 10 Sept 2026, 19:19 | 2,686 | -350 |
| 5 Sept 2026, 14:17 | 3,036 | -257 |
| 1 Sept 2026, 11:14 | 3,293 | -8 |
| 29 Aug 2026, 08:18 | 3,301 | -2 |
| 26 Aug 2026, 13:34 | 3,303 | -4 |
| 23 Aug 2026, 11:37 | 3,307 | -9 |
| 19 Aug 2026, 12:03 | 3,316 | -1 |
| 18 Aug 2026, 17:30 | 3,317 | 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.
@Fixed_matcheBet365 · 58,934
Telegram ranks this channel #9 of 60 here — alongside 59 others — read 9 September 2026
@adabari · 208,414
Telegram ranks this channel #21 of 52 here — alongside 51 others — read 2 September 2026
@drawexperttipss · 101,141
Telegram ranks this channel #23 of 64 here — alongside 63 others — read 21 August 2026
@Forex_Signal_Fx_Signals_Best · 34,763
Telegram ranks this channel #53 of 60 here — alongside 59 others — read 15 September 2026
@Europefixedmatch · 133,586
Telegram ranks this channel #65 of 77 here — alongside 76 others — read 18 August 2026
@FreshersJobsUpdates · 22,745
Telegram ranks this channel #70 of 81 here — alongside 80 others — read 20 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“BET365” (@fixedmatchserviceBet), 2,532 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/fixedmatchserviceBet.
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.