Channel
VIRAT TOSS KING
@toss_kingk
On this record: Growth · Engagement · Telegram's recommendations · Cite this entry
28,170subscribers
-103 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001612232949 |
|---|---|
| Type | Channel |
| Username | @toss_kingk |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/toss_kingk |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 15:01 | 28,170 | -103 |
| 13 Sept 2026, 23:51 | 28,273 | 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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@caribbean_premier_league_t20 · 7,784#1
@PSL_MATCH_AND_TOSS_FIXER · 280#2
@IPL_MATCHy · 1,054 (as read 14 September 2026)#3
@RANVEER_DADA_TOSS_MATCH_FIXER · 892#4
@levinho_toss_load_prediction · 2,586#5
@vsportsinfo · 650 (as read 14 September 2026)#6
@VIJAY_IPL_TOSS_MATCH_PREDICTIONS · 5,575#7
@dubaitossfixerrrr · 1,307#8
@hunttoss · 2,345#9
@livecricketprediction · 1,784#10
@Betting_Guruji_Aryan_Batting · 7,391#11
@TheMarsTossOriginal · 32,174#12
@JAMES_FIXER_BHAI · 7,394#13
@hitman_toss_king_rohit_ka_baba · 1,605#14
@PREDICTIONS_T20 · 479#15
@cricketbettingtips6979 · 17,123#16
@legend_football_fc · 25,415#17
@kittu_cricket_prediction_sunny_3 · 264#18
@adhirajxcricket · 20,822#19
@vplfix · 8,620#20
@WinningRaceHorses · 534#21
@ajitkumarpm · 3,501#22
@InstaKASforKPSC · 14,071#23
@PRINCE_BULLET_APPLE_FERRARI_LINE · 873#24
@indianracespeedtips · 1,015#25
@Nammaforesightkas · 11,100#26
Read from Telegram’s recommendation API, most recently 14 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@FreeCricketTips7 · 46,597
Telegram ranks this channel #6 of 40 here — alongside 39 others — read 13 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“VIRAT TOSS KING” (@toss_kingk), 28,170 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/toss_kingk.
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.