🚾2ed ENGLAND 🇵🇷👆🏻 🚾🚾 wicket nhi gya to sabko 10000₹ Paytm DEGA YE BNDA 😳😳☝️☝️ 🚾 All CALL 🚾 YAHAN UPER 🚾👆🏿
Signed .

Channel
@shanvimem
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
50,342subscribers
-13,311 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001161207337 |
|---|---|
| Type | Channel |
| Username | @shanvimem |
| Description | 𝘼𝙥𝙠𝙞 𝙢𝙖𝙟𝙗𝙪𝙧𝙞 𝙖𝙥𝙠𝙤 𝙢𝙚𝙧𝙚 𝙥𝙖𝙖𝙨 𝙡𝙖𝙚𝙜𝙞🙏 Channel Link 👇 https://t.me/+zD12bMQNsdNmNzk1 Owner 👉 @SHANVI_THAKUR |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/shanvimem |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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.
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.
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 9 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @shanvimem/304017 · this entry10 Oct 2026, 15:31 UTC | @DTLLEAKER_ORIGINAL/25827310 Oct 2026, 15:33 UTC | 1.00 | 2 minutes |
| @shanvimem/304149 · this entry12 Oct 2026, 03:32 UTC | @DTLLEAKER_ORIGINAL/25847012 Oct 2026, 03:32 UTC | 1.00 | under a minute |
| @shanvimem/304240 · this entry13 Oct 2026, 06:31 UTC | @DTLLEAKER_ORIGINAL/25851113 Oct 2026, 06:33 UTC | 1.00 | 2 minutes |
| @DTLLEAKER_ORIGINAL/25868614 Oct 2026, 06:33 UTC | @shanvimem/304340 · this entry14 Oct 2026, 06:35 UTC | 1.00 | 2 minutes |
| @DTLLEAKER_ORIGINAL/25977423 Oct 2026, 15:47 UTC | @shanvimem/305196 · this entry23 Oct 2026, 15:47 UTC | 1.00 | under a minute |
| @shanvimem/305587 · this entry28 Oct 2026, 03:32 UTC | @DTLLEAKER_ORIGINAL/26025528 Oct 2026, 03:33 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DTLLEAKER_ORIGINAL | 26 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (20–6) |
| @SanjaychawlaCricket | 25 (8/8 hand-verifiable sample passed) | 1.00 | 25 minutes | @SanjaychawlaCricket (16–9) |
| @peterfantasy | 23 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (16–7) |
| @ALL_TOSS_LOAD_AVAILABLE | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @tossfixer_tossload | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (12–8) |
| @ARYANTHEBRANDTOSS | 19 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (12–7) |
| @ARYAN_THE_BRAND_MATCHH | 19 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (11–8) |
| @Ferrari_Toss_Load_Original | 19 (8/8 hand-verifiable sample passed) | 0.98 | under a minute | @Ferrari_Toss_Load_Original (10–9) |
| @KINGTOSSLINE111 | 14 (8/8 hand-verifiable sample passed) | 1.00 | 19 hours | @KINGTOSSLINE111 (9–5) |
| @TheTossExpertt | 14 (8/8 hand-verifiable sample passed) | 1.00 | 30 hours | @TheTossExpertt (11–3) |
| @Cricket_it_A_Mystery | 14 (8/8 hand-verifiable sample passed) | 1.00 | 15 hours | @Cricket_it_A_Mystery (13–1) |
| @cricket_its_a_mystery | 12 (8/8 hand-verifiable sample passed) | 1.00 | 27 hours | @cricket_its_a_mystery (9–3) |
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. 159 of the 159 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 452 comparable posts for this entry, running 13 August 2026 to 17 November 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.
Of the group of 9 channels, the one whose matching posts we hold earliest is @shanvimem — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 18 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.
This channel is in a group of 9 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.
1 more channel is in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 23:37 | 50,342 | -164 |
| 14 Nov 2026, 23:48 | 50,506 | -2,714 |
| 12 Nov 2026, 01:11 | 53,220 | -254 |
| 10 Nov 2026, 05:58 | 53,474 | -232 |
| 8 Nov 2026, 19:28 | 53,706 | -112 |
| 7 Nov 2026, 12:44 | 53,818 | -96 |
| 6 Nov 2026, 10:49 | 53,914 | -100 |
| 5 Nov 2026, 12:59 | 54,014 | -124 |
| 4 Nov 2026, 15:39 | 54,138 | -195 |
| 3 Nov 2026, 18:57 | 54,333 | -877 |
| 2 Nov 2026, 19:59 | 55,210 | -304 |
| 1 Nov 2026, 17:06 | 55,514 | -167 |
| 31 Oct 2026, 18:57 | 55,681 | -220 |
| 30 Oct 2026, 20:55 | 55,901 | -543 |
| 29 Oct 2026, 20:27 | 56,444 | -121 |
| 28 Oct 2026, 22:10 | 56,565 | -67 |
| 27 Oct 2026, 18:31 | 56,632 | -65 |
| 26 Oct 2026, 19:29 | 56,697 | -82 |
| 25 Oct 2026, 16:08 | 56,779 | -142 |
| 24 Oct 2026, 17:55 | 56,921 | first reading |
1,447 posts held, back to 12 August 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 200 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 1,447 (12 August 2026 – 18 November 2026) |
| Views total | 483,833 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 04:42 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
Telegram’s own ‘edited’ marker: 1 of 466 posts held from the last 30 days (0.215%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🚾2ed ENGLAND 🇵🇷👆🏻 🚾🚾 wicket nhi gya to sabko 10000₹ Paytm DEGA YE BNDA 😳😳☝️☝️ 🚾 All CALL 🚾 YAHAN UPER 🚾👆🏿
Signed .
🚾WICKET 🚾WICKET 🚾 1st🚾wkt call check✔️ 2nd🚾wkt call check✔️ 3rd 🚾wkt call check✔ 4th 🚾wkt call check✔️ 5th 🚾wkt call check✔️ 6th 🚾wkt call check✔️ 🔗⚡️ JOIN & CHECK FAST 👍👇👇 https://t.me/+Qi3DMU99b0E2MDg9 https://t.me/+Qi3DMU99b0E2MDg9
Signed .
India's Best Betting Site 24/7 Deposit Withdrawal Avilable ⭐️ My Only Garunte crownbet.live 🌎
Signed Team Jay Ho
Australia 🆚 England Exclusive ID Available On crownbet.live 👑Match Bet 📈Session Bet 💥300+ Fancy Bet ✔️Minimum Id 300 Rs ✔️Minimum Bet 100 Rs ✔️24 Hour Fast Working Site ✔️No Need Documentation Cashout Option Available ( Ek Click Mein Book Set ) Register Fast 👇 crownbet.live | crownbet.live crownbet.live | crownbet.live 📱For Vip ID Min Id 2000 https://t.me/Crownbetvip 📱Telegram Official Channel https://t.me/cro…
Signed Team Jay Ho
Sticker, posted without a caption
Signed [sнαиνι] [ôwner]™
BIG LIMIT TOSS READY ✔️💯👆 TOSS OVER SURE FIXX HAI ✔️💯👆
Signed [sнαиνι] [ôwner]™
1 TOSS FEES ➖ 600/- UNLIMITED PLAY 💯✔️ https://wa.me/916387124398 https://wa.me/916387124398
Signed [sнαиνι] [ôwner]™
Download Our Official Apk 📱 Smooth Safe Secure 🔐
Signed Team Jay Ho
MARKET KE 90% BOOKIE KE HALAT 👇 ⚠️ Withdrawal Pending? 📈 Slow Settlement? ✔️ Punter Ka Paisa Time Par Na Milna? 🚨 Bank Freeze Hone Ki Tension? 😤 In sabhi problems se pareshan hain? 💎 TOH MILIYE crownbet.live SE! 💎 ⚡️ Fast Transactions 🔒 Security-Focused Platform 🚀 Smooth Settlement Experience 🤝 24/7Customer Support Signup🌎 crownbet.live Signup🌎 crownbet.live 📱For Vip ID Min Id 2000 https://t.me/Crownbetvip 📱Te…
Signed Team Jay Ho
🇦🇺 ADELAIDE STRIKERS WOMEN 🇦🇺 HAVE WON THE TOSS AND OPTED TO BOWL FIRST ✔️✔️ FULL LIMIT TOSS PASS ✅✅✅✅✅✅
Signed [sнαиνι] [ôwner]™
🇵🇰 PAKISTAN 🇵🇰 HAVE WON THE TOSS AND OPTED TO BAT FIRST ✔️✔️ FULL LIMIT TOSS PASS ✅✅✅✅✅
Signed [sнαиνι] [ôwner]™
2/2 MORNING TOSS PASSS 🔥🔥🔥🔥
Signed [sнαиνι] [ôwner]™
Showing the 12 most recent of 1,447 posts we hold for @shanvimem. 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.
We recorded 12 posts on @shanvimem as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 21 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 47 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“SHANVI ™” (@shanvimem), 50,342 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/shanvimem.
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.