Channel
@nowz_siyun
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
69subscribers
-1 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002407445639 |
|---|---|
| Type | Channel |
| Username | @nowz_siyun |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/nowz_siyun |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 05:15 | 69 | -1 |
| 29 Aug 2026, 02:15 | 70 | no change |
| 29 Aug 2026, 02:01 | 70 | first reading |
13 posts held, back to 24 August 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.
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. It is computed over the 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 13 (24 August 2026 – 28 August 2026) |
| Views total | 296 |
| Reactions total | 56 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 02:15 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.
Measured directly from 3 videos 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.
56 reactions across 12 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5406873434888093272 | 28 | 50.0% | |
| custom 5452109615292515455 | 28 | 50.0% |
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 12 of the 13 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 24 August 2026 to 28 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.
⋆. 𐙚˚࿔ 蜂蜜 why not, i don’t know 𝜗𝜚˚⋆ жизнь порой полна крахов, разочарований и мучений. несмотря на это, мы продолжаем, иногда закапывая себя глубже под земле, а иногда в надежде выискиваем причины не останавливаться. 🌟 наша мега представляет вам каналы, которые помогут скрасить серые будни ; 🌟 primrose 🌟 yuhz | sechan (yuhz) 🌟 doi ( h//pe princess ) 🌟 rino ( h//pe princess ) …
Signed яблочная мэллистяша 🍎
사랑，28/08 youtube update ：Do it NOW
custom 54068734348880932722custom 54521096152925154552
Signed яблочная мэллистяша 🍎
사랑，27/08 berriz update ：совсем забыл про пост.. с днем рождения нашего Рунчана! 🥳
custom 54068734348880932722custom 54521096152925154552
Signed яблочная мэллистяша 🍎
GUYS HE'S SO PRETTY I AM CRYING ㅠㅠ
custom 54521096152925154553custom 54068734348880932721
Signed яблочная мэллистяша 🍎
выступление мальчиков с 'achilles'
custom 54068734348880932722custom 54521096152925154551
Signed яблочная мэллистяша 🍎
🤩науз на kwda blue carpet сегодня
custom 54068734348880932722custom 54521096152925154552
Signed яблочная мэллистяша 🍎
사랑，25/08 youtube update ：'achilles' choreography behind
custom 54068734348880932722custom 54521096152925154552
Signed яблочная мэллистяша 🍎
сиюн ведет лайв в берриз !
custom 54068734348880932722custom 54521096152925154552
Signed яблочная мэллистяша 🍎
my twoyoonz crumbs </3
custom 54068734348880932723custom 54521096152925154552
Signed яблочная мэллистяша 🍎
사랑，24/08 tiktok update ：SIYUN'S BIRTHDAY 🦊🎉
custom 54068734348880932723custom 54521096152925154553
Signed яблочная мэллистяша 🍎
사랑，24/08 berriz update by jinhyuk ：Мой любимый Шун, с днём рождения тебя! 🤍 Надеюсь, сегодняшний день сделает тебя самым счастливым. И в будущем я тоже всегда буду рядом и буду первым поздравлять тебя с днём рождения. Люблю тебя 🫠
custom 54068734348880932723custom 54521096152925154553
Signed яблочная мэллистяша 🍎
사랑，24/08 berriz update by yoon ：С днём рождения нашего Сиюна! Хёну каждый раз хочется ещё больше о тебе заботиться, но прости, ты всё ещё малыш, хех. И всё же спасибо, что ты тоже так хорошо обо мне заботишься. Наши Туюнз, пусть наша дружба и дальше остаётся неизменной, и давай будем счастливы! Через 3 дня мой день рождения, хех-хех. Кажется, я выбрал фотографию, на которой из нас четверых я получился самым красивым,…
custom 54068734348880932723custom 54521096152925154553
Signed яблочная мэллистяша 🍎
Showing the 12 most recent of 13 posts we hold for @nowz_siyun. 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.
Named by 6 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.
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.
“maknáe with golden hánds” (@nowz_siyun), 69 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/nowz_siyun.
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.