Channel
@dvgups_hockey
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
302subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002095799441 |
|---|---|
| Type | Channel |
| Username | @dvgups_hockey |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/dvgups_hockey |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 03:08 | 302 | +1 |
| 8 Aug 2026, 08:02 | 301 | no change |
| 8 Aug 2026, 00:03 | 301 | first reading |
20 posts held, back to 28 April 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 pageof 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 9 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
69 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 33.3% | |
| 🔥 | 16 | 23.2% | |
| ❤🔥 | 9 | 13.0% | |
| 🥰 | 6 | 8.70% | |
| 🎉 | 5 | 7.25% | |
| 😁 | 3 | 4.35% | |
| 🫡 | 3 | 4.35% | |
| 👻 | 2 | 2.90% | |
| 👏 | 1 | 1.45% | |
| 🤔 | 1 | 1.45% |
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 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 69reactions 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 28 April 2026 to 9 May 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.
С Днём Великой Победы! 🎆🇷🇺 9 Мая — это праздник, который объединяет всех нас. Это день памяти, гордости и бесконечной благодарности за мирное небо над головой. Пусть мужество и стойкость наших героев всегда будут примером истинной любви к Родине. Желаем всем мира, добра, благополучия и крепкого здоровья! Пусть в каждом доме царит гармония, а в сердцах живет вечная память о великом подвиге. С праздником! Помним и го…
❤3🫡2😁1
Sticker, posted without a caption
Отдельная благодарность — нашему «шестому игроку»! 🔥 Спасибо всем, кто не спал ночами, смотрел наши трансляции и писал слова поддержки. Мы знаем, как это было непросто, и очень ценим вашу преданность. Ваша вера в команду — это то, что дает нам силы двигаться вперед. Завершаем этот выезд на теплой ноте. Увидимся в следующем сезоне! 👋🏒✨
❤14🔥7🥰4😁2
Ну что, наше путешествие подошло к концу — мы едем домой! 🏠✈️ Это были невероятно насыщенные 6 дней, которые мы запомним надолго. Мы успели всё: сражались на льду, гуляли по атмосферным улицам Питера и ловили ритм Москвы. 🏙️🏒 За эту неделю мы испытали целую палитру эмоций — от предматчевого волнения и спортивного азарта до полного восторга от красоты обеих столиц. Уезжаем уставшие, но с полным багажом впечатлений и…
🔥9❤4🥰2
С праздником, друзья! С 1 Мая! ☀️🌱 Поздравляем всех-всех-всех: наших преданных болельщиков, друзей и каждого, кто идет к своей цели! Пусть этот праздник весны и труда принесет в ваши дома тепло, радость и море позитивной энергии. Спасибо, что вы с нами! Желаем всем отличных выходных, яркого солнца и классного настроения! Мир, труд, май! 🕊️🏒✨ СХК «ЛОКО ДВ» ЖЕЛЕЗКА
❤🔥9
Матч окончен Локомотив ДВ 2:3 Запад России (по буллитам)
3 период ✅✅✅ Локомотив ДВ 2:2 Запад России
Video, posted without a caption
2 период ✅✅✅ Локомотив ДВ 2:1 Запад России
2 период ✅✅✅ Локомотив ДВ 2:0 Запад России С передачи Александра Деменка,шайбу забросил Даниил Вакарин
1 период ✅✅✅ Локомотив ДВ 1:0 Запад России Шайбу забросил Александр Данилов
Video, posted without a caption
Showing the 12 most recent of 20 posts we hold for @dvgups_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.
Citation-graph rank — 974,289 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“СХК ЛОКО ДВ / Kachesov team” (@dvgups_hockey), 302 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/dvgups_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.