Posted without readable text
🙏187custom 530984394321354235136❤10custom 51931161380866377874

Channel
@caser_cs2
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
151,652subscribers
+65,674 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1003698858532 |
|---|---|
| Type | Channel |
| Username | @caser_cs2 |
| Description | Кейсы как в игре. Дроп как нигде ✌️ 🔗 Сайт - https://casergg.com/telegram 💬 Чат - @cs2caser_chat 📦 Выдача призов - @caser_prize |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/caser_cs2 |
Gambling & betting — 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 21 August 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 12:36 | 151,652 | +325 |
| 16 Sept 2026, 05:36 | 151,327 | +737 |
| 14 Sept 2026, 09:54 | 150,590 | +2,930 |
| 12 Sept 2026, 16:16 | 147,660 | +17,118 |
| 10 Sept 2026, 19:00 | 130,542 | +30,476 |
| 7 Sept 2026, 18:55 | 100,066 | +4,245 |
| 4 Sept 2026, 17:22 | 95,821 | +3,395 |
| 3 Sept 2026, 00:37 | 92,426 | +357 |
| 1 Sept 2026, 22:45 | 92,069 | -806 |
| 31 Aug 2026, 23:45 | 92,875 | +174 |
| 31 Aug 2026, 00:07 | 92,701 | +578 |
| 30 Aug 2026, 02:05 | 92,123 | +655 |
| 29 Aug 2026, 05:12 | 91,468 | -15 |
| 28 Aug 2026, 05:52 | 91,483 | -97 |
| 27 Aug 2026, 05:16 | 91,580 | +5 |
| 26 Aug 2026, 03:06 | 91,575 | +264 |
| 25 Aug 2026, 06:32 | 91,311 | +447 |
| 24 Aug 2026, 04:42 | 90,864 | +1,092 |
| 22 Aug 2026, 12:47 | 89,772 | +3,062 |
| 21 Aug 2026, 03:12 | 86,710 | first reading |
174 posts held, back to 1 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 110 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 27 September 2026 |
|---|---|
| Posts held | 174 (1 August 2026 – 27 September 2026) |
| Views total | 2,173,260 |
| Reactions total | 30,060 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 12:10 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 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 17 videos 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.
42,847 reactions across 174 posts, in 16 distinct kinds. The most used accounts for 33.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14,501 | 33.8% | |
| custom 5193116138086637787 | 7,861 | 18.3% | |
| custom 5400030430999093702 | 7,621 | 17.8% | |
| 👍 | 3,720 | 8.68% | |
| 🙏 | 2,138 | 4.99% | |
| 🔥 | 1,572 | 3.67% | |
| custom 5309843943213542351 | 1,566 | 3.65% | |
| 🤯 | 1,437 | 3.35% | |
| 🤣 | 1,012 | 2.36% | |
| custom 5357132473740313212 | 561 | 1.31% | |
| custom 5195349860382940090 | 327 | 0.763% | |
| 😈 | 244 | 0.569% | |
| custom 5256126752882731298 | 136 | 0.317% | |
| custom 5458493895199468609 | 112 | 0.261% | |
| custom 5254010515121808441 | 36 | 0.084% | |
| 😁 | 3 | 0.007% |
Custom emoji. 8 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 174 of the 174 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 42,847 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 174 most recent posts we hold, published 1 August 2026 to 27 September 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.
Posted without readable text
🙏187custom 530984394321354235136❤10custom 51931161380866377874
Posted without readable text
custom 530984394321354235192❤33custom 519311613808663778731
press “F” легенде
custom 5357132473740313212561❤120🙏27🤯14🔥3
Posted without readable text
custom 519311613808663778783❤52custom 530984394321354235137🤯3🔥2
Posted without readable text
custom 53098439432135423511,400❤33custom 519311613808663778725custom 51953498603829400905👍2
Мы кое что для вас приготовили…
🤯247custom 5195349860382940090123custom 519311613808663778758❤33🔥4
Posted without readable text
custom 5195349860382940090195❤64🤯24custom 51931161380866377878👍2
Posted without readable text
❤75custom 519311613808663778726👍6custom 51953498603829400904🤯2
Posted without readable text
🙏345❤71👍11custom 51931161380866377873🔥2
Posted without readable text
❤192custom 519311613808663778717👍5🙏2
Posted without readable text
❤234custom 519311613808663778735👍31🔥19🤯14
Posted without readable text
👍321❤40🤯30custom 519311613808663778724🙏4
Showing the 12 most recent of 174 posts we hold for @caser_cs2. 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.
@caser_cs2 edited 32 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 10 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“КЕЙСЕР” (@caser_cs2), 151,652 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/caser_cs2.
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.