Telegram RegisterThe public register of Telegram

Channel

🌼 miu-ki 🌼

@miiuiuiim

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

109subscribers

-1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002234715051
TypeChannel
Username@miiuiuiim
Descriptionрисовака и чертила
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
On Telegramt.me/miiuiuiim

Growth

109110109.56 August 2026 — 110 subscribers7 August 2026 — 109 subscribers9 August 2026 — 109 subscribers6 August 20269 August 2026
3 measurements spanning 2 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 109–110 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 07:31109no change
7 Aug 2026, 01:52109-1
6 Aug 2026, 22:18110first reading

Engagement

15 posts held, back to 1 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
124.8%
avg views ÷ 109 subscribers
Avg views / post
136
11 posts measured
Reaction rate
14.4%
reactions ÷ views · ER floor
Posts in window
11
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held15 (1 July 20264 August 2026)
Views total1,496
Reactions total216
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 07:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
207
Videos
4
Links
5

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

311 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 56.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 546325805760776072717756.9%
💋289.00%
custom 5381982145197654105227.07%
custom 5429169829892359159227.07%
custom 5424970262409924967216.75%
custom 5265184826025067103175.47%
💯82.57%
custom 526478010266683117772.25%
🎉51.61%
custom 538219750774277791441.29%

Custom emoji. 7 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 areTelegram’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 15 of the 15 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 311reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 1 July 2026 to 4 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.

Recent posts

4 Aug 2026, 02:44 UTC53 views6 reactionsread 9 August 2026

смаритееее 🌟

custom 54632580576077607275custom 53821975077427779141

4 Aug 2026, 02:44 UTC42 views16 reactionsread 9 August 2026
Forwarded from @tihvinnedostupenPhoto

Подарочек для дорогой https://t.me/miiuiuiim

custom 54632580576077607278custom 52647801026668311774custom 52651848260250671033custom 54249702624099249671

25 Jul 2026, 18:39 UTC91 views25 reactionsread 9 August 2026
Photo

извините, забыла как одежду рисовать🤩

💋13custom 53819821451976541055custom 54291698298923591594custom 54632580576077607272custom 54249702624099249671

24 Jul 2026, 20:04 UTC335 views16 reactionsread 9 August 2026
Photo

разрядим обстановку скетчегифтиком, он давно напрашивался, но руки дошли только сейчас 👅 https://t.me/tihvinnedostupen 🌟🩸

custom 546325805760776072711custom 54291698298923591595

24 Jul 2026, 17:23 UTC82 views20 reactionsread 9 August 2026
Photo

🛡🛡🛡🛡🛡🛡🛡🛡🛡 щащащаща я отдохну и продолжу

custom 546325805760776072713custom 52651848260250671034custom 52647801026668311773

24 Jul 2026, 16:02 UTC71 views15 reactionsread 9 August 2026
Photo

я уж не знаю правда ли это или очередной разводняк от тамблерских но как будто не прикольно 😐

custom 546325805760776072715

23 Jul 2026, 16:25 UTC72 views21 reactionsread 9 August 2026
Photo

не теряйте🌟

custom 546325805760776072713💋8

21 Jul 2026, 06:41 UTC92 views20 reactionsread 9 August 2026
Photo

это кстати моя новая малышка, выкупила её недавно 🥰 когда нибудь я дорисую все реквесты и нафигачу чибиков своим персонажам👅

custom 546325805760776072713custom 54249702624099249677

20 Jul 2026, 17:57 UTC94 views26 reactionsread 9 August 2026
Photo

угадайте что 🥳 🌟🌟🌟 🌟🌟🌟🌟 🌟🌟🌟🌟

custom 546325805760776072712custom 53819821451976541058🎉5custom 54249702624099249671

17 Jul 2026, 17:49 UTC414 views26 reactionsread 9 August 2026
Photo

я влюбилась в темненького, хорошенький такой 😹 все пуси сюси ням ням

custom 546325805760776072716custom 526518482602506710310

15 Jul 2026, 17:44 UTC150 views25 reactionsread 9 August 2026
Photo

хпхаха боже, пока я дорисую всех уже все забудут 🤩

custom 546325805760776072716custom 54291698298923591596custom 53821975077427779143

11 Jul 2026, 21:56 UTC159 views17 reactionsread 9 August 2026
Photo

соточка 😁 спасибо ребятке 😭 также напоминаю, что реквестики открыты под вон тем постом😘 рисую всех в порядке очереди, скидываю файлики в лс и выкладываю сюды

custom 546325805760776072716custom 54291698298923591591

Showing the 12 most recent of 15 posts we hold for @miiuiuiim. 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.

Citation-graph rank

Citation-graph rank — 20,396 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 2 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.

Cite this entry

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“🌼 miu-ki 🌼” (@miiuiuiim), 109 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/miiuiuiim.

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.