Telegram RegisterThe public register of Telegram
Telegram profile photo for Baazigar Cricket Report ™

Channel

Baazigar Cricket Report ™

@CRICKET_REPORT_BETTING_BAZIGAR

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

631subscribers

-583 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001810729381
TypeChannel
Username@CRICKET_REPORT_BETTING_BAZIGAR
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held22
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/CRICKET_REPORT_BETTING_BAZIGAR

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
@vccrickettips7/202726 May 2026, 14:23 UTC@CRICKET_REPORT_BETTING_BAZIGAR/1793 · this entry26 May 2026, 14:23 UTC1.00under a minute
@vccrickettips7/202827 May 2026, 15:22 UTC@CRICKET_REPORT_BETTING_BAZIGAR/1794 · this entry27 May 2026, 15:22 UTC1.00under a minute
@CRICKET_REPORT_BETTING_BAZIGAR/1797 · this entry30 May 2026, 13:02 UTC@vccrickettips7/203130 May 2026, 13:02 UTC1.00under a minute
@vccrickettips7/203230 May 2026, 13:41 UTC@CRICKET_REPORT_BETTING_BAZIGAR/1798 · this entry30 May 2026, 13:41 UTC1.00under a minute
@vccrickettips7/203331 May 2026, 07:25 UTC@CRICKET_REPORT_BETTING_BAZIGAR/1799 · this entry31 May 2026, 07:25 UTC1.00under a minute
@vccrickettips7/203431 May 2026, 14:40 UTC@CRICKET_REPORT_BETTING_BAZIGAR/1800 · this entry31 May 2026, 14:43 UTC1.002 minutes
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
@vccrickettips77 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (6–1)
@Georgbett7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (7–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 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 11 comparable posts for this entry, running 6 May 2026 to 1 June 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 @CRICKET_REPORT_BETTING_BAZIGAR — 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

6311,214922.57 August 2026 — 1,214 subscribers7 August 2026 — 1,214 subscribers11 August 2026 — 1,212 subscribers14 August 2026 — 1,209 subscribers18 August 2026 — 1,206 subscribers20 August 2026 — 1,203 subscribers24 August 2026 — 1,201 subscribers2 September 2026 — 1,198 subscribers6 September 2026 — 1,195 subscribers11 September 2026 — 1,194 subscribers15 September 2026 — 1,190 subscribers29 September 2026 — 1,176 subscribers6 October 2026 — 1,172 subscribers13 October 2026 — 1,160 subscribers15 October 2026 — 1,149 subscribers18 October 2026 — 1,134 subscribers21 October 2026 — 1,111 subscribers24 October 2026 — 1,089 subscribers27 October 2026 — 1,051 subscribers30 October 2026 — 969 subscribers6 November 2026 — 771 subscribers15 November 2026 — 631 subscribers7 August 202615 November 2026
22 measurements spanning 100 days, net -583. 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 544–1,301 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
15 Nov 2026, 21:09631-140
6 Nov 2026, 18:28771-198
30 Oct 2026, 17:56969-82
27 Oct 2026, 16:301,051-38
24 Oct 2026, 17:091,089-22
21 Oct 2026, 19:291,111-23
18 Oct 2026, 19:391,134-15
15 Oct 2026, 21:341,149-11
13 Oct 2026, 05:211,160-12
6 Oct 2026, 16:011,172-4
29 Sept 2026, 23:161,176-14
15 Sept 2026, 19:011,190-4
11 Sept 2026, 16:201,194-1
6 Sept 2026, 17:171,195-3
2 Sept 2026, 11:531,198-3
24 Aug 2026, 12:051,201-2
20 Aug 2026, 16:361,203-3
18 Aug 2026, 00:521,206-3
14 Aug 2026, 15:171,209-3
11 Aug 2026, 13:551,212first reading

Engagement

19 posts held, back to 6 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 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 19 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
28s
Average length
28s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

6 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤466.7%
👍233.3%

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 3 of the 19 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 6 May 2026 to 29 July 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

18 Jul 2026, 02:51 UTC189 viewsread 7 August 2026
Photo

🌹 जय नीम करौली बाबा🌹 𝐆𝐎𝐎𝐃 𝐌𝐎𝐑𝐍𝐈𝐍𝐆 𝐄𝐕𝐄𝐑𝐘𝐎𝐍𝐄 🔼 𝐇𝐀𝐕𝐄 𝐀 𝐍𝐈𝐂𝐄 𝐃𝐀𝐘...........✅✅✔️📊✔️✔️↗️↗️↗️↗️

21 Jun 2026, 02:01 UTC399 views3 reactionsread 7 August 2026
Video

Good morning 🌄 सभी भाई चैनल में एक्टिव रहे आज बिग धमाका होगा 🔥🔥🔥💪💪💪

❤3

1 Jun 2026, 04:35 UTC521 viewsread 7 August 2026

🏆𝗙𝗜𝗡𝗔𝗟 𝗖𝗨𝗣 𝗪𝗜𝗡𝗡𝗘𝗥 ➡️ ❤️ 𝐑𝐂 𝐁𝐄𝐍𝐆𝐀𝐋𝐔𝐑𝐔 ❤️ ✅✅ 𝗠𝗘𝗥𝗜 𝗕𝗢𝗟𝗜 𝗕𝗔𝗡𝗗𝗢𝗢𝗞 𝗞𝗜 𝗚𝗢𝗟𝗜 … 𝗘𝗞 𝗔𝗨𝗥 𝗝𝗘𝗘𝗧 𝗔𝗔𝗣𝗞𝗜 𝗝𝗛𝗢𝗟𝗜 𝗠𝗘𝗜𝗡 🙏🏻🙏🏻 𝗖𝗢𝗡𝗚𝗥𝗔𝗧𝗨𝗟𝗔𝗧𝗜𝗢𝗡𝗦 💥💥✔️❤️✅

31 May 2026, 14:43 UTC482 viewsread 7 August 2026
Photo

🏆🏆 𝗜𝗡𝗗𝗜𝗔𝗡 𝗣𝗥𝗘𝗠𝗜𝗘𝗥 𝗟𝗘𝗔𝗚𝗨𝗘 𝟮𝟬𝟮𝟲 🏆🏆 𝗠𝗔𝗧𝗖𝗛 𝗡𝗢. = 𝗙𝗜𝗡𝗔𝗟,𝗧𝟮𝟬 ❤️ 𝗥𝗖 𝗕𝗘𝗡𝗚𝗔𝗟𝗨𝗥𝗨 ❤️ 🩵🩵 🩶 𝗚𝗨𝗝𝗔𝗥𝗔𝗧 𝗧𝗜𝗧𝗔𝗡𝗦 🩶 𝗧𝗩 𝗕𝗔𝗡𝗗 𝗥𝗘𝗣𝗢𝗥𝗧...... 𝗧𝗘𝗟𝗘𝗚𝗥𝗔𝗠 𝗧𝗢𝗗 𝗥𝗘𝗣𝗢𝗥𝗧 ..... 𝗗𝗔𝗧𝗘 🗓 :- 𝟯𝟭-𝟬𝟱-𝟮𝟬𝟮𝟲 𝗧𝗜𝗠𝗘 :- 𝟳:𝟯𝟬 𝗣𝗠 𝗠𝗔𝗧𝗖𝗛 𝗪𝗜𝗡𝗡𝗘𝗥 💰 ❤️ 𝗥𝗖 𝗕𝗘𝗡𝗚𝗔𝗟𝗨𝗥𝗨 ❤️ ✅✅

31 May 2026, 07:25 UTC396 viewsread 7 August 2026
Photo

𝗧𝗢𝗦𝗦 𝗪𝗜𝗡𝗡𝗘𝗥 ▶️ ❤️ 𝗥𝗖 𝗕𝗘𝗡𝗚𝗔𝗟𝗨𝗥𝗨 ❤️ 🏆 ⚜️𝗟𝗜𝗙𝗘 𝗧𝗜𝗠𝗘 𝗟𝗢𝗦𝗦 𝗖𝗢𝗩𝗘𝗥 𝗧𝗢𝗦𝗦 ⚜️ 𝗡𝗢 𝗟𝗜𝗠𝗜𝗧 𝗙𝗜𝗫𝗘𝗗 𝗧𝗢𝗦𝗦 ✔️✔️ 𝗚𝗥𝗢𝗨𝗡𝗗 𝗙𝗜𝗫𝗜𝗡𝗚 𝗧𝗢𝗦𝗦 ✔️✔️ 🎏🙏🙏 𝗝𝗔𝗜 𝗛𝗔𝗡𝗨𝗠𝗔𝗡 𝗝𝗜 𝗞𝗜 🙏🙏🎏

30 May 2026, 13:41 UTC292 viewsread 7 August 2026
Photo

🏆🏆 𝗜𝗡𝗗𝗜𝗔 𝗪𝗢𝗠𝗘𝗡 𝗧𝗢𝗨𝗥 𝗢𝗙 𝗘𝗡𝗚𝗟𝗔𝗡𝗗 𝟮𝟬𝟮𝟲 🏆🏆 𝗠𝗔𝗧𝗖𝗛 𝗡𝗢. 𝟮𝗻𝗱,𝗧𝟮𝟬 🇮🇳 𝗜𝗡𝗗𝗜𝗔 𝗪𝗢𝗠𝗘𝗡 🇮🇳 🅰️🅰 🏴󠁧󠁢󠁥󠁮󠁧󠁿 𝗘𝗡𝗚𝗟𝗔𝗡𝗗 𝗪𝗢𝗠𝗘𝗡 🏴󠁧󠁢󠁥󠁮󠁧󠁿 𝗧𝗩 𝗕𝗔𝗡𝗗 𝗥𝗘𝗣𝗢𝗥𝗧...... 𝗧𝗘𝗟𝗘𝗚𝗥𝗔𝗠 𝗧𝗢𝗗 𝗥𝗘𝗣𝗢𝗥𝗧 ..... 𝗗𝗔𝗧𝗘 🗓 :- 𝟯𝟬-𝟬𝟱-𝟮𝟬𝟮𝟲 𝗧𝗜𝗠𝗘 :- 𝟳:𝟬𝟬 𝗣𝗠 𝗠𝗔𝗧𝗖𝗛 𝗪𝗜𝗡𝗡𝗘𝗥 💰 🇮🇳 𝗜𝗡𝗗𝗜𝗔 𝗪𝗢𝗠𝗘𝗡 🇮🇳 ✔️⭐

30 May 2026, 13:02 UTC178 viewsread 7 August 2026
Photo

🏆🏆 𝗔𝗨𝗦𝗧𝗥𝗔𝗟𝗜𝗔 𝗧𝗢𝗨𝗥 𝗢𝗙 𝗣𝗔𝗞𝗜𝗦𝗧𝗔𝗡 𝟮𝟬𝟮𝟲 🏆🏆 𝗠𝗔𝗧𝗖𝗛 𝗡𝗢. 𝟭𝗦𝗧,𝗢𝗗𝗜 🇦🇺 𝗔𝗨𝗦𝗧𝗥𝗔𝗟𝗜𝗔 🇦🇺 ⚽ 🇵🇰 𝗣𝗔𝗞𝗜𝗦𝗧𝗔𝗡 🇵🇰 𝗧𝗩 𝗕𝗔𝗡𝗗 𝗥𝗘𝗣𝗢𝗥𝗧...... 𝗧𝗘𝗟𝗘𝗚𝗥𝗔𝗠 𝗧𝗢𝗗 𝗥𝗘𝗣𝗢𝗥𝗧 ..... 𝗗𝗔𝗧𝗘 🗓 :- 𝟯𝟬-𝟬𝟱-𝟮𝟬𝟮𝟲 𝗧𝗜𝗠𝗘 :- 𝟱:𝟬𝟬 𝗣𝗠 𝗠𝗔𝗧𝗖𝗛 𝗪𝗜𝗡𝗡𝗘𝗥 💰 🇦🇺 𝗔𝗨𝗦𝗧𝗥𝗔𝗟𝗜𝗔 🇦🇺 ✅✅

27 May 2026, 15:22 UTC154 viewsread 7 August 2026
Photo

🏆🏆 𝗜𝗡𝗗𝗜𝗔𝗡 𝗣𝗥𝗘𝗠𝗜𝗘𝗥 𝗟𝗘𝗔𝗚𝗨𝗘 𝟮𝟬𝟮𝟲 🏆🏆 𝗠𝗔𝗧𝗖𝗛 𝗡𝗢. 𝗘𝗟𝗜𝗠𝗜𝗡𝗔𝗧𝗢𝗥,𝗧𝟮𝟬 🩷𝗥𝗔𝗝𝗔𝗦𝗧𝗛𝗔𝗡 𝗥𝗢𝗬𝗔𝗟𝗦 🩷 🅰️🅰️ 🧡 𝗦𝗨𝗡𝗥𝗜𝗦𝗘𝗥𝗦 𝗛𝗬𝗗𝗘𝗥𝗔𝗕𝗔𝗗 🧡 𝗧𝗩 𝗕𝗔𝗡𝗗 𝗥𝗘𝗣𝗢𝗥𝗧...... 𝗧𝗘𝗟𝗘𝗚𝗥𝗔𝗠 𝗧𝗢𝗗 𝗥𝗘𝗣𝗢𝗥𝗧 ..... 𝗗𝗔𝗧𝗘 🗓 :- 𝟮𝟳-𝟬𝟱-𝟮𝟬𝟮𝟲 𝗧𝗜𝗠𝗘 :- 𝟳:𝟯𝟬 𝗣𝗠 𝗠𝗔𝗧𝗖𝗛 𝗪𝗜𝗡𝗡𝗘𝗥 💰 🩷 𝗥𝗔𝗝𝗔𝗦𝗧𝗛𝗔𝗡 𝗥𝗢𝗬𝗔𝗟𝗦 🩷 ✔️⭐

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

Mentions

Named by 3 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.

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.

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

“Baazigar Cricket Report ™” (@CRICKET_REPORT_BETTING_BAZIGAR), 631 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/CRICKET_REPORT_BETTING_BAZIGAR.

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.