Channel
@manhvi1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
106subscribers
+8 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002378023320 |
|---|---|
| Type | Channel |
| Username | @manhvi1 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/manhvi1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 06:00 | 106 | -1 |
| 9 Sept 2026, 12:38 | 107 | +4 |
| 24 Aug 2026, 01:55 | 103 | +5 |
| 9 Aug 2026, 11:31 | 98 | no change |
| 8 Aug 2026, 18:01 | 98 | first reading |
9 posts held, back to 20 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 9 posts for this entry, the most recent from 7 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.
119 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 33.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 40 | 33.6% | |
| custom 5253651997021718065 | 22 | 18.5% | |
| custom 5382061687991969339 | 15 | 12.6% | |
| ❤🔥 | 15 | 12.6% | |
| 🥰 | 13 | 10.9% | |
| 💘 | 11 | 9.24% | |
| 💋 | 2 | 1.68% | |
| 🍓 | 1 | 0.84% |
Custom emoji. 2 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 8 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 119 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 20 July 2026 to 7 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.
Принимаю эстафету от Ксу и Кошки🤩 Я возьму Сатериазиса Веномания, так как он один из моих любимых косплеев👾 Интересный факт: грех этого персонажа не относиться ко мне хах, но как же мне нравиться его лор Передаю эстафету Чаре и Шиэру🤩
❤8🥰6custom 52536519970217180654
Давайте так, осталось совсем немного, поэтому на 100 подписчиков делаю сигны💜
❤5custom 52536519970217180652❤🔥1
Я думаю, что первый час ночи, это идеальное время, чтобы выложить допы по Тигру в его глазах🌸
❤12🥰6❤🔥3custom 52536519970217180652💘1custom 53820616879919693391
╞════✞ᑯ૯ⲙ૦ⲛ ⲙɪⲍɪ✞═════╡ 🖤 ╭━─━─━─━❦ Βραɥμ ϰαημωγτ ϻϰε ɞ ӄαρτσɥӄε «ϰεɞραϲτεϰμӄ» Λεɥεϰμε: ϻεɠμӄαϻεϰτƅɩ μ ϕμӡμɥεϲӄμύ τργɠ, Α ꤎ, τσϰγψμύ ɞ μλε, ϻσλɥα ϲϻστρελ ɞσӄργӷ Ͷ ηρσϲτσ χστελ, ɥτσδ ϻεϰꤎ λબδμλμ ❦ ━─━─━─━╯ Буду благодарна за рт и реакции!! 𝑻𝒉𝒆 𝑨𝒖𝒕𝒐𝒓 : Sua Doll 𝑯𝒂𝒔𝒉𝒕𝒂𝒈𝒔: #alienstage #mizi #закоскосплей ꒷︶꒷꒥꒷‧₊˚꒷︶꒷꒥꒷‧₊˚
❤🔥5❤2
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ✝️ 🤩🤩🤩🤩🤩🤩 ✝️ "ⲏᥱ 𐔤ⲙυρᥲύ υⳅ-ⳅᥲ ⲙᥱⲏя, Аⲕυ. ⲕ𐔖𐔏ⲇᥲ я 𐔤ⲙρ𐔤, ⲧы ᥴⲙ𐔖ⲿᥱɯь ᥒ𐔖ᥒ᥈ᥲⲕᥲⲧь 𐔖ⳝ𐔖 ⲙⲏᥱ" 🤩𝐹𝑎𝑛𝑑𝑜𝑚: 𝐶ℎ𝑎𝑖𝑛𝑠𝑎𝑤 𝑀𝑎𝑛 🤩𝐶𝑜𝑠𝑝𝑙𝑎𝑦𝑒𝑟: 𝑆ℎ𝑖𝑒𝑟𝑢 🤩 𝑤𝑖𝑔 Реакты 🩶
custom 53820616879919693394❤2❤🔥1
Рест/~Руи~Розы под шампанским 🌹🍾 pinned a photo
🌟🌟🌟🌟🌟🌟🌟🌟 🤩🤩 🤩🤩🤩🤩🤩 🌟🌟🌟🌟🌟🌟🌟🌟🍃 🤩🤩 🤩:: Бом А, когда я выздоровею вернемся обратно в твою деревню? Cosplayer: Rui Fandom: taming the tiger Рт, реакции
💘10custom 52536519970217180655❤4❤🔥4custom 53820616879919693393🍓1🥰1
Готовы? Завтра будет пост) А именно пост с Ан Гым Ху, который занял 3 место на фесте в тополях🤩
custom 52536519970217180659custom 53820616879919693394❤1
Резкий деп репостами, вообще у меня столько постов для вас, нужно время найти для оформления, так что готовьтесь🌟
❤6custom 53820616879919693393💋2❤🔥1
Showing the 9 most recent of 9 posts we hold for @manhvi1. 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.
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.
Named by 5 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Рест/~Руи~Розы под шампанским 🌹🍾” (@manhvi1), 106 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/manhvi1.
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.