Channel
@inf0miyu
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
13subscribers
+0 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002053776119 |
|---|---|
| Type | Channel |
| Username | @inf0miyu |
| Created | 14 January 2024 — measured — dated from the channel’s first post |
| First recorded | 26 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 4 times, most recently 18 September 2026 |
| On Telegram | t.me/inf0miyu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 20:44 | 13 | no change |
| 26 Aug 2026, 19:31 | 13 | first reading |
7 posts held, back to 14 January 2024 — 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 7 posts for this entry, the most recent from 10 April 2024. An engagement rate over an empty window would be a number about nothing.
718 reactions across 6 posts, in 27 distinct kinds. The most used accounts for 28.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5280895232278279792 | 204 | 28.4% | |
| custom 5192903593040035346 | 57 | 7.94% | |
| custom 5282792761714556519 | 51 | 7.10% | |
| custom 5262606930819426800 | 50 | 6.96% | |
| custom 5431725124980058062 | 40 | 5.57% | |
| custom 5269476821203693814 | 38 | 5.29% | |
| custom 5276173766139852084 | 36 | 5.01% | |
| custom 5431677631231699526 | 36 | 5.01% | |
| custom 5335005820138564214 | 26 | 3.62% | |
| custom 5265032182887362809 | 20 | 2.79% | |
| 💘 | 20 | 2.79% | |
| custom 5269263266839802989 | 19 | 2.65% | |
| ❤🔥 | 19 | 2.65% | |
| custom 5269582421564601567 | 17 | 2.37% | |
| custom 5386690150908575339 | 16 | 2.23% | |
| custom 5393539193521586235 | 15 | 2.09% | |
| custom 5343719226450385808 | 12 | 1.67% | |
| custom 5388946486207721989 | 9 | 1.25% | |
| custom 5256041592271157291 | 8 | 1.11% | |
| custom 5118357331742032622 | 4 | 0.557% | |
| 7 further kinds | 21 | 2.92% |
Custom emoji. 18 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 6 of the 7 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 718 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 14 January 2024 to 10 April 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://t.me/cut3miyu
custom 528279276171455651951custom 533500582013856421426custom 526503218288736280920custom 52560415922711572918custom 51183573317420326224custom 52152343606675495003custom 54562718766889860453custom 60620324878638150833
ркмдляблядей https://t.me/cut3miyu
custom 519290359304003534657custom 527617376613985208422custom 526958242156460156717custom 52808952322782797929custom 54317251249800580627custom 52332982329053107674custom 52626069308194268004custom 52692632668398029894
https://t.me/cut3miyu
custom 528089523227827979252custom 526947682120369381424💘20custom 53866901509085753395custom 53437192264503858084custom 54316776312316995263❤🔥2custom 52626069308194268002
Photo, posted without a caption
custom 528089523227827979243custom 526260693081942680023❤🔥17custom 52692632668398029898custom 52761737661398520844custom 53866901509085753394custom 53935391935215862354custom 52694768212036938143
https://t.me/cut3miyu
custom 528089523227827979246custom 543167763123169952622custom 543172512498005806213custom 52694768212036938145custom 53889464862077219895custom 52761737661398520844custom 52626069308194268003custom 52692632668398029893
Photo, posted without a caption
custom 528089523227827979254custom 526260693081942680018custom 543172512498005806217custom 52694768212036938146custom 53935391935215862356custom 52692632668398029894custom 52761737661398520844custom 53866901509085753394
Channel created
Showing the 7 most recent of 7 posts we hold for @inf0miyu. 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.
Named by 1 registered channel — 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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“.” (@inf0miyu), 13 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/inf0miyu.
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.