Telegram RegisterThe public register of Telegram
Telegram profile photo for S.E.Reborn

Channel

S.E.Reborn

@S_E_Reborn

On this record: Topic · Growth · Engagement · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

22,405subscribers

+16 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001179006758
TypeChannel
Username@S_E_Reborn
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live1 October 2026
Measurements held32
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/S_E_Reborn

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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

22,35522,40522,3806 August 2026 — 22,389 subscribers7 August 2026 — 22,389 subscribers8 August 2026 — 22,400 subscribers9 August 2026 — 22,395 subscribers10 August 2026 — 22,390 subscribers11 August 2026 — 22,388 subscribers12 August 2026 — 22,392 subscribers13 August 2026 — 22,389 subscribers14 August 2026 — 22,386 subscribers17 August 2026 — 22,381 subscribers18 August 2026 — 22,385 subscribers19 August 2026 — 22,382 subscribers20 August 2026 — 22,379 subscribers22 August 2026 — 22,378 subscribers23 August 2026 — 22,384 subscribers25 August 2026 — 22,386 subscribers26 August 2026 — 22,380 subscribers27 August 2026 — 22,381 subscribers28 August 2026 — 22,384 subscribers29 August 2026 — 22,387 subscribers30 August 2026 — 22,384 subscribers31 August 2026 — 22,373 subscribers1 September 2026 — 22,365 subscribers2 September 2026 — 22,362 subscribers3 September 2026 — 22,363 subscribers4 September 2026 — 22,358 subscribers8 September 2026 — 22,355 subscribers11 September 2026 — 22,367 subscribers14 September 2026 — 22,368 subscribers16 September 2026 — 22,365 subscribers18 September 2026 — 22,374 subscribers1 October 2026 — 22,405 subscribers6 August 20261 October 2026
32 measurements spanning 56 days, net +16. 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 22,348–22,413 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
1 Oct 2026, 23:1522,405+31
18 Sept 2026, 14:2022,374+9
16 Sept 2026, 07:5922,365-3
14 Sept 2026, 12:4122,368+1
11 Sept 2026, 00:2122,367+12
8 Sept 2026, 01:5922,355-3
4 Sept 2026, 21:1522,358-5
3 Sept 2026, 09:0622,363+1
2 Sept 2026, 03:1622,362-3
1 Sept 2026, 02:1322,365-8
31 Aug 2026, 02:1422,373-11
30 Aug 2026, 02:3822,384-3
29 Aug 2026, 03:4222,387+3
28 Aug 2026, 02:2222,384+3
27 Aug 2026, 02:3622,381+1
26 Aug 2026, 02:2622,380-6
25 Aug 2026, 04:4322,386+2
23 Aug 2026, 23:3922,384+6
22 Aug 2026, 05:5922,378-1
20 Aug 2026, 20:3422,379first reading

Engagement

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

ERR · 30 days
5.55%
avg views ÷ 22,405 subscribers
Avg views / post
1,240
32 posts measured
Reaction rate
0.337%
reactions ÷ views · ER floor
Posts in window
32
of 97 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 23 of 32 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 September 2026
Posts held97 (28 July 2026 – 30 September 2026)
Views total39,825
Reactions total98
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Oct 2026, 08:09 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

313 reactions across 75 posts, in 26 distinct kinds. The most used accounts for 40.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤12640.3%
🤣3410.9%
😁3310.5%
🔥227.03%
⚡113.51%
✍113.51%
💊113.51%
😭113.51%
🆒72.24%
👀61.92%
☃51.60%
😱51.60%
🤯51.60%
😐41.28%
😢41.28%
❤‍🔥30.958%
🐳20.639%
👌20.639%
💯20.639%
🙉20.639%
6 further kinds72.24%

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 79 of the 97 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 313 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 97 most recent posts we hold, published 28 July 2026 to 30 September 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
5.15%
5 of 97 posts carry an ad marker
Regulatory tokens
5
posts carrying an erid · 5 distinct tokens
Median views · ads
1,350
over 5 measured posts
Median views · rest
1,380
over 92 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqv8Aft7126 August 202626 August 2026
2W5zFH22wrR121 September 202621 September 2026
2W5zFJRG8xR125 September 202625 September 2026
2W5zFJhD8zV111 August 202611 August 2026
2W5zFJyvXiR12 September 20262 September 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 97 most recent posts we hold, published 28 July 2026 to 30 September 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.

Recent posts

30 Sept 2026, 11:33 UTC711 views1 reactionsread 1 October 2026

