Telegram RegisterThe public register of Telegram
Telegram profile photo for Пост Лукацкого

Channel

Пост Лукацкого

@alukatsky

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry

38,465subscribers

+1,021 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001077356912
TypeChannel
Username@alukatsky
DescriptionУникальный контент про кибербезопасность от Алексея Лукацкого (@alukatsk) - мысли, полезные ссылки, комментарии к текущим событиям, юмор и мемасики. Канал личный - мой работодатель никак не влияет на то, что здесь публикуется. Рекламу не размещаю!!!
Created31 July 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/alukatsky

Topic

Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Growth

37,44438,46537,954.56 August 202611 November 2026
63 measurements spanning 98 days, net +1,021. 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 37,291–38,618 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
11 Nov 2026, 15:4638,465+34
9 Nov 2026, 22:0038,431+20
8 Nov 2026, 16:1738,411-11
7 Nov 2026, 06:2838,422+5
6 Nov 2026, 08:4838,417+10
5 Nov 2026, 09:5138,407+9
4 Nov 2026, 07:5738,398+11
3 Nov 2026, 06:3038,387+5
2 Nov 2026, 09:2938,382-5
1 Nov 2026, 12:4838,387-8
31 Oct 2026, 10:0938,395+18
30 Oct 2026, 08:1138,377-8
28 Oct 2026, 02:1838,385+12
27 Oct 2026, 04:3538,373+13
26 Oct 2026, 05:3738,360+12
24 Oct 2026, 03:1438,348+15
22 Oct 2026, 23:4638,333+19
21 Oct 2026, 18:1938,314+1
19 Oct 2026, 19:5638,313+10
18 Oct 2026, 17:3938,303first reading

Engagement

399 posts held, back to 31 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 191 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.8%
avg views ÷ 38,465 subscribers
Avg views / post
6,080
128 posts measured
Reaction rate
0.695%
reactions ÷ views · ER floor
Posts in window
128
of 399 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
WindowRolling 30 days · latest post in window 16 November 2026
Posts held399 (31 July 2026 – 16 November 2026)
Views total777,640
Reactions total5,402
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 11:21 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
≈7,230
Videos
≈520
Links
≈8,060

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
12m 25s
Average length
44s

Measured directly from 17 videos 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

17,284 reactions across 385 posts, in 70 distinct kinds. The most used accounts for 20.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁3,57120.7%
👍3,31319.2%
🔥2,84216.4%
❤2,17612.6%
🤣1,6499.54%
💯8564.95%
🤔5183.00%
🤡2791.61%
✍2041.18%
👏1901.10%
🤝1580.914%
😢1530.885%
😱1150.665%
🤯1100.636%
👀1040.602%
🤬830.48%
💩710.411%
😭630.364%
⚡550.318%
❤‍🔥550.318%
50 further kinds7194.16%

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 394 of the 399 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 17,669 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 399 most recent posts we hold, published 31 July 2026 to 16 November 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
80
across the posts below
Posts paid on
36
of 396 we hold a reading for · 9%
Most on one post
31
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @alukatsky. 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 399 most recent posts we hold for this entry, published 31 July 2026 to 16 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 128 posts held from the last 30 days (1.56%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 11:02 UTC≈1,160 views31 reactionsread 16 November 2026
Photo

Неравный бой с мошенничеством продолжается... #мошенничество #юмор

😁25💯3🤣2❤1

16 Nov 2026, 08:31 UTC≈2,840 views11 reactionsread 16 November 2026
Photo

Легенды гласят, что когда-то была актуальна такая угроза, как броадкастовый шторм, реализуемая на 2-м уровне модели OSI (если кто еще помнит, что это такое) – большое количество пакетов, которые из-за петель Ethernet (или неисправности оборудования, или DoS-атаки) еще и кратно умножались, приводило к тому, что сеть не могла обрабатывать обычный трафик, тратя все ресурсы на обработку broadcast'а. И вот на прошлой неде…

❤6🔥3🤔2

16 Nov 2026, 06:31 UTC≈3,750 views17 reactionsread 16 November 2026

История с падением Microsoft интересна не столько самим своим фактом (как ни странно, но размер потенциальных застрахованных потерь оценивается всего в 300-500 миллионов долларов, что на порядок меньше последствий от инцидента с CrowdStrike), сколько тем, как компании приспосабливались к недоступности цифровых сервисов: ✔️ Euronext, оператор европейских бирж предложил компаниям использовать телефон для решения вопрос…

👍12🤔3❤2

13 Nov 2026, 06:45 UTC≈7,300 views108 reactionsread 16 November 2026

Трое суток прошло, а фейковая новость, которую запустили ради троллинга, до сих висит на сайте СМИ, позиционирующего себя как профессиональное. А оно и раньше было замечено в копипасте чужих постов. Фи таким быть... #фейк #уязвимость

😁73🤣33🤡2

12 Nov 2026, 18:32 UTC≈9,020 views42 reactionsread 16 November 2026
Photo

В Даркнете продается еще и переписка бывшего главы НТС ФСБ, в ведении которого находился и 8-й Центр ФСБ вместе с ГосСОПКОЙ? Куда смотрит ГосСОПКА, хочется спросить? Хотя, стоп, я в 2022-м году уже задавался этим сакраментальным вопросом... И кажется мне, что на фоне истории с Solaris, "Глазом Бога", UserBox, "Черным кубом", "Незабудкой", "Петрушкой" и т.п. все это объяснимо 😕 #утечка

💯25😁12😱3❤1🔥1

12 Nov 2026, 15:39 UTC≈8,790 views74 reactionsread 16 November 2026
Video

Вспоминая фильмы «Солт», «Красный воробей» и иже с ними и видя списки глав крупнейших американских компаний с китайскими подругами… а вдруг это реально готовящаяся десятилетями шпионская кампания по внедрению китайских детей в Америку для последующего захвата тел и мыслей глав бигтехов, кражи секретов и разваливания американской экономики? Вот будет сюрприз-то и сюжет для очередного блокбастера 🥷 Причем для государс…

😁49👍10❤6👏3🤔3💩1💯1🤣1

12 Nov 2026, 13:38 UTC≈7,490 views15 reactionsread 16 November 2026

10 ноября директор по надзору Центробанка Бразилии заявил, что закрыл организацию из-за существенной потери ликвидиности в результате инцидента ИБ. Имел ли он ввиду ликвидированный в апреле 2026 года кредитный кооператив Creditag, отключенный от национальной государственной системы мгновенных электронных платежей Pix после атаки на C&M Software. На этом фоне интересно посмотреть на свежий отчет Information Risk Ins…

❤5✍4👌3👍3

12 Nov 2026, 09:06 UTC≈6,130 views58 reactionsread 16 November 2026

Кстати, в сентябре в Бразилии приняли закон о специальном налоговом режиме ReData, согласно которому, компании получают масштабные налоговые льготы на 5 лет, если обязуются выделять минимум 10% мощностей ЦОДа для внутреннего рынка Бразилии. Эти 10% нельзя использовать для собственных нужд компании или экспортировать зарубежным клиентам, даже если внутри Бразилии на них временно не хватает спроса. Программа ReData ос…

🔥33💯12❤6👍4🤔3

12 Nov 2026, 06:24 UTC≈6,070 views32 reactionsread 16 November 2026

А вот новый ресурс с записями полутора тысяч конференций по ИБ, 27+ тысячами спикеров из 56 стран. Я даже себя в списке нашел, хотя всего 2-3 выступления. Там местами странное. Тот же PHD вроде как и есть, но не все сотни выступлений за каждый год, а всего несколько десятков, а то и единиц за каждый год. Но по зарубежным евентам вроде как и неплохо. В любом случае подборка неплохая. #мероприятие

👍24🔥4❤3😱1

11 Nov 2026, 17:52 UTC≈9,750 views134 reactionsread 16 November 2026
Video

Не знаю, к чему я больше готов, к спрогнозированному 60+ лет назад на эту пятницу концу света или к откровению Луки? 😦 #видео

😁71🔥37❤11👏7💯4👍2🐳1🫡1

11 Nov 2026, 14:48 UTC≈6,190 views55 reactionsread 16 November 2026
Photo

Чего скрывать, я активно использую ИИ в своей работе. Например, с его помощью можно создавать офигенные интерактивы по ИБ. Например, на "Проверке на прочность" я такой делал по метрикам ИБ. А сегодня у меня интерактивная деловая командная игра с уникальным сценарием. Без ИИ я бы такое сам не сделал или пришлось бы заплатить немало денег разработчикам, которые бы еще и делали это все не меньше месяца. А тут вечер уход…

🔥23❤11💯7👍5🤣5👎2👌1🤔1

11 Nov 2026, 10:34 UTC≈5,960 views53 reactionsread 16 November 2026
Photo

Вдруг что-то в предверие смены колес оплаты налогов мысль пришла. Если бы я решил продать свою переписку, выдав ее за утечку, мне надо было бы уплачивать с полученного дохода НДФЛ? ЗЫ. Вопрос никак не связан со скриншотом, просто навеяло. #утечка

😁47⚡3👍1🤔1😈1

Showing the 12 most recent of 399 posts we hold for @alukatsky. 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

@alukatsky edited 4 posts 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
11 August 2026
Most recent edit
23 October 2026

Polls

The 6 most recent of 8 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

17 Oct 2026, 11:28 UTCAnonymous Poll1,350 voters approx.

Делайте ваши ставки, какое решение может быть принято? #опрос

  1. Заблокировать все иностранное38%
  2. Ввести посадки за использование в его несуверенного5%
  3. Разрешить только посконное4%
  4. Дружить с Китаем глубже5%
  5. «Бомбить Воронеж» (это мем из 2010-х, а не призыв)7%
  6. Инвестировать в развитие своего ИИ10%
  7. Украсть на дискете модели и датасеты у Qwen’а3%
  8. Запретить кибератаки, ать-два15%
  9. Ушел за грибами; потом гляну результаты12%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

26 Sept 2026, 05:11 UTCAnonymous Quiz805 voters

Если вы следите за новостями рынка ИБ и знакомились с материалами судебного дела А40-290966/2023, то как вы думаете, что согласно мнению суда сделали хакеры, которые взломали организацию и получили доступ к компьютеру гендира с электронной подписью?

  1. Использовали ПК как точку входа, после чего уничтожили всю инфраструктуру12%
  2. Украли деньги из банка, пользуясь ключом электронной подписи15%
  3. Оформили налоговую декларацию за компанию и отправили ее в ФНС17%
  4. Украли коллекцию фото и видео директора5%
  5. Ничего не сделали, так как компьютер был на Астре, а хакеры не были знакомы с этой ОС13%
  6. Пропатчили компьютер и настроили на нем механизмы ИБ15%
  7. Затрудняюсь с ответом23%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

23 Sept 2026, 13:45 UTCAnonymous Quiz1,310 voters approx.

Как называется единица измерения риска?

  1. Микроморт8%
  2. Меш8%
  3. Сантиморган4%
  4. Вар15%
  5. Рискограмм11%
  6. Бред, риск не имеет единицы измерения54%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

23 Sept 2026, 11:10 UTCAnonymous Poll419 voters

У вас есть плейбук по работе с ИИ-инцидентами (утечки через LLM, злоупотребления ИИ-агентов, кража обучающих корпусов, атаки на локальный харнесс и т.п.)? #опрос #ии

  1. Да, есть полноценный плейбук под специфичные ИИ-инциденты4%
  2. Да, но мы включили эти инциденты в типовые плейбуки5%
  3. Нет, но мы в процессе разработки/тестирования9%
  4. Нет, но мы планируем разработать их в ближайшие полгода16%
  5. Нет, и пока не планируем (не видим необходимость)34%
  6. Затрудняюсь ответить / Не мой профиль32%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

21 Sept 2026, 11:57 UTCAnonymous Poll951 voters

А вы 30 сентября какую ИБ-конфу решили посетить? #опрос

  1. GIS DAYS (Питер)4%
  2. ZeroNights (Питер)7%
  3. Онлайн-конфа по автономным SOCам (AM Live)2%
  4. Я вообще на KazHackStan поеду (Астана)12%
  5. Буду на мероприятии не из списка выше3%
  6. У меня отходняк от BIS Summit предыдущего дня запланирован2%
  7. С «Инфобез без иллюзий» еще не успею вернуться1%
  8. Мероприятие по грамотному планированию мероприятий5%
  9. А работать кто будет?64%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

11 Sept 2026, 08:30 UTCAnonymous Poll577 voters

А как у вас преимущественно строится бюджет на ИБ в 2027-м году?

  1. На основе требований бизнеса8%
  2. В соответствие с требованиями регуляторики10%
  3. Опираясь на угрозы и риски14%
  4. Хоть что-то бы дали, а там выкручиваться буду21%
  5. Бюджет? Что это? Кому-то еще и деньги на ИБ дают?31%
  6. Начальство есть – пусть оно о бюджете думает15%

Shares as published, totalling 99%. 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 399 most recent posts we hold, published 31 July 2026 to 16 November 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Кот на яблоне
@kot_na_tree · 47
3 posts
ИТ-Диалог
@ITDialog_official · 961
2 posts
Я у мамы SecMemOps
@secmemops · 5,435
2 posts
Авангард Медиа | Про ИБ и не только
@Avangardmedia · 940
1 post
HireHack
@IThirehack · 3,860
1 post
ML Seva100p0l
@ML_Sevastopol · 1
1 post
Remote Meme Execution
@RemoteMemeExecution · 1,663
1 post
SecurityLab.ru
@SecLabNews · 86,623
1 post
AI Attacks
@aiattacks · 1,125
1 post
AI SecOps
@aisecops · 1,243
1 post
Антивирусное ДНО
@avdno · 1,648
1 post
BearPass — берлога безопасности
@bearpass_news · 198
1 post
Пиэмэмим кибербез
@cyberbez_pmm · 150
1 post
Cyber Security Club Moscow
@cybersecurityclub · 654
1 post
Единая биометрическая система | 572-ФЗ
@ebs_572fz · 1,819
1 post
Fisher.Talks
@fisher_talks · 233
1 post
Fun Science
@funscience · 34,158
1 post
gbwce
@gbwcel · 47
1 post
UNLIM
@ibbezgranic · 80
1 post
Inside
@in51d3 · 7,952
1 post
Информация без опасностей (безопасность)
@infobezopasnost · 1,519
1 post
Integral Security
@integral_security · 1,712
1 post
Зоопарк из слоновой кости
@ivoryzoo · 32,078
1 post
ИнфоПовод
@kaluginprofit · 5,829
1 post
Sasha Kruasanova PROIT
@kruasanova_as · 2,184
1 post
Mobile AppSec World
@mobile_appsec_world · 8,589
1 post
NetSkills
@netskills · 4,600
1 post
ODC
@odc_kib · 40
1 post
papirsec
@papirsec · 775
1 post
Pentester
@pentester · 212
1 post
Похек meme
@poxek_meme · 798
1 post
DPO отвечает
@privacy_tech · 968
1 post
Про tech и этих
@protechietich · 20,844
1 post
Редакция
@redaktionen · 25
1 post
Избранное про ИБ
@sergeyborisov23 · 1,122
1 post
Защита персональных данных и не только
@shudrova_pdn · 1,570
1 post
какиетоновости
@stable_news · 58
1 post
Технологический Болт Генона
@tech_b0lt_Genona · 10,642
1 post
Эшер II. A+
@usher2 · 16,551
1 post
Учимся визуализировать
@visual_scheme · 202
1 post
WeLoveNoFraud
@welovenofraud · 276
1 post
SbX | Security by Xyurity
@xyuriti · 1,227
1 post
yoprstcon
@yoprstcon · 403
1 post
ЗаТелеком 🌐
@zatelecom · 64,482
1 post
⁣Злой Админ
@zloyadm_in · 232
1 post

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 45 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. The 22 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

SecurityLab.ru
@SecLabNews · 86,623
#1
Positive Technologies
@Positive_Technologies · 29,648
#2
Управление Уязвимостями и прочее
@avleonovrus · 12,653
#3
SecAtor
@true_secator · 42,222
#4
BI.ZONE
@bizone_channel · 11,635
#5
OFFZONE
@offzone_moscow · 7,539
#6
Резбез
@Rez_in_Bez · 2,642
#7
AM Live
@anti_malware · 13,158
#8
Похек
@poxek · 17,327
#9
Кибервойна
@cyberguerre · 8,922
#10
ESCalator
@ptescalator · 8,425
#11
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,141
#12
НеКасперский
@NeKaspersky · 16,229
#13
Hacker News
@HNews · 7,261
#14
Sachok
@CyberSachok · 11,358
#15
Топ кибербезопасности Батранкова
@safebdv · 10,031
#16
k8s (in)security
@k8security · 13,330
#17
Russian OSINT
@Russian_OSINT · 48,526
#18
Вакансии в ИБ | infosec
@infosec_work · 16,381
#19
AlexRedSec
@alexredsec · 4,030
#20
Positive Development Community
@POSIdev · 3,254
#21
Солар
@solar_security · 6,625
#22
CISOCLUB - кибербезопасность и ИТ
@cisoclub · 7,194
#23
infosec
@it_secur · 63,564
#24
PWN AI
@pwnai · 7,679
#25
Social Engineering
@Social_engineering · 124,636
#26
AppSec Journey
@AppSecJourney · 3,539
#27
RED Security
@redsecurity_co · 5,200
#28
YAH
@YAH_Channel · 7,638
#29
Кибербез образование | cybersecurity-roadmap.ru
@cyber_edu · 6,019
#30
Солдатов в Телеграм
@soldatov_in_telegram · 2,290
#31
Порвали два трояна
@kasperskyb2b · 9,480
#32
Хакер — Xakep.RU
@xakep_ru · 40,322
#33
Positive Events
@PositiveEvents · 6,116
#34
Мероприятия по ИБ
@InfoBezEvents · 5,702
#35
CyberCamp
@CYBERCAMP_ONLINE · 8,739
#36
Codeby
@codeby_sec · 37,076
#37
ZLONOV security
@zlonov_security · 3,986
#38
Makrushin
@makrushin · 4,092
#39
Echelon Eyes
@EchelonEyes · 6,538
#40
BESSEC
@bessec · 4,781
#41
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,367
#42
Cybred
@cybred · 11,636
#43
IT's positive investing
@positive_investing · 9,197
#44
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,052
#45
КИБЕР МЕДИА
@secmedia · 6,082
#46
Inside
@in51d3 · 7,952
#47
Kaspersky
@kasperskylab_ru · 29,326
#48
SOC FORUM | Неделя кибербезопасности
@forumsoc · 3,193
#49
Cybersecurity memes off
@cybersecurity_memes_off · 1,706
#50
Информация опасносте
@alexmakus · 18,744
#51
S.E.Reborn
@S_E_Reborn · 22,441
#52
RPPA PRO: Privacy • AI • Cybersecurity • IP
@GDPRru · 6,149
#53
APT
@APT_Notes · 17,394
#54
Аналитический центр RPPA
@Persdata · 7,736
#55
ISACARuSec
@IsacaRuSec · 2,267
#56
Евгений Касперский
@e_kaspersky · 6,613
#57
Код ИБ: ИИ & КиберБезопасность
@codeibnews · 7,020
#58
Анонсы ИБ мероприятий
@secwebinars · 6,137
#59
BIS Journal — Информационная безопасность
@BISInside · 2,271
#60
Privacy Advocates
@prv_adv · 21,819
#61
Life-Hack - Хакер
@haccking · 63,001
#62
Кибердом
@cyberdom_business · 12,782
#63
infosecurity
@tg_infosec · 26,828
#64
Blue (h/c)at Café
@bh_cat · 4,005
#65
R-Vision
@rvision_pro · 2,531
#66
Денис Лукаш | Privacy Expert
@privacyexpert · 13,399
#67
RuSecJobs Channel
@RuSecJobs · 11,632
#68
Утечки информации
@dataleak · 117,550
#69
БДУ ФСТЭК России
@bdufstecru · 10,634
#70
Раньше всех. Ну почти.
@bbbreaking · 1,975,202
#71
Information Security Memes
@infosecmemes · 9,619
#72
Минцифры России
@mintsifry · 232,126
#73
Mash
@mash · 3,138,471
#74
Банкста
@banksta · 439,853
#75
Багхантер 2.0
@bughunter_circuit · 18,687
#76
Positive Hack Days Media
@positivehackmedia · 30,000
#77
CyberSquatting RU Alerts
@CyberSquattingChannel · 2,527
#78
ГосСОПКА Центр
@sopkacentr · 6,119
#79
Эксплойт
@exploitex · 2,020,421
#80
Двач
@dvachannel · 968,751
#81
AppSec & DevSecOps Jobs
@appsec_job · 4,907
#82
DevSecOps Talks
@devsecops_weekly · 8,089
#83
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,735
#84
ИБ в "Законе"
@MetaSecurityInformation · 4,081
#85
linkmeup
@linkmeup_podcast · 17,587
#86
#ПоИБэшечка
@Poibeshechka · 1,848
#87
The After Times
@theaftertimes · 16,839
#88
PT SWARM
@ptswarm · 7,620
#89

Read from Telegram’s recommendation API, most recently 31 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Листок бюрократической защиты информации
@bureaucraticsecurity · 19,141
Telegram ranks this channel #1 of 98 here — alongside 97 others — read 4 October 2026
Positive Technologies
@Positive_Technologies · 29,648
Telegram ranks this channel #1 of 87 here — alongside 86 others — read 9 September 2026
SecurityLab.ru
@SecLabNews · 86,623
Telegram ranks this channel #1 of 90 here — alongside 89 others — read 18 August 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,367
Telegram ranks this channel #2 of 85 here — alongside 84 others — read 21 September 2026
IT и безопасность
@tg_security · 26,783
Telegram ranks this channel #2 of 91 here — alongside 90 others — read 12 September 2026
SecAtor
@true_secator · 42,222
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 29 August 2026
Kaspersky
@kasperskylab_ru · 29,326
Telegram ranks this channel #5 of 96 here — alongside 95 others — read 9 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,322
Telegram ranks this channel #5 of 83 here — alongside 82 others — read 30 August 2026
Russian OSINT
@Russian_OSINT · 48,526
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 26 August 2026
Информация опасносте
@alexmakus · 18,744
Telegram ranks this channel #6 of 85 here — alongside 84 others — read 5 October 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,735
Telegram ranks this channel #7 of 94 here — alongside 93 others — read 18 August 2026
I’m CTO, bitch
@ctobtch · 20,226
Telegram ranks this channel #8 of 95 here — alongside 94 others — read 28 September 2026
КиберДед official
@deedcoin_club · 23,016
Telegram ranks this channel #8 of 84 here — alongside 83 others — read 25 September 2026
Privacy Advocates
@prv_adv · 21,819
Telegram ranks this channel #8 of 98 here — alongside 97 others — read 22 September 2026
Пакет Безопасности
@package_security · 34,225
Telegram ranks this channel #9 of 82 here — alongside 81 others — read 4 September 2026
Codeby
@codeby_sec · 37,076
Telegram ranks this channel #9 of 76 here — alongside 75 others — read 1 September 2026
Вестник Киберполиции России
@cyberpolice_rus · 82,783
Telegram ranks this channel #9 of 92 here — alongside 91 others — read 18 August 2026
Утечки информации
@dataleak · 117,550
Telegram ranks this channel #9 of 83 here — alongside 82 others — read 14 August 2026
Investigation & Forensic TOOLS
@forensictools · 22,620
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 20 September 2026
Life-Hack - Хакер
@haccking · 63,001
Telegram ranks this channel #10 of 85 here — alongside 84 others — read 21 August 2026
infosec
@it_secur · 63,564
Telegram ranks this channel #11 of 81 here — alongside 80 others — read 22 August 2026
S.E.Reborn
@S_E_Reborn · 22,441
Telegram ranks this channel #12 of 66 here — alongside 65 others — read 20 September 2026
S.E.Book
@S_E_Book · 23,075
Telegram ranks this channel #12 of 64 here — alongside 63 others — read 19 September 2026
Интернет-Розыск
@irozysk · 45,699
Telegram ranks this channel #12 of 79 here — alongside 78 others — read 27 August 2026

This channel appears in 51 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Пост Лукацкого” (@alukatsky), 38,465 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/alukatsky.

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.