Channel
@michellopng
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
389subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001549227031 |
|---|---|
| Type | Channel |
| Username | @michellopng |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/michellopng |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 19:41 | 389 | -3 |
| 21 Aug 2026, 05:48 | 392 | +1 |
| 8 Aug 2026, 06:01 | 391 | no change |
| 7 Aug 2026, 12:56 | 391 | first reading |
18 posts held, back to 23 April 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 18 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
90 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 46.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5222148368955877900 | 42 | 46.7% | |
| custom 5222400230133081714 | 31 | 34.4% | |
| custom 5334665104677941170 | 17 | 18.9% |
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 13 of the 18 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 90 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 23 April 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.
Мне уже 22 годикааа, с Днём Рожденияяя меняяя ฅ^>⩊<^ฅ ּ ֶָ֢.๋࣭ ⭑⚝ И по традиции конечно же лучший подарок для художника репостики 🩵 ๋࣭ ⭑⚝
custom 53346651046779411705custom 52221483689558779002
Сегодня день рождения нашей рисовашки мяу мяу 🐈⬛ ☺️ сердечно поздравляем
custom 52221483689558779005
Альбом ждете ?
custom 52224002301330817148
ну шо ?
custom 52221483689558779003
правильно иду озвучивать хентай проно вместо работы
custom 52221483689558779007custom 53346651046779411703
угадайте чо наконец делаю
custom 52221483689558779005custom 53346651046779411703
тута релиз а артик делала Великолепная мяумяу
custom 52221483689558779002
там кстати релиз если шо уже вышел старой песенки
Заебала шота меня работа ниче не успеваю делать
Я тут вспомнила что не выкладывала вот эти порисульки из анимации :> ♡♡♡♡♡♡♡♡♡♡♡♡♡ https://t.me/rassvet_3_333
custom 52224002301330817146
слушать релиз 🤤 Ссылочка на меня 🙂 ссылочка на янки⭐
custom 52221483689558779007
Сегодня сикс севен А значит сегодня дроп 👍😎
custom 52221483689558779007
Showing the 12 most recent of 18 posts we hold for @michellopng. 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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“emVI / МИШЕЛЬ ВЕРМИШЕЛЬ” (@michellopng), 389 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/michellopng.
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.