Channel
π₯ππ’ππ¬ ππ₯πππππ§ πππ‘π
@RaodyCricketLine
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
10,670subscribers
-1,132 since we began measuring on 10 September 2026
Risers and fallers across the register Β· movement among entries of 10,000β31,623.
Register entry
| Telegram ID | -1001393594646 |
|---|---|
| Type | Channel |
| Username | @RaodyCricketLine |
| Created | Between 1 March 2018 and 31 July 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/RaodyCricketLine |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 30 Oct 2026, 10:55 | 10,670 | -286 |
| 29 Oct 2026, 12:09 | 10,956 | -15 |
| 28 Oct 2026, 12:59 | 10,971 | -32 |
| 27 Oct 2026, 13:36 | 11,003 | -26 |
| 26 Oct 2026, 11:21 | 11,029 | -16 |
| 25 Oct 2026, 09:35 | 11,045 | -9 |
| 24 Oct 2026, 06:07 | 11,054 | -8 |
| 23 Oct 2026, 02:44 | 11,062 | -74 |
| 22 Oct 2026, 00:34 | 11,136 | -37 |
| 20 Oct 2026, 22:19 | 11,173 | -4 |
| 19 Oct 2026, 23:50 | 11,177 | -5 |
| 18 Oct 2026, 21:36 | 11,182 | -2 |
| 18 Oct 2026, 00:26 | 11,184 | -5 |
| 17 Oct 2026, 00:15 | 11,189 | -6 |
| 16 Oct 2026, 00:05 | 11,195 | -14 |
| 14 Oct 2026, 23:40 | 11,209 | -40 |
| 13 Oct 2026, 20:18 | 11,249 | -121 |
| 10 Oct 2026, 08:56 | 11,370 | -42 |
| 6 Oct 2026, 06:20 | 11,412 | -99 |
| 1 Oct 2026, 04:38 | 11,511 | 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.
@infinitetradingroom_trading_room Β· 28,622
Telegram ranks this channel #9 of 40 here β alongside 39 others β read 10 September 2026
@session_toss_match_king_crypto Β· 20,317
Telegram ranks this channel #18 of 23 here β alongside 22 others β read 22 September 2026
@Aneesprediction Β· 24,216
Telegram ranks this channel #26 of 35 here β alongside 34 others β read 14 September 2026
This channel appears in 3 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 30 October 2026 β this entry's latest reading, not the date you are reading this.
βπ₯ππ’ππ¬ ππ₯πππππ§ πππ‘πβ (@RaodyCricketLine), 10,670 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/RaodyCricketLine.
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.