5 measurements spanning 6 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 1,224–1,233 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 15:26
1,232
+2
10 Aug 2026, 16:14
1,230
+4
8 Aug 2026, 01:27
1,226
+1
7 Aug 2026, 23:03
1,225
no change
7 Aug 2026, 16:22
1,225
first reading
Engagement
18 posts held, back to 27 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
28.2%
avg views ÷ 1,232 subscribers
Avg views / post
347
18 posts measured
Reaction rate
12.7%
reactions ÷ views · ER floor
Posts in window
18
of 18 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
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
18 (27 July 2026 – 7 August 2026)
Views total
6,246
Reactions total
792
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 23:03 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
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
792 reactions across 18 posts, in 21 distinct kinds. The most used accounts for 39.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5440603247582672333
309
39.0%
custom 5397710813651837478
74
9.34%
custom 6230796458891676650
57
7.20%
custom 5442654511078330658
50
6.31%
custom 5244661780067665942
41
5.18%
custom 6230796403057101249
39
4.92%
custom 5456115299361235190
36
4.55%
custom 5370706589030303861
34
4.29%
custom 6244410014866348386
26
3.28%
custom 5868530918255237355
24
3.03%
custom 5456615963698927570
19
2.40%
custom 6230883702562359548
19
2.40%
custom 5400160658702480767
16
2.02%
custom 6161117198698940987
14
1.77%
💋
8
1.01%
custom 5445163708282073774
7
0.884%
custom 5282943987513079748
6
0.758%
custom 5240275871134129747
4
0.505%
custom 5460844333232037004
4
0.505%
💯
4
0.505%
1 further kind
1
0.126%
Custom emoji. 18 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 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 18 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 792reactions 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 27 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 18 we hold a reading for · 6%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kurisanko. 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 18 most recent posts we hold for this entry, published 27 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.
У Лаогоу по чисто флексит на районе: походка уточкой – носки по сторонам и ноги выше головы! 😆 Крутой, капец крутой! 😇
🍚 Сегодня в 19:00 по МСК совместный просмотр 17-й и 18-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
9️⃣ Ссылка на стрим-комнату:
🌐 https://wparty.net/s/oocjl4u0ask
9️⃣ #ТаинственнаяДевятка
9️⃣ #УЛаогоу #ЦзэнШуньси
🌐 @kurisanko #_стрим
Знаете что было бы забавно... Если бы у Лю Сана объявился дедушка, которого сыграл тот же актёр. 😊
Вы заметили, что в девятке сразу несколько актеров играют и внука и деда? 👌
У Лаогоу — У Се
Се Цзюе — Се Юйчэнь
Давайте представим тогда, что Лю Сан условно внук Чжан Сяоцзиня... 🌚 Тогда стремление набить тату как у Чжана, острый слух как особый навык заимеют новые корни. 😊
Ну а Чжаны с другой фамилией нам и ранее вст…
Мы увидели Лю Чана на экране уже семь раз 🍚
Когда-то я уже делала эдит с Наньпай Саньшу и его ролями в экранизациях цикла. А теперь наконец-то пришла очередь его любимого артиста! ☺️
🌟 Очередность ролей по годам:
🤎 Ван Цань — Песчаное море (2018)
🤎 Лю Сан — Странный портрет (2018)
🤎 Лю Сан — Затерянная гробница: Перезагрузка (2020)
🤎 Лю Цяньмо | Лю Сан — История демона Утуна (2020)
🤎 Цзян У | Лю Сан — Эхо падения …
Меня так покоряет то, как Фо Е всегда приходит на выручку Ба Е! Настолько он им дорожит и всегда впадает в дикое бешенство, если кто-то посмеет ему навредить. ☺️
🍚 Сегодня в 19:00 по МСК совместный просмотр 15-й и 16-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
9️⃣ Ссылка на стрим-комнату:
🌐 https://wparty.net/s/oocjl4u0ask
9️⃣ #ТаинственнаяДевятка
9️⃣ #ЧэньВэйтин #ЧжанЦишань
🌐 @kurisanko #_стрим
Заметила, что многие путаются в красавчиках из семьи У, поэтому сделала вам памятку 9️⃣
💫🌧️🌧️🌧️🌧️🌧️🌧️🌧️🌧️🌧️✨
9️⃣ #ТаинственнаяДевятка
9️⃣ #УЧжэньюань #УАоле #УТяньпэн #УХэйфэй #УЦзюаньлянь #УЛаогоу
🍚 #DMBJ_каст
🌐 @kurisanko
Ловлю жёсткий краш на девятого господина Се 😍
Какой же он пьянящий и эффектный! 🩲
🍚 Сегодня в 19:00 по МСК совместный просмотр 13-й и 14-й серии «Таинственная девятка 2»
9️⃣ Ссылка на стрим-комнату:
🌐 https://wparty.net/s/oocjl4u0ask
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
9️⃣ #ТаинственнаяДевятка
9️⃣ #СеЦзюе #ЦзиСяобин
🌐@kurisanko #_стрим
Какой очаровательный У Лаогоу с Саньцуньдином 😍🩷
🍚 Сегодня в 19:00 по МСК совместный просмотр 11-й и 12-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
UPD: Просмотр завершён. 9️⃣
Встретимся завтра! 🐥
9️⃣ #ТаинственнаяДевятка
9️⃣ #ЦзэнШуньси #ДжозефЦзэн
🌐 @kurisanko #_стрим
Вот и ещё один обалденный фанмит за плечами! Сегодня на сцене собрались почти все актеры верхушек девятки! И вновь режиссер с автором новеллы задали жару вместе с ними 🤣
🍚 Сегодня в 19:00 по МСК совместный просмотр 9-й и 10-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
UPD: Просмотр завершён. 9️⃣
Встретимся завтра! 🐥
9️⃣ #ТаинственнаяДевятка
🌐 @kurisanko #_стрим
😌 Здоровский фанмит сегодня был! Столько классных кадров! Даже автор новеллы Наньпай Саньшу принял участие! 👌
🍚 Сегодня в 19:00 по МСК совместный просмотр 7-й и 8-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
UPD: Просмотр завершён. 9️⃣
Встретимся завтра! 🐥
9️⃣ #ТаинственнаяДевятка
🌐 @kurisanko #_стрим
🔥 «Таинственная девятка 2» бьёт все рекорды 2026 года и уже на третий день достигла 10100 индекса популярности, став первой дорамой в этом году, которая достигла этого высоченного значения!
🍚 Сегодня в 19:00 по МСК совместный просмотр 5-й и 6-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
UPD: Просмотр завершён. 9️⃣
Встретимся завтра! 🐥
9️⃣ #ТаинственнаяДевятка
🍚 #ЦзэнШуньси #ЧэньВэйтин #ЧэньЯо
🌐 @kurisanko #_стрим
Популярность каждого главного героя Таинственной девятки 2: Чжан Цишаня, У Лаогоу и Хо Сяньгу на Youku превысила 100 миллионов! ✨
🍚 Сегодня в 19:00 по МСК совместный просмотр 3-й и 4-й серии «Таинственная девятка 2»
🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍
UPD: Просмотр завершён. 9️⃣
Встретимся завтра! 🐥
9️⃣ #ТаинственнаяДевятка
🍚 #ЦзэнШуньси #ЧэньВэйтин #ЧэньЯо
🌐 @kurisanko #_стрим
Showing the 12 most recent of 18 posts we hold for @kurisanko. 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.
Citation-graph rank
Citation-graph rank — 1,018,885 of 1,340,412entries 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.
Mentions
Named by 1 registered channel — 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.
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
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.
