Завтра второй раз в сезоне сыграем против СКА в Санкт-Петербурге ⚡️ ПРЕВЬЮ 🖥
custom 5449759615346548186147🔥32🙏26custom 539552702894022163420custom 53932238054831015466custom 53796438146778483685⚡1custom 54517149421577243121

Channel
@dynamo_ru
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cross-platform identity · Cite this entry
45,428subscribers
+538 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001087632472 |
|---|---|
| Type | Channel |
| Username | @dynamo_ru |
| Description | Одна жизнь — одна команда 🤍💙 Официальный сайт: dynamo.ru Билеты: tickets.dynamo.ru Обсуждаем новости: t.me/TribunaD |
| Created | 18 October 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/dynamo_ru |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 13:14 | 45,428 | -39 |
| 8 Nov 2026, 03:46 | 45,467 | -22 |
| 6 Nov 2026, 22:46 | 45,489 | -2 |
| 5 Nov 2026, 21:48 | 45,491 | +17 |
| 4 Nov 2026, 23:01 | 45,474 | +19 |
| 3 Nov 2026, 21:29 | 45,455 | -24 |
| 2 Nov 2026, 19:39 | 45,479 | -16 |
| 1 Nov 2026, 18:38 | 45,495 | -25 |
| 31 Oct 2026, 15:35 | 45,520 | -12 |
| 30 Oct 2026, 18:41 | 45,532 | -31 |
| 29 Oct 2026, 15:56 | 45,563 | -39 |
| 28 Oct 2026, 16:37 | 45,602 | -31 |
| 27 Oct 2026, 14:18 | 45,633 | -12 |
| 26 Oct 2026, 17:26 | 45,645 | -51 |
| 25 Oct 2026, 15:05 | 45,696 | -53 |
| 24 Oct 2026, 17:10 | 45,749 | -46 |
| 23 Oct 2026, 16:36 | 45,795 | -56 |
| 22 Oct 2026, 15:10 | 45,851 | -77 |
| 21 Oct 2026, 08:48 | 45,928 | +7 |
| 20 Oct 2026, 08:59 | 45,921 | first reading |
1,329 posts held, back to 4 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 192 pages of 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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 1,329 (4 August 2026 – 10 November 2026) |
| Views total | 2,228,112 |
| Reactions total | 91,020 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 00:54 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 169 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.
221,631 reactions across 998 posts, in 55 distinct kinds. The most used accounts for 32.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5449759615346548186 | 72,368 | 32.7% | |
| 🔥 | 26,021 | 11.7% | |
| custom 5395527028940221634 | 20,398 | 9.20% | |
| 🤬 | 12,954 | 5.84% | |
| custom 5217965538961018249 | 12,858 | 5.80% | |
| 🤣 | 9,430 | 4.25% | |
| custom 5271682149471252535 | 8,746 | 3.95% | |
| 😁 | 6,459 | 2.91% | |
| custom 5379643814677848368 | 6,176 | 2.79% | |
| 🙏 | 5,107 | 2.30% | |
| 😍 | 5,045 | 2.28% | |
| custom 5393223805483101546 | 4,515 | 2.04% | |
| 👍 | 3,994 | 1.80% | |
| custom 5451714942157724312 | 3,444 | 1.55% | |
| 😢 | 2,864 | 1.29% | |
| 😭 | 2,398 | 1.08% | |
| 🥰 | 2,323 | 1.05% | |
| 🎉 | 1,919 | 0.866% | |
| 🥴 | 1,401 | 0.632% | |
| 😈 | 1,177 | 0.531% | |
| 35 further kinds | 12,034 | 5.43% |
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 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 998 of the 1,000 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 221,631 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 31 August 2026 to 10 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dynamo_ru. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 31 August 2026 to 10 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqvtguhY | 1 | 2 November 2026 | 2 November 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 31 August 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 44 of 406 posts held from the last 30 days (10.8%) 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).
Завтра второй раз в сезоне сыграем против СКА в Санкт-Петербурге ⚡️ ПРЕВЬЮ 🖥
custom 5449759615346548186147🔥32🙏26custom 539552702894022163420custom 53932238054831015466custom 53796438146778483685⚡1custom 54517149421577243121
Video message, posted without a caption
🔥115😍59custom 544975961534654818641🥰26custom 539552702894022163413custom 53796438146778483683😈1
🛫Полетели в Санкт-Петербург! 💙Вратари: Максим Моторыгин, Владислав Подъяпольский, Вадим Жеренко. 💙Защитники: Игорь Ожиганов, Марио Паталаха, Даниил Пыленков, Артем Блажиевский, Лука Профака, Елисей Рябыкин, Артем Сергеев, Магомед Шараканов, Сергей Зборовский. 💙Нападающие: Артем Швец-Роговой, Максим Летунов, Дмитрий Зуган, Дилан Сикьюра, Никита Коростелев, Игорь Мартынов, Андрей Никонов, Булат Шафигуллин, Артем Бон…
custom 5395527028940221634228custom 544975961534654818684custom 521796553896101824947🙏15🔥8🏆6custom 54517149421577243124😭3
⚡Егор Римашевский выведен из списка травмированных 87-й номер московского «Динамо» вернулся в общую группу и готов принять участие в ближайших матчах команды. С возвращением, Егор 💙 @dynamo_ru
custom 5449759615346548186587🔥178👍87custom 521796553896101824945custom 539552702894022163429😍16🎉7👏5
Потренировались перед вылетом, теперь следуем в аэропорт 😉 @dynamo_ru
custom 5449759615346548186137⚡36🥰21custom 521796553896101824914custom 53955270289402216346custom 53932238054831015462😈1custom 54517149421577243121
В Хабаровске молодежка забирает два очка 💪
custom 5217965538961018249153custom 544975961534654818651custom 539322380548310154626🔥5custom 53796438146778483683👏2😈1
🏆 Подводим итоги «Кубка Будущего 2026» Елисей Рябыкин и Михаил Меликов в составе сборной России U20 стали победителями турнира. Миша Меликов вышел на лед в одном матче и забросил шайбу в меньшинстве. А Елисей Рябыкин принял участие в трех играх и отметился одной результативной передачей. Кроме этого, в полуфинале турнира 3х3 27-й номер бело-голубых вышел в роли капитана и отдал два ассиста, а в финале сыграл Елисе…
🔥163custom 5395527028940221634116👍21😈1custom 54517149421577243121
Молодежка продолжает покорять Дальний Восток. Удачи парням!
custom 539552702894022163442😈30custom 53796438146778483687custom 52179655389610182492custom 53932238054831015462custom 54517149421577243121
🏒 Смотрим хоккей в «Синема Парк»! 15 ноября бело-голубые сыграют с «Сибирью» на выезде. Приглашаем вас поддержать команду в классной атмосфере кинотеатра — с друзьями и попкорном 🍿 Скорее выбирайте комфортные места 🎟
custom 539552702894022163499custom 544975961534654818634custom 521796553896101824923custom 54517149421577243123😈2custom 53932238054831015462🫡1custom 53796438146778483681
Сикки и Никон: *делают красоту* Сергей Владимирович за воротами: ☃️
😁200😍84custom 539322380548310154678custom 544975961534654818630custom 539552702894022163415🔥6👍4😈4
🧘Всегда сохраняйте спокойствие, как Влад. И не верьте слухам 😉 @dynamo_ru
custom 5449759615346548186585🔥134💯69custom 539552702894022163437🙏25😍10custom 54517149421577243129custom 53932238054831015468
Шайба Дмитрия Зугана в ворота «Шанхай Дрэгонс» — в топе лучших голов прошедшей недели 🔥 ⚡️Дима, продолжай! @dynamo_ru
🔥229custom 544975961534654818664⚡32custom 539552702894022163418👏6😍2🤣1😁1
Showing the 12 most recent of 1,329 posts we hold for @dynamo_ru. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@dynamo_ru edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 82 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
@dynamo_ru named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 27 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 64 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | HC Dynamo Moscow |
|---|---|
| Description | Russian professional ice hockey club based in Moscow |
| X / Twitter | @dynamo_ru |
| YouTube | UCa4WDk_1875pqe2xyIhdTQg |
| Official site | http://www.dynamo.ru |
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“ХК «Динамо» Москва | HC Dynamo Moscow” (@dynamo_ru), 45,428 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/dynamo_ru.
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.