6 measurements spanning 14 days, net -32. 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 3,507–3,549 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
6 Sept 2026, 01:38
3,512
-12
2 Sept 2026, 02:28
3,524
-6
30 Aug 2026, 01:34
3,530
-10
26 Aug 2026, 18:34
3,540
+5
24 Aug 2026, 00:43
3,535
-9
23 Aug 2026, 04:45
3,544
first reading
Engagement
20 posts held, back to 31 March 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 · 30 days
11.9%
avg views ÷ 3,512 subscribers
Avg views / post
417
2 posts measured
Reaction rate
11.5%
reactions ÷ views · ER floor
Posts in window
2
of 20 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 20 August 2026
Posts held
20 (31 March 2026 – 20 August 2026)
Views total
834
Reactions total
96
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Aug 2026, 04:45 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
16s
Average length
16s
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
3,240 reactions across 20 posts, in 28 distinct kinds. The most used accounts for 20.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5337325939997028554
678
20.9%
custom 5312450301167413840
385
11.9%
custom 5327761777973272131
378
11.7%
❤
353
10.9%
❤🔥
340
10.5%
custom 5282802528470191900
192
5.93%
💘
177
5.46%
custom 5339532088603328350
161
4.97%
🍓
130
4.01%
😢
93
2.87%
🔥
80
2.47%
🦄
65
2.01%
🖕
32
0.988%
💊
31
0.957%
💋
28
0.864%
🕊
28
0.864%
custom 5339398944617153685
18
0.556%
👍
18
0.556%
😭
12
0.37%
🙏
10
0.309%
8 further kinds
31
0.957%
Custom emoji. 6 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 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 20 of the 20 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,240 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 March 2026 to 20 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
8
across the posts below
Posts paid on
2
of 20 we hold a reading for · 10%
Most on one post
5
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @diss_413. 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 20 most recent posts we hold for this entry, published 31 March 2026 to 20 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.
🦀ГЛАВА ВЫШЛА🦀ЧАСТЬ: 1/3
🩸🩸🩸🩸🩸🩸🩸🩸
Полтора года ожиданий стоят того, чтобы наконец окунуться в историю с головой.
Начало второй главы уже доступно
Вторая и третья часть будут доступны позже. Когда - сообщим совсем скоро
➡️СКАЧАТЬ ВТОРУЮ ГЛАВУ⬅️
➡️Любые скрины и теории прячьте под спойлер - пусть они останутся тайной для тех, кто ещё не ступил на эту тропу. Впечатлениями и багами делитесь не здесь: для этого есть о…
Важная информация для тех, кто держит фулл пропуск вот так включенным
Пожалуйста, включайте его только для скипа и выключайте, когда доскипали до нужного момента, иначе эта настройка ломает все with в играх на renpy (почти всех новеллах, крч) исчезает плавность и многие эффекты. Благодарю за внимание
Если кто думает, что мы умерли, опровергаю это. Я работал над продолжением другого проекта. Кто знает какого, тот знает, у нас много общей фанбазы
Сегодня продолжаю делать 413. Как кодер я ожил, возрадуйтесь, 2.1 не за горами
Официально разрешаю делать мерч кому угодно без нашей доли (забирайте все монеты крч)
Ток уведомьте, чтобы прорекламил хоть
Разбирайте кому надо, мне в падлу самому заниматься мерчом
Showing the 12 most recent of 20 posts we hold for @diss_413. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Начали хайповать плейлисты персов (видел у мбд и натк, чтоб не сказали, что все украл и не сказал) стоит ли сделать тоже или мы антихайп?
Делай59%
Антихайп, не надо8%
Называй меня Дазай💋34%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 31 March 2026 to 20 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Визуальные новеллы для Android | VienDesu! Porting Team @visual_novels_for_android · 57,750 Telegram ranks this channel #16 of 57 here — alongside 56 others — read 23 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 September 2026 — this
entry's latest reading, not the date you are reading this.
“413: Пропаганда📝” (@diss_413), 3,512 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/diss_413.
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.
