Sports — 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 96% 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.
Growth
7 measurements spanning 39 days, net -12. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 313–330 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Sept 2026, 03:55
316
+1
7 Sept 2026, 04:40
315
-4
29 Aug 2026, 03:24
319
-3
21 Aug 2026, 19:09
322
-2
15 Aug 2026, 10:23
324
-4
8 Aug 2026, 07:18
328
no change
7 Aug 2026, 15:31
328
first reading
Engagement
11 posts held, back to 7 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 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 11 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
5s
Average length
5s
Measured directly from 1 video 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
73 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 49.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
36
49.3%
custom 5422609245872856755
14
19.2%
🏆
10
13.7%
😁
5
6.85%
🤩
3
4.11%
custom 5445005674960401495
2
2.74%
💯
1
1.37%
🔥
1
1.37%
🤝
1
1.37%
Custom emoji. 2 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 9 of the 11 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 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 7 July 2026 to 3 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.
Два матча — две победы
⠀
Контрольная встреча #2. 4:2 vs «Южный Урал».
⠀
Во втором матче против «Южного Урала» тренерский штаб «Челмета» внёс 12 изменений в состав. Челябинцы пропустили первыми, но забросили четыре шайбы подряд. В концовке «чёрно-белые» пропустили, но оставили за собой победу в матче.
Челмет vs Южный Урал — 4:2 (2:1, 1:0, 1:1)
0:1 — Лапшин — 06:40
1:1 — Горбунов (Сивирчуков, Низамеев) — 17:45
2:1 — А…
Контрольные матчи #1 и #2. «Челмет» vs «Южный Урал»
⠀
«Челмет» завершает первый цикл предсезонных сборов, в ходе которого команда уже провела двустороннюю игру с «Белыми Медведями». Теперь «чёрно-белые» сыграют в контрольных матчах с «Южным Уралом».
⠀
В прошлом сезоне «Челмет» дважды обыграл «Южный Урал» — 5:4 (ОТ) дома и 3:2 в гостях. Но в предстоящих контрольных матчах «чёрно-белые» встретятся с совершенно другой к…
Спасибо за игру | Александр Филатов
Защитник переходит в «Югру» в обмен на денежную компенсацию.
Александр Филатов — воспитанник челябинского хоккея. Всю профессиональную карьеру защитник провел на Южном Урале, где выступал за «Белых Медведей» в МХЛ и «Челмет» в ВХЛ. За команду Всероссийской хоккейной лиги Александр играл с сезона 2023/2024. Всего в ВХЛ в его активе 175 матчей и 29 (7+22) очков.
Благодарим Алексан…
⚡️Искусственный интеллект дал прогноз на выступление «Челмета» в сезоне 26/27
👥 Команда: «Челмет»
🔮 Прогноз ИИ:
Регулярный чемпионат: В межсезонье клуб сохранил тренерский штаб, удержал ключевых бомбардиров и точечно усилился, но качественного скачка вверх, скорее всего, не произойдёт. «Челмет» традиционно делает ставку на воспитанников системы «Трактора» и собственных молодых игроков, и это видно по трансферной ка…
Состав для подготовки к новому сезону
В список «Челмета» вошли четыре вратаря, 12 защитников и 23 нападающих, которые уже сегодня начнут работу во Дворце спорта «Юность».
🚜 @hcchelmet
Хотите стать частью мира кино? Приготовили для вас классный вариант 🎬🍿
Уже на следующей неделе в нашей Арене пройдет съемка сериала ТНТ «Челябинский раджа», и мы приглашаем всех желающих принять участие. С вас классное настроение, с нас — интересный опыт и крутая компания.
🗓️ 17 июля с 09:00 до 20:00
💻 Регистрация здесь
📍Челябинск, ЛА «Трактор» имени В.К. Белоусова
❗️Обязательно быть в черно-белой атрибутике «Тракт…
Showing the 11 most recent of 11 posts we hold for @xk_rankograd74. 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.
Mentions
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.
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 15 September 2026 — this
entry's latest reading, not the date you are reading this.
“Fan Zone HC” (@xk_rankograd74), 316 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/xk_rankograd74.
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.
