Telegram RegisterThe public register of Telegram
Telegram profile photo for ℳ𝒾𝓏𝓊𝒸𝓀𝒽𝒶

Channel

ℳ𝒾𝓏𝓊𝒸𝓀𝒽𝒶

@Mizuckha_cos

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

619subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002305342725
TypeChannel
Username@Mizuckha_cos
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/Mizuckha_cos

Growth

6198 Aug 2026, 21:31 — 619 subscribers9 Aug 2026, 01:12 — 619 subscribers8 Aug 2026, 21:319 Aug 2026, 01:12
2 measurements taken within a single day. 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 618–620 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 01:12619no change
8 Aug 2026, 21:31619first reading

Engagement

12 posts held, back to 24 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
222.9%
avg views ÷ 619 subscribers
Avg views / post
1,380
12 posts measured
Reaction rate
6.34%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 8 August 2026
Posts held12 (24 July 20268 August 2026)
Views total16,560
Reactions total1,050
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 21: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.

Reaction mix

1,050 reactions across 12 posts, in 38 distinct kinds. The most used accounts for 8.95% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5431421526626821478948.95%
custom 5298688259583414703888.38%
custom 5469648758490823816736.95%
custom 5343828383044238280686.48%
custom 5215591676176777536595.62%
custom 5201827766281987735565.33%
custom 5213422326850278273545.14%
custom 5215551037196222502504.76%
custom 5199663850089116603424.00%
custom 5190590869115268569373.52%
custom 5343941804540595045373.52%
custom 5409044987532836488333.14%
custom 5343692434444417425312.95%
custom 5190842854846522475302.86%
custom 5424633614283334304292.76%
custom 5291961348660420691282.67%
custom 5312232864153110099272.57%
custom 5420168102425956605272.57%
custom 5309935636470323386252.38%
custom 5199799416436852168222.10%
18 further kinds14013.3%

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 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 1,050reactions 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 24 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

8 Aug 2026, 15:48 UTC130 views45 reactionsread 8 August 2026

Хочу провести стримочек в тт, во вт вечерком если мне прийдёт новы штатив🥛 Наверн буду в закосе на Чоколу👋 Чо думаете?

custom 530993563647032338625custom 542039160822905751810custom 54203244821851868099custom 54206335136720689731

7 Aug 2026, 09:56 UTC210 views74 reactionsread 8 August 2026
Photo

А вот и бэки с фотосика в Клумбе, фоткаться летом отдельный ад конечно, очень жарко даже с кондеем, ещё и костюм весь разваливался, но мы с девчулями выжили🤩 ➿➿➿➿➿➿➿➿➿➿ Пара оч красивых фотографий в Колумбине уже ждёт вас на бусти 🤩🤩🤩🤩 https://boosty.to/mizuckhacos Буду благодарна за покупку 😌

custom 529868825958341470336custom 519979941643685216819custom 519966385008911660317custom 52962399349511663542

3 Aug 2026, 18:09 UTC451 views110 reactionsread 8 August 2026
Photo

💜Примерочка Колумбины🤩 Нежнятинка просто, очень жду фотос У меня какие то проблемки с левым глазом, я им вижу плохо надеюсь все хорошо будет к среде и я смогу линзы надеть 😢 #costest

custom 529868825958341470352custom 531223286415311009927custom 519966385008911660325custom 51997994164368521683custom 52962399349511663543

2 Aug 2026, 10:22 UTC471 views74 reactionsread 8 August 2026
Photo

Предзаказ сигн в Колумбине🤩🤩🤩 на студии 🤩🤩🤩 150р/150⭐/180 бусти лс @Mizuckha2 Покупкой поможете покрыть аренду студии🎀👋 2200701316923744 https://boosty.to/mizuckhacos До 5 авг 8:00

custom 521342232685027827336custom 520397658566481609418custom 520182776628198773517custom 52040257630403547262custom 52041652206284578521

31 Jul 2026, 14:57 UTC544 views73 reactionsread 8 August 2026
Photo

Опять с плюш п-чанчиком🍥 Кстате скоро ждите коспле на хумку п-чана в джирае, чота типа такого, вчера как раз ходила на репу для выступления в нём, и потом ещё Амэ переснять хотелос бы👽🎀 #jf

