Полноценный пост с ним будет сегодня вечером или завтра!

Channel
Mizumi-san.cos
@Mizumi_chan_cos
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
162subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002137281792 |
|---|---|
| Type | Channel |
| Username | @Mizumi_chan_cos |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 13 September 2026 |
| On Telegram | t.me/Mizumi_chan_cos |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 01:20 | 162 | +1 |
| 28 Aug 2026, 17:34 | 161 | +3 |
| 15 Aug 2026, 20:47 | 158 | -1 |
| 8 Aug 2026, 17:31 | 159 | no change |
| 7 Aug 2026, 06:02 | 159 | first reading |
Engagement
18 posts held, back to 14 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 18 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 18s
- Average length
- 18s
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.
Reaction mix
131 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 25.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 33 | 25.2% | |
| ❤ | 27 | 20.6% | |
| ❤🔥 | 26 | 19.8% | |
| custom 5877631043422391684 | 12 | 9.16% | |
| custom 5809644086243627995 | 11 | 8.40% | |
| 💘 | 11 | 8.40% | |
| custom 5262842015854386303 | 9 | 6.87% | |
| 🙏 | 1 | 0.763% | |
| 🥰 | 1 | 0.763% |
Custom emoji. 3 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 15 of the 18 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 131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 14 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.
Recent posts
💙 🤩нтерактив 💙 💙💙💙💙💙💙💙💙 Суть интерактива: сделать коллаж под косплей персонажа, который вы делали последним. затем передать другому 💙💙💙💙💙💙💙💙 Приняла эстафету от Коффи Передаю: Ярск, Немцу и всем желающим! #косплей #пвл #Лондон
❤3custom 58776310434223916842🔥1
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷 А вот и то, что вчера было сказано. Говорила же, что будет бомба? И вот она прекрасная) Совсем скоро вас будет 🤩🤩🤩🤩🤩 И в честь этого мы с прекрасной дамой договорились на прекрасный приз ручной работы. 🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷🍷 🤩🤩🤩🤩 Самим призом будет любая куколка ручной работы на выбор победителя. Я уверенна, что каждый из вас мечтает поселить на своих полочках мини версию любимого персонажа и мы д…
Video message, posted without a caption
❤4🔥3🥰1🙏1
Кто-то ждал ино?)
🔥2
Video message, posted without a caption
❤1
Сегодня снова в москвабургах, но на Акамару 🤩🤩
🔥8
Video message, posted without a caption
🔥6❤4custom 58776310434223916843custom 52628420158543863032
Поздний #анонс Сегодня пригонем с Ярск на Кицу в москвабургах 🤩🤩 Будем где-то к 12:30 С кем увидимся?)
🔥7
Решила попробовать новую функцию статья Она пока прям сырая, лагает и тяжеловато с ней работать лично мне, но выглядит прикольно) А вам как?
❤5
Posted without readable text
❤🔥11custom 58096440862436279956custom 58776310434223916845🔥2
🦄🌺🌺🌺🌺🌺🌺🌺🌺🦄 3⃣ билета на 💩💩💩💩💩💩💩 + крутые бьюти-подарки ❤️Тык❤️ 〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️ 🦄 Привет, Лучики! Наконец-то тот самый момент: я официально еду на Акамару Фест как приглашённый блогер! 🟣ВСТРЕЧАЕМСЯ🟣 уже 26 июля в КЦ ЗИЛ, чтобы вместе как следует повеселиться! ❤️ И раз уж мы собираемся такой большой компанией, я решила устроить для вас главный движ этого лета! Прямо сейчас разыгрываю 3 билета на фестиваль и п…
Showing the 12 most recent of 18 posts we hold for @Mizumi_chan_cos. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Будет ли вам интересно следить за моим щитпостом если создам?
- Мне будет интересно следить за щп каналом86%
- Не люблю отдельные щп каналы, скорее всего не подпишусь5%
- Не люблю щп впринципе (и в основе и отдельные каналы)5%
- Лучше пусть будет больше щп в основе чем отдельный канал38%
The shares total 134%, 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 18 most recent posts we hold, published 14 July 2026 to 8 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.
Forward network
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 3 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Mizumi-san.cos” (@Mizumi_chan_cos), 162 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/Mizumi_chan_cos.
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.