Channel
BETTING ITA⏳
@bettingita0
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,052subscribers
+3 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001369304062 |
|---|---|
| Type | Channel |
| Username | @bettingita0 |
| Description | • Sfatiamo i tabù del Betting📊 • Canale totalmente gratuito✅ • Per info: @Bettingita_bot 🤖 IL GIOCO E’ VIETATO AI MINORI DI ANNI 18 🔞, SE SEI MINORENNE NON GIOCARE! |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 October 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 11 |
| On Telegram | t.me/bettingita0 |
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 8 October 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 |
|---|---|---|
| 8 Oct 2026, 03:57 | 1,052 | no change |
| 30 Sept 2026, 21:38 | 1,052 | +6 |
| 16 Sept 2026, 12:55 | 1,046 | -2 |
| 12 Sept 2026, 14:59 | 1,048 | +1 |
| 8 Sept 2026, 21:57 | 1,047 | +1 |
| 3 Sept 2026, 09:42 | 1,046 | -2 |
| 31 Aug 2026, 02:24 | 1,048 | -1 |
| 28 Aug 2026, 01:42 | 1,049 | +2 |
| 24 Aug 2026, 19:14 | 1,047 | -1 |
| 18 Aug 2026, 09:12 | 1,048 | -1 |
| 17 Aug 2026, 14:30 | 1,049 | 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.
@blablive · 19,525
Telegram ranks this channel #11 of 54 here — alongside 53 others — read 1 October 2026
@DunkestOfficial · 26,501
Telegram ranks this channel #13 of 65 here — alongside 64 others — read 12 September 2026
@StrangerTop · 42,616
Telegram ranks this channel #28 of 51 here — alongside 50 others — read 30 August 2026
@BoomBetITA · 115,284
Telegram ranks this channel #31 of 64 here — alongside 63 others — read 23 August 2026
@betfoods · 104,433
Telegram ranks this channel #64 of 72 here — alongside 71 others — read 17 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total, of which the 5 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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“BETTING ITA⏳” (@bettingita0), 1,052 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/bettingita0.
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.