Channel
@vDOLGUshin
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,595subscribers
-18 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001924380666 |
|---|---|
| Type | Channel |
| Username | @vDOLGUshin |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/vDOLGUshin |
Personal blog — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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, 15:59 | 1,595 | -5 |
| 14 Sept 2026, 06:00 | 1,600 | -4 |
| 10 Sept 2026, 06:18 | 1,604 | -3 |
| 5 Sept 2026, 04:15 | 1,607 | -2 |
| 1 Sept 2026, 12:52 | 1,609 | +2 |
| 29 Aug 2026, 16:02 | 1,607 | +1 |
| 26 Aug 2026, 18:14 | 1,606 | -2 |
| 23 Aug 2026, 22:09 | 1,608 | +1 |
| 17 Aug 2026, 10:13 | 1,607 | -5 |
| 13 Aug 2026, 17:37 | 1,612 | -2 |
| 10 Aug 2026, 06:55 | 1,614 | +1 |
| 6 Aug 2026, 11:35 | 1,613 | no change |
| 6 Aug 2026, 10:46 | 1,613 | first reading |
6 posts held, back to 7 June 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 2 pages 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
125 reactions across 6 posts, in 7 distinct kinds. The most used accounts for 42.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 53 | 42.4% | |
| 🔥 | 32 | 25.6% | |
| 🥰 | 11 | 8.80% | |
| 👍 | 9 | 7.20% | |
| 👏 | 8 | 6.40% | |
| 💯 | 8 | 6.40% | |
| 😍 | 4 | 3.20% |
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 6 of the 6 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 125 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 7 June 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.
Фанатам LEGO Как давний поклонник и коллекционер квадратных фигурок не мог пройти мимо яркого перфоманса сборной Нидерландов до ЧМ. Такой матчевый вымпел я бы точно оставил себе. А вообще круто и супер неочевидно. Только после этого реально задумываешься, что классические вымпелы уже надоели и пора бы переосмыслить и продать и эту опцию. #мироваяпрактика
❤5👏3🔥1
Никогда бы не подумал, что самым сложным в организации ивентом в моей жизни будет свадьба! В конце августа увидите результаты, а пока можете насладиться фотками из ЗАГСа 🤍
❤29🔥14🥰11😍2
Публикуем неизданное Не для кого ни секрет, что Apple спонсирует MLS уже не первый год: трансляции на Apple TV, подписки и другие атрибуты рынка Америки. Но внимание как всегда привлекают неординарные и смелые проекты. Так, например, один из матчей был снят полностью на их продукт – айфоны. Не огромные камеры, а обычные «прошки», на которые мы делаем селфи каждый день. Поражает, с какой легкостью там делают крутые …
❤4🔥3👍2👏1
Рынок Азии Если смотреть на Азию и кейсы, которые приходят оттуда, складывается ощущение, что привычная и актуальная для нас сейчас реклама была там лет 10 назад. Кстати, это, например, адаптировал Медибаскет, молодцы. Поставили разбитую тачку перед местом проведения финала – получили кучу UGC-контента. Предлагал варианты и для МФЛ, но, к сожалению, не срослось. Из нового и крутого, Adidas Running в коллабе с корей…
❤7👍4🔥2💯1😍1
Свои плюсы Яндекс Пэй сейчас активно поддерживает спорт: видел точки на «Спартаке», как я понял, сейчас это титульный спонсор «Уличного футбола» – такой возможностью нужно пользоваться (особенно в тяжелые времена), адаптировав, например, кейсы ЧМ. Яндекс еще в 2024 делал что-то подобное, но охваты Матча тура, к сожалению, чуть меньше ЧМ, поэтому про кейс Uberа вы наверняка слышали, а про отечественных маркетологов –…
🔥9💯7👍3👏1
ЧМ Главное упущение за последние полгода – неактивное ведение своего канала. К счастью, нашел силы перед ЧМ, чтобы разобрать для вас несколько классных кейсов (если вы вдруг их пропустили). Вообще поражает, как модные дома заходят в индустрию спорта и футбола, в частности. Связываю это, прежде всего, со становлением футбольного матча не просто спортивным событием, но и модным досугом для аудитории (как финал РГ, на…
❤8👏3🔥3😍1
Showing the 6 most recent of 6 posts we hold for @vDOLGUshin. 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 3 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.
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.
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.
“я у вас в ДОЛГУшин” (@vDOLGUshin), 1,595 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vDOLGUshin.
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.