Channel
@academydynamovn
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
536subscribers
+5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002017628138 |
|---|---|
| Type | Channel |
| Username | @academydynamovn |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 14 September 2026 |
| On Telegram | t.me/academydynamovn |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 28 Aug 2026, 15:08 | 536 | +2 |
| 14 Aug 2026, 15:08 | 534 | +3 |
| 6 Aug 2026, 18:31 | 531 | no change |
| 6 Aug 2026, 08:51 | 531 | first reading |
15 posts held, back to 1 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 15 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
77 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 29.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 23 | 29.9% | |
| ❤ | 20 | 26.0% | |
| custom 5463427090340673974 | 16 | 20.8% | |
| custom 5463358194770278766 | 9 | 11.7% | |
| 👏 | 9 | 11.7% |
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 10 of the 15 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 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 1 August 2026 to 6 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 тура Первенства СЗФО. Эйгстер Матвей уже в добавленное время точно пробил головой по воротам соперника💙
❤7custom 54633581947702787661custom 54634270903406739741
Второй матч группового этапа первенства СЗФО проведём с ФК Калининград🏆 🏟6 августа, 14:30, стадион "Машиностроитель" ФК "Калининград" - "Динамо-Электрон" 🖥Ссылка на трансляцию https://vkvideo.ru/video-91520717_456241467 Болеем за наших💙
Теперь такие красавцы будут возить нас на соревнования😍 Увидел в городе - обязательно посигналь👋
👍13custom 54633581947702787662custom 54634270903406739742👏1
Первая победа💙 Побеждаем в первом матче первенства СЗФО СШОР № 2 Невского района (Санкт-Петербург) со счётом 4:1. Первые пропустили, но переломили ход игры и одержали уверенную победу. Двигаемся дальше🫡
❤4👍2
Сегодня стартуем в розыгрыше FONBET Кубка России ◻️🔵 🆚 #ФакелДинамо 🔛 18:30 🏟 Стадион «Факел» 💙 Сектор В 🖥 Матч Премьер @fcdynamo
Отправились в Псков🚍 Желаем удачи нашим парням💙
👏7custom 54634270903406739745custom 54633581947702787663
Доброе утро🌤 Наши парни 2012 года рождения начинают свой путь в первенстве СЗФО. Уже сегодня, 5 августа, в Пскове проведём первый матч с СШОР № 2 Невского района (Санкт-Петербург). Стартовый свисток прозвучит в 14:30. Поддержать команду и посмотреть матч можно по ссылке👇 https://vkvideo.ru/video-91520717_456241458
❤2
Динамо-Электрон 2012 отправляется на первенство СЗФО🏆 С 5 по 12 августа в Пскове на стадионе «Машиностроитель» пройдет первенство СЗФО по футболу среди мальчиков до 15 лет. В соревновании примут участие 16 команд из шести регионов. В турнире сыграют мальчики не старше 2012 года рождения. Участники разделены на четыре группы по четыре команды. По два лидера каждого квартета выйдут в четвертьфинал. Наши соперники по …
👍1custom 54633581947702787661custom 54634270903406739741
Турнир завершен🫡 Бились и старались, радовались и огорчались, проигрывали и побеждали, оставили все силы на футбольном поле. Таким получился наш Турнир по футболу памяти Г.И.Смертина. Благодарим команду и тренеров за турнир. Насыпим лайков команде💙
❤4👍3custom 54634270903406739742
Мы всегда рядом🫶 4000 тысячи не расстояние для наших самых преданных и самых дорогих болельщиков - родителей наших воспитанников. Мы слышали Вас, мы играли для Вас. Спасибо, что были рядом. Мы команда💙
custom 54634270903406739742👍1👏1
В заключительном матче Турнира по футболу памяти Г.И.Смертина побеждаем "Динамо" Ульяновск со счётом 2:1 и занимаем итоговое 13 место📋 Спасибо тем, кто болел за нас, поддерживал и верил. Разбираем ошибки, делаем правильные выводы и возвращаемся сильнее💙
❤3custom 54634270903406739742custom 54633581947702787661
Заключительный матч Турнира по футболу памяти Г.И.Смертина✊️ 🗓3 августа, 06:00 (МСК) 🇷🇺"Динамо" Ульяновск - 🇷🇺"Динамо-Электрон" Новгородская область 🖥прямая трансляция https://vkvideo.ru/video-75562179_456239348
Showing the 12 most recent of 15 posts we hold for @academydynamovn. 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.
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.
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.
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 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Великий Новгород — Академия «Динамо» им. Л.И. Яшина” (@academydynamovn), 536 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/academydynamovn.
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.