Channel
CRICKET LINE LIVE SCORE
@Cricket_Line_Live_Score
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,879subscribers
-124 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001714149594 |
|---|---|
| Type | Channel |
| Username | @Cricket_Line_Live_Score |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/Cricket_Line_Live_Score |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 6 Nov 2026, 16:36 | 2,879 | -4 |
| 3 Nov 2026, 06:07 | 2,883 | -5 |
| 30 Oct 2026, 22:21 | 2,888 | -2 |
| 28 Oct 2026, 06:28 | 2,890 | +1 |
| 25 Oct 2026, 03:59 | 2,889 | -4 |
| 21 Oct 2026, 19:40 | 2,893 | -3 |
| 19 Oct 2026, 00:27 | 2,896 | -5 |
| 15 Oct 2026, 16:09 | 2,901 | -8 |
| 12 Oct 2026, 21:41 | 2,909 | -17 |
| 6 Oct 2026, 10:38 | 2,926 | -13 |
| 28 Sept 2026, 22:38 | 2,939 | -13 |
| 19 Sept 2026, 13:18 | 2,952 | -6 |
| 15 Sept 2026, 03:15 | 2,958 | -3 |
| 11 Sept 2026, 23:31 | 2,961 | no change |
| 11 Sept 2026, 01:38 | 2,961 | -9 |
| 6 Sept 2026, 03:39 | 2,970 | -3 |
| 2 Sept 2026, 06:43 | 2,973 | -6 |
| 29 Aug 2026, 21:04 | 2,979 | -4 |
| 27 Aug 2026, 00:16 | 2,983 | -7 |
| 23 Aug 2026, 15:56 | 2,990 | 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.
@Aryan_Bettings · 78,366
Telegram ranks this channel #8 of 57 here — alongside 56 others — read 28 August 2026
@Cricket_Betfair_Market_Load · 74,127
Telegram ranks this channel #32 of 56 here — alongside 55 others — read 19 August 2026
@SESSION_KING_CRICKET_DANIEL8 · 81,796
Telegram ranks this channel #37 of 51 here — alongside 50 others — read 26 August 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“CRICKET LINE LIVE SCORE” (@Cricket_Line_Live_Score), 2,879 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/Cricket_Line_Live_Score.
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.