custom 520182776628198773539custom 521342232685027827318custom 520416522062845785215custom 52039765856648160941

30 Jul 2026, 11:37 UTC532 views42 reactionsread 8 August 2026

Posted without readable text

custom 521555103719622250223custom 521092784420449313211custom 54069925558060638935custom 54070052345495259672custom 54090449875328364881

29 Jul 2026, 14:42 UTC557 views123 reactionsread 8 August 2026
Photo

Выложила фотки в Кангел на Бусти, некоторые кадры эксклюзив только там будут 😀😀😀😀😀😀 https://boosty.to/mizuckhacos Буду очень благодарна за покупку так как заново коплю на Чоколу😭 #kangel #nso

custom 521559167617677753659custom 540904498753283648832custom 521555103719622250227custom 52109278442044931323custom 54069925558060638932

28 Jul 2026, 01:11 UTC710 views136 reactionsread 8 August 2026
Photo

28 июля 4:11 - Юки сказал что любит меня, от счастья я не могла прицелиться..🥛 ➿➿➿➿➿➿➿➿➿➿ Ждала всего лишь 3 года, чтобы сделать пост в Юно в 4:11 Один из немногих моих старых косплей фотосов, который я прям обожаю, надеюсь ещё помните мою Юно, побольше фоточек можно глянуть за сентябрь на канале🎀 Хочу попозже сделать ремейк этого образа #YunoGasai #FutureDairy

custom 543142152662682147859custom 519059086911526856937custom 519084285484652247530custom 51908699603851269836custom 51908198681815579632custom 51927981816576997582

27 Jul 2026, 22:58 UTC608 views52 reactionsread 8 August 2026

Я как то удалила обсуждалку канала и пропали все комы..🐰

custom 542016810242595660525custom 546964875849082381614custom 543173521815322222913

26 Jul 2026, 11:59 UTC≈11,100 views129 reactionsread 8 August 2026
Photo

🌟🌟🌟🌟🍥🍥 🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟 ➿➿➿➿➿➿➿➿➿➿ ℐ 𝒹ℴ𝓃’𝓉 𝒷ℯ𝓁𝒾ℯ𝓋ℯ, 𝓎ℴ𝓊'𝓇ℯ 𝒶 𝓁𝒾𝒶𝓇 나의 어둠과 너의 어둠이 겹쳐질때 그대로 내게 맡겨🎀 ➿➿➿➿➿➿➿➿➿➿ Ph⬅️🍬 #Mizi #alnst

custom 546964875849082381659custom 543142152662682147835custom 529196134866042069128custom 54182583752825623013custom 54201681024259566052custom 54204668689410006122

25 Jul 2026, 20:52 UTC642 views56 reactionsread 8 August 2026
Forwarded from @stellarAdiPhoto

🤩🎀🤩🎀🎀𝑲𝒂𝒏𝒈𝒆𝒍🎀🎀🤩🎀🤩 🎀🎀🎀🎀🌟🤩🤩🤩🤩🎀😆 «𝓣𝓮𝓷 𝓸𝓾𝓽 𝓸𝓯 𝓽𝓮𝓷!!!!!!!!!» Арт с косплея прекрасной Мизучки🎀 #гифт #дидж

custom 542463361428333430429custom 547416320291061233215custom 529406110233686376512

24 Jul 2026, 09:20 UTC605 views136 reactionsread 8 August 2026
Photo

🫎ℒ𝒶𝓊𝓂𝒶🫎🫎🫎🫎🫎 🫎 ➿➿➿➿➿➿➿➿➿ Немного домашних фоток в закосе на Лауму, надеюсь в будущем сделаю фулл и уложу парик нормально, а то мне лень была #Lauma #GenshinImpact

custom 534382838304423828068custom 534394180454059504537custom 534369243444441742531

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

Citation-graph rank

Citation-graph rank — 143,290 of 1,481,217entries 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 5 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.

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.

“ℳ𝒾𝓏𝓊𝒸𝓀𝒽𝒶” (@Mizuckha_cos), 619 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Mizuckha_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.