Telegram RegisterThe public register of Telegram
Telegram profile photo for COME TO WIN

Channel

COME TO WIN

@Malik_mumbai_official_2026

On this record: Topic · Growth · Engagement · Citations · Cite this entry

6,836subscribers

+177 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002297505297
TypeChannel
Username@Malik_mumbai_official_2026
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live26 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/Malik_mumbai_official_2026

Topic

Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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

6,6586,8366,7477 August 2026 — 6,659 subscribers7 August 2026 — 6,658 subscribers10 August 2026 — 6,660 subscribers13 August 2026 — 6,665 subscribers16 August 2026 — 6,673 subscribers19 August 2026 — 6,684 subscribers23 August 2026 — 6,702 subscribers26 August 2026 — 6,704 subscribers27 August 2026 — 6,704 subscribers28 August 2026 — 6,713 subscribers31 August 2026 — 6,712 subscribers3 September 2026 — 6,716 subscribers9 September 2026 — 6,726 subscribers13 September 2026 — 6,729 subscribers17 September 2026 — 6,772 subscribers26 September 2026 — 6,836 subscribers7 August 202626 September 2026
16 measurements spanning 50 days, net +177. 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 6,631–6,863 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 05:006,836+64
17 Sept 2026, 14:216,772+43
13 Sept 2026, 09:186,729+3
9 Sept 2026, 04:146,726+10
3 Sept 2026, 11:566,716+4
31 Aug 2026, 11:246,712-1
28 Aug 2026, 22:066,713+9
27 Aug 2026, 22:006,704no change
26 Aug 2026, 05:276,704+2
23 Aug 2026, 09:386,702+18
19 Aug 2026, 15:576,684+11
16 Aug 2026, 15:486,673+8
13 Aug 2026, 06:266,665+5
10 Aug 2026, 11:326,660+2
7 Aug 2026, 20:546,658-1
7 Aug 2026, 11:476,659first 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“COME TO WIN” (@Malik_mumbai_official_2026), 6,836 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/Malik_mumbai_official_2026.

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.