Telegram RegisterThe public register of Telegram

Channel

Инфо ШииВиоки | Мфэмкс правят миром

@ShiiVioInfo

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001873763499
TypeChannel
Username@ShiiVioInfo
DescriptionНе плдписывайтемь бдяьяьытцл Лс – @ShiiVioWHAT фантасика🙌🏻🙌🏻😍😍😍детки в его возрасте РЕДКО ходить могут, а этот пляшет стоит уверенно🙌🏻🙌🏻👏👏👏👏 РОДИТЕЛИ, СРОЧНО ОТДАВАЙТЕ МАЛЫША НА СВО!!!!
Created11 August 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/ShiiVioInfo

Growth

110 August 2026 — 1 subscribers14 August 2026 — 1 subscribers10 August 202614 August 2026
2 measurements spanning 4 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:321no change
10 Aug 2026, 06:481first reading

Engagement

4 posts held, back to 11 August 2023the 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 4 posts for this entry, the most recent from 17 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 14 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.

Reaction mix

33 reactions across 2 posts, in 6 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1236.4%
😍927.3%
💘618.2%
🥰39.09%
❤‍🔥26.06%
🔥13.03%

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

Measured over the 4 most recent posts we hold, published 11 August 2023 to 17 January 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.

Recent posts

17 Jan 2026, 03:33 UTC22 viewsread 14 August 2026

Временно не могу поменять пост, мне уже 17🥹🥹🥹

5 Sept 2023, 14:13 UTC≈1,040 views14 reactionsread 14 August 2026

Под этим постом будут стикерпаки/гиф которые я использую на данный момент, если вам нужно – берите.🐈 ‼️Прошу ничего не писать в комментариях. 🎀

😍9💘3🥰2

11 Aug 2023, 00:18 UTC≈1,190 views19 reactionsread 14 August 2026
File

ЭЭЭ ШО ШИВЯ ДУРП КУДА 🌟🌟 💜 𝕴𝖓𝖋𝖔𝖗𝖒𝖆𝖙𝖎𝖔𝖓 𝖆𝖇𝖔𝖚𝖙 𝖒𝖊 : Обращения, которые я предпочитаю: ❄ ➡️ ШииВио/Вио/Шивя ❄️ ➡️ Мей/Мафую ❄️ Все прозвища акутальные, используйте какие вам удобно! ❄️ 𝕻𝖗𝖔𝖓𝖔𝖚𝖓'𝖘 – she/he/they 📌 A priority – She/Her ❄️ 𝙼𝙱𝚃𝙸 – ENTP-A / INTP-A (Ambivert) ❄️ Расслабленно-вовлеченный ❄️ // Вовлечено-избегающий ❄️ 𝕰𝖓𝖓𝖊𝖆𝖌𝖗𝖆𝖒 – 4w5 ❄️ ➡️День рождения 17.01, янва

12💘3❤‍🔥2🔥1🥰1

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

Mentions

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

“Инфо ШииВиоки | Мфэмкс правят миром” (@ShiiVioInfo), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ShiiVioInfo.

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.