Channel
ดูบอลฟรี24Hr.
@ravenslot
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,588subscribers
-273 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001804215439 |
|---|---|
| Type | Channel |
| Username | @ravenslot |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/ravenslot |
Topic
Sports — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 19 Sept 2026, 14:01 | 4,588 | -24 |
| 14 Sept 2026, 18:40 | 4,612 | -21 |
| 11 Sept 2026, 01:00 | 4,633 | -35 |
| 5 Sept 2026, 15:17 | 4,668 | -26 |
| 2 Sept 2026, 20:22 | 4,694 | no change |
| 1 Sept 2026, 21:06 | 4,694 | -14 |
| 30 Aug 2026, 04:35 | 4,708 | -18 |
| 27 Aug 2026, 09:39 | 4,726 | -18 |
| 24 Aug 2026, 14:34 | 4,744 | -34 |
| 20 Aug 2026, 21:36 | 4,778 | -29 |
| 17 Aug 2026, 17:16 | 4,807 | -20 |
| 14 Aug 2026, 14:27 | 4,827 | -10 |
| 11 Aug 2026, 10:46 | 4,837 | -17 |
| 8 Aug 2026, 20:13 | 4,854 | -7 |
| 7 Aug 2026, 23:12 | 4,861 | 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.
@v1_369joker · 53,338
Telegram ranks this channel #3 of 37 here — alongside 36 others — read 4 September 2026
@betbath88 · 27,525
Telegram ranks this channel #7 of 66 here — alongside 65 others — read 10 September 2026
@Lava1688th · 25,782
Telegram ranks this channel #12 of 67 here — alongside 66 others — read 13 September 2026
@wink666plus · 38,536
Telegram ranks this channel #15 of 64 here — alongside 63 others — read 4 September 2026
@pgplay_999 · 33,547
Telegram ranks this channel #39 of 56 here — alongside 55 others — read 4 September 2026
@addbunny123 · 39,629
Telegram ranks this channel #42 of 70 here — alongside 69 others — read 4 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“ดูบอลฟรี24Hr.” (@ravenslot), 4,588 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ravenslot.
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.