🇩🇪 MOUZ — чемпион ▫ IEM Beijing 2026. 😀 «Мышки» обыграли 🇲🇳 The MongolZ со счётом 3:0 и заработали $360 000 призовых. 😀 xertioN cтал MVP чемпионата с рейтингом 1.28.
custom 519051870507477274516custom 51905301253928124464custom 51885684033753296202

Channel
@offstage_cs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
9,298subscribers
+1,833 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002541484735 |
|---|---|
| Type | Channel |
| Username | @offstage_cs |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/offstage_cs |
Gaming — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 01:31 | 9,298 | -55 |
| 7 Nov 2026, 05:29 | 9,353 | -14 |
| 4 Nov 2026, 14:46 | 9,367 | -22 |
| 1 Nov 2026, 11:46 | 9,389 | -115 |
| 29 Oct 2026, 18:46 | 9,504 | -38 |
| 26 Oct 2026, 20:27 | 9,542 | -53 |
| 23 Oct 2026, 14:36 | 9,595 | -42 |
| 20 Oct 2026, 05:58 | 9,637 | -55 |
| 17 Oct 2026, 12:56 | 9,692 | -52 |
| 14 Oct 2026, 04:26 | 9,744 | -48 |
| 10 Oct 2026, 09:01 | 9,792 | -105 |
| 4 Oct 2026, 07:17 | 9,897 | -226 |
| 25 Sept 2026, 15:20 | 10,123 | -179 |
| 17 Sept 2026, 08:39 | 10,302 | -44 |
| 15 Sept 2026, 05:58 | 10,346 | -55 |
| 13 Sept 2026, 14:59 | 10,401 | -51 |
| 11 Sept 2026, 21:59 | 10,452 | -57 |
| 9 Sept 2026, 11:40 | 10,509 | -81 |
| 6 Sept 2026, 02:02 | 10,590 | -45 |
| 3 Sept 2026, 20:22 | 10,635 | first reading |
368 posts held, back to 4 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 45 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. It is computed over the 30 of 31 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 368 (4 August 2026 – 8 November 2026) |
| Views total | 26,007 |
| Reactions total | 362 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 22:57 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.
Measured directly from 31 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.
5,383 reactions across 367 posts, in 8 distinct kinds. The most used accounts for 38.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5190518705074772745 | 2,054 | 38.2% | |
| custom 5190862585926294842 | 1,035 | 19.2% | |
| custom 5190530125392812446 | 1,019 | 18.9% | |
| custom 5190700532515251908 | 554 | 10.3% | |
| custom 5188568403375329620 | 326 | 6.06% | |
| custom 5190869062736972574 | 194 | 3.60% | |
| custom 5364307066284447802 | 118 | 2.19% | |
| custom 5364176185746037113 | 83 | 1.54% |
Custom emoji. Every row above is a 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 367 of the 368 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 5,383 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 368 most recent posts we hold, published 4 August 2026 to 8 November 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.
Telegram’s own ‘edited’ marker: 13 of 31 posts held from the last 30 days (41.9%) 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).
🇩🇪 MOUZ — чемпион ▫ IEM Beijing 2026. 😀 «Мышки» обыграли 🇲🇳 The MongolZ со счётом 3:0 и заработали $360 000 призовых. 😀 xertioN cтал MVP чемпионата с рейтингом 1.28.
custom 519051870507477274516custom 51905301253928124464custom 51885684033753296202
🔸 Расписание заключительного дня ▫ IEM Beijing 2026. 7:00 мск — BETBOOM TEAM vs Natus Vincere (матч за 3-е место) 10:30 — MOUZ vs The MongolZ (гранд-финал, bo5)
custom 51905301253928124464custom 51905187050747727451custom 51908625859262948421
😀 The MongolZ vs MOUZ — гранд-финал ▫ IEM Beijing 2026 — итоги полуфиналов. — The MongolZ 2:0 Natus Vincere — MOUZ 2:0 BETBOOM TEAM 😀 Natus Vincere и BETBOOM TEAM сыграют матч за 3-е место.
custom 51905301253928124464custom 51908625859262948422custom 51905187050747727451
🔸 Расписание матчей второго дня плей-офф ▫ IEM Beijing 2026. 9:30 мск — The MongolZ vs Natus Vincere 12:45 — MOUZ vs BETBOOM TEAM
😀 Итоги четвертьфиналов ▫️ IEM Beijing 2026. — PARIVISION 1:2 Natus Vincere — FURIA 1:2 BETBOOM TEAM 🔸 По результатам этапа нас ждут полуфинальные матчи: 🇺🇦 Natus Vincere vs 🇲🇳 The MongolZ и 🟡 BETBOOM TEAM vs 🇩🇪 MOUZ. Проигравшие команды покинули турнир.
custom 51905187050747727456custom 51905301253928124462
⚡️ Леонид «chopper» Вишняков официально стал свободным агентом — его контракт с 🇷🇺 Team Spirit подошел к концу
custom 519051870507477274520custom 51905301253928124464
🔸 Расписание матчей первого дня плей-офф ▫️ IEM Beijing 2026. 9:30 мск — PARIVISION vs Natus Vincere 12:45 — FURIA vs BETBOOM TEAM
custom 51905301253928124464custom 51905187050747727452custom 51908625859262948422
😀 😀 Rune Eaters представила обновлённый состав. 🔸 Новый ростер: — dukefissura — noni — demente — tasman — nota — sorrow (тренер)
custom 519053012539281244613custom 51905187050747727453custom 51885684033753296201
🔸 Стала известна сетка плей-офф ▫️ IEM Beijing 2026 — итоги заключительного дня групповой стадии. 😀 Группа A: — Natus Vincere 2:0 B8 — HEROIC 0:2 Team Falcons — FURIA 1:2 The MongolZ — Natus Vincere 2:1 Team Falcons 😀 Группа B: — Team Liquid 2:0 TYLOO — Aurora Gaming 0:2 BETBOOM TEAM — MOUZ 2:0 PARIVISION — Team Liquid 1:2 BETBOOM TEAM 😀 PARIVISION, NAVI, FURIA и BETBOOM TEAM прошли в четвертьфинал плей-офф, а The…
custom 51905187050747727456custom 51885684033753296201custom 51905301253928124461
🔸 Расписание матчей заключительного дня групповой стадии ▫️ IEM Beijing 2026. 😀 Группа A: 07:30 мск — Natus Vincere vs B8 07:30 — HEROIC vs Team Falcons 12:30 — FURIA vs The MongolZ 12:30 — Победитель Natus Vincere/B8 vs победитель HEROIC/Team Falcons 😀 Группа B: 05:00 — Team Liquid vs TYLOO 05:00 — Aurora Gaming vs BETBOOM TEAM 10:00 — MOUZ vs PARIVISION 10:00 — Победитель Team Liquid/TYLOO vs победитель Aurora Ga…
custom 51905187050747727452custom 51905301253928124461custom 51908625859262948421
😀 Итоги второго игрового дня ▫️ IEM Beijing 2026. 😀 Группа A: — The MongolZ 2:0 HEROIC — FaZe Clan 1:2 Team Falcons — FURIA 2:1 Natus Vincere — Legacy 1:2 B8 😀 Группа B: — Team Liquid 0:2 PARIVISION — Aurora Gaming 2:1 G2 Esports — MOUZ 2:0 BETBOOM TEAM — TYLOO 2:0 9z Team 😀 The MongolZ, FURIA, MOUZ и PARIVISION гарантировали себе места в плей-офф, а 9z, G2, FaZe и Legacy покинули турнир, заработав по $8 000.
custom 51908625859262948424custom 51905187050747727452custom 51905301253928124461
🔸 Расписание матчей второго игрового дня ▫️ IEM Beijing 2026. 😀 Группа A: 10:00 мск — The MongolZ vs HEROIC 10:00 — FaZe Clan vs Team Falcons 12:30 — FURIA vs Natus Vincere 12:30 — Legacy vs B8 😀 Группа B: 05:00 — Team Liquid vs PARIVISION 05:00 — Aurora Gaming vs G2 Esports 07:30 — MOUZ vs BETBOOM TEAM 07:30 — TYLOO vs 9z Team
custom 51905187050747727454custom 51885684033753296202custom 51905301253928124461
Showing the 12 most recent of 368 posts we hold for @offstage_cs. 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.
@offstage_cs edited 1 post 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“OFFSTAGE CS2” (@offstage_cs), 9,298 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/offstage_cs.
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.