Telegram RegisterThe public register of Telegram
Telegram profile photo for WORLD CUP TOSS MATCH

Channel

WORLD CUP TOSS MATCH

@WORLD_CUP_TOSS_MATCH_SESSIONNS

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

57,752subscribers

-1,535 since we began measuring on 1 September 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001617972342
TypeChannel
Username@WORLD_CUP_TOSS_MATCH_SESSIONNS
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live27 October 2026
Measurements held28
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/WORLD_CUP_TOSS_MATCH_SESSIONNS

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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

57,75259,28758,519.51 September 2026 — 59,287 subscribers1 September 2026 — 59,287 subscribers1 September 2026 — 59,278 subscribers2 September 2026 — 59,237 subscribers4 September 2026 — 59,190 subscribers7 September 2026 — 59,080 subscribers10 September 2026 — 58,958 subscribers12 September 2026 — 58,908 subscribers13 September 2026 — 58,866 subscribers15 September 2026 — 58,831 subscribers17 September 2026 — 58,771 subscribers27 September 2026 — 58,564 subscribers4 October 2026 — 58,402 subscribers9 October 2026 — 58,294 subscribers13 October 2026 — 58,201 subscribers14 October 2026 — 58,151 subscribers15 October 2026 — 58,119 subscribers16 October 2026 — 58,081 subscribers17 October 2026 — 58,024 subscribers18 October 2026 — 57,990 subscribers19 October 2026 — 57,954 subscribers20 October 2026 — 57,932 subscribers22 October 2026 — 57,896 subscribers23 October 2026 — 57,858 subscribers24 October 2026 — 57,816 subscribers24 October 2026 — 57,790 subscribers26 October 2026 — 57,769 subscribers27 October 2026 — 57,752 subscribers1 September 202627 October 2026
28 measurements spanning 56 days, net -1,535. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 57,522–59,517 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
27 Oct 2026, 00:2057,752-17
26 Oct 2026, 01:3057,769-21
24 Oct 2026, 22:3657,790-26
24 Oct 2026, 01:1157,816-42
23 Oct 2026, 02:1057,858-38
22 Oct 2026, 03:1857,896-36
20 Oct 2026, 19:0957,932-22
19 Oct 2026, 17:3657,954-36
18 Oct 2026, 20:1757,990-34
17 Oct 2026, 19:4058,024-57
16 Oct 2026, 22:1658,081-38
15 Oct 2026, 22:2858,119-32
14 Oct 2026, 20:5858,151-50
13 Oct 2026, 09:3458,201-93
9 Oct 2026, 06:4058,294-108
4 Oct 2026, 19:1858,402-162
27 Sept 2026, 03:3658,564-207
17 Sept 2026, 12:3958,771-60
15 Sept 2026, 12:5658,831-35
13 Sept 2026, 22:3958,866first reading

Engagement

No public post preview. We read this entry on 1 September 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

Malik Mumbai
@Malik_Mumbaibhai1 · 21,998
#1
MALIK MUMBAI
@malikmumbailearn · 105,225 (as read 1 September 2026)
#2
MELBET MEGAPARI MATCH 1WIN INDIA🇮🇳
@MELBET_MEGAPARI_1WIN · 36,997
#3
Kunal Rathi SpiderMan 🧿
@KunalRathiSpiderMan · 5,409
#4
RANVEER DADA
@RANVEER_DADA_TOSS_MATCH_FIXER · 872
#5
New search @sonylineofficial
@SonyLine · 52,884
#6
BetFIRE - Cricket Trader
@betfire00 · 1,033
#7
DEVID 1XBET BET365 BETFAIR
@DEVID_1XBET_BET365_BETFAIR · 46,205
#8
IPL T20 MATCH TOSS FIXER 🏆
@IPL_T20_MATCH_PREDICTION_2025 · 515
#9
PREDICTION™️
@sagarprediction_01 · 6,216
#10
SMRITI MANDHANA
@smiriti_g · 89,874
#11
Ipl Match Report ❤️
@ipl_match_reportd · 1,790
#12
MITHALI RAJ
@Monukumarsingh · 95,915
#13
HARMANPREET KAUR
@harman_preet_kaur1 · 94,056
#14
TODAY MATCH PREDICTION
@Today_Match_Toss_Prediction · 13,002
#15
CRIC BY RAHUL [ 2020 ]♤
@cricbyrahull · 7,243
#16
SANJEEV CHAWLA ORIGINAL
@chawla_sanjeevpro · 7,492
#17
Salim Mumbai
@Mumbai_Salim · 1,511
#18
CRICBOUNCER TOSS LINE ™
@CRICBOUNCERTOSSLINE · 13,409
#19
Bablu Balast 🔥
@Bk_Roy_vipin_Singh · 202,759
#20
Chetan Singh Cricket Tips 🔵
@Chetan_Singh_Chetansing · 3,188
#21
Ferrari 🏆
@ferrailiveline · 1,232
#22
Betting Trader kannada
@karnataca · 275
#23
Football Expert Betting Predictions
@footballexpertbettingpredictions · 365
#24
Prediction Raja ( Crypto )
@PredictionRaja_Prediction_Rajaa · 1,540
#25
Anurag Dwivedi 🏏
@AnuragxCricket · 1,923,087
#26
KHAN DADA
@khandada_ipl · 33,904
#27
Colorwiz Prediction
@WinnerExpertOfficial · 204
#28
DOGS Community
@dogs · 6,620,572
#29
Rohit fauji lovers 🇮🇳⚔️
@rohitfujilovers · 5,436
#30
Hamster Kombat Announcement
@hamster_kombat · 19,981,647
#31
foxblog channel
@wolfchannel2 · 2,081
#32
🇮🇳INDIAN OFFSHORE OFFICERS🚢⚓
@IndianOffshoreOfficers · 719
#33
𝐇𝐞𝐦𝐮 𝐀𝐯𝐚𝐝𝐡🫈
@ICC_MATCH_CRICKET_PREDICTION · 2,253 (as read 1 September 2026)
#34
FREE CRYPTO FINDER
@cryptolootstop · 298
#35
Rohan Cricket Fantasy
@tohancricketfantasy · 3,151
#36

Read from Telegram’s recommendation API, most recently 1 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.

Malik Mumbai
@Malik_Mumbaibhai1 · 21,998
Telegram ranks this channel #2 of 33 here — alongside 32 others — read 21 September 2026
MELBET MEGAPARI MATCH 1WIN INDIA🇮🇳
@MELBET_MEGAPARI_1WIN · 36,997
Telegram ranks this channel #12 of 40 here — alongside 39 others — read 1 September 2026

This channel appears in 2 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 27 October 2026 — this entry's latest reading, not the date you are reading this.

“WORLD CUP TOSS MATCH” (@WORLD_CUP_TOSS_MATCH_SESSIONNS), 57,752 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/WORLD_CUP_TOSS_MATCH_SESSIONNS.

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.