1 LIMIT USE KRO OR 1.90 LIMIT PLUS KRO RIPPLES PAR RIPPLES PLUS KRKE AAO SABHI

Channel
𝙎𝙋𝙀𝘾𝙄𝘼𝙇 𝙎𝙐𝙈𝙄𝙏 𝘽𝙃𝘼𝙄™
@cricwithsumitbhai
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
63,418subscribers
+52,494 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001543460058 |
|---|---|
| Type | Channel |
| Username | @cricwithsumitbhai |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/cricwithsumitbhai |
Topic
Crypto & trading — 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 94% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 01:36 | 63,418 | +8 |
| 8 Sept 2026, 03:36 | 63,410 | +9 |
| 5 Sept 2026, 02:19 | 63,401 | +3 |
| 3 Sept 2026, 06:44 | 63,398 | -1 |
| 2 Sept 2026, 00:08 | 63,399 | +5 |
| 1 Sept 2026, 03:24 | 63,394 | -1 |
| 31 Aug 2026, 00:04 | 63,395 | -2 |
| 30 Aug 2026, 01:18 | 63,397 | +3 |
| 28 Aug 2026, 04:48 | 63,394 | +3 |
| 27 Aug 2026, 06:35 | 63,391 | -5 |
| 26 Aug 2026, 04:23 | 63,396 | +6 |
| 25 Aug 2026, 03:45 | 63,390 | -5 |
| 23 Aug 2026, 21:45 | 63,395 | +2 |
| 22 Aug 2026, 06:14 | 63,393 | -2 |
| 20 Aug 2026, 22:35 | 63,395 | +18,477 |
| 20 Aug 2026, 00:37 | 44,918 | +21,103 |
| 18 Aug 2026, 23:36 | 23,815 | +12,984 |
| 17 Aug 2026, 20:45 | 10,831 | -9 |
| 16 Aug 2026, 17:43 | 10,840 | -10 |
| 15 Aug 2026, 00:35 | 10,850 | first reading |
Engagement
88 posts held, back to 12 June 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 50 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.27%
- avg views ÷ 63,418 subscribers
- Avg views / post
- 2,070
- 73 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 73
- of 88 held
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 31 August 2026 |
|---|---|
| Posts held | 88 (12 June 2026 – 31 August 2026) |
| Views total | 151,248 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 11:55 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.
Recent posts
FOR ANY QUIRY AND SUGGESTION MASSAGE HERE @sumitbhai_agl
AJ SE PURANA SAB KAAM BHUL JAO JITNA BHI OPEN DUNGA 1 FULL LIMIT KI ENTRY K HISAB SE EVRY MONDAY PROFIT LOSS COUNT KRENGE EVERY MONDAY COMPLETE BNAKAR DALENGE KYA WIN KYA LOSS RAHA AJ SE START SABHI OPEN MATCH KA PAID MATCH YAHA COUNT NAHI KRENGE KEWAL OPEN MATCH KA EK CARD BANAYENGE KI MONDAY TO MONDAY HAMNE KYA KAMAYA
GOOD MORNING FAMILY HAR HAR MAHADEV JAI SHRI RAM
ST KITTS WILL WIN 1ST BALL SE ENTRY KENA HAI UNDER 30p CASH OUT MUST WINNER ST KITTS
37 🅿️🅰️💲💲
34 5 👈🏽👨🏻✈️ 6 OVER 👨🏻✈️ Yes kr do sabhi 6 over
15 7 🇸🇨 GLASGOW 🇸🇨 Dublin win kro Dublin plus kro Tandav kr do sabhi
वक्त तुमने मुझे यूँ झुका तो लिया, हौसलों को मेरे न डिगा पाओगे।। पंख काटे हैं तुमने बेशक मेरे, पर गगन को न मुझसे बचा पाओगे।। मैं हूँ चंचल सा जल, रुक न पाऊँ कहीं कैसे कह दूँ कि मंजिल को पाऊँ नहीं मैं गिरूँगा तेरी ठोकरों से मगर, सोचना मत कि उठ न पाऊँ कहीं। चाहे काँटे लगा लो चाहुँओर तुम, फूल खुशियाँ मेरी न छुपा पाओगे। वक्त तुमने मुझे यूँ झुका तो लिया, हौसलों को मेरे न डिगा पाओगे।। आज मीठे हो तुम, और खारा हूँ मैं है अंधेर…
GOOD MORNING FAMILY HAR HAR MAHADEV JAI SHRI RAM
श्री ॐकारेश्वर ज्योतिर्लिंग मंगला आरती श्रृंगार | 28.08.2026 Shri Omkareshwar Jyotirlinga Mangala Aarti Shringar | 28.08.2026
Video message, posted without a caption
Showing the 12 most recent of 88 posts we hold for @cricwithsumitbhai. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“𝙎𝙋𝙀𝘾𝙄𝘼𝙇 𝙎𝙐𝙈𝙄𝙏 𝘽𝙃𝘼𝙄™” (@cricwithsumitbhai), 63,418 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/cricwithsumitbhai.
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.