Channel
@qb_channel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
436subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001669939384 |
|---|---|
| Type | Channel |
| Username | @qb_channel |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/qb_channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 12:46 | 436 | +2 |
| 6 Aug 2026, 19:18 | 434 | no change |
| 6 Aug 2026, 09:19 | 434 | first reading |
11 posts held, back to 6 December 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 20 May 2026. An engagement rate over an empty window would be a number about nothing.
21 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 42.9% | |
| 👍 | 6 | 28.6% | |
| 🔥 | 4 | 19.0% | |
| 🎉 | 2 | 9.52% |
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 5 of the 11 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 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 6 December 2025 to 20 May 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.
CTI Meetup #5 __________________________ What: #meetup Where: Лофт «Москва» по адресу Москва, Берсеневская набережная, 6с3 Who: INSECA & CyberThreatTech When: 23.05.2026 How: offline __________________________ Друзья, здравствуйте! 🙋♂️ Уже в эту субботу состоится пятый (уже пятый, представляете!) CTI митап. Сходка для всех кому интересно направление Threat Intelligence. Вас ждёт как обычно добрая и непринуждённая …
❤4🔥1
Всем привет 👋. Инсека и Технологии киберугроз приглашают вас на CTI meetup #5. 🍻 обсуждаем рабочие моменты, делимся опытом 📆 23 мая, 14:00-20:00 📍 Место: Лофт «Москва» по адресу Москва, Берсеневская набережная, 6с3 Программа CTI meetup #5: Сбор гостей 13:30-14:00 Начало выступлений 14:00 1. Threat Hunting в опенсорсе: злоумышленники используют ИИ, мы тоже, но есть нюанс Раковский Станислав (руководитель группы Su…
Cognitive Biases Handbook __________________________ What: #book Where: #web Who: Swiss Federal Intelligence Service (FIS) When: 05.01.2026 How: just read __________________________ Друзья, здравствуйте! 🙋♂️ На прошлой неделе Федеральная разведывательная служба Швейцарии опубликовала материал, посвящённый когнитивным искажениям. За грамматику сильно не пинайте, т.к. авторы сами признаются, что This text has been t…
❤5
Happy New Year 2026 🍾 __________________________ What: #celebration Where: #everywhere Who: Qwerty Bubble When: 31.12.2025 How: as you wish __________________________ Друзья, здравствуйте! 🙋♂️ 2025 год был непростым наконец-то закончился. Обычно в последний день уходящего года всё подводят итоги того, как они прожили эти 365 дней. Не зацикливайтесь на том, что не получилось сделать или на чём-то, что не успели из …
👍6🎉2
Финальный архив по теме поиска киберугроз 🤓 Описание к материалам (пароль threathunting): 1. The Threat Hunter’s Cookbook. Руководство как хантить в Splunk 2. Cyborg Security. Threat Hunting Framework. Хороший материал по выстраиванию процесса. Расскажут и про пользу, и про команду, про примеры гипотез и про метрики. 3. Threat Hunting for Effective Cybersecurity. Брошюра от Sixgill. 4. Cyber Threat Hunting Framework…
🔥2
Рассказываем, как прошел CTI meetup №4 - Собрали 100+ специалистов ИБ из более чем 35 организаций; - 5 часов концентрированной пользы по теме CTI; - С докладами выступили 7 экспертов: 🔹Как закалялась сталь: путь к отчёту о проукраинских кибергруппировках Никита Назаров и Кирилл Митрофанов, Лаборатория Касперского 🔹Что не так с киберразведкой? Николай Токарев 🔹История одного британского вигиланта Александр Бадаев,…
Threat Hunting Process __________________________ What: #notes __________________________ Публикую третью часть с литературой по процессу поиска киберугроз в дополнение к предыдущим двум (раз, два). Поехали!
🔥1
Описание к материалам (пароль threathunting): 1. Packt. Threat Hunting with Elastic Stack. В книге (2021г) рассказывается база по Threat Hunting + автор демонстрирует как на базе ELK собрать домашнюю лабу. Много практики по ёлке. 2. Hunt.io Modern Threat Hunting. Брошюра от hunt.io, показывающая как можно исследовать сетевые индикаторы. 3. Hunt.io The Threat Hunter's Query Playbook. Тоже небольшая брошюрка от hunt.io…
Photo, posted without a caption
ThreatCluster __________________________ What: #tip Where: #site Who: Icabus When: Autumn 2025 How: via web __________________________ Друзья, здравствуйте! 🙋♂️ Буквально на этой неделе в паблике появилась информация про новый сервис ThreatCluster. Если в двух словах, автор парсит 3,363 различных источников в интернете (security blogs, vendor advisories etc., government feeds, CERT advisories, research publicatio…
☃️ Winter is coming ❄️ __________________________ What: #chat Where: #qbchannel Who: Qwerty Bubble When: 06/12/2025 How: just read __________________________ Друзья, здравствуйте! 🙋♂️ Прерываю полугодовое молчание несколькими хорошими новостями 1️⃣ Неделю назад в третий раз выступил с докладом, в котором рассказал про процесс написания отчёта о проукраинских группировках, на четвёртом CTI Meetup, организованном И…
Showing the 11 most recent of 11 posts we hold for @qb_channel. 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.
Citation-graph rank — 1,216,621 of 1,480,688entries 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.
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.
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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“QB_channel” (@qb_channel), 436 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/qb_channel.
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.