Channel
@e1_supfest
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,110subscribers
-17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002189931262 |
|---|---|
| Type | Channel |
| Username | @e1_supfest |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/e1_supfest |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 18:23 | 1,110 | -2 |
| 30 Aug 2026, 04:47 | 1,112 | -3 |
| 27 Aug 2026, 03:08 | 1,115 | -4 |
| 24 Aug 2026, 04:56 | 1,119 | -1 |
| 20 Aug 2026, 13:43 | 1,120 | -1 |
| 17 Aug 2026, 12:08 | 1,121 | -3 |
| 14 Aug 2026, 04:14 | 1,124 | -2 |
| 11 Aug 2026, 06:43 | 1,126 | -1 |
| 7 Aug 2026, 23:48 | 1,127 | no change |
| 7 Aug 2026, 13:09 | 1,127 | first reading |
6 posts held, back to 13 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 6 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
143 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 35.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 51 | 35.7% | |
| 🔥 | 36 | 25.2% | |
| custom 5321036507727833242 | 22 | 15.4% | |
| custom 5323458525685389520 | 10 | 6.99% | |
| 😍 | 8 | 5.59% | |
| 👍 | 5 | 3.50% | |
| custom 5425141507050973573 | 4 | 2.80% | |
| 😢 | 4 | 2.80% | |
| 👎 | 3 | 2.10% |
Custom emoji. 3 of the rows above are 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 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 143 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 13 July 2026 to 3 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.
🏄♂️ Победительница нашего сап-феста заняла призовое место ещё и в Питере у наших коллег на «Фонтанка SUP». Поздравляем! Елена написала, что они выиграли в «Самой блестящей номинации», заняли 1 и 2 место в костюма Киркорова и голубей. Передаёт всем привет! В Екатеринбурге победа была в номинации «Командный заплыв» с костюмами пчёл.
🔥22😍8❤3👍1
Перед вами сложный выбор: сап-фест в Тюмени или в ЧЕЛЯБИНСКЕ 😺 Коллеги объявили о дате проведения. У них все подробности — в этом канале @supfest74
custom 53210365077278332429
😍 Огромное спасибо за подарок передает Варлен, он был в костюме Буратино. Мы все ещё вручаем призы от E1 SUP FEST за победу в номинациях после фестиваля и за попадание в топ-30 к нашему юбилею.
❤15🔥6👍3
Вновь готовьте костюмы! Можно скататься в Тюмень 8 августа. Там тоже пройдет наш сап-карнавал у коллег из 72.RU Все о номинациях, программе и прочем читайте в канале — @supfest_72 🏄♂️ Спойлер: там немного отличается от Екатеринбурга
❤11custom 53210365077278332424custom 54251415070509735734
Выбрали 30 победителей в номинации к 30-летию E1.RU 🥳 Признаемся: вы сделали настолько крутые костюмы, что выбирать было очень непросто — хотелось наградить каждого, но конкурс есть конкурс. Посмотрите на 30 фото этих счастливчиков! Если вы нашли себя на снимках, пожалуйста, свяжитесь с редакцией в Telegram @e1_event или по почте [email protected]. Укажите, что вы победитель спецноминации E1 SUP FEST. Мы расскажем…
❤15🔥7😢4custom 53210365077278332424👎2
Итоги в номинации «Лучший рилс». Видео в посте — по порядку 📸 🔖 Варвара (varvara.alexo) повторила образ из «Истории игрушек» и рассказала в рилс, в какую сумму обошлись костюмы. Варвара, вы старались не зря! Поздравляем! 🔖 Анастасия Тарасова показала эффектное перевоплощение. Короткий, но такой запоминающийся ролик! 🔖 Анна Ауэрбах, ваш голубь в розовых колготках нас покорил! Как и интересный монтаж. 🔖 Яркие пират…
custom 532345852568538952010❤7custom 53210365077278332425👍1👎1🔥1
Showing the 6 most recent of 6 posts we hold for @e1_supfest. 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“E1 SUP FEST: важная информация” (@e1_supfest), 1,110 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/e1_supfest.
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.