Posted without readable text

Channel
Гусь в игре
@gus_v_igre
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
677subscribers
+102 since we began measuring on 5 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003475974004 |
|---|---|
| Type | Channel |
| Username | @gus_v_igre |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 November 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/gus_v_igre |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 07:57 | 677 | +94 |
| 6 Nov 2026, 00:06 | 583 | +8 |
| 5 Nov 2026, 17:22 | 575 | first reading |
Engagement
18 posts held, back to 31 October 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 26.0%
- avg views ÷ 677 subscribers
- Avg views / post
- 176
- 18 posts measured
- Reaction rate
- 3.37%
- reactions ÷ views · ER floor
- Posts in window
- 18
- of 18 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. It is computed over the 17 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 18 (31 October 2026 – 5 November 2026) |
| Views total | 3,167 |
| Reactions total | 102 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 17:22 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.
What this channel posts
- Video runtime
- 1m 29s
- Average length
- 18s
Measured directly from 5 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.
Reaction mix
102 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 51.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 51.0% | |
| 👀 | 18 | 17.6% | |
| 🔥 | 17 | 16.7% | |
| ⚡ | 4 | 3.92% | |
| 🤔 | 4 | 3.92% | |
| 💊 | 3 | 2.94% | |
| 👍 | 2 | 1.96% | |
| 🤡 | 2 | 1.96% |
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 17 of the 18 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 31 October 2026 to 5 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.
Recent posts
Telegram’s own ‘edited’ marker: 4 of 18 posts held from the last 30 days (22.2%) 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).
🏒 Победы с характером, разгромы и реабилитация «железнодорожников» ⚓️ «Адмирал» и ❄️ «Сибирь» одержали уверенные победы, 🚜 «Трактор» прервал серию неудач. А 💚 «Салават Юлаев» не оставил шансов 🚙 «Ладе», у которой приключения начались ещё по дороге на матч. А теперь переносимся в Москву на игру 🔴 «Спартака» и 🚂 «Локомотива». Стартовый отрезок матча получился энергичным. Особенно активно действовали хозяева: больше …
❤3👍2🔥2
🏒 Гол с подвохом и выкрутасы Лямкина Кто-то скажет: «СКА уехал из Владивостока без голов». Как бы не так! «Армейцы» всё-таки отличились, вот только есть нюанс: шайба залетела в собственные ворота. А автором гола записали голкипера ⚓️ «Адмирала» Никиту Бояркина — ведь именно он последним из «моряков» коснулся хоккейного снаряда. А 🟢 Никита Лямкин в Новосибирске решил не ограничиваться хоккеем и продемонстрировал тал…
🔥3👀2
Posted without readable text
👀3💊3🤔2
🏒 Голевая феерия в Магнитогорске и борьба в Сочи и Питере 🐉 «Драконы» врываются в топ-3 Запада после победы над 🟡 «Северсталью», а 🐺 «Нефтехимик» дожимает 🐆 «Сочи». А теперь — в Магнитогорск! Разбираем матч, который набрал больше всего ваших голосов. Первый период активнее начали «армейцы», однако вскоре игра выровнялась, а борьба стала более плотной. В концовке хозяева добавили, завладели инициативой и получили ч…
❤1👀1🔥1
🥊 В конце встречи на льду разгорелись страсти 🦊 Люк Джонсон и 🐴 Николай Коваленко, а также 🦊 Андрей Козлов и 🐴 Иван Дроздов сошлись в кулачных поединках. 📲 Подписывайся на «Гусь в игре»
❤4🔥1
🏒 В Магнитогорске лучше не отходить за попкорном 🍿 После сухого первого периода команды выдали голевую феерию в начале второй трети — три шайбы за 64 секунды! 🦊 Сиряцкий, 🦊 Михайлис и 🐴 Соркин — герои этой скоростной серии. Кажется, это тот самый случай, когда задержался в буфете на пару минут, а вернулся уже к совсем другой игре. 🔄 Матч завершился в пользу 🐴 со счётом 7️⃣:3️⃣ 😂 #ГусьБезСерьёзности 📲 Подписы…
❤5🔥2👀1
Posted without readable text
❤3👀1
🏒 Понедельник остался за гостями ⭐️ СКА в упорном противостоянии одолел 🟢 «Ак Барс». По результатам голосования наибольший интерес вызвала встреча в Ярославле. Давайте разберёмся, как развивались события. Первый период 🚂 «Локомотив» начал активно. Затем игра успокоилась, и соперники действовали на равных. У 🚙 «Лады» был шанс открыть счёт, но Мельничук справился. После этого тольяттинцы стали удаляться, чем помогли…
❤4🤔1
⚡️ Лука Профака: «Нет, мы не обращаем на это внимания» Защитник московского 🔵 «Динамо» Лука Профака оценил прошедшее дерби, поделился эмоциями от юбилейного «сухаря» Моторыгина и объяснил, как команда отреагировала на свист трибун. 💬 Дерби впервые в этом сезоне было сыграно в Минске. Поделитесь впечатлениями от игры здесь. Здесь отличная атмосфера. Хорошая поддержка, но мы придерживались своего плана на игру и засл…
❤3👀2🤡2
⚡️«Я не знаю, что произошло в этой игре». Ксавье Уэлле подвёл итоги дерби По итогам динамовского дерби побеседовал с защитником минчан Ксавье Уэлле. Обсудили игру команды, атмосферу в раздевалке, новое подписание, свист трибун и причины невысокой результативности. 💬 Провели третий матч с московским «Динамо» в сезоне. Вновь результат неутешительный, что не получилось? Я не знаю, что произошло в этой игре. Мы должны …
❤3👀1🤔1
Posted without readable text
❤2👀1
Showing the 12 most recent of 18 posts we hold for @gus_v_igre. 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
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.
Mentions
Named by 2 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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“Гусь в игре” (@gus_v_igre), 677 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/gus_v_igre.
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.