Channel
@Sikandar_Mumbai
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,668subscribers
-33 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001305243338 |
|---|---|
| Type | Channel |
| Username | @Sikandar_Mumbai |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Sikandar_Mumbai |
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 47% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 02:17 | 2,668 | -2 |
| 13 Sept 2026, 04:59 | 2,670 | -3 |
| 9 Sept 2026, 15:58 | 2,673 | -5 |
| 31 Aug 2026, 08:06 | 2,678 | -4 |
| 28 Aug 2026, 15:41 | 2,682 | -1 |
| 26 Aug 2026, 00:33 | 2,683 | -2 |
| 22 Aug 2026, 22:43 | 2,685 | -3 |
| 19 Aug 2026, 05:52 | 2,688 | -3 |
| 16 Aug 2026, 02:28 | 2,691 | -5 |
| 12 Aug 2026, 07:12 | 2,696 | -3 |
| 8 Aug 2026, 21:14 | 2,699 | -2 |
| 8 Aug 2026, 07:00 | 2,701 | no change |
| 8 Aug 2026, 06:53 | 2,701 | first reading |
20 posts held, back to 11 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.
➡️Baazigar✅⬇️ t.me/Baazigar_Crypto_IPL ➡️ IPL Prediction ✅🔽 t.me/IPL_King_IPL_King ➡️ Toss King Jupiter ✅⬇️ t.me/Toss_King_Crypto_IPL ➡️Cricket Toss Session✅👇 t.me/Trade_Toss_Session #Stock #Bitcoin #Trade #Trading #Durov #Movie #Crypto
Toss match @VIKRAM_DADA
Toss match @VIKRAM_DADA
MATCH ABANDONED ✅
𝐈𝐍𝐃𝐈𝐀𝐍 𝐏𝐑𝐄𝐌𝐈𝐄𝐑 𝐋𝐄𝐀𝐆𝐔𝐄 𝟐𝟎𝟐𝟔 🏆 PUNJAB VS KOLKATA MATCH WINNER - PUNJAB full Fix Match Hai....Open Challenge To Full Market Punjab Win Hogi... 𝙇𝙊𝙎𝙎𝘾𝙐𝙏 & 𝘽𝙊𝙊𝙆𝙎𝙀𝙏 𝘼𝙏 𝙇𝙊𝙒 𝙍𝘼𝙏𝙀
𝐈𝐍𝐃𝐈𝐀𝐍 𝐏𝐑𝐄𝐌𝐈𝐄𝐑 𝐋𝐄𝐀𝐆𝐔𝐄 𝟐𝟎𝟐𝟔 🏆 BENGLURU VS CHENNAI MATCH WINNER - CHENNAI full Fix Match Hai....Open Challenge To Full Market Chennai Win Hogi... 𝙇𝙊𝙎𝙎𝘾𝙐𝙏 & 𝘽𝙊𝙊𝙆𝙎𝙀𝙏 𝘼𝙏 𝙇𝙊𝙒 𝙍𝘼𝙏𝙀
💙MUMBAI💙 WIN MATCH ✅ Noncuting Match Pass.... Bolke diya sabko.... Sabne kamaya hoga... Bookie barbaad.... Esko bolte Hai kaam....
63-6 🇩🇪 KOLKATA 🇩🇪 CLOSE RATE ✔️
INDIAN PREMIER LEAGUE 2026🏆 KOLKATA VS MUMBAI MATCH WINNER - MUMBAI full Fix Match Hai....Open Challenge To Full Market Mumbai Win Hogi...
IPL 2026 1ST MATCH LOSS..👍 LOSS ACCEPT KARTA HU..🙏
82-5 🇩🇪 BENGALURU 🇩🇪 TAKE YOUR 1ST ENTRY
INDIAN PREMIER LEAGUE 2026🏆 BENGALURU VS HYDERABAD MATCH WINNER - HYDERABAD full Fix Match Hai....Open Challenge To Full Market Hyderabad Win Hogi... LOSSCUT & BOOKSET AT LOW RATE
Showing the 12 most recent of 20 posts we hold for @Sikandar_Mumbai. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Sikandar Mumbai” (@Sikandar_Mumbai), 2,668 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Sikandar_Mumbai.
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.