Telegram RegisterThe public register of Telegram
Telegram profile photo for Ayush bhai

Channel

Ayush bhai

@aayush_ayushbhai_bhai_vicky

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

2,988subscribers

-262 since we began measuring on 13 August 2026

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

Register entry

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

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@IPL_FIXER_KHAN_DADA/2149826 Mar 2026, 10:38 UTC@aayush_ayushbhai_bhai_vicky/32758 · this entry26 Mar 2026, 10:38 UTC1.00under a minute
@aayush_ayushbhai_bhai_vicky/32764 · this entry29 Mar 2026, 07:33 UTC@IPL_FIXER_KHAN_DADA/2150529 Mar 2026, 07:34 UTC1.00under a minute
@aayush_ayushbhai_bhai_vicky/32765 · this entry29 Mar 2026, 10:14 UTC@IPL_FIXER_KHAN_DADA/2150629 Mar 2026, 10:14 UTC1.00under a minute
@IPL_FIXER_KHAN_DADA/2150729 Mar 2026, 12:33 UTC@aayush_ayushbhai_bhai_vicky/32766 · this entry29 Mar 2026, 12:33 UTC1.00under a minute
@IPL_FIXER_KHAN_DADA/2150829 Mar 2026, 12:33 UTC@aayush_ayushbhai_bhai_vicky/32767 · this entry29 Mar 2026, 12:33 UTC1.00under a minute
@IPL_FIXER_KHAN_DADA/2151030 Mar 2026, 11:37 UTC@aayush_ayushbhai_bhai_vicky/32769 · this entry30 Mar 2026, 11:37 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
@IPL_FIXER_KHAN_DADA8 (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 10 comparable posts for this entry, running 26 March 2026 to 6 April 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 2 channels, the one whose matching posts we hold earliest is @aayush_ayushbhai_bhai_vicky — 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 2 registered channels linked by matching posts. 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,9883,2503,11913 August 2026 — 3,250 subscribers15 August 2026 — 3,249 subscribers18 August 2026 — 3,240 subscribers22 August 2026 — 3,227 subscribers25 August 2026 — 3,221 subscribers28 August 2026 — 3,215 subscribers30 August 2026 — 3,199 subscribers3 September 2026 — 3,186 subscribers8 September 2026 — 3,171 subscribers12 September 2026 — 3,165 subscribers16 September 2026 — 3,162 subscribers24 September 2026 — 3,146 subscribers4 October 2026 — 3,121 subscribers10 October 2026 — 3,104 subscribers14 October 2026 — 3,092 subscribers17 October 2026 — 3,085 subscribers20 October 2026 — 3,074 subscribers23 October 2026 — 3,066 subscribers25 October 2026 — 3,057 subscribers28 October 2026 — 3,045 subscribers31 October 2026 — 3,029 subscribers3 November 2026 — 3,023 subscribers6 November 2026 — 3,015 subscribers9 November 2026 — 3,000 subscribers14 November 2026 — 2,988 subscribers13 August 202614 November 2026
25 measurements spanning 92 days, net -262. 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 2,949–3,289 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, 04:102,988-12
9 Nov 2026, 12:153,000-15
6 Nov 2026, 13:563,015-8
3 Nov 2026, 17:463,023-6
31 Oct 2026, 10:073,029-16
28 Oct 2026, 11:063,045-12
25 Oct 2026, 21:193,057-9
23 Oct 2026, 06:383,066-8
20 Oct 2026, 08:293,074-11
17 Oct 2026, 13:103,085-7
14 Oct 2026, 09:453,092-12
10 Oct 2026, 18:583,104-17
4 Oct 2026, 20:223,121-25
24 Sept 2026, 21:383,146-16
16 Sept 2026, 17:383,162-3
12 Sept 2026, 17:363,165-6
8 Sept 2026, 23:413,171-15
3 Sept 2026, 12:223,186-13
30 Aug 2026, 22:043,199-16
28 Aug 2026, 00:133,215first reading

Engagement

20 posts held, back to 26 July 2025 — 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 6 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Apr 2026, 12:44 UTC309 viewsread 13 August 2026
Photo

🚩 जय श्री राम 🔱 जय हनुमान 🚩 TOSS ➡️ KOLKATA KNIGHT RIDERS 🔔 FIXED TOSS....📣 FIXED TOSS....📣 FIXED TOSS....📣 सारा जमाना जलने लगा 💥 जब नाम अपना चलने लगा 💥

6 Apr 2026, 12:44 UTC312 viewsread 13 August 2026
Photo

🚩 जय श्री राम 🔱 जय हनुमान 🚩 TOSS ➡️ RAWALPINDIZ 🔔 FIXED TOSS....📣 FIXED TOSS....📣 FIXED TOSS....📣 सारा जमाना जलने लगा 💥 जब नाम अपना चलने लगा 💥

31 Mar 2026, 11:40 UTC345 viewsread 13 August 2026
Photo

🚩 जय श्री राम 🔱 जय हनुमान 🚩 TOSS ➡️ PESHAWAR ZALMI🔔 FIXED TOSS....📣 FIXED TOSS....📣 FIXED TOSS....📣 सारा जमाना जलने लगा 💥 जब नाम अपना चलने लगा 💥

31 Mar 2026, 11:40 UTC317 viewsread 13 August 2026
Photo

🚩 जय श्री राम 🔱 जय हनुमान 🚩 TOSS ➡️ 🏏PUNJAB KINGS🏏🔔 FIXED TOSS....📣 FIXED TOSS....📣 FIXED TOSS....📣 सारा जमाना जलने लगा 💥 जब नाम अपना चलने लगा 💥

30 Mar 2026, 11:37 UTC234 viewsread 13 August 2026

🕉️ जय श्री राम 🔱 जय हनुमान 🕉️ TOSS -- 🚩 CHENNAI SUPER KINGS 🚩 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 सारा जमाना जलने लगा ❗️ जब नाम अपना चलने लगा ❗️

29 Mar 2026, 14:34 UTC195 viewsread 13 August 2026

🇱🇻 MUMBAI 🇱🇻 WON THE TOSS & OPTED TO BAT FIRST ✅ TOSS PASS ♥️♥️

29 Mar 2026, 12:33 UTC192 viewsread 13 August 2026
Photo

🕉️ जय श्री राम 🔱 जय हनुमान 🕉️ TOSS -- 🚩 MUMBAI INDIAN 🚩 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 सारा जमाना जलने लगा ❗️ जब नाम अपना चलने लगा ❗️

29 Mar 2026, 12:33 UTC164 viewsread 13 August 2026
Photo

🕉️ जय श्री राम 🔱 जय हनुमान 🕉️ TOSS -- 🚩 KARACHI KINGS 🚩 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 सारा जमाना जलने लगा ❗️ जब नाम अपना चलने लगा ❗️

29 Mar 2026, 10:14 UTC137 viewsread 13 August 2026

🇵🇰 QUETTA GLADIATORS 🇵🇰 HAVE WON THE TOSS AND OPTED TO BOWL FIRST ✔️✔️ “हमारी नकल करने के चक्कर में तो समुंदर भी सूख गए

29 Mar 2026, 07:33 UTC137 viewsread 13 August 2026
Photo

🕉️ जय श्री राम 🔱 जय हनुमान 🕉️ TOSS -- 🚩 QUETTA 🚩 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 FIXED TOSS.... 🔥 सारा जमाना जलने लगा ❗️ जब नाम अपना चलने लगा ❗️

27 Mar 2026, 03:07 UTC154 viewsread 13 August 2026

🏳️‍🌈 LAHORE QALANDARS 🏳️‍🌈 WON THE TOSS & OPTED TO BAT FIRST ✅

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

RAJAN TIPS ❤️ CRICKET BETTING PREDICTION
@rajan_ds · 119,744
Telegram ranks this channel #15 of 51 here — alongside 50 others — read 13 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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.

“Ayush bhai” (@aayush_ayushbhai_bhai_vicky), 2,988 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/aayush_ayushbhai_bhai_vicky.

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.