Бились до последнего, но соперник оказался сильнее. «Армия СКА» — ЦСКА — 0:3 🏒«Кубок Овечкина U12»
❤4👀2✍1

Channel
@army_ska_hockey
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,286subscribers
+25 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001832886721 |
|---|---|
| Type | Channel |
| Username | @army_ska_hockey |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/army_ska_hockey |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 18 Sept 2026, 21:40 | 1,286 | +3 |
| 14 Sept 2026, 13:38 | 1,283 | -1 |
| 11 Sept 2026, 07:19 | 1,284 | -4 |
| 6 Sept 2026, 12:56 | 1,288 | +13 |
| 2 Sept 2026, 04:33 | 1,275 | -6 |
| 30 Aug 2026, 02:07 | 1,281 | +10 |
| 23 Aug 2026, 22:34 | 1,271 | -2 |
| 20 Aug 2026, 12:52 | 1,273 | -5 |
| 17 Aug 2026, 16:58 | 1,278 | -2 |
| 14 Aug 2026, 22:23 | 1,280 | +12 |
| 11 Aug 2026, 22:55 | 1,268 | +6 |
| 8 Aug 2026, 15:08 | 1,262 | +1 |
| 7 Aug 2026, 22:48 | 1,261 | no change |
| 7 Aug 2026, 18:08 | 1,261 | first reading |
12 posts held, back to 5 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 12 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
167 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 35.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5296583257456937847 | 60 | 35.9% | |
| ❤ | 60 | 35.9% | |
| 🔥 | 29 | 17.4% | |
| ⚡ | 4 | 2.40% | |
| 🤩 | 4 | 2.40% | |
| 😁 | 3 | 1.80% | |
| ✍ | 2 | 1.20% | |
| ❤🔥 | 2 | 1.20% | |
| 👀 | 2 | 1.20% | |
| 💯 | 1 | 0.599% |
Custom emoji. One 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 count beside it is 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 12 of the 12 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 167 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 5 August 2026 to 7 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.
Бились до последнего, но соперник оказался сильнее. «Армия СКА» — ЦСКА — 0:3 🏒«Кубок Овечкина U12»
❤4👀2✍1
Через час встречаемся в армейском дерби против «ЦСКА» за пятое место на «Кубке Овечкина U12» ⚔️ Подключаемся к трансляции и болеем за наших! 🌟
🔥3custom 52965832574569378473❤2
Заряжаемся положительными эмоциями, листая сразу две победные галереи с последних матчей на групповом этапе «Кубке Овечкина U12» 🥰 📲«Лада» — «Армия СКА» — 2:6 🤳🏻«Авангард» — «Армия СКА» — 2:4 Фото: Мособлспорт
❤6custom 52965832574569378473🔥1
🔵🔴💪🏻
❤6custom 52965832574569378475🔥2
Армейцы 2016 г. р. продолжают свою подготовку к новому сезону 🏃🏼🏒🌳
custom 52965832574569378476❤3🔥3
«Армия СКА 2018» в тренде 🔝 Попросили наших ребят дополнить фразы, и, кажется, тут явно есть к чему прислушаться 😁
custom 52965832574569378478❤4😁3
В матче четвертьфинала «Кубка Овечкина U12» уступаем «Академии Михайлова» со счетом 1:3. Первый период провели достаточно ровно: команды обменялись острыми моментами, но обошлось без голов. Во втором периоде соперник реализовал большинство и открыл счет встречи, однако уже в следующей смене армейцы сравняли счет. Затем хоккеисты «Академии Михайлова» вновь вышли вперед и вскоре увеличили свое преимущество — 3:1. В тр…
custom 52965832574569378476❤3❤🔥2⚡1✍1💯1🤩1
Шагаем в плей-офф «Кубка Овечкина U12» 🔛 Через час стартуем в матче 1/4 против «Академии Михайлова». 📹 Подключаемся к трансляции и болеем за армейцев, поддержим наших хоккеистов! ❤️
🔥3custom 52965832574569378473❤2
Мотивация перед плей-офф — максимальная! 💪🏻 Перед матчем 1/4 финала «Кубка Овечкина U12» раздевалку армейцев посетил Александр Овечкин. Напутственные слова от легенды мирового хоккея и памятное фото — эмоции, которые останутся с ребятами навсегда ♾️
🔥8❤4⚡3🤩2
🏆 Завершился групповой этап «Кубка Овечкина» среди юношей 2014 г. р. «Армия СКА» сыграла в группе «Б». В первом матче против «Торпедо» команда одержала уверенную победу со счетом 11:2, затем обыграла «Крылья Советов» — 4:2. В армейском дерби против ЦСКА наши ребята имели все шансы обыграть столичную команду: дважды сокращали отставание, но уступили со счетом 5:9. В последующих двух встречах армейцы реабилитировались…
custom 529658325745693784712🔥4❤3
🎒 Предсезонные сборы «Армии СКА 2012» в Нижегородской области завершены! Две недели упорной работы, сотни часов тренировок и полная готовность к грядущему сезону. Впереди новые вызовы, яркие матчи и большие победы 👊🏻
❤15custom 529658325745693784710🔥4
В объективе камеры — «Армия СКА 2010» 📸 Команда проводит тренировки на арене «АСК-С» в Стрельне и уже совсем скоро отправится на предсезонные сборы в Смоленск ✈️ ❤️ — если скучали!
❤8custom 52965832574569378474🔥1🤩1
Showing the 12 most recent of 12 posts we hold for @army_ska_hockey. 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.
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 1 registered channel — 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Армия СКА” (@army_ska_hockey), 1,286 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/army_ska_hockey.
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.