Video message, posted without a caption
custom 57897013633823606608custom 53800299580075852344custom 52200058502901004773
Signed LIPEN

Channel
@vistavkadushoffc
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
498subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002126807653 |
|---|---|
| Type | Channel |
| Username | @vistavkadushoffc |
| 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 | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/vistavkadushoffc |
Music — 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 |
|---|---|---|
| 13 Sept 2026, 06:01 | 498 | +2 |
| 4 Sept 2026, 22:58 | 496 | +3 |
| 21 Aug 2026, 07:35 | 493 | -1 |
| 15 Aug 2026, 00:23 | 494 | -1 |
| 6 Aug 2026, 18:47 | 495 | no change |
| 6 Aug 2026, 10:08 | 495 | first reading |
15 posts held, back to 21 July 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
184 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 37.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5789701363382360660 | 68 | 37.0% | |
| custom 5380029958007585234 | 50 | 27.2% | |
| custom 5341316707644351077 | 49 | 26.6% | |
| custom 5220005850290100477 | 9 | 4.89% | |
| custom 5379836315112079393 | 8 | 4.35% |
Custom emoji. Every 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 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 15 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 184 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 21 July 2026 to 4 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.
Video message, posted without a caption
custom 57897013633823606608custom 53800299580075852344custom 52200058502901004773
Signed LIPEN
ДУШЕВНЫЕ НАШИ!💜 сегодня мы вернулись домой с крутейшего фестиваля «ЗЕЙСКИЙ БЕРЕГ»!🔥 спасибо за вашу энергию, это было мощно!🤘🏻 мы разделили сцену с лучшими командами Дальнего Востока и гостями из Поднебесной!🇨🇳 а добраться обратно был тот еще квест…🚇 сначала мы в течении часа пытались заказать такси до вокзала, а затем наш и без того поздний поезд задержали на 2 часа, так что пол ночи мы провели на вокзале (сели…
custom 578970136338236066011custom 53798363151120793934custom 53800299580075852344custom 53413167076443510772
Signed LIPEN
Video message, posted without a caption
custom 53800299580075852345custom 57897013633823606604custom 52200058502901004772
Signed LIPEN
Video message, posted without a caption
custom 53413167076443510774custom 53800299580075852344custom 53798363151120793931
Signed LIPEN
Video message, posted without a caption
custom 53413167076443510775
Signed LIPEN
Video message, posted without a caption
custom 53413167076443510777custom 57897013633823606607custom 53800299580075852345
Signed LIPEN
Video message, posted without a caption
custom 53800299580075852347custom 57897013633823606605custom 53413167076443510773
Signed LIPEN
Video message, posted without a caption
custom 57897013633823606603custom 53413167076443510771custom 53800299580075852341
Signed LIPEN
Video message, posted without a caption
custom 53413167076443510773custom 53800299580075852343custom 57897013633823606601
Signed LIPEN
Video message, posted without a caption
custom 53413167076443510777custom 57897013633823606604custom 53800299580075852342
Signed LIPEN
Video message, posted without a caption
custom 57897013633823606606custom 53413167076443510773custom 53800299580075852343
Signed LIPEN
ДУШЕВНЫЕ НАШИ!💜 18 июля нашему треку «море» исполнился год! 🌊 интересные факты про трек: 🐳 18.07 мы исполнили и так сказать, поздравили его на нашем сольнике «НА 8 ЭТАЖЕ»! ⚠️ во время съемок сниппета группа чуть не лишилась фронтмена (в конце сниппета можно заметить мое падение)) 🔥 23.08.25 «море» услышали более 60 тысяч человек на фестивале РОК НАД АМУРОМ! 📻 трек был полгода в ротации на радио 25-й Регион 🎸ме…
custom 534131670764435107710custom 53800299580075852346custom 53798363151120793932custom 57897013633823606601
Signed LIPEN
Showing the 12 most recent of 15 posts we hold for @vistavkadushoffc. 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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“ВЫСТАВКА ДУШ” (@vistavkadushoffc), 498 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/vistavkadushoffc.
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.