Channel
ππππΔ°ππ
@bethizm1
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
6,460subscribers
-153 since we began measuring on 5 September 2026
Risers and fallers across the register Β· movement among entries of 3,162β10,000.
Register entry
| Telegram ID | -1001819696533 |
|---|---|
| Type | Channel |
| Username | @bethizm1 |
| Created | Between 1 October 2022 and 30 September 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 29 October 2026 |
| On Telegram | t.me/bethizm1 |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 |
|---|---|---|
| 29 Oct 2026, 08:48 | 6,460 | -6 |
| 26 Oct 2026, 03:25 | 6,466 | -18 |
| 22 Oct 2026, 18:07 | 6,484 | +6 |
| 19 Oct 2026, 06:46 | 6,478 | +4 |
| 15 Oct 2026, 23:59 | 6,474 | +4 |
| 13 Oct 2026, 05:10 | 6,470 | -49 |
| 7 Oct 2026, 02:40 | 6,519 | -24 |
| 30 Sept 2026, 05:20 | 6,543 | -58 |
| 19 Sept 2026, 14:57 | 6,601 | -12 |
| 15 Sept 2026, 04:19 | 6,613 | -8 |
| 11 Sept 2026, 23:57 | 6,621 | +37 |
| 7 Sept 2026, 11:56 | 6,584 | -29 |
| 5 Sept 2026, 12:24 | 6,613 | no change |
| 5 Sept 2026, 01:47 | 6,613 | 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.
@kuponazeresmi Β· 19,279
Telegram ranks this channel #1 of 46 here β alongside 45 others β read 2 October 2026
@tahmin_iddaa_kupon Β· 30,868
Telegram ranks this channel #18 of 33 here β alongside 32 others β read 14 September 2026
@Bizimle_tehsil Β· 29,533
Telegram ranks this channel #19 of 65 here β alongside 64 others β read 8 September 2026
@azetelebe Β· 20,520
Telegram ranks this channel #46 of 71 here β alongside 70 others β read 24 September 2026
@LORISBETS Β· 19,103
Telegram ranks this channel #69 of 81 here β alongside 80 others β read 2 October 2026
@azvak1 Β· 32,125
Telegram ranks this channel #70 of 79 here β alongside 78 others β read 5 September 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total, of which the 6 where it ranks highest are shown above. 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 29 October 2026 β this entry's latest reading, not the date you are reading this.
βππππΔ°ππβ (@bethizm1), 6,460 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/bethizm1.
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.