👩‍💻 ++ 101 Linux commands. • Объемная книга (CheatSheet) для изучения командной строки Linux. Материал пригодиться не только начинающим, но и опытным пользователям Linux. Содержание следующее: • Basics; - File Hierarchy Standard (FHS); - Commands; • Disk and File System Management; - General Disk Manipulation (non-LVM); - Globs (Wildcards); - Regex; - Stream redirection; • Text Readers & Editors; - Less…

✍1

30 Sept 2026, 10:38 UTC711 views13 reactionsread 1 October 2026
Photo

• В даркнете случилась настоящая драма: администратор форума Prime Market опубликовал объявление для всех своих пользователей, что если они не заплатят по 100 баксов до 1 октября, то он сольет их данные. • Судя по объявлению, админ планирует слить имена, адреса и историю заказов. Требования касаются всех участников форума - как продавцов, так и покупателей. • Забавно, но ранее админы форума сообщали, что они не …

🤣10🐳2😁1

29 Sept 2026, 18:10 UTC888 viewsread 1 October 2026
Forwarded from @true_secator

Новый вариант атаки Spectre v2 - Branch Target Reuse (BTR), позволяет восстанавливать хэши паролей root с компьютеров Intel под управлением Linux всего за несколько минут. Атака BTR использует устаревшую информацию в алгоритме предсказания ветвлений процессора после того, как JIT-компилятор повторно использует память для нового кода. Манипулируя этой остаточной информацией, злоумышленник может обмануть процессор, з…

29 Sept 2026, 11:33 UTC≈1,000 views3 reactionsread 1 October 2026

🕷 Неуловимый баг. • Случай, о котором пойдет речь, произошел в 2008 году. Во время разработки первой части игры LittleBigPlanet — оригинального паззл-платформера, который должен быть стать эксклюзивом для PlayStation 3 — разработчикам компании пришлось столкнуться с воистину неуловимым багом. • Обычно для получения «зелёного света» на выпуск игры на консолях требуется пройти сертификацию — выполнить некоторый наб…

❤3

28 Sept 2026, 20:39 UTC≈1,090 views9 reactionsread 1 October 2026
Photo

• Хакеры, которые ранее взломали туроператора Tez Tour, сообщили о взломе Додо Пиццы. Тем временем Додо подтвердили информацию о кибератаке, но никаких подробностей от них пока нет. • В свою очередь хакеры пишут, что выкачали данные 68 млн. клиентов на несколько терабайт: (ФИО, дату рождения, телефон, адреса проживания, заказы и почтовые адреса). • Будем ждать более детальную информацию об инциденте от Додо. #Н…

😁5✍2🔥2

28 Sept 2026, 14:38 UTC≈1,020 views3 reactionsread 1 October 2026
Forwarded from @true_secator

Google в лице Mandiant и GTIG предупреждает о новой массовой кампании ShinyHunters, которой удалось модифицироваnm свой эксплойт для новых атак, нацеленных на уязвимость PeopleSoft. Комплексное ПО для планирования ресурсов предприятия (ERP) PeopleSoft используется во многих крупных компаниях для управления основными бизнес-функциями, включая финансы, управление персоналом, расчет заработной платы и цепочку поставок.…

❤3

28 Sept 2026, 11:33 UTC≈1,040 views2 reactionsread 1 October 2026

🖥 Краткая история «синего экрана смерти». • Более молодые пользователи ПК представления не имеют о том, насколько распространён был раньше этот сеющий панику экран, или что он означал. Всё, над чем вы работали, пропадало, ваш компьютер требовал перезагрузки — тогда это могло занять и десять минут. По сию пору BSoD — узнаваемый символ чего-то не работающего, но зачем он вообще появился? • В Windows 3.1 не было BSo…

❤2

27 Sept 2026, 11:33 UTC≈1,260 views2 reactionsread 1 October 2026

👾 Вредоносное ПО, вошедшее в историю. Form — 1990 год. • Вирус из Швейцарии, заражавший загрузочный сектор вместо главной загрузочной записи. При загрузке компьютера из зараженного сектора Form становился резидентным, захватывая таблицу векторов прерываний. Далее оригинальный загрузочный сектор (в котором и прятался вирус) помечался как неисправный. Вирус заражал любые носители, которые взаимодействовали с инфициро…

❤2

26 Sept 2026, 11:33 UTC≈1,360 viewsread 1 October 2026
Photo

👨‍💻 Attacking Policy. • Open Policy Agent — это open-source-инструмент контроля доступа, основанный на политиках, который создан в 2016 году и с тех пор стабильно развивается. Сейчас он входит в каталог дипломированных проектов Cloud Native Computing Foundation (CNCF). Его используют Netflix, Pinterest, TripAdvisor и другие компании. • В этой статье перечислены определенные векторы атак, которые могут быть вызван…

