Channel
IPL TOSS MATCH PREDICTIONS
@TOS_IPL
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,904subscribers
-1,844 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001324509902 |
|---|---|
| Type | Channel |
| Username | @TOS_IPL |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/TOS_IPL |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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, 13:07 | 1,904 | -232 |
| 3 Nov 2026, 16:07 | 2,136 | -234 |
| 31 Oct 2026, 19:01 | 2,370 | -249 |
| 28 Oct 2026, 09:26 | 2,619 | -229 |
| 25 Oct 2026, 13:26 | 2,848 | -135 |
| 22 Oct 2026, 04:41 | 2,983 | -252 |
| 18 Oct 2026, 18:58 | 3,235 | -192 |
| 15 Oct 2026, 23:08 | 3,427 | -122 |
| 12 Oct 2026, 23:07 | 3,549 | -80 |
| 6 Oct 2026, 15:40 | 3,629 | -11 |
| 30 Sept 2026, 00:56 | 3,640 | -21 |
| 16 Sept 2026, 03:01 | 3,661 | -5 |
| 12 Sept 2026, 14:20 | 3,666 | -6 |
| 8 Sept 2026, 14:39 | 3,672 | -18 |
| 7 Sept 2026, 00:07 | 3,690 | no change |
| 3 Sept 2026, 17:19 | 3,690 | -12 |
| 31 Aug 2026, 07:48 | 3,702 | -12 |
| 28 Aug 2026, 10:28 | 3,714 | -11 |
| 25 Aug 2026, 05:26 | 3,725 | -20 |
| 22 Aug 2026, 00:27 | 3,745 | 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.
@Sky_cricket_prediction · 21,519
Telegram ranks this channel #27 of 29 here — alongside 28 others — read 22 September 2026
@Malikmumbai_oficial · 54,760
Telegram ranks this channel #33 of 53 here — alongside 52 others — read 22 August 2026
@sidragaming_Nomankhan · 141,670
Telegram ranks this channel #40 of 58 here — alongside 57 others — read 26 August 2026
@someshthakrert · 81,389
Telegram ranks this channel #45 of 52 here — alongside 51 others — read 20 August 2026
This channel appears in 4 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.
“IPL TOSS MATCH PREDICTIONS” (@TOS_IPL), 1,904 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/TOS_IPL.
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.