5 measurements spanning 16 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 504–511 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
23 Aug 2026, 08:55
510
+3
15 Aug 2026, 16:17
507
+1
8 Aug 2026, 13:17
506
+1
8 Aug 2026, 04:16
505
no change
7 Aug 2026, 20:01
505
first reading
Engagement
18 posts held, back to 10 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
58.0%
avg views ÷ 510 subscribers
Avg views / post
296
2 posts measured
Reaction rate
4.22%
reactions ÷ views · ER floor
Posts in window
2
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 5 August 2026
Posts held
18 (10 March 2026 – 5 August 2026)
Views total
592
Reactions total
25
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 04:16 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
1m 30s
Average length
1m 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
242 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 45.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
110
45.5%
❤
69
28.5%
custom 5231280349895471371
14
5.79%
👍
14
5.79%
☃
9
3.72%
custom 5337080053119336309
6
2.48%
✍
4
1.65%
👨💻
4
1.65%
custom 5231481126731658116
3
1.24%
👀
3
1.24%
custom 5231083326860703699
2
0.826%
⚡
2
0.826%
🆒
1
0.413%
👾
1
0.413%
Custom emoji. 4 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 17 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 242reactions 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 10 March 2026 to 5 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.
Друзья, желаем доброго утра из Нижнего Новгорода! ☀️
Сегодня и завтра здесь проходит конференция #PAYMENTSECURITY
Регистрация уже открылась, с нетерпением ждём вас и скоро начнём!
Актуальную информацию о конференции вы сможете найти на канале.
🚀 Программа #PAYMENTSECURITY уже на сайте!
Заглядывайте, изучайте расписание, отмечайте самое интересное и готовьтесь к насыщенному дню.
Увидимся на #PAYMENTSECURITY!
📣 Всем привет!
До Practical Security Village осталось всего 2 недели!
Пока мы вовсю готовимся к воркшопу, делимся с вами частью закулисья - концепт-артами, которые легли в основу принтов для нашего традиционного, лимитированного мерча
Воркшоп пройдет 05-06 августа в Нижнем Новгороде в рамках конференции #PAYMENTSECURITY
Регистрация доступна на сайте
До встречи на Practical Security Village! 🚀
📣 Напоминаем, что 5-6 августа в рамках конференции #PAYMENTSECURITY пройдет воркшоп Practical Security Village, который для вас проведут пентестеры из Deiteriy Lab
Вас ждут:
🟢 интересные задания разного уровня сложности на взлом мобильных и веб-приложений, инфраструктуры и AI
🟢 воркшоп по пайке - вы сможете собрать собственный хакерский девайс и проверить его в деле на секции hardware
🟢 традиционный лимитированный м…
Новая версия PCI Secure Software Standard 2.0: обзор изменений и даты вступления в силу
Совет PCI SSC опубликовал новую версию стандарта PCI Secure Software Standard (PCI SSS) 2.0, являющегося частью фреймворка PCI Software Security Framework (SSF).
Напомним, что фреймворк PCI SSF был создан в результате пересмотра и разделения устаревшего стандарта PCI PA-DSS. На его основе сформированы два взаимодополняющих станда…
Вебинар «ИБ-аутсорсинг или штатный отдел: когда, что и как отдавать»
📆Дата и время: 21 июля в 11:00 (мск)
‼️РЕГИСТРАЦИЯ! Участие бесплатное
Модератор - Царев Евгений, управляющий, ООО «РТМ ТЕХНОЛОГИИ»
Спикеры:
Екатерина Витенбург, руководитель направления информационной безопасности, Б-152;
Иванцов Александр, директор по экспертизе, Deiteriy Compliance.
О чём поговорим❓
🔹Аутсорсинг внешний и внутренний. Взаимодей…
📹 Друзья, подготовка к #PAYMENTSECURITY идёт полным ходом.
А пока предлагаем вспомнить какой яркой и насыщенной конференция была в прошлом году!
Напоминаем, что регистрация на #PAYMENTSECURITY уже открыта на сайте.
Следите за анонсами - впереди ещё много интересного!
🚨 Объявляем конкурс докладов на #PAYMENTSECURITY!
Друзья, приглашаем вас выступить с докладом на #PAYMENTSECURITY и поделиться вашим практическим опытом и рекомендациями.
Отправляйте тему и тезисы на электронную почту: [email protected].
Программный комитет рассмотрит все заявки и отберет самые интересные.
🔴Прием заявок — до 14 июля 2026 года.
🔴Продолжительность доклада — 40 минут.
🔴Доклад не должен быть рек…
❗️ Друзья, приглашаем вас на #PAYMENTSECURITY 2026!
5–6 августа 2026 года на берегу Волги в Нижнем Новгороде пройдёт наша десятая конференция.
В программе:
1. Экспертные доклады на тему ИБ в финтехе.
2. Живой диалог с ведущими экспертами ИБ и ИТ.
3. Воркшоп по практической информационной безопасности Practical Security Village от пентестеров Deiteriy Lab.
4. PCI DSS TRAINING от экспертов Deiteriy Compliance.
5. Ну…
В феврале 2026 года введены изменения в Положение Банка России № 757-П
Согласно соответствующему Указанию Банка России № 7219-У, изменения вступают в силу с 1 января 2027 года, за исключением пунктов Положения Банка России № 757-П, для которых предусмотрены иные сроки вступления в силу. Ниже представлен краткий перечень изменений:
🔺 Расширен состав некредитных финансовых организаций, которые должны осуществлять защ…
Что же из себя представляет SoftPOS-решение?
На самом деле, всё довольно просто. В работе с каноничными POS-терминалами зачастую возникают проблемы: терминалы зависают, ломаются, затирают криптографические ключи или конфигурацию. Ключи и конфигурацию нужно уметь обновить через непривычный интерфейс POS-терминала. Мерчанты не всегда способны решить подобные проблемы самостоятельно. Им приходится обращаться к банкам-э…
PCI PIN Security в рамках SoftPOS-транзакций
Компании, которые рассматривают внедрение бизнес-процессов, связанных с обработкой транзакций через SoftPOS, получают требования от НСПК - пройти аудит по PCI PIN Security. Возникает вопрос: каков же скоуп этого аудита в контексте SoftPOS? Давайте разберёмся.
Первое, что следует учесть при формировании скоупа PCI PIN Security, это каналы передачи PIN-кода. В самом просто…
🔥6❤3👾1
Showing the 12 most recent of 18 posts we hold for @tolbukhin. 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.
К бизнес-процессу какого типа относится описанная функциональность?
Бизнес-процесс мерчанта37%
Бизнес-процесс поставщика услуг63%
Shares as published. 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 18 most recent posts we hold, published 10 March 2026 to 5 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.
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 23 August 2026 — this
entry's latest reading, not the date you are reading this.
“Толбухин маяк” (@tolbukhin), 510 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/tolbukhin.
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.