Telegram RegisterThe public register of Telegram
Telegram profile photo for MAZUKI || IZU

Channel

MAZUKI || IZU

@huyanmaaa

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

7,185subscribers

+7 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001759227215
TypeChannel
Username@huyanmaaa
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/huyanmaaa

Growth

7,1787,2197,198.57 August 2026 — 7,178 subscribers8 August 2026 — 7,190 subscribers11 August 2026 — 7,194 subscribers14 August 2026 — 7,210 subscribers18 August 2026 — 7,219 subscribers20 August 2026 — 7,210 subscribers24 August 2026 — 7,209 subscribers30 August 2026 — 7,202 subscribers3 September 2026 — 7,192 subscribers8 September 2026 — 7,185 subscribers7,1857 August 20268 September 2026
10 measurements spanning 32 days, net +7. 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 7,172–7,225 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 12:157,185-7
3 Sept 2026, 08:567,192-10
30 Aug 2026, 23:437,202-7
24 Aug 2026, 20:477,209-1
20 Aug 2026, 20:087,210-9
18 Aug 2026, 01:247,219+9
14 Aug 2026, 22:087,210+16
11 Aug 2026, 05:417,194+4
8 Aug 2026, 00:527,190+12
7 Aug 2026, 03:017,178first reading

Engagement

22 posts held, back to 29 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 13 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
25.4%
avg views ÷ 7,185 subscribers
Avg views / post
1,820
5 posts measured
Reaction rate
14.8%
reactions ÷ views · ER floor
Posts in window
5
of 22 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 19 August 2026
Posts held22 (29 July 202619 August 2026)
Views total9,120
Reactions total1,351
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 11:51 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

Video runtime
1m 44s
Average length
1m 44s

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

8,845 reactions across 22 posts, in 2 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52290773709750525824,74953.7%
custom 53684221904148392914,09646.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 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 22 of the 22 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 8,845 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 29 July 2026 to 19 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.

Telegram Stars

Stars received
657
across the posts below
Posts paid on
16
of 22 we hold a reading for · 73%
Most on one post
218
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @huyanmaaa. 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 22 most recent posts we hold for this entry, published 29 July 2026 to 19 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.

Recent posts

19 Aug 2026, 21:13 UTC≈1,020 views79 reactionsread 20 August 2026

АВАВВОАОА

custom 536842219041483929155custom 522907737097505258224

19 Aug 2026, 21:13 UTC≈1,020 views183 reactionsread 20 August 2026
Forwarded from @ROSIII_lolPhoto

💤чай пить будем @huyanmaaa👼

custom 5229077370975052582131custom 536842219041483929152

19 Aug 2026, 19:31 UTC≈1,210 views106 reactionsread 20 August 2026
Forwarded from @EzellixVideo

У САМОЙ КРАСИВОЙ ЛЕДИ НАСТУПИЛО ДЕНЬ РОЖДЕНИЕ! •https://t.me/nedelkaart - Ака человек с золотыми ручками, человек с невероятными глазами наполненными добротой и шутливым озорным взором. Ты художник с большой буквы, ты творец, ты та кого можно хвалить за каждую работу. • Я поздравляю тебя ещё и с пре-релизом анимации по Дотторе и Панталоне! •А сейчас мои овации лишь тебе. Мы долго думали что можно преподнести, люту

custom 522907737097505258276custom 536842219041483929130

12 Aug 2026, 19:19 UTC≈2,670 views438 reactions106 Starsread 20 August 2026

Posted without readable text

custom 5229077370975052582328custom 5368422190414839291110

12 Aug 2026, 10:07 UTC≈3,200 views545 reactions5 Starsread 20 August 2026
Photo

🤩 Заказец с Майки/Раном. для Имы /маф воскрес/ #commission #Mikey #Ran

custom 5229077370975052582401custom 5368422190414839291144

10 Aug 2026, 19:16 UTC≈2,890 views467 reactionsread 20 August 2026
Photo

Тык Микро чибик моего друна 🤍 Сегодня выживаю, бошка болит капец #sketch

custom 5229077370975052582348custom 5368422190414839291119

6 Aug 2026, 20:12 UTC≈4,200 views585 reactions73 Starsread 20 August 2026
Photo

Вроде начиналось хорошо а закончилось......не закончилось, в конце тильт словился так что оставлю таким грязным 👻 #Hanma #Kazutora #sketch

custom 5229077370975052582433custom 5368422190414839291152

5 Aug 2026, 20:12 UTC≈3,930 views500 reactions109 Starsread 20 August 2026

Posted without readable text

custom 5368422190414839291336custom 5229077370975052582164

5 Aug 2026, 17:54 UTC≈3,760 views426 reactions1 Starread 20 August 2026
Photo

🤍 Заказец для драгоценной роднульки Виктории ❤️ #commission

custom 5229077370975052582317custom 5368422190414839291109

5 Aug 2026, 11:32 UTC≈3,040 views278 reactions8 Starsread 20 August 2026

Спасибо за звёзды 🥴 Ладно возвращаюсь к заказам, а то чета заигралась 👻

custom 5368422190414839291195custom 522907737097505258283

5 Aug 2026, 11:03 UTC≈3,300 views639 reactions66 Starsread 20 August 2026
Photo

Ваши предположения что произойдет через секунду после этого кадра

custom 5368422190414839291452custom 5229077370975052582187

5 Aug 2026, 10:23 UTC≈3,040 views515 reactions57 Starsread 20 August 2026
Photo

Так называемый интернет герой

custom 5368422190414839291354custom 5229077370975052582161

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

Forward network

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.

Mentions

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

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

“MAZUKI || IZU” (@huyanmaaa), 7,185 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/huyanmaaa.

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.