Друг нашего канала проводит розыгрыш совместно с БХ! Можете участвовать
custom 52918963142656381508

Channel
@tverdiiznakkhockey
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
381subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002465446864 |
|---|---|
| Type | Channel |
| Username | @tverdiiznakkhockey |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/tverdiiznakkhockey |
Giveaways & airdrops — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 26 Sept 2026, 00:22 | 381 | -7 |
| 12 Sept 2026, 15:37 | 388 | +2 |
| 4 Sept 2026, 17:38 | 386 | +1 |
| 29 Aug 2026, 03:34 | 385 | -1 |
| 23 Aug 2026, 00:06 | 386 | -1 |
| 15 Aug 2026, 07:07 | 387 | -3 |
| 8 Aug 2026, 17:36 | 390 | +1 |
| 8 Aug 2026, 06:02 | 389 | no change |
| 7 Aug 2026, 18:08 | 389 | first reading |
20 posts held, back to 2 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
215 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 39.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5291896030797797483 | 84 | 39.1% | |
| custom 5289850513968374632 | 51 | 23.7% | |
| 👍 | 34 | 15.8% | |
| custom 5291896314265638150 | 27 | 12.6% | |
| 🙏 | 7 | 3.26% | |
| 💔 | 4 | 1.86% | |
| 😁 | 3 | 1.40% | |
| custom 5290010011873876702 | 2 | 0.93% | |
| 🤡 | 2 | 0.93% | |
| 🤔 | 1 | 0.465% |
Custom emoji. 4 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 20 of the 20 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 215 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 2 August 2026 to 5 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 52918963142656381508
🎁Это невероятно! Подарим вам сезонный абонемент на матчи вашего любимого белорусского клуба Экстралиги! Для участия в розыгрыше нужно выполнить два простых условия: 1) Быть подписанным на аккаунты @selivons и @extraleague_belarushockey 2) Нажать кнопку «Участвую!» под этим постом. 👉Итоги подведём 18 августа. ❗️Конкурс только для жителей Беларуси. 🍀Всем удачи!
👍7
⭐️ Пока админ думает, предлагаю подписчикам написать свои три звезды по итогам этой встречи. ✍️ Делитесь своим мнением в комментариях!
custom 52918963142656381505
✅ Одерживаем первую победу в кубке Салея! Перебросали в два раза, тотально доминировали первые два периода. В третьем периоде игра стала быстрее, «Могилев» стал активнее цепляться за шайбу. Удаляться столько в конце встречи, конечно, нельзя, другие команды не простят такое. Тем не менее, выстояли, смогли забросить в формате 4 на 4, и после Олег Качеловский закрыл встречу, забросив четвертую шайбу в пустые. Очень по…
custom 529189603079779748312
🎉🎉🎉🎉 Нассер Субхи! 3:1! Как же мне нравится игра Нассера в этом сезоне, как и всего первого звена. Молодец!
custom 528985051396837463210
❌ После второго периода счет 2:1. Куча моментов была, нужно работать над реализацией. «Могилев» же вытерпел и смог забросить после контратаки. Вратарская шайба, конечно, но ничего страшного пока не произошло. Ждем третий период! ❤️ Нужна победа!
custom 529189603079779748310
❌ Пропускаем курьезную шайбу. 2:1. И вот так каждый раз, возили «Могилев» просто беспощадно, не выпускали их из своей зоны, красиво комбинировали. Однако вот было без завершения. Не забиваешь ты — забивают тебе
👍8
✅ Ведем со счетом 2:0 после первого периода! Шикарный период, толком ничего не дали сделать сопернику, могу вспомнить только один опасный момент после индивидуальной ошибки нашего игрока где-то в концовке периода. Доминируем по всем компонентам статистики, а самое главное — в счете. Но рано радоваться, нужно продолжать играть так же во втором периоде!
custom 529189631426563815012custom 52918960307977974832
🎉🎉🎉🎉 Дмитрий Иванчиков! 2:0! Забрасываем еще одну под занавес первого периода!
custom 52898505139683746326custom 52918960307977974832
🎉🎉🎉🎉 Вадим Кравченко! 1:0! Открываем счет! Сразу после вбрасывания бросал Кравченко со своей любимой точки. Не ожидал вратарь броска, а форвард точно смог поразить ворота.
custom 52918960307977974837custom 52898505139683746323
⚡️ Состав на игру! Точечные изменения в составе. Лубский на воротах, интересное решение. Гостев и Колышкин не появились в заявке. Ротация? Хоромандо будет в первой связке с Анохиным, вместо Колышкина в третьем звене Головач. Появился в заявке Войтович, вновь в четвертом звене вместе с Качеловским. ❤️ Сегодня нужна победа! Верим в команду!
custom 52898505139683746328custom 52918960307977974833
📅📅📅📅📅📅 🐱🫡🦁 Кубок Салея. Матч №2. Первая официальная домашняя игра сезона! Товарищеский матч с «Могилевом» нам всем запомнился борьбой и эмоциями. Всегда приятно вкатываться в сезон через такие игры, будто сразу задают тон предстоящему сезону. Но есть и другая сторона медали: у «Могилева» явно осталось желание взять реванш, только уже в официальной игре. Пусть мы и победили в товарищеском матче, не стоит рассчитыват…
custom 52918960307977974839custom 52898505139683746324
Showing the 12 most recent of 20 posts we hold for @tverdiiznakkhockey. 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.
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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“ъ об экстралиге” (@tverdiiznakkhockey), 381 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/tverdiiznakkhockey.
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.