Telegram RegisterThe public register of Telegram
Telegram profile photo for MALIK MUMBAI ( 2015 )

Channel

MALIK MUMBAI ( 2015 )

@Rajat_malik_mumbai_bombay

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

2,227subscribers

-1,797 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1001405463511
TypeChannel
Username@Rajat_malik_mumbai_bombay
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live14 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/Rajat_malik_mumbai_bombay

Topic

Gambling & betting — 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 96% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Rajat_malik_mumbai_bombay/12397 · this entry17 Apr 2026, 14:32 UTC@TENIS_TENNIS_KING/586817 Apr 2026, 14:32 UTC1.00under a minute
@Rajat_malik_mumbai_bombay/12399 · this entry18 Apr 2026, 11:53 UTC@TENIS_TENNIS_KING/587018 Apr 2026, 11:53 UTC1.00under a minute
@Rajat_malik_mumbai_bombay/12401 · this entry18 Apr 2026, 15:07 UTC@TENIS_TENNIS_KING/587218 Apr 2026, 15:08 UTC1.0072 seconds
@Rajat_malik_mumbai_bombay/12405 · this entry19 Apr 2026, 06:50 UTC@TENIS_TENNIS_KING/587619 Apr 2026, 06:50 UTC1.00under a minute
@Rajat_malik_mumbai_bombay/12408 · this entry19 Apr 2026, 12:01 UTC@TENIS_TENNIS_KING/587919 Apr 2026, 12:01 UTC1.00under a minute
@Rajat_malik_mumbai_bombay/12411 · this entry20 Apr 2026, 08:11 UTC@TENIS_TENNIS_KING/588120 Apr 2026, 08:12 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@TENIS_TENNIS_KING8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)
@pooja_verma_sakshi_patel_anjali8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 17 April 2026 to 29 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @Rajat_malik_mumbai_bombay — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2,2274,0243,125.511 August 2026 — 4,024 subscribers12 August 2026 — 4,009 subscribers15 August 2026 — 3,896 subscribers18 August 2026 — 3,778 subscribers21 August 2026 — 3,711 subscribers25 August 2026 — 3,559 subscribers27 August 2026 — 3,505 subscribers31 August 2026 — 3,423 subscribers3 September 2026 — 3,290 subscribers8 September 2026 — 3,190 subscribers12 September 2026 — 2,938 subscribers16 September 2026 — 2,819 subscribers30 September 2026 — 2,613 subscribers7 October 2026 — 2,501 subscribers13 October 2026 — 2,447 subscribers16 October 2026 — 2,378 subscribers19 October 2026 — 2,368 subscribers22 October 2026 — 2,357 subscribers25 October 2026 — 2,301 subscribers28 October 2026 — 2,294 subscribers31 October 2026 — 2,267 subscribers3 November 2026 — 2,258 subscribers6 November 2026 — 2,248 subscribers9 November 2026 — 2,239 subscribers14 November 2026 — 2,227 subscribers11 August 202614 November 2026
25 measurements spanning 95 days, net -1,797. 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 1,957–4,294 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
14 Nov 2026, 11:502,227-12
9 Nov 2026, 11:012,239-9
6 Nov 2026, 12:002,248-10
3 Nov 2026, 16:552,258-9
31 Oct 2026, 18:092,267-27
28 Oct 2026, 12:542,294-7
25 Oct 2026, 19:182,301-56
22 Oct 2026, 21:582,357-11
19 Oct 2026, 23:502,368-10
16 Oct 2026, 13:282,378-69
13 Oct 2026, 11:262,447-54
7 Oct 2026, 10:192,501-112
30 Sept 2026, 21:012,613-206
16 Sept 2026, 14:412,819-119
12 Sept 2026, 14:372,938-252
8 Sept 2026, 15:373,190-100
3 Sept 2026, 10:193,290-133
31 Aug 2026, 00:383,423-82
27 Aug 2026, 18:473,505-54
25 Aug 2026, 01:463,559first reading

Engagement

20 posts held, back to 17 April 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 29 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

