Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
14 measurements spanning 41 days, net +55. 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 6,756–6,873 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Sept 2026, 13:00
6,852
-7
13 Sept 2026, 00:41
6,859
+3
9 Sept 2026, 01:16
6,856
+81
3 Sept 2026, 09:34
6,775
+6
31 Aug 2026, 12:26
6,769
-3
28 Aug 2026, 01:54
6,772
-3
25 Aug 2026, 03:54
6,775
-1
22 Aug 2026, 00:23
6,776
-6
18 Aug 2026, 21:45
6,782
-8
15 Aug 2026, 16:27
6,790
-3
12 Aug 2026, 10:48
6,793
-1
9 Aug 2026, 15:14
6,794
-6
7 Aug 2026, 01:12
6,800
+3
6 Aug 2026, 05:06
6,797
first reading
Engagement
46 posts held, back to 22 July 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 12 pages of 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 46 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
262 reactions across 37 posts, in 20 distinct kinds. The most used accounts for 25.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
66
25.2%
🔥
62
23.7%
👍
31
11.8%
👎
31
11.8%
❤🔥
11
4.20%
⚡
9
3.44%
😁
8
3.05%
✍
5
1.91%
🎉
5
1.91%
👌
5
1.91%
👏
5
1.91%
🙏
5
1.91%
💯
4
1.53%
🤣
3
1.15%
🥰
3
1.15%
🦄
3
1.15%
🤩
2
0.763%
🤯
2
0.763%
😇
1
0.382%
😍
1
0.382%
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 40 of the 46 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 267 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 46 most recent posts we hold, published 22 July 2026 to 19 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.
Advertising
Ad load
4.35%
2 of 46 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
430
over 2 measured posts
Median views · rest
474
over 44 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2W5zFHHpCzu
1
29 July 2026
29 July 2026
2W5zFHrMEqX
1
8 August 2026
8 August 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 46 most recent posts we hold, published 22 July 2026 to 19 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
📌 Корпоративная безопасность ИИ: 7
ключевых мер #опытэкспертов
Материал подготовлен на основе выступления Дениса Батранкова в рамках образовательного курса «Директор по кибербезопасности 8.0», модуль «Безопасность ИИ». 👇🏻
Минимальный обязательный набор для любой организации внедряющей ИИ:
1. Политики использования ИИ
Кто, где и как может использовать модели. Утверждённый реестр разрешённых инструментов с уровнями …
После летней паузы возвращаемся в эфир — и начинаем 5-й модуль годовой программы «Директор по кибербезопасности 8.0».
✔️ Первое занятие — открытое
«Риски третьих сторон и цепочки поставок»
Вас могут взломать не через вашу инфраструктуру, а через того, кому вы доверяете: поставщика ПО, подрядчика, облако, аутсорс или даже open source.
На открытом занятии разберём, как CISO выстроить работающую систему TPRM:
— кого счи…
Иногда десять минут в баре полезнее часа в зрительном зале на серьезной конференции.
Потому что именно за бокалом пенного кто-нибудь обязательно скажет: «Вот здесь все сломалось». Затем другой человек подключится с похожим кейсом. И через пять минут завяжется разговор, из которого каждый что-то с собой унесет.
Для таких разговоров облачный провайдер Nubes придумал ИЗИфест — фестиваль для тех, кто отвечает за ИИ, ИТ…
Практика, экспертиза и открытый диалог — именно ради этого участники приезжают на Код ИБ ПРОФИ снова и снова.
📍9–13 сентября | Сочи
До встречи на ПРОФИ
#ИБнужныПРОФИ
С 27 по 29 августа в Екатеринбурге пройдёт AI Growth Days (ex-AGDays) — конференция от Alto, которая уже шестой год объединяет объединяет на одной площадке заказчиков digital-услуг, рынок аутсорс-разработку.
В этом году основная тема — как использовать искусственный интеллект для рост бизнеса.
В программе — три дня пользы и общения:
🔴27 августа: Pre-party конференции — знакомимся и настраиваемся на продуктивную пя…
Какой PAM нужен современной инфраструктуре
Сегодня привилегированный доступ — это не только администраторы. Повышенные права есть у подрядчиков, сервисных учётных записей, облачных ролей, API и автоматизированных процессов.
🔥 19 августа в 11:00 в прямом эфире AM Live разберём, каким должен быть PAM для современной гибридной и облачной инфраструктуры.
С экспертами обсудим:
— какие типы привилегированного доступа ну…
🌟 До ПРОФИ в Сочи — 23 дня
🤖 ИИ меняет безопасность быстрее, чем появляются новые регламенты. Узнайте о лучших практиках от CISO крупнейших компаний на интенсиве.
🌟 До ПРОФИ в Сочи — 25 дней
🤝 Самые сильные знакомства в ИБ происходят не в Zoom, а за чашкой кофе. Успейте забронировать место на интенсиве.
🔥1
Showing the 12 most recent of 46 posts we hold for @codeibnews. 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.
Posts edited after publishing
@codeibnews edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
20 August 2026
Most recent edit
20 August 2026
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
Named by 4 registered channels — 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Об ЭП и УЦ @ep_uc · 21,240 Telegram ranks this channel #33 of 97 here — alongside 96 others — read 24 September 2026
Борьба с киберпреступностью | F6 @f6_cybersecurity · 22,318 Telegram ranks this channel #47 of 85 here — alongside 84 others — read 21 September 2026
Privacy Advocates @prv_adv · 21,918 Telegram ranks this channel #57 of 98 here — alongside 97 others — read 22 September 2026
Пост Лукацкого @alukatsky · 37,862 Telegram ranks this channel #58 of 89 here — alongside 88 others — read 31 August 2026
Kaspersky @kasperskylab_ru · 28,831 Telegram ranks this channel #59 of 96 here — alongside 95 others — read 9 September 2026
IT и безопасность @tg_security · 26,560 Telegram ranks this channel #71 of 91 here — alongside 90 others — read 12 September 2026
Positive Hack Days Media @positivehackmedia · 30,694 Telegram ranks this channel #72 of 88 here — alongside 87 others — read 6 September 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this
entry's latest reading, not the date you are reading this.
“Код ИБ: ИИ & КиберБезопасность” (@codeibnews), 6,852 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/codeibnews.
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.