2 measurements taken within a single day, net -1. 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 449–450 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Aug 2026, 23:54
449
-1
7 Aug 2026, 03:15
450
first reading
Engagement
9 posts held, back to 8 June 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
33.3%
avg views ÷ 449 subscribers
Avg views / post
149
3 posts measured
Reaction rate
4.91%
reactions ÷ views · ER floor
Posts in window
3
of 9 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
9 (8 June 2026 – 5 August 2026)
Views total
448
Reactions total
22
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 03:15 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
91 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 28.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5316683438114235535
26
28.6%
custom 5289487069540806692
19
20.9%
custom 5289854168985528317
18
19.8%
custom 5291912368853379431
11
12.1%
custom 5291940874551325192
7
7.69%
custom 5289602221908980245
4
4.40%
custom 5298958224047761779
4
4.40%
custom 5291845530572322521
2
2.20%
Custom emoji. Every 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 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 9 of the 9 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 91reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 8 June 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.
После прошлого поста решил посмотреть, что именно закон говорит про маркировку ИИ-контента. Мне интересно это именно с точки зрения ведения канала, разработки скриптов и использования ИИ-инструментов в пентестах
Оказалось, здесь есть интересный нюанс.
🔍С 1 марта 2027 года вступают в силу положения о маркировке материалов, созданных с использованием ИИ.
Но это не означает, что с этой даты каждый автор Telegram-кана…
Всем привет!
А вы заметили, что уже заканчивается июль 🤷♂
Лето скоро совсем пройдет, а столько планов ещё… надо возобновлять посты. И для этого даже есть темы!
🔍На днях был подписан Федеральный закон от 26.07.2026 №243-ФЗ «О поддержке развития технологий искусственного интеллекта в Российской Федерации». Большая часть его положений вступит в силу с 1 сентября 2026 года, отдельные нормы — позже.
Закон вводит осно…
Ловите отличный материал от моей коллеги, Анастасии Березовской
"Путь атакующего Kubernetes"
Как атакующий проходит путь от уязвимости в приложении до захвата Kubernetes-кластера? На практических демо разбираем RCE, SSRF, побег из контейнера, опасные Security Context и Linux Capabilities, а также способы защиты: Network Policies, Seccomp, Falco и принцип минимальных привилегий.
Приятного просмотра:
- 📹 Youtube
- 📺V…
🕷Универсальный стартовый набор для багхантера
Команда Intigriti подготовила гайд со всем необходимым для начинающего багхантера: от разведки и выбора цели до эксплуатации уязвимостей ⬇️
1️⃣Как составить полную карту приложения
2️⃣Основной тулинг, который упрощает работу
3️⃣Поиск и эксплуатация SQLi, XSS, IDOR
🔗 Канал в МАХ
🔑 Onelogon: Taking over Active Directory Accounts via Netlogon
We analyzed Netlogon, bypassed the Zerologon patch, resulting in a full auth bypass. An attacker can leverage this to compromise computer accounts, or even the entire AD. Non-standard config must be present tho
Exploit: https://github.com/rub-softsec/onelogon
https://github.com/Pennyw0rth/NetExec/pull/1291
From: https://x.com/al3x_n3ff/status/206948262…
Потусил сегодня на standoff talks (часть фоток честно взял из стендоффа)
Кайфово, атмосферно, круто. Рад был встретиться с подписчиками :) Даже смог залететь к товарищам поломать EDR 💻
На прошлой неделе принял участие в мероприятии родного университета в роли жюри - студенты демонстрировали результаты своей работы по проектной деятельности. Темы были максимально разнообразные. Автономное беспилотное судно, СКУД по голосу, автоматический башмакосбрасыватель… Я, конечно, отучился в рждшном вузе, но о башмакосбрасывателях услышал впервые 😱
Круто, что в университетах появляются дисциплины не только пр…
Showing the 9 most recent of 9 posts we hold for @pentestlead. 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.
Кто завтра будет на standoff talks 🤷♂ пишите, обязательно пересечемся!
Буду!22%
Ты чё, рабочий день78%
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 9 most recent posts we hold, published 8 June 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.
Citation-graph rank
Citation-graph rank — 1,060,805 of 1,151,006entries 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
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
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 7 August 2026 — this
entry's latest reading, not the date you are reading this.
“Pentest Lead Notes” (@pentestlead), 449 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/pentestlead.
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.
