Уже совсем скоро Все ли команды пройдут испытания до конца — вопрос, который остаётся открытым БИЛЕТЫ
custom 54291635119954684159custom 54295079597826760319custom 54317936812480656128

Channel
@vspyshka_fest
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,012subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001194546176 |
|---|---|
| Type | Channel |
| Username | @vspyshka_fest |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/vspyshka_fest |
Gaming — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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, 20:57 | 1,012 | -5 |
| 14 Sept 2026, 11:59 | 1,017 | -1 |
| 11 Sept 2026, 00:17 | 1,018 | -4 |
| 6 Sept 2026, 01:00 | 1,022 | -5 |
| 1 Sept 2026, 22:15 | 1,027 | +2 |
| 30 Aug 2026, 05:07 | 1,025 | -1 |
| 27 Aug 2026, 08:52 | 1,026 | -3 |
| 24 Aug 2026, 05:47 | 1,029 | +1 |
| 20 Aug 2026, 21:34 | 1,028 | -7 |
| 17 Aug 2026, 18:17 | 1,035 | -7 |
| 14 Aug 2026, 15:57 | 1,042 | +8 |
| 11 Aug 2026, 08:28 | 1,034 | +7 |
| 8 Aug 2026, 09:50 | 1,027 | +8 |
| 7 Aug 2026, 10:16 | 1,019 | first reading |
14 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 14 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
813 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 33.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5429507959782676031 | 275 | 33.8% | |
| custom 5429163511995468415 | 264 | 32.5% | |
| custom 5431793681248065612 | 253 | 31.1% | |
| custom 5429456162477083539 | 21 | 2.58% |
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 14 of the 14 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 813 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 1 August 2026 to 7 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.
Уже совсем скоро Все ли команды пройдут испытания до конца — вопрос, который остаётся открытым БИЛЕТЫ
custom 54291635119954684159custom 54295079597826760319custom 54317936812480656128
Тот самый момент, когда пора отложить телефон БИЛЕТЫ
custom 542950795978267603115custom 542916351199546841513custom 543179368124806561210
Пора взять билет? БИЛЕТЫ
custom 542916351199546841515custom 542950795978267603114custom 543179368124806561210
Лес, костёр, гитара и Сиббиттер. Традиции, которые согревают. БИЛЕТЫ
custom 542950795978267603117custom 543179368124806561216custom 542916351199546841514
Рубрикатор «Вспышки» — ориентируйся в лесу #трансфер — как добраться, где встретить машинку и не потеряться по пути. Всё, чтобы ты доехал без приключений (ну, или почти без них). #расписание — когда йога, когда диджей, когда бежать на мастер-класс, а когда просто лежать и смотреть в небо. Твой личный гид по событиям. #билеты — покупка, вопросы, условия, включённые опции. Если ты ещё сомневаешься — этот раздел для …
custom 543179368124806561213custom 542950795978267603110custom 54294561624770835399custom 54291635119954684154
SIBSA приносит вайб нового мира даже в лесную чащу. Освежающие напитки, которые звучат в унисон с энергией «Вспышки».
custom 542950795978267603124custom 542916351199546841522custom 543179368124806561220
«Арктика» дарит термос, чтобы твой чай на «Вспышке» оставался горячим даже в лесную прохладу. Участвуй в розыгрыше — и твой напиток не остынет до самого костра. Условия участия: 1. Подписаться на канал «Арктики» 2. Подписаться на канал «Вспышки» 3. Кинуть реакцию на этот пост 4. Нажать кнопку "Участвую!" Итоги подведем уже 12 августа в 18:00!
custom 542916351199546841534custom 542950795978267603126custom 543179368124806561226custom 54294561624770835399
Разыгрываем подарки вместе с рюмочной «Культурно Коротко» 😱 «Культурно Коротко» — сеть атмосферных рюмочных, где вкус и общение всегда важнее формальностей. Проект появился в Воронеже в 2019 году, а сегодня уже объединяет 12 заведений, в том числе два в Москве. Их визитная карточка — около 60 вкусов фирменных настоек и уютная атмосфера, в которую хочется возвращаться 🔥 Вместе мы подготовили для вас два приза: 1 мес…
custom 542950795978267603129custom 542916351199546841520custom 543179368124806561219custom 54294561624770835393
Закрываем фестиваль красиво. Воскресное расписание — чтобы ты точно не пропустил самое важное. БИЛЕТЫ
custom 542950795978267603127custom 543179368124806561219custom 542916351199546841515
Суббота на «Вспышке» — каждый час новый повод не скучать. Держи расписание, чтобы ничего не пропустить. БИЛЕТЫ
custom 543179368124806561226custom 542950795978267603118custom 542916351199546841514
Палатки, спальники, коврики — всё готово, но форма заполняется не бесконечно. Успей сказать «да» до того, как мы скажем «всё разобрали». АРЕНДОВАТЬ
custom 542916351199546841519custom 542950795978267603113custom 543179368124806561212
Вода, лес и август — кажется, идеальное сочетание На Вспышку приезжает WHATSUPTOUR — команда, которая превращает обычные выходные в настоящие приключения на воде. Их стихия — сапы, байдарки, каяки и путешествия по рекам и озерам России. И хорошая новость: покататься на сапах на фестивале сможет каждый — это входит в билет БИЛЕТЫ
custom 542916351199546841536custom 543179368124806561231custom 542950795978267603125
Showing the 12 most recent of 14 posts we hold for @vspyshka_fest. 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.
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.
“Хроники Вспышки” (@vspyshka_fest), 1,012 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vspyshka_fest.
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.