Channel
@Mizi_zomst
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Cite this entry
192subscribers
+43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003968465620 |
|---|---|
| Type | Channel |
| Username | @Mizi_zomst |
| Created | Between 1 April 2026 and 19 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Mizi_zomst |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 34% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 12:56 | 192 | +18 |
| 9 Sept 2026, 05:56 | 174 | -2 |
| 31 Aug 2026, 00:48 | 176 | +6 |
| 23 Aug 2026, 05:19 | 170 | +10 |
| 15 Aug 2026, 20:54 | 160 | +11 |
| 8 Aug 2026, 20:15 | 149 | no change |
| 7 Aug 2026, 19:40 | 149 | first reading |
20 posts held, back to 19 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
280 reactions across 13 posts, in 11 distinct kinds. The most used accounts for 25.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6309731785924155497 | 72 | 25.7% | |
| custom 6312011971176698457 | 59 | 21.1% | |
| custom 5327815641158161208 | 34 | 12.1% | |
| custom 5332462185887081751 | 33 | 11.8% | |
| custom 6186245519044515265 | 30 | 10.7% | |
| custom 5332401566718665406 | 12 | 4.29% | |
| custom 5332780567517763074 | 12 | 4.29% | |
| custom 5373173519460903769 | 12 | 4.29% | |
| custom 5330157411946765905 | 9 | 3.21% | |
| custom 5372849726171421525 | 4 | 1.43% | |
| custom 5332473997047145951 | 3 | 1.07% |
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 13 of the 20 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 280 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 19 July 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Mizi_zomst. 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 20 most recent posts we hold for this entry, published 19 July 2026 to 7 August 2026. 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.
#сапп: В последнее время я не особо уверена в своих постах, поэтому приму любую критику и советы. (коммы/анонка) 🥹 И кстати, обои снова ушли в далекие края...
custom 63097317859241554979custom 53278156411581612084custom 63120119711766984571
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🌟🌟 — 🔤ир на вееесь мир! 🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🐏🤩отела бы я выбрать то же, что и вы, но, увы, решение здесь не в моей власти - и, пожалуй, даже не в вашей. ~ 🤩го руки скользят по моим, переплетаются с ними, и каждое движение - это обещание забраться ещё дальше. Но я понимаю: если он возьмёт меня целиком - я перестану быть желанной добычей. Исчезнет та самая недоступность, что держит его на крючке.🎶 🤩незапно - …
custom 630973178592415549710custom 53731735194609037695custom 53324739970471459513custom 53301574119467659051custom 61862455190445152651custom 63120119711766984571
Sticker, posted without a caption
#сапп: ОМГ, огромное спасибо!!! 🌟 Каждому бустеру передаю по воздушному поцелуйчику! ❤️
custom 532781564115816120811custom 61862455190445152651
#сапп: Благодарю за буст! 🩷 Теперь на шаг ближе к обоям, хаха, остался еще один.
custom 53278156411581612087
#сапп: Обои тю-тю. Поможете вернуть? 😭
custom 63097317859241554978custom 53731735194609037693
Sticker, posted without a caption
#сапп: 143 подписчика! А вы знаете, что значит это число? Оно значит «я люблю тебя». Мило!! 🌟🌟
custom 631201197117669845717custom 53278156411581612087custom 61862455190445152654
Sticker, posted without a caption
🎀х, дорогие читатели! Кажется, время, - стать вершителем аморальных судеб! 💕
The shares total 133%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🌟🌟 — Снова и снова...Это так противно! 🎀 🤩 моей сумке всего три вещи: • Зеркальце, чтобы поправить макияж. • Тушь. Важная штучка для каждой девушки, вы ведь понимаете меня? • Игла. Сотрудники цирка запрещают носить с собой такие опасные вещички, но мы никому не скажем, правда? 🤩отя нет… Было ещё что-то. Где же я могла её потерять? 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ...🤩 гримёрку ворвался неизвестный мне человек. В его руках тихо трещ…
custom 618624551904451526520custom 53301574119467659058custom 53278156411581612085custom 63097317859241554975custom 53731735194609037694
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @Mizi_zomst. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
🎀х, дорогие читатели! Кажется, время, - стать вершителем аморальных судеб! 💕
The shares total 133%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
𝘠𝘰𝘶𝘳 𝘧𝘢𝘷𝘰𝘳𝘪𝘵𝘦?? 🌟🌟
The shares total 156%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 19 July 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 11 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“𖥔 𝘮𝘪𝘻𝘪 .” (@Mizi_zomst), 192 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Mizi_zomst.
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.