3 measurements spanning 8 days, net -5. 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 383–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
3 Sept 2026, 18:56
384
-5
27 Aug 2026, 05:42
389
no change
26 Aug 2026, 15:30
389
first reading
Engagement
7 posts held, back to 16 May 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
172.1%
avg views ÷ 384 subscribers
Avg views / post
661
2 posts measured
Reaction rate
1.74%
reactions ÷ views · ER floor
Posts in window
2
of 7 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 26 August 2026
Posts held
7 (16 May 2026 – 26 August 2026)
Views total
1,322
Reactions total
23
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
26 Aug 2026, 15:30 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
30s
Average length
30s
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
74 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 52.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
39
52.7%
🔥
12
16.2%
👍
11
14.9%
😢
4
5.41%
custom 5206432082892432744
3
4.05%
⚡
3
4.05%
👏
1
1.35%
🕊
1
1.35%
Custom emoji. One 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 count beside it is 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 7 of the 7 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 74 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 16 May 2026 to 26 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.
⁉️ «Охота на Охотный ряд»: как устроена работа Госдумы изнутри!
Хочу порекомендовать вам эту книгу, потому что обычно о парламенте принято писать либо в хвалебном ключе, либо в разоблачительном. Автор этой книги, Павел Склянчук, выбрал иной путь: он показывает механизм принятия решений, как проходят законопроекты, почему некоторые инициативы буксуют, какую роль играют комитеты - обо всём этом рассказано интересно и …
💙 Наши идеи - в главной программе страны!
В Москве завершился второй этап XXIII съезда «Единой России». Принята новая Народная программа, с которой партия идёт на выборы.
🤩 Удмуртию на съезде представляла делегация во главе с врио Главы республики Ольгой Абрамовой. В составе делегации также были наши молодогвардейцы: руководитель регионального отделения Владимир Лисин, руководитель аппарата Владислав Суслов.
🔊 До …
Друзья, хотелось бы начать этот день иначе, но ситуация на текущий момент такова.
Одно из предприятий в Удмуртской Республике подверглось атаке беспилотников со стороны киевского режима.
По оперативным данным, пострадавших нет. На месте дежурят кареты скорой помощи. Там же работают все оперативные службы. Дополнительную информацию буду сообщать по мере поступления.
Напоминаю, задача врага – посеять панику, но мы в…
Съезд Партии «Единая Россия» в Москве
Сегодня вместе с делегацией Удмуртского регионального отделения Партии принимаю участие в рабочей программе федерального Съезда.
На мероприятии присутствует почти четыре тысячи человек. Большинство участников и делегатов XXIII Съезда представляют региональные отделения партии. На мероприятии собрались победители предварительного голосования партии из числа ветеранов СВО, в том …
22 июня.
85 лет назад прозвучали слова, изменившие всё: «Наше дело правое. Враг будет разбит. Победа будет за нами!».
В канун Дня памяти и скорби с командой «Молодой Гвардии» возложил цветы в Сквере Победы. Мы склонили головы перед героями-земляками, не вернувшимися с войны, и перед тружениками, поколением победителей. Также принял участие в акции «Огненная картина войны».
Мы обязаны помнить не только горечь 22 ию…
Труд – великая объединяющая сила. Это еще раз подтвердил сегодня субботник в Ворошиловском лесу.
Более 100 ижевчан разного возраста очистили полюбившуюся городскую территорию от мусора и валежника, чтобы было комфортно гулять.
Инициатором субботника стал заместитель Председателя Госсовета УР – председатель постоянной комиссии по физической культуре, спорту и молодежной политике Черезов. Его идею поддержали коллеги …
❤8👍2🔥2⚡1👏1
Showing the 7 most recent of 7 posts we hold for @panslavs1713. 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.
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
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.
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 3 September 2026 — this
entry's latest reading, not the date you are reading this.
“Наброски на полях/Владислав Суслов” (@panslavs1713), 384 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/panslavs1713.
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.
