⋆ ˚。⋆୨୧°𝙉𝙞𝙣𝙜 𝙔𝙞𝙣𝙜𝙮𝙞𝙣𝙜°୨୧⋆。˚ ⋆ —Шисюн, если он не хочет, то и ладно, ничего страшного! Не нужно заставлять его! 🌷🌷🌷🌷🌷🌷🌷🌷🌷🌷🌷🌷🌷 𝘾𝙤𝙨𝙥𝙡𝙖𝙮𝙚𝙧: 𝙢𝙚 𝙋𝙝𝙤𝙩𝙤/𝙧𝙚𝙩𝙤𝙪𝙘𝙝: 𝙔𝙤𝙠𝙤 Рт/реакт/коммы?
custom 53233636369729133402
![Telegram profile photo for [РЕСТ] 🕯Ꮲᴇᴧиᴦия Ꮯᴇᴧяниɜʍ ♰](https://cdn.tgregister.com/av/65/65ad276293296c74b97e2058c1366110872d5009bbf1c4973b584b47bcf511a0.jpg)
Channel
@vernissomnoyvgusu
On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
159subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002090427054 |
|---|---|
| Type | Channel |
| Username | @vernissomnoyvgusu |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/vernissomnoyvgusu |
@vernissomnoyvgusu was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 17:26 | 159 | -4 |
| 22 Aug 2026, 17:36 | 163 | -1 |
| 8 Aug 2026, 16:30 | 164 | no change |
| 7 Aug 2026, 19:04 | 164 | first reading |
9 posts held, back to 4 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 9 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
12 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5197169766875302037 | 9 | 75.0% | |
| custom 5323363636972913340 | 2 | 16.7% | |
| custom 5980990994768728018 | 1 | 8.33% |
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 6 of the 9 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 4 August 2026 to 8 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 53233636369729133402
❤🐚🐚✅🔠🔠🔠⛈ 🩵🩵🩵❤️❤️❤️❤️❤️ — Вокс (me)🌟 — Вал💕🌟 ✨✨✨ #staticmoth #cosplay #hazbinhotel ✨✨✨✨✨
custom 51971697668753020372
🖤🖤🐚🐚✅🐚🐚🐚🖤🖤 ㅤㅤㅤㅤㅤㅤ🖤🖤🖤 •отсняли воксвалов) сегодняшним мемом была мой жопа, вокак •Вокси💙 •Валентино(me)🌟 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩
custom 51971697668753020373
🪐 GALAXY EVENT 🪐 5 сентября (сб) 💫 начало ~ в 13:00 💫 ТРЦ Галактика г. Барнаул, Строителей 17 Конкурсная программа: ⚫️Одиночное косплей дефиле ⚫️Групповое косплей дефиле ⚫️Cover Dance Solo/Duet ⚫️Cover Dance Team 💥 Участие бесплатное Подача заявок до 29 августа 23:59 ➡️ https://galaxy2026.cosplay2.ru/
заманчиво, ох как заманчиво..
Провожая лето, невольно задумываешься - а что там дальше? Сентябрь, осень, школа... 📚 ☁️ Для кого-то школьное время - это лишь старое воспоминание, для других - жизнь здесь и сейчас. Так или иначе, предлагаем вместе провести последние летние деньки и, немного забегая вперед, окунуться в школьную атмосферу... 🆕 SCHOOL AU - конкурс для косплееров, которые давно хотели воплотить своих любимых персонажей в школьной фор…
~|Эндрю Миньярд|~ -Да или нет? !Закос! Фд: Всё ради игры Косплеер: Радио Рэй Рт/рк? #ЭндрюМиньярд #Закос #УраПост
custom 51971697668753020373
💙💙💙 ☑️☑️☑️ ☑️☑️☑️☑️⭐ ⭐ ⭐ ⭐ ⭐ 😨: Я готов возжечь и преподнести богам тысячу лампад, готов озарить светом долгую Ночь, и даже если сам сгорю, как мотылёк, в огне, моего сердца не коснётся страх. Но я не желаю склонять голову в покаянии за свершённое бла…
custom 59809909947687280181
Мне сегодня 23) Я в шоке, как быстро год прошёл👀 Спасибо вам за то, что всё ещё остаётесь со мной♥️ Буду рада репосту мои работ)
custom 51971697668753020371
Showing the 9 most recent of 9 posts we hold for @vernissomnoyvgusu. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“[РЕСТ] 🕯Ꮲᴇᴧиᴦия Ꮯᴇᴧяниɜʍ ♰” (@vernissomnoyvgusu), 159 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/vernissomnoyvgusu.
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.