🐾Коллаб с Чёрным Пушистиком 🐾 С днём мёртвых! 🌺 #ос [ @Mizukihth // Mizuki ]
custom 524926350681284082210❤3☃1custom 53753270718976589461

Channel
@Mizukihth
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
80subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001891527328 |
|---|---|
| Type | Channel |
| Username | @Mizukihth |
| Description | Качество > количество Рекомендую закрепы к прочтению для ознакомления По любым вопросам, не стесняйтесь, в лс: @Laguha69 27.06.2023 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Mizukihth |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 17:30 | 80 | no change |
| 10 Aug 2026, 17:17 | 80 | first reading |
12 posts held, back to 22 January 2025 — 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 pageof 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 12 posts for this entry, the most recent from 2 November 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
186 reactions across 12 posts, in 21 distinct kinds. The most used accounts for 17.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 32 | 17.2% | |
| ❤🔥 | 30 | 16.1% | |
| custom 5249263506812840822 | 20 | 10.8% | |
| custom 5426941734003164839 | 20 | 10.8% | |
| custom 5382336428459964351 | 18 | 9.68% | |
| custom 5233670739713861453 | 17 | 9.14% | |
| 💘 | 16 | 8.60% | |
| custom 5222108309795908493 | 6 | 3.23% | |
| custom 5228737046356445964 | 5 | 2.69% | |
| custom 5375327071897658946 | 4 | 2.15% | |
| custom 5222472119295684375 | 3 | 1.61% | |
| custom 5377674988784459513 | 2 | 1.08% | |
| 🍓 | 2 | 1.08% | |
| 👍 | 2 | 1.08% | |
| 😱 | 2 | 1.08% | |
| 🙈 | 2 | 1.08% | |
| ☃ | 1 | 0.538% | |
| 🎉 | 1 | 0.538% | |
| 💊 | 1 | 0.538% | |
| 💋 | 1 | 0.538% | |
| 1 further kind | 1 | 0.538% |
Custom emoji. 9 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 12 of the 12 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 186reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 22 January 2025 to 2 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Mizukihth. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 12 most recent posts we hold for this entry, published 22 January 2025 to 2 November 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🐾Коллаб с Чёрным Пушистиком 🐾 С днём мёртвых! 🌺 #ос [ @Mizukihth // Mizuki ]
custom 524926350681284082210❤3☃1custom 53753270718976589461
Давненько я сюда скетчи не выкладывала 🤍 #скетч #ос #геншин #хср [ @Mizukihth // Mizuki ]
❤10custom 52492635068128408222💋1😭1custom 53753270718976589461
🌟 🌟 🌟 🌟 🤍 «Добрый вечер! Я Зарянка, певица из Семьи. Оставим формальности, пусть это будет простая закулисная беседа. Уделишь мне минутку?». 🤍 🌟 🌟 🌟 🌟 #хср [ @Mizukihth // Mizuki ]
💘11🍓2❤1💊1custom 52221083097959084931custom 52224721192956843751custom 52492635068128408221custom 53753270718976589461
📎☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️📎 Парочка старых артиков, которые были нарисованы ещё в первом полугодии 📎☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️📎 #геншин #хср [ @Mizukihth // Mizuki ]
custom 52492635068128408227❤5custom 54269417340031648394custom 52221083097959084932custom 52224721192956843751custom 53753270718976589461custom 53776749887844595131
⚡️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️⚡️ «Элио сказал, что я хороша в создании страха, хотя мне он не ведом.» ⚡️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️⚡️ #хср [ @Mizukihth // Mizuki ]
custom 542694173400316483910custom 52336707397138614534custom 52221083097959084932
📎☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️📎 🦋Сплеш-арт моей оски 🦋 Результаты коллаба 📎☁️☁️☁️☁️☁️☁️☁️☁️☁️☁️📎 #ос [ @Mizukihth // Mizuki ]
❤🔥4custom 52336707397138614533❤2custom 54269417340031648391
С днём рождения, дорогой мой Сивик! 💗 📎Отдельное спасибо авторам замечательных артов к празднику 📎 1. Мизуки 2/3. Чёрный Пушистик 4. Тазик 5. Пандора Сладкие поздравления на 3 арте от: CTACnino Пандора Фуки Чёрный Пушистик Мизуки ⬇️Не забываем подписываться на дорогого именинника ➡️
custom 52336707397138614539❤🔥3custom 54269417340031648391
Well...
😱2
Posted without readable text
❤5custom 54269417340031648393custom 52224721192956843751
❤️С 8 марта, любимые дамы!! 💖 #лололош
custom 538233642845996435116❤🔥5💘2❤1custom 52221083097959084931custom 52287370463564459641custom 52336707397138614531custom 54269417340031648391
꧁ᬊᬁ Ангелочку ᬊ᭄꧂ С днём рождения Мизуки!! ☆Желаю тебе крепкого здоровья и побольше нервов:) ☆ А так же успех в рисовании, что бы рисование было не в тягость, а в радость.
❤🔥6❤3custom 52287370463564459643🎉1👍1💘1🙈1custom 53823364284599643511
Сегодня 22 января, а это значит, что у меня сегодня 🌟🌟🌟🌟 🌟🌟🌟🌟🌟🌟🌟🌟 Лучший подарок художнику - это репост его работ, поэтому буду рада активчику 🤗 #арт
❤🔥12❤2💘2👍1🙈1custom 52287370463564459641custom 53823364284599643511
Showing the 12 most recent of 12 posts we hold for @Mizukihth. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 887,862 of 1,345,403entries 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.
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 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.
@Mizukihth named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Mizuki” (@Mizukihth), 80 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Mizukihth.
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.