19 reactions across 11 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤19100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 12 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 17 April 2026 to 29 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

29 May 2026, 14:30 UTC346 views1 reactionsread 11 August 2026

Indian Premier League 2026 Qualifier 2 T20 Match... Gujarat Titans Vs Rajasthan Royals 85p Gujarat Titans Fav. He Entry Kro...✅ Rajasthan Royals Will Win & Defend.... Play Each Every Rate On Rajasthan Win... Winner -- Rajasthan Royals ❤️ Use Only Single Limit In This Match...

❤1

21 Apr 2026, 16:53 UTC≈1,100 views4 reactionsread 11 August 2026

INDIAN PREMIER LEAGUE 2026 MATCH NO :- 31TH || T20 DELHI CAPITALS 🆚 SUNRISERS HYDERABAD MATCH WINNER --- HYDERABAD 🏆 Play with Ur Limit....👌🏻 Nothing is 💯% but it's 99.99%

❤4

21 Apr 2026, 16:50 UTC≈1,060 viewsread 11 August 2026

WINNER 🏳️‍🌈 MUMBAI 🏳️‍🌈 35p Ka Jackpot Cashed..

20 Apr 2026, 08:11 UTC≈1,100 views0 reactionsread 11 August 2026

Indian Premier League 2026 30th IPL Match... MUMBAI Vs GUJARAT Khao Open Rate Se GUJARAT Ko & MUMBAI Win Krte Chalo...✅ Mumbai Will Win & .... Play Each Every Rate On Mumbai Win... Winner -- Mumbai ...❤️ Use Only Single Limit In This Match...

20 Apr 2026, 07:57 UTC≈1,010 viewsread 11 August 2026

Dono match ache huye kal ke aaj bhi aapke sath opan मे jackpot match millega advance update ke sath

20 Apr 2026, 07:56 UTC993 views3 reactionsread 11 August 2026

**RAJASTHAN VS KOLKATA FULL PUNTER DREAM MATCH HUAA I HOPE SABNE ACHA KAMAYA HOGA** WINNER 🏳️‍🌈 PUNJAB 🏳️‍🌈

❤3

19 Apr 2026, 12:01 UTC941 views2 reactionsread 11 August 2026

INDIAN PREMIER LEAGUE 2026 ✅ Match No. 29th Lucknow Vs Punjab Winner 👉 punjab ❤️ Punjab Will Win this Match... Loss Cut & Book Set Under 20p..

❤2

19 Apr 2026, 06:50 UTC573 views1 reactionsread 11 August 2026

INDIAN PREMIER LEAGUE 2026 ✅ Match No. 28th RAJASTHAN ROYALS Vs KOLKATA KNIGHTS RIDERS Winner 👉 RAJASTHAN ❤️ RAJASTHAN Will Win this Match... Loss Cut & Book Set Under 20p..

❤1

18 Apr 2026, 18:14 UTC388 views1 reactionsread 11 August 2026

12p Chennai Kings To 👇 🇩🇪 HYDERABAD (SRH) 🇩🇪 WIN* ✅ Jackpot Mubarak Ho Sabhi Ko ❤️ Ab Kal Milenge 2 Match Hai 🙏

❤1

Showing the 12 most recent of 20 posts we hold for @Rajat_malik_mumbai_bombay. 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.

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 🏏
@MalikMumbai_Cricket_Tipper · 44,302
Telegram ranks this channel #13 of 42 here — alongside 41 others — read 27 August 2026
Bullet Ferrari Cricket
@Aryan_Bettings · 78,313
Telegram ranks this channel #30 of 57 here — alongside 56 others — read 28 August 2026
Mahakal Prediction🏏🏏
@Mahakal_Cricket_Prediction_01 · 295,416
Telegram ranks this channel #31 of 41 here — alongside 40 others — read 11 August 2026

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

“MALIK MUMBAI ( 2015 )” (@Rajat_malik_mumbai_bombay), 2,227 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Rajat_malik_mumbai_bombay.

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.