Channel
ππππ ππππ & ππΏπΏπ
@sure_1xbet_rollover
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
1,724subscribers
-89 since we began measuring on 23 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001154050202 |
|---|---|
| Type | Channel |
| Username | @sure_1xbet_rollover |
| Created | Between 1 September 2018 and 31 May 2022 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/sure_1xbet_rollover |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 41% 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 |
|---|---|---|
| 5 Nov 2026, 22:05 | 1,724 | -1 |
| 2 Nov 2026, 22:20 | 1,725 | -1 |
| 30 Oct 2026, 20:58 | 1,726 | -9 |
| 28 Oct 2026, 03:26 | 1,735 | -4 |
| 25 Oct 2026, 02:29 | 1,739 | -7 |
| 22 Oct 2026, 03:16 | 1,746 | -10 |
| 18 Oct 2026, 19:38 | 1,756 | -15 |
| 15 Oct 2026, 21:06 | 1,771 | -1 |
| 12 Oct 2026, 20:29 | 1,772 | -2 |
| 6 Oct 2026, 05:58 | 1,774 | -13 |
| 29 Sept 2026, 01:41 | 1,787 | -10 |
| 23 Sept 2026, 03:04 | 1,797 | no change |
| 19 Sept 2026, 05:56 | 1,797 | +4 |
| 15 Sept 2026, 01:18 | 1,793 | -5 |
| 11 Sept 2026, 06:18 | 1,798 | +1 |
| 6 Sept 2026, 10:17 | 1,797 | -5 |
| 2 Sept 2026, 06:06 | 1,802 | -2 |
| 30 Aug 2026, 16:47 | 1,804 | -6 |
| 27 Aug 2026, 19:43 | 1,810 | -3 |
| 23 Aug 2026, 12:30 | 1,813 | 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.
@sure_odds_1xbet Β· 22,598
Telegram ranks this channel #15 of 56 here β alongside 55 others β read 22 September 2026
@SportyBetBr Β· 28,408
Telegram ranks this channel #21 of 47 here β alongside 46 others β read 13 September 2026
@sportybet_free_codes Β· 67,352
Telegram ranks this channel #22 of 58 here β alongside 57 others β read 23 August 2026
@accuratedailytips2022 Β· 73,223
Telegram ranks this channel #24 of 75 here β alongside 74 others β read 5 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 5 November 2026 β this entry's latest reading, not the date you are reading this.
βππππ ππππ & ππΏπΏπβ (@sure_1xbet_rollover), 1,724 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/sure_1xbet_rollover.
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.