Завтра выложим пост с результатами сегодняшнего матча ❤️
custom 53596190278764788354

Channel
@Kuchaa_twitch
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
227subscribers
-2 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001356548579 |
|---|---|
| Type | Channel |
| Username | @Kuchaa_twitch |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/Kuchaa_twitch |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 13:25 | 227 | -2 |
| 10 Aug 2026, 00:17 | 229 | first reading |
19 posts held, back to 25 July 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 pageof 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 13 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 19 (25 July 2026 – 9 August 2026) |
| Views total | 7,414 |
| Reactions total | 121 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 00:17 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.
121 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 45.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5359420235315184585 | 55 | 45.5% | |
| custom 5298652439556161384 | 13 | 10.7% | |
| 😭 | 13 | 10.7% | |
| 👍 | 11 | 9.09% | |
| custom 5461053571153796261 | 8 | 6.61% | |
| custom 5379782344553021289 | 6 | 4.96% | |
| 🔥 | 6 | 4.96% | |
| custom 5359619027876478835 | 4 | 3.31% | |
| custom 5461160872321752023 | 3 | 2.48% | |
| custom 5341749008987594957 | 2 | 1.65% |
Custom emoji. 7 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 areTelegram’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 13 of the 19 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 121reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 25 July 2026 to 9 August 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.
Завтра выложим пост с результатами сегодняшнего матча ❤️
custom 53596190278764788354
🐶🐶🐶🐶🐶🐶🐶🐶 Мы близки к финишу, заходите поддержать команды 🎬 https://www.twitch.tv/kuchaa__
custom 54611608723217520232custom 52986524395561613841
Результаты сегодняшних матчей 🎮🔥 Сегодняшний игровой день подарил нам много классных, интересных и напряжённых матчей. Команды шли наравне друг с другом и не сдавались до самого конца. Все показали достойную игру! ❤️ А уже завтра команды продолжат борьбу за выход в финал! 🐶 🕓 Начало трансляции в 16:00 по МСК. Приходите на стрим, следите за матчами и поддерживайте любимые команды. Впереди нас ждут самые важные и эмо…
custom 54610535711537962613
🐶МЫ НАЧИНАЕМММ 🐶 🎬 https://www.twitch.tv/kuchaa__
Первый день нашего турнира завершён! 🎮 Теперь мы можем спокойно переходить ко второму дню, где команды продолжат борьбу за выход в полуфинал. 🔥 Отдельно хотим поблагодарить всех участников за понимание, терпение и за то, что шли нам навстречу во время технических неполадок. Спасибо за вашу поддержку и адекватное отношение - мы это очень ценим! ❤️ Уже сегодня в 17:00 мы продолжаем турнир! Заходите на трансляции, …
🔥4
Сетка АЛЬФЫ УЖЕ СТРИМИТСЯ 🙃 https://www.twitch.tv/k1ss33
МЫЫЫ НАЧИНАЕМ ❤️ 🎬https://www.twitch.tv/kuchaa__
Дорогие друзья, наша турнирная сетка готова! 🎮🔥 Уже сегодня команды сразятся друг с другом и начнут свой путь к победе! 🏆 Приходите на трансляции, поддерживайте любимую команду и ставьте баллы на исход матчей! 👀 🎁 Также во время стримов мы будем разыгрывать коды, поэтому не пропустите свой шанс забрать приз! Ждём всех на трансляциях. Всем командам удачи и красивых игр! ❤️
custom 53594202353151845857custom 53417490089875949571custom 54611608723217520231
🌸рисуем+ смотрим фильм 🎬 https://www.twitch.tv/kuchaa__
Скидывайте фото своих питомцев ✨
custom 535942023531518458514custom 52986524395561613844
Дорогие друзья! К счастью или к сожалению, мы объявляем о закрытии регистрации на турнир все 16 команд уже собраны! 🎉 Тем, кто не успел подать заявку или чья команда не прошла отбор, не стоит расстраиваться. Во время трансляций турнира мы будем разыгрывать VALORANT Points, поэтому обязательно приходите на стрим и не упустите возможность залутать ВПшки! 🎁
custom 53594202353151845859😭4custom 54610535711537962613custom 52986524395561613841
📢Временно закрываем регистрацию
😭9
Showing the 12 most recent of 19 posts we hold for @Kuchaa_twitch. 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.
Citation-graph rank — 684,350 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Мысык” (@Kuchaa_twitch), 227 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Kuchaa_twitch.
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.