#Miaou_spoilers
custom 605061713480594910110custom 60509032053976659342

Channel
@MiaMiaouMiaou
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
114subscribers
+7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002807386967 |
|---|---|
| Type | Channel |
| Username | @MiaMiaouMiaou |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/MiaMiaouMiaou |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 17:56 | 114 | +5 |
| 8 Sept 2026, 12:41 | 109 | +2 |
| 30 Aug 2026, 16:55 | 107 | -1 |
| 15 Aug 2026, 06:55 | 108 | +1 |
| 9 Aug 2026, 08:16 | 107 | no change |
| 6 Aug 2026, 12:05 | 107 | first reading |
8 posts held, back to 2 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 8 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 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.
164 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 38.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5188263550891606249 | 63 | 38.4% | |
| custom 5789680086114373014 | 34 | 20.7% | |
| custom 5789910498224902138 | 18 | 11.0% | |
| custom 6050617134805949101 | 15 | 9.15% | |
| custom 5787484361393705665 | 13 | 7.93% | |
| custom 5787289185194872666 | 10 | 6.10% | |
| custom 6050903205397665934 | 9 | 5.49% | |
| custom 5787501369464197401 | 2 | 1.22% |
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 8 of the 8 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 164 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 2 July 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.
#Miaou_spoilers
custom 605061713480594910110custom 60509032053976659342
Карточка игрока для Ивента ❤️ Доюн капитан команды! Он очень стильный и хитрый мальчик. 🪷 #Miaou_event
custom 51882635508916062497custom 60509032053976659347custom 60506171348059491014
🏐━━━━━━━━━━━━━━🏐 🔤🔤🔤ИТОГИ ИВЕНТА 🔤🔤• NIGHT WOLVES • Вот и подошёл к концу мой первый волейбольный арт-ивент Night Wolves! 🐺🏐 Хочу искренне поблагодарить каждого участника за то, что доверились моей идее и стали частью этого проекта. Для меня это был новый опыт как для организатора, и я очень рада, что вместе нам удалось воплотить его в жизнь. Каждая карточка получилась уникальной и отлично передала характер своего…
custom 51882635508916062493custom 60506171348059491011
#Miaou_spoilers
custom 578968008611437301411
Скажите что я молодец, я магистр!❤️ #Miaou_diplom_2026
custom 518826355089160624918custom 578968008611437301413custom 57899104982249021387
😮 #PortfolioDay
custom 518826355089160624917custom 57874843613937056658
Скетчики 💩 Пупсик любит готовить🍿 #Miaou_character_design
custom 578991049822490213811custom 578728918519487266610custom 51882635508916062493
🐈 #Miaou_character_design
custom 518826355089160624915custom 578968008611437301410custom 57874843613937056655custom 57875013694641974012
Showing the 8 most recent of 8 posts we hold for @MiaMiaouMiaou. 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 6 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“MIAOU” (@MiaMiaouMiaou), 114 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/MiaMiaouMiaou.
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.