25 Sept 2026, 13:11 UTC≈1,390 views5 reactionsread 1 October 2026
Photo

🃏 В чём истинное предназначение «Косынки» и «Сапёра». • Пасьянс «Косынка», «Свободная ячейка» и «Сапёр» — популярные игры, которые входят в базовый комплект Windows. Это довольно простые, но увлекательные игры: некоторые люди готовы часами играть, не отрываясь. Но мало кто знает, с какой целью их разработали. • Самая старая из перечисленных «Косынка» появилась в версии Windows 3.0 в 1990 году. Хотя эту игру приду…

❤4❤‍🔥1

25 Sept 2026, 10:04 UTC≈1,350 views3 reactionsread 1 October 2026
Advertisementerid 2W5zFJRG8xRPhoto

🧮 Больше ядер — не всегда быстрее. Иногда это просто больше счетов за электричество Раньше сервер выбирали как арбуз: чем больше, тем лучше. С Intel Xeon 6 так уже не работает — ядра теперь трех характеров, и «взять с запасом» слишком часто значит переплатить. ➡️ P-ядра — спринтеры: быстрые на поток, держат отклик в базах и аналитике, но прожорливые. ➡️ E-ядра берут числом — поодиночке скромные, зато их много и они …

❤3

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

@S_E_Reborn 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
12 August 2026
Most recent edit
12 August 2026

Forward network

Republished by

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

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 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.

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.

Social Engineering
@Social_engineering · 125,007
#1
infosec
@it_secur · 62,112
#2
S.E.Book
@S_E_Book · 23,146
#3
SecAtor
@true_secator · 41,748
#4
SecurityLab.ru
@SecLabNews · 84,654
#5
Cybred
@cybred · 11,118
#6
Похек
@poxek · 16,849
#7
Codeby
@codeby_sec · 37,041
#8
infosecurity
@tg_infosec · 26,779
#9
Russian OSINT
@Russian_OSINT · 47,943
#10
APT
@APT_Notes · 16,685
#11
Пост Лукацкого
@alukatsky · 37,915
#12
Life-Hack - Хакер
@haccking · 63,183
#13
Investigation & Forensic TOOLS
@forensictools · 22,417
#14
Лаборатория хакера
@lab_hack · 25,556
#15
no system is safe // cybersec
@nsis_cybersec · 21,518
#16
Хакер — Xakep.RU
@xakep_ru · 39,610
#17
Архив Безопасника
@secure_archive · 10,833
#18
Чёрный Треугольник
@black_triangle_tg · 63,850
#19
Управление Уязвимостями и прочее
@avleonovrus · 12,122
#20
YAH
@YAH_Channel · 7,569
#21
Order of Six Angles
@orderofsixangles · 5,378
#22
k8s (in)security
@k8security · 13,151
#23
T.Hunter
@tomhunter · 14,226
#24
SecuriXy.kz
@securixy_kz · 10,202
#25
BI.ZONE
@bizone_channel · 11,270
#26
Admin Guides | Сисадмин
@admguides · 11,942
#27
Hacker News
@HNews · 7,280
#28
Записки Безопасника
@infosec_globe · 18,074
#29
ИБ Книга | Библиотека ИБ
@itbook_library · 15,826
#30
ZeroDay | Кибербезопасность
@cybersec_academy · 42,833
#31
Серверная Админа | Компьютерные сети
@school_network · 26,588
#32
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,381
#33
AP Security
@ap_security · 3,981
#34
Blue (h/c)at Café
@bh_cat · 3,968
#35
Белый хакер
@bezopasno_soft · 29,652
#36
PWN AI
@pwnai · 7,375
#37
Positive Technologies
@Positive_Technologies · 29,062
#38
CyberINS // Лаборатория ИБешника
@cyberins · 11,425
#39
Бункер Хакера
@book_academ · 21,429
#40
Пакет Безопасности
@package_security · 33,011
#41
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,557
#42
AM Live
@anti_malware · 13,154
#43
НеКасперский
@NeKaspersky · 16,061
#44
КИБЕР МЕДИА
@secmedia · 5,902
#45
Mr. Robot
@elliot_cybersec · 38,917
#46
Утечки информации
@dataleak · 119,057
#47
Open Source
@open_source_friend · 52,304
#48
OFFZONE
@offzone_moscow · 7,400
#49
vx-underground
@vxunderground · 52,210
#50
Inside
@in51d3 · 8,013
#51
SHADOW:Group
@shadow_group_tg · 11,482
#52
Вакансии в ИБ | infosec
@infosec_work · 15,755
#53
Offensive Xwitter
@OffensiveTwitter · 21,041
#54
Эксплойт
@exploitex · 2,048,279
#55
PRO:PENTEST
@pro_pentest · 10,108
#56
Information Security Memes
@infosecmemes · 9,677
#57
RuSecJobs Channel
@RuSecJobs · 11,387
#58
Кладовка Pavlu
@KladovkaPavlu · 65,054
#59
Kali Linux
@linuxkalii · 55,412
#60
PurpleBear
@purple_medved · 4,627
#61
AlexRedSec
@alexredsec · 4,008
#62
The Bug Bounty Hunter
@thebugbountyhunter · 51,082
#63
быдло.jazz
@tvoijazz · 11,784
#64
♻️ Переходник ♻️
@bughunter_circuit · 10
#65
r0 Crew (Channel)
@R0_Crew · 8,962
#66

Read from Telegram’s recommendation API, most recently 20 September 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.

S.E.Book
@S_E_Book · 23,146
Telegram ranks this channel #1 of 64 here — alongside 63 others — read 19 September 2026
infosec
@it_secur · 62,112
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 22 August 2026
Investigation & Forensic TOOLS
@forensictools · 22,417
Telegram ranks this channel #5 of 74 here — alongside 73 others — read 20 September 2026
Social Engineering
@Social_engineering · 125,007
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 13 August 2026
PulSe
@Pulsechanel · 19,875
Telegram ranks this channel #6 of 69 here — alongside 68 others — read 29 September 2026
infosecurity
@tg_infosec · 26,779
Telegram ranks this channel #6 of 74 here — alongside 73 others — read 11 September 2026
Life-Hack - Хакер
@haccking · 63,183
Telegram ranks this channel #7 of 85 here — alongside 84 others — read 21 August 2026
no system is safe // cybersec
@nsis_cybersec · 21,518
Telegram ranks this channel #8 of 71 here — alongside 70 others — read 23 September 2026
Лаборатория хакера
@lab_hack · 25,556
Telegram ranks this channel #10 of 71 here — alongside 70 others — read 14 September 2026
SecAtor
@true_secator · 41,748
Telegram ranks this channel #10 of 78 here — alongside 77 others — read 29 August 2026
Этичный Хакер
@hack_less · 233,911
Telegram ranks this channel #11 of 81 here — alongside 80 others — read 12 August 2026
Бункер Хакера
@book_academ · 21,429
Telegram ranks this channel #12 of 72 here — alongside 71 others — read 23 September 2026
Codeby
@codeby_sec · 37,041
Telegram ranks this channel #12 of 76 here — alongside 75 others — read 1 September 2026
Серверная Админа | Компьютерные сети
@school_network · 26,588
Telegram ranks this channel #13 of 85 here — alongside 84 others — read 12 September 2026
Russian OSINT
@Russian_OSINT · 47,943
Telegram ranks this channel #13 of 82 here — alongside 81 others — read 26 August 2026
BZD • Книги для программистов
@bzd_channel · 36,402
Telegram ranks this channel #14 of 57 here — alongside 56 others — read 1 September 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,557
Telegram ranks this channel #16 of 85 here — alongside 84 others — read 13 September 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,833
Telegram ranks this channel #16 of 70 here — alongside 69 others — read 29 August 2026
Хакер — Xakep.RU
@xakep_ru · 39,610
Telegram ranks this channel #17 of 83 here — alongside 82 others — read 30 August 2026
Интернет-Розыск
@irozysk · 45,953
Telegram ranks this channel #17 of 79 here — alongside 78 others — read 27 August 2026
TechNews
@techlucker · 43,532
Telegram ranks this channel #20 of 79 here — alongside 78 others — read 28 August 2026
SecurityLab.ru
@SecLabNews · 84,654
Telegram ranks this channel #21 of 90 here — alongside 89 others — read 18 August 2026
Кладовка Pavlu
@KladovkaPavlu · 65,054
Telegram ranks this channel #23 of 76 here — alongside 75 others — read 4 September 2026
Белый хакер
@bezopasno_soft · 29,652
Telegram ranks this channel #24 of 78 here — alongside 77 others — read 8 September 2026

This channel appears in 57 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 1 October 2026 — this entry's latest reading, not the date you are reading this.

“S.E.Reborn” (@S_E_Reborn), 22,405 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/S_E_Reborn.

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.