9 measurements spanning 8 days, net -11. 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 12,158–12,173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 23:35
12,160
-1
13 Aug 2026, 18:25
12,161
-3
12 Aug 2026, 13:54
12,164
-2
11 Aug 2026, 14:32
12,166
-3
10 Aug 2026, 12:10
12,169
-2
9 Aug 2026, 09:53
12,171
+1
8 Aug 2026, 12:46
12,170
-1
7 Aug 2026, 06:00
12,171
no change
7 Aug 2026, 05:48
12,171
first reading
Engagement
16 posts held, back to 29 April 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 16 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
33.6%
avg views ÷ 12,160 subscribers
Avg views / post
4,090
1 post measured
Reaction rate
6.53%
reactions ÷ views · ER floor
Posts in window
1
of 16 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 28 July 2026
Posts held
16 (29 April 2026 – 28 July 2026)
Views total
4,090
Reactions total
267
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
13 Aug 2026, 03:37 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
3,351 reactions across 16 posts, in 36 distinct kinds. The most used accounts for 28.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
939
28.0%
🔥
569
17.0%
❤
559
16.7%
😁
523
15.6%
🙏
192
5.73%
🤯
165
4.92%
🤷♂
105
3.13%
😱
37
1.10%
🍌
36
1.07%
🌚
29
0.865%
😢
25
0.746%
😍
22
0.657%
✍
20
0.597%
😨
14
0.418%
💅
11
0.328%
🆒
10
0.298%
🥰
10
0.298%
🎉
9
0.269%
👌
9
0.269%
😐
9
0.269%
16 further kinds
58
1.73%
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 16 of the 16 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 3,351reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 29 April 2026 to 28 July 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
23
across the posts below
Posts paid on
13
of 16 we hold a reading for · 81%
Most on one post
4
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @SergeyKuvaevJPtelegram. 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 16 most recent posts we hold for this entry, published 29 April 2026 to 28 July 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.
Advertising
Ad load
6.25%
1 of 16 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
6,480
over 1 measured post
Median views · rest
8,380
over 15 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2VfnxwivcQA
1
30 April 2026
30 April 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 16 most recent posts we hold, published 29 April 2026 to 28 July 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Сегодня около половины пятого вечера в Кумамото произошло очень сильное землетрясение магнитудой 7,1. В эпицентре зафиксировали максимальную для Японии интенсивность 7. В Токио я его практически не почувствовал, но на Кюсю последствия оказались серьёзными.
Самая тяжёлая ситуация сейчас в городе Касива, где частично обрушился крупный торговый центр AEON. По предварительной информации, перед этим там мог произойти взр…
Сегодня утром проходил мимо местного храма, где готовились к мацури. Так в Японии называют традиционные районные и храмовые праздники.
И поймал себя на мысли, что если бы не знал, что происходит, то решил бы, что попал на сходку местной шпаны.
Самые активные участники подготовки оказались загорелые, почти коричневые ребята. Трое из них вообще стояли и курили прямо возле храма. Другие рассекали на мотороллерах без шле…
Первые арбузики нормального размера в этом году.
Пока фотографировал их в магазине, рядом остановились две японки лет 50-60.
Одна посмотрела на арбузы, потом на меня и с улыбкой произнесла: «Вери биг сайз!».
Я улыбнулся в ответ. А потом ещё какое-то время думал: «Как она узнала?»
Сразу вспомнились российские 90-е, когда ради сдачи в цветмет исчезало всё, вплоть до канализационных люков.
___________________
В Японии начали воровать медь даже с храмов и синтоистских святилищ.
В префектуре Канагава неизвестные сняли около 60 медных панелей с территории синтоистского святилища Адзума, которое, согласно легендам, существует уже около 1900 лет.
Панели были буквально оторваны силой с крыши огражд…
Если так дальше пойдёт, иностранцам в Японии скоро придётся конкурировать за зрелых японок уже с самими японцами.
_____________________
В Японии продолжает расти количество браков, где жена старше мужа. И это уже не редкость, а вполне заметный социальный тренд.
По данным японской демографической статистики, около четверти всех новых браков сейчас приходится на пары, где женщина старше мужчины. Для Японии это рекорд…
На днях пропал голос полностью. Уже считай 3й день, только шепотом или жестами получается разговаривать. Тем не менее, снимался сегодня для японского ТВ(телепередача, не сериал), история про шпионаж. Япония как раз в этом году пересматривает законы, в отношении шпионской деятельности.
Хорошо, что на японском ТВ всех иностранцев всегда переозвучивает диктор, даже если события происходят в Японии и персонаж говорит по…
В японских новостях появилась примечательная новость, которая ещё недавно казалась почти невозможной.
Нефтяной танкер с российской нефтью проекта Сахалин 2 уже находится в пути в Японию. Груз направляется компании Taiyo Oil в префектуру Эхимэ.
Согласно сайту отслеживания судов MarineTraffic, танкер вышел с Сахалина в конце апреля.
Японские эксперты сейчас говорят о том, что когда на кону электричество, отопление, б…
Наткнулся на этот раритет. Автомат по продаже батареек в Киото.
👍149🔥48❤20🆒9😁5🍾1
Showing the 12 most recent of 16 posts we hold for @SergeyKuvaevJPtelegram. 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 — 952,602 of 1,345,403entries 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.
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.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“SergeyKuvaevJP” (@SergeyKuvaevJPtelegram), 12,160 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/SergeyKuvaevJPtelegram.
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.
