Telegram RegisterThe public register of Telegram
Telegram profile photo for POPUSK 2026

Channel

POPUSK 2026

@popyskalovo

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,129subscribers

+16 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001539804178
TypeChannel
Username@popyskalovo
Created1 July 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/popyskalovo

Topic

Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.

Growth

1,1131,1341,123.56 August 2026 — 1,113 subscribers7 August 2026 — 1,115 subscribers10 August 2026 — 1,118 subscribers14 August 2026 — 1,131 subscribers17 August 2026 — 1,134 subscribers20 August 2026 — 1,132 subscribers27 August 2026 — 1,131 subscribers11 September 2026 — 1,130 subscribers15 September 2026 — 1,129 subscribers1,1296 August 202615 September 2026
9 measurements spanning 39 days, net +16. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,110–1,137 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 02:581,129-1
11 Sept 2026, 11:361,130-1
27 Aug 2026, 01:361,131-1
20 Aug 2026, 14:041,132-2
17 Aug 2026, 18:121,134+3
14 Aug 2026, 16:251,131+13
10 Aug 2026, 21:011,118+3
7 Aug 2026, 21:501,115+2
6 Aug 2026, 21:471,113first reading

Engagement

11 posts held, back to 10 June 2025 — 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 11 posts for this entry, the most recent from 28 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

271 reactions across 8 posts, in 14 distinct kinds. The most used accounts for 28.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7728.4%
🔥5319.6%
🤡4717.3%
👎165.90%
❤‍🔥124.43%
🖕124.43%
😁124.43%
💩114.06%
👍103.69%
💊72.58%
👏62.21%
💯31.11%
🤝31.11%
😱20.738%

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 8 of the 11 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 271 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 10 June 2025 to 28 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Jul 2025, 17:11 UTC≈2,000 views44 reactionsread 6 August 2026
Photo

Лес чист, мусор увезен, команда покинула локацию, а это значит, что последний Попуск официально состоялся! Выражаем благодарность каждому приехавшему участнику сего мероприятия, это были поистине волшебные моменты❤️ Тем же, кто хочет поддержать рублём, доступна функция донатов по номеру +7-900-647-3997 т банк Увидимся когда-нибудь, где-нибудь, с кем-нибудь!

❤33🔥7👍3💊1

21 Jul 2025, 17:05 UTC≈3,130 views39 reactionsread 6 August 2026

И у озёр у наших села Батарейка! За июнь столько всего переигралось, что многие подумали, что уже будет отмена движа🤷‍♂ Но таков стилёк наших анонсов: запилить в таком же духе финал, как и начало — за несколько дней до выезда🤪 Будет разная музыка, электронная и живая, какое-то количество сцен и барчик с крафтом) даже шоукейс гостевой все же будет от наших любимых габберов Питера😅 Короче, наш занятный туснячок всё…

❤18❤‍🔥7💊6😁5🔥3

18 Jun 2025, 13:31 UTC≈3,110 views95 reactionsread 6 August 2026

Что за джазу мы с вами дадим уже через месяц с небольшим, ё-моё...

🤡28🔥21👎16💩11❤5🖕5👍4😱2

15 Jun 2025, 18:16 UTC≈3,070 views33 reactionsread 6 August 2026

В этот раз мейном будет днб сцена от команды Bass In Face

🔥14🤡9🖕7❤1❤‍🔥1🤝1

14 Jun 2025, 21:56 UTC≈2,540 views9 reactionsread 6 August 2026

Говорят, это может быть весьма концептуально

👍2💯2🔥2❤‍🔥1🤝1😁1

13 Jun 2025, 11:57 UTC≈2,270 views7 reactionsread 6 August 2026
Forwarded from @kontaktpartyPhoto

Итоговое расписание сегодняшнего рейва! Сохраняйте, чтобы не потерять🙏

❤6❤‍🔥1

12 Jun 2025, 08:50 UTC≈1,740 viewsread 6 August 2026

Последний день работы промокода Popusk для Mystic Rave! По нему вход 1000р, уже завтра нам его отключат, и будет фул прайс за 2к🤷‍♂ Успевайте, кто хочет, мы там сами обязательно будем🙏

10 Jun 2025, 11:48 UTC≈1,840 views23 reactionsread 6 August 2026

По идее, уже совсем скоро мы начнём объявлять всамделишных артистов с фотографиями и прочими причиндалами, а пока, так же текстом, тихонько, скажем, что в этом году на попуске будет ночь габбы от Hakkenation на Бодрящей..😇 P.S. в ночь с 26 на 27 июля 2025, с 23:59 до 6 утра👯‍♂️

❤10👏6😁5❤‍🔥1🤝1

10 Jun 2025, 11:35 UTC≈1,420 views21 reactionsread 6 August 2026

Как же быть, Как быть, Запретить себе тебя любить? Не могу я это сделать, не могу! Такие слова вы можете услышать, проходя мимо сцены Fantasy во время выступления DJ AIMP☺️ Разные русские и не очень сопливые хиты, проверенные временем🤪 Иванушки International, Отпетые Мошенники, Кристина Агилера, No Doubt, Dobie Gray, УмаТурман - и многие-многие другие, кого вы давно слышали, но случайно могли позабыть, могут всплыт…

🤡10🔥6❤4👍1

10 Jun 2025, 11:13 UTC≈1,220 viewsread 6 August 2026

Поздравляем победителей! Как только организаторы вышлют билеты, редакция журнала Аудиоформат раскидает их всем победителям🙏 Остальные, не отчаивайтесь — для вас всё ещё действует промокод Popusk😎 И да, скоро продолжатся посты-анонсы нашего грядущего эпичнейшего сходнячка, не переключайтесь😏

Showing the 11 most recent of 11 posts we hold for @popyskalovo. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 12 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.

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.

Cite this entry

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“POPUSK 2026” (@popyskalovo), 1,129 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/popyskalovo.

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.