Telegram RegisterThe public register of Telegram
Telegram profile photo for Naman Tyagi

Channel

Naman Tyagi

@namantyagiofficial

Verified by Telegram

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Cite this entry

7,941subscribers

-857 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-1001349783526
TypeChannel
Username@namantyagiofficial
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/namantyagiofficial

Topic

Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 77% 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 4 other registered channels. This entry also sits inside a group of 5 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
@namantyagiofficial/3026 · this entry6 May 2026, 14:21 UTC@Match_Football/42716 May 2026, 14:23 UTC1.002 minutes
@namantyagiofficial/3032 · this entry16 May 2026, 14:10 UTC@Match_Football/427616 May 2026, 14:12 UTC1.002 minutes
@namantyagiofficial/3038 · this entry22 May 2026, 14:27 UTC@Match_Football/428222 May 2026, 15:24 UTC1.0058 minutes
@namantyagiofficial/3039 · this entry23 May 2026, 14:01 UTC@Match_Football/428323 May 2026, 14:03 UTC1.002 minutes
@namantyagiofficial/3041 · this entry26 May 2026, 14:13 UTC@Match_Football/428526 May 2026, 14:15 UTC1.002 minutes
@namantyagiofficial/3042 · this entry27 May 2026, 14:06 UTC@Match_Football/428627 May 2026, 14:08 UTC1.0072 seconds
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
@Match_Football19 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (19–0)
@Tennis_Match19 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (19–0)
@Namanpachori19 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (13–6)
@Jaanvi_and_Maanvi_Cricket_Report16 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (16–0)

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 6 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 20 comparable posts for this entry, running 5 May 2026 to 31 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 5 channels, the one whose matching posts we hold earliest is @Jaanvi_and_Maanvi_Cricket_Report. 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 5 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

7,9418,7988,369.57 August 2026 — 8,798 subscribers7 August 2026 — 8,798 subscribers7 August 2026 — 8,790 subscribers11 August 2026 — 8,763 subscribers14 August 2026 — 8,732 subscribers17 August 2026 — 8,697 subscribers21 August 2026 — 8,668 subscribers24 August 2026 — 8,647 subscribers27 August 2026 — 8,629 subscribers30 August 2026 — 8,606 subscribers2 September 2026 — 8,583 subscribers5 September 2026 — 8,559 subscribers10 September 2026 — 8,527 subscribers14 September 2026 — 8,508 subscribers18 September 2026 — 8,488 subscribers27 September 2026 — 8,436 subscribers5 October 2026 — 8,374 subscribers12 October 2026 — 8,301 subscribers15 October 2026 — 8,264 subscribers18 October 2026 — 8,232 subscribers21 October 2026 — 8,203 subscribers24 October 2026 — 8,162 subscribers27 October 2026 — 8,141 subscribers30 October 2026 — 8,113 subscribers1 November 2026 — 8,094 subscribers4 November 2026 — 8,064 subscribers8 November 2026 — 8,029 subscribers11 November 2026 — 7,994 subscribers17 November 2026 — 7,941 subscribers7 August 202617 November 2026
29 measurements spanning 102 days, net -857. 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 7,812–8,927 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
17 Nov 2026, 13:107,941-53
11 Nov 2026, 23:167,994-35
8 Nov 2026, 03:018,029-35
4 Nov 2026, 17:468,064-30
1 Nov 2026, 19:208,094-19
30 Oct 2026, 05:308,113-28
27 Oct 2026, 03:288,141-21
24 Oct 2026, 10:198,162-41
21 Oct 2026, 03:068,203-29
18 Oct 2026, 01:488,232-32
15 Oct 2026, 03:498,264-37
12 Oct 2026, 10:378,301-73
5 Oct 2026, 17:408,374-62
27 Sept 2026, 21:178,436-52
18 Sept 2026, 06:178,488-20
14 Sept 2026, 03:558,508-19
10 Sept 2026, 15:398,527-32
5 Sept 2026, 16:568,559-24
2 Sept 2026, 00:248,583-23
30 Aug 2026, 05:188,606first reading

Engagement

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

What this channel posts

Photos
≈1,200
Links
≈181

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

31 May 2026, 14:31 UTC972 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 FINAL 🏏 ROYALS CHALLENGERS BANGLORE VS GUJRAT TITANS MATCH WINNER PREDICTION ➡️ BANGLORE OR RCB WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

29 May 2026, 14:17 UTC936 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 QUALIFIER 2ND 🏏 RAJASTHAN ROYALS VS GUJRAT TITANS MATCH WINNER PREDICTION ➡️ GUJRAT OR GT WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

27 May 2026, 14:06 UTC777 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 ELEMINATION 1ST 🏏 RAJASTHAN ROYALS VS SUNRISERS HYDERABAD MATCH WINNER PREDICTION ➡️ HYDERABAD OR SRH WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

26 May 2026, 14:13 UTC747 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 QUALIFER 1ST 🏏 GUJRAT TITANS VS ROYAL CHALLENGERS BANGLORE MATCH WINNER PREDICTION ➡️ GUJRAT OR GT WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

24 May 2026, 10:21 UTC415 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 69TH T20 🏏 MUMBAI INDIANS VS RAJASTHAN ROYALS MATCH WINNER PREDICTION ➡️ MUMBAI OR MI WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

23 May 2026, 14:01 UTC348 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 68TH T20 🏏 LUCKNOW SUPER KINGS VS PUNJAB KINGS MATCH WINNER PREDICTION ➡️ PUNJAB OR PKBS WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

22 May 2026, 14:27 UTC311 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 67TH T20 🏏 SUNRISERS HYDERABAD VS ROYAL CHALLENGERS BANGLORE MATCH WINNER PREDICTION ➡️ BANGLORE OR RCB WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

21 May 2026, 14:16 UTC300 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 66TH T20 🏏 CHENNAI SUPER KINGS VS GUJRAT TITANS MATCH WINNER PREDICTION ➡️ GUJARAT OR GT WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

20 May 2026, 14:07 UTC297 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 65TH T20 🏏 MUMBAI INDIAN VS KOLKATA KNIGHT RIDERS MATCH WINNER PREDICTION ➡️ KOLKATA OR KKR WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

19 May 2026, 14:05 UTC290 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 64TH T20 🏏 RAJASTHAN ROYALS VS LUCKNOW SUPER GIANTS MATCH WINNER PREDICTION ➡️ RAJASTHAN OR RR WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

18 May 2026, 14:10 UTC295 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 63TH T20 🏏 CHENNAI SUPER KINGS VS SUNRISERS HYDERABAD MATCH WINNER PREDICTION ➡️ HYDERABAD OR SRH WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

17 May 2026, 10:11 UTC294 viewsread 18 November 2026

🏆INDIAN PREMIER LEAGUE 2026🏆 61ST T20 🏏 PUNJAB KINGS VS ROYAL CHALLENGERS BANGLORE MATCH WINNER PREDICTION ➡️ PUNJAB OR PKBS WILL COME BELOW 20 PAISA Verified Channel ka Link Share Kardo Sab Dosto ko 👇 https://t.me/+qcD5LdmqYgYwMGE0 #NAMAN_CRICKET ✅ ˢᵉᵃʳᶜʰ ᵒⁿ ᵀᵉˡᵉᵍʳᵃᵐ

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

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

“Naman Tyagi” (@namantyagiofficial), 7,941 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/namantyagiofficial.

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.