Channel
@evnnesupport
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
25subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002025198839 |
|---|---|
| Type | Channel |
| Username | @evnnesupport |
| Description | добро пожаловать на канал, посвященный поддержке EVNNE здесь будет информация о голосованиях, стриминге, чартах. посты публикуются админами @evnne_seungeon & @evnnejellyfish |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/evnnesupport |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 10:01 | 25 | no change |
| 8 Aug 2026, 02:49 | 25 | first reading |
17 posts held, back to 16 June 2024 — 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 pageof 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 17 posts for this entry, the most recent from 14 February 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
у нас есть шанс дать hot mess победу на show champion и music bank !! у нас еще есть 3 дня отслеживания до 16 февраля, чтобы увеличить наши шансы, поэтому вот что мы можем сделать, чтобы забрать награду 🎨 слушайте песни на bugs и получайте цифровые баллы 🎨 смотрите клип на ютубе и получайте баллы sns 🎨 приготовьтесь к предварительному голосованию, победа должна быть с большим отрывом show champion: приложение idolc…
— : Чарт Bugs в реальном времени: — 23:00 KST #1 EVNNE 'HOT MESS' [+8] ~~> @evnnesupport
— : Чарт Hanteo – 10.02.2025 Продажи EVNNE 'HOT MESS' преодолели отметку в 70,764 копий за первый день (*подсчет все еще идет)❕❕❕ это ОЧЕНЬ хороший результат по сравнению с прошлыми альбомами 😭🥹 ~~> @evnnesupport
— : 📝Список того, что нужно делать Энви каждый день❕ & если есть вопросы, обращайтесь в комментарии *все материалы взяты с аккаунта GlobalEVNNE (X) ~~> @evnnesupport
— : в преддверии камбэка, пройдемся по приложениям для голосования на муз.шоу. ! вы можете начать их собирать прямо сейчас, чтобы не упустить возможность отдать максимально большое количество голосов во время самого камбэка : • star planet: the show - собирайте heart jelly (после 16-го января) • idolchamp: show champion - собирайте голубые и розовые чамсимы • allchart: music bank - собирайте сердечки • mubeat: show!…
EVNNE 4th MINI ALBUM HOT MESS 🔜 2025.02.10 6PM (KST)🎥
— : Предварительное голосование для Show Champion в приложении IDOLCHAMP открыто❕ Напоминаем про гайд#1 и гайд#2 ‼️На данный момент EVNNE занимают лишь 3-е место. Успейте отдать все свои накопления до 24 июня 9.00 утра по мск‼️ & если есть вопросы, обращайтесь в комментарии ~~> @evnnesupport
EVNNE SUPPORT pinned a photo
— : напоминаем о том, чтобы вы не забывали собирать валюту в приложениях ! ! давайте постараемся подарить победу ивен и в этом камбеке 🥹🩶
— : Ежедневный чарт альбомов Bugs. — 17.06.2024 #2 RIDE or DIE [NEW] ~~> @evnnesupport
— : Ежедневный чарт песен Bugs. — 17.06.2024 #69 Badder Love [NEW] ~~> @evnnesupport
— : Чарт Bugs в реальном времени. — 13:00 KST #5 Badder Love [+56] *new peak ~~> @evnnesupport
Showing the 12 most recent of 17 posts we hold for @evnnesupport. 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“EVNNE SUPPORT” (@evnnesupport), 25 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/evnnesupport.
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.