Channel
@mirryry
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
82subscribers
+16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003668640204 |
|---|---|
| Type | Channel |
| Username | @mirryry |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 27 September 2026 |
| On Telegram | t.me/mirryry |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 02:57 | 82 | +6 |
| 6 Sept 2026, 23:41 | 76 | +4 |
| 29 Aug 2026, 03:13 | 72 | -1 |
| 22 Aug 2026, 21:17 | 73 | +3 |
| 15 Aug 2026, 17:23 | 70 | +4 |
| 10 Aug 2026, 01:46 | 66 | no change |
| 7 Aug 2026, 06:02 | 66 | first reading |
16 posts held, back to 30 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 16 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
62 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 35.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5246719279855837046 | 22 | 35.5% | |
| custom 5201767632444877520 | 16 | 25.8% | |
| ❤ | 12 | 19.4% | |
| custom 5404606688588214852 | 8 | 12.9% | |
| custom 5330183473808303971 | 2 | 3.23% | |
| 💅 | 2 | 3.23% |
Custom emoji. 4 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 10 of the 16 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 62 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 30 July 2026 to 9 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.
Вчера мы отметили день рождения своей компанией, это было очень круто и очень весело! Вкусная еда, приятная компания, и ОЧЕНЬ ВКУСНЫЙ ТОРТИК С МАКСИКОМ Спасибо огромное что разделили этот день со мной! А я напомню что 11 я уеду, и вы скоро узнаете куда
custom 52467192798558370462custom 52017676324448775201
Signed 𝐑𝐮𝐫𝐮
мы с руру тут совместный щитпост по приколу создали, так что заходите: https://t.me/+qs2O0n9cWQVkNTZi
Signed 𝐑𝐮𝐫𝐮
Дискриминация какая-то
Signed 𝐑𝐮𝐫𝐮
вы понимаете, что робуксы не дают за паркур????
Signed 𝐑𝐮𝐫𝐮
Напоминаю про мои другие соц. Сети, Интстаграмм тоже~
Signed 𝐑𝐮𝐫𝐮
11 я снова отправлюсь кое куда😎
❤1
Signed 𝐑𝐮𝐫𝐮
Мы с Гео
❤1custom 52467192798558370461
Signed 𝐑𝐮𝐫𝐮
ААААААА
💅2custom 52467192798558370462custom 52017676324448775201
Signed 𝐑𝐮𝐫𝐮
👽🧦™️🦄🛼🥑🐈™️🪀🍷 Представь, что мы делаем с тобой парный косплей. Кого будем делать и почему? 👁 Или кем ты меня видишь в пару к уже своему сделанному образу? 😇
Signed 𝐑𝐮𝐫𝐮
Я теперь амбассадор резиновых слёпок
Signed 𝐑𝐮𝐫𝐮
Сколько приятных поздравлений я получаю! Мне очень очень приятно!
❤1
Signed 𝐑𝐮𝐫𝐮
🥰 😆🙃😅🙂 😍😉😂😆🥹🙃🥲🤩☺️ дорогая Руру! сегодня день рождения у человека, который очень помог мне влиться в косплейкм по настоящему и улучшить качество моих образов. я искренне благодарен, что судьба свела нас, потому что Руру — очень хороший друг, который всегда будет рядом не смотря ни на что. спасибо тебе за все: за советы, за помощь, за те счастливые моменты, проведенные вместе. за то, что ты буквально готова еха…
❤1
Signed 𝐑𝐮𝐫𝐮
Showing the 12 most recent of 16 posts we hold for @mirryry. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Лужайка Руру🍃” (@mirryry), 82 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/mirryry.
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.