2 measurements taken within a single day. 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 620–622 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
6 Aug 2026, 17:33
621
no change
6 Aug 2026, 09:36
621
first reading
Engagement
16 posts held, back to 23 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
33.8%
avg views ÷ 621 subscribers
Avg views / post
210
4 posts measured
Reaction rate
1.45%
reactions ÷ views · ER floor
Posts in window
4
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. It is computed over the 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 28 July 2026
Posts held
16 (23 April 2026 – 28 July 2026)
Views total
839
Reactions total
10
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 17:33 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
Photos
202
Videos
10
Links
149
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
93 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 34.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5330437392274827570
32
34.4%
🔥
29
31.2%
custom 5465262274031659421
18
19.4%
👍
7
7.53%
custom 5470060791883374114
2
2.15%
👏
2
2.15%
custom 5465465194056525619
1
1.08%
👎
1
1.08%
🤯
1
1.08%
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 14 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 93reactions 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 23 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
1
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @redbluenotes. 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 23 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.
Классный. Познавательный. Интересный.
Это все про него — про райтап от MN3STRASHN0 🌟
В нем автор разбирает решение машины Rawmatex и показывает, как пройти путь от первичной разведки до получения финального флага.
По легенде, компания MetalliKO использует внутренний портал Rawmatex для отслеживания поставок сырья, заказов и связанных документов.
Цель решения — получить доступ к учетной записи администратора порта…
ШОК! ЖЕСТЬ! БЛИН! ВЫШЕЛ!
Новый выпуск подкаста "ZeroDay На завтрак!"
Взяли интервью у крашей. В смысле — у команды cR4.sh ❤️
Ребята, которые регулярно рубятся на CTF и Standoff. Договориться по времени было непросто, но оно того стоило.
CTF умер! Или всё-таки нет?
Спросили обо всём, что обычно обсуждают в чатах, но не под запись: убивают ли нейросети CTF, как люди вообще оказываются в информационной безопасности…
КАМЕРЫ НАБЛЮДЕНИЯ - ТИХИЙ ФРОНТ КИБЕРАТАК
IP-камеры 📷 - никсы с RTSP и веб-сервером. Миллионы устройств Hikvision, Dahua, Axis и их OEM-клонов торчат в интернет с прошивками 2017–2021 годов. И злоумышленники этим активно пользуются. Мой любимый реальный кейс - это когда у APT была наводка, что пароли пишут на маркерной доске, но её закрывал открытый шкаф, который несколько месяцев не закрывали, и вот APT ждали пару …
Побеги из контейнеров и discovery в Docker/K8s
Выкатили объёмный (да, как обычно, лонгрид) материал про container escape и техники discovery в Kubernetes и Docker. Постарались собрать не разрозненные заметки, а базу и best practices, будет полезно и тем, кто атакует, и тем, кто защищает свою инфру.
Если материал оказался полезным, то лучшая инвестиция в канал это лайк! ❤️
И раз уж заговорили про новые темы — есть …
Docker Escape: что искать внутри контейнера
Пост имеет ознакомительный характер и предназначен для специалистов по безопасности. Автор и редакция не несут ответственности за любой вред, причиненный с применением изложенной информации. Распространение вредоносных программ, нарушение работы систем и нарушение тайны переписки преследуются по закону
Если вы уже внутри контейнера, это еще не значит, что история закончилас…
Standoff 17 💻
Раньше я посещал Standoff как зритель, но в этом году удалось поучаствовать в кибербитве. Сидел на банковском сегменте 🏦, было очень интересно, потому что до этого у меня не было опыта атаки банковского сектора, но не смотря на это удалось сделать пару критов 🔓. А сегодня под финал заехал на Standoff Talks посмотреть на полигон в кибердоме
Снова удалось побывать на Assume Birch — безумно классное мероприятие, рад, что звёзды сошлись 🍩
Как обычно, было много интересных докладов.
Первый, от Яндекса, оказался не совсем моей темой и довольно сложным для восприятия. Очень низкоуровнево, бутлоадеры, secure boot и всё такое.
А вот доклад про то, как один атакующий получил доступ сразу к двум компаниям, очень зашёл! В одной был мониторинг, в другой нет, и р…
Интересные туннели, которые всё чаще появляются в отчётах
В последнее время всё чаще стал замечать в отчётах по пентестам, подломам новые инструменты для туннелирования. Если раньше почти везде встречались Chisel, FRP, Ligolo-NG и другие известные решения, то сейчас появляются совсем другие проекты.
Самое интересное, что многие из них изначально создавались вовсе не для пентестеров. Это полноценные платформы для уд…
Атака на цепочку поставок: как один npm роняет полмира
Окей, представьте сценарий мечты для злоумышленника. Он не ломает периметр жертвы. Он вообще к нему не прикасается. Он просто отравляет то, что жертва сама скачает и запустит у себя в проде. Налил яд в источник, а дальше тысячи разработчиков выстроились в очередь попить.Это и есть атака на цепочку поставок (supply chain attack). И в 2025–2026 она переехала из от…
Шок, жесть блин! Вышел! Новый СПЕЦвыпуск!
❗️ Осторожно: в выпуске присутствует ненормативная лексика!
Это немного личный для нас выпуск. Позвали одного из лучших преподавателей, который нас когда-либо обучал, и поговорили о том, что обычно остаётся за кадром: как превратить диплом в стартап и реально получить за него деньги, как не выгорать, существует ли синдром самозванца на самом деле и что такое геймификация и к…
Showing the 12 most recent of 16 posts we hold for @redbluenotes. 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 — 354,203 of 1,336,469entries 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@redbluenotes named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@tanstack named in 1 post, 8 August 2026 – 8 August 2026
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“RedBlue Notes” (@redbluenotes), 621 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/redbluenotes.
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.
