Telegram RegisterThe public register of Telegram
Telegram profile photo for Серверная Админа | Компьютерные сети

Channel

Серверная Админа | Компьютерные сети

@school_network

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

26,560subscribers

-209 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001595432650
TypeChannel
Username@school_network
DescriptionЯ действующий сетевой инженер, расскажу вам о сетях в доступной форме. Реклама - @bashmak_media Мы на бирже: https://telega.in/c/school_network РКН: https://vk.cc/cHYqt5
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/school_network

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 100% 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

26,56026,77026,6657 August 2026 — 26,769 subscribers7 August 2026 — 26,770 subscribers8 August 2026 — 26,765 subscribers9 August 2026 — 26,759 subscribers10 August 2026 — 26,751 subscribers11 August 2026 — 26,743 subscribers12 August 2026 — 26,735 subscribers13 August 2026 — 26,738 subscribers14 August 2026 — 26,735 subscribers15 August 2026 — 26,727 subscribers17 August 2026 — 26,723 subscribers18 August 2026 — 26,718 subscribers19 August 2026 — 26,710 subscribers20 August 2026 — 26,707 subscribers21 August 2026 — 26,703 subscribers22 August 2026 — 26,702 subscribers24 August 2026 — 26,704 subscribers25 August 2026 — 26,703 subscribers26 August 2026 — 26,695 subscribers28 August 2026 — 26,682 subscribers29 August 2026 — 26,684 subscribers30 August 2026 — 26,675 subscribers31 August 2026 — 26,667 subscribers1 September 2026 — 26,660 subscribers2 September 2026 — 26,655 subscribers3 September 2026 — 26,650 subscribers5 September 2026 — 26,662 subscribers9 September 2026 — 26,671 subscribers11 September 2026 — 26,660 subscribers13 September 2026 — 26,658 subscribers15 September 2026 — 26,647 subscribers17 September 2026 — 26,634 subscribers19 September 2026 — 26,624 subscribers26 September 2026 — 26,588 subscribers4 October 2026 — 26,560 subscribers7 August 20264 October 2026
35 measurements spanning 58 days, net -209. 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 26,529–26,802 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
4 Oct 2026, 14:0126,560-28
26 Sept 2026, 10:2126,588-36
19 Sept 2026, 14:2026,624-10
17 Sept 2026, 00:3726,634-13
15 Sept 2026, 04:3826,647-11
13 Sept 2026, 16:1726,658-2
11 Sept 2026, 18:0226,660-11
9 Sept 2026, 07:5826,671+9
5 Sept 2026, 23:3826,662+12
3 Sept 2026, 22:2226,650-5
2 Sept 2026, 13:3426,655-5
1 Sept 2026, 14:0426,660-7
31 Aug 2026, 17:2626,667-8
30 Aug 2026, 18:4626,675-9
29 Aug 2026, 20:5526,684+2
28 Aug 2026, 21:1626,682-13
26 Aug 2026, 18:3226,695-8
25 Aug 2026, 15:0526,703-1
24 Aug 2026, 17:0626,704+2
22 Aug 2026, 23:3626,702first reading

Engagement

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

ERR · 30 days
10.2%
avg views ÷ 26,560 subscribers
Avg views / post
2,720
28 posts measured
Reaction rate
0.404%
reactions ÷ views · ER floor
Posts in window
28
of 73 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 26 of 28 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 6 October 2026
Posts held73 (20 July 2026 – 6 October 2026)
Views total76,069
Reactions total295
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 18:44 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
≈1,290
Videos
≈8
Links
≈1,400

Lifetime counters from Telegram’s own channel header, read 6 October 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.

Reaction mix

911 reactions across 68 posts, in 27 distinct kinds. The most used accounts for 36.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍32936.1%
❤15216.7%
🔥14315.7%
😁10411.4%
😭363.95%
💯353.84%
✍222.41%
🌚171.87%
👏90.988%
👾90.988%
🤨70.768%
💅60.659%
💘60.659%
👌50.549%
👨‍💻50.549%
🤪50.549%
⚡40.439%
👀40.439%
🕊30.329%
🗿20.22%
7 further kinds80.878%

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

Measured over the 73 most recent posts we hold, published 20 July 2026 to 6 October 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
3
across the posts below
Posts paid on
2
of 73 we hold a reading for · 3%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @school_network. 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 73 most recent posts we hold for this entry, published 20 July 2026 to 6 October 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.

Advertising

Ad load
4.11%
3 of 73 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
2,460
over 3 measured posts
Median views · rest
3,170
over 70 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
eridPostsFirst seenLast seen
2VtzqvEduEL12 October 20262 October 2026
2VtzqxJ7bjz124 September 202624 September 2026
2W5zFHkZgNM131 July 202631 July 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 73 most recent posts we hold, published 20 July 2026 to 6 October 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

6 Oct 2026, 16:00 UTC519 viewsread 6 October 2026
Photo

👋 Привет, сетевой друг! Сегодня про Network Doctor - TUI для диагностики сети, который пытается не просто показать пачку вывода от ping, dig и curl, а найти место, где именно ломается соединение. 🟣Запускаете: netdoc github.com И инструмент последовательно проверяет DNS, TCP, TLS и HTTP, связывая результаты между собой. Если DNS не работает, зависимые проверки не запускаются, а итог прямо говорит, что проблема в р…

6 Oct 2026, 07:00 UTC≈1,410 views7 reactionsread 6 October 2026
Photo

Как хаотичные подсети убивают масштабируемость В статье показывают, как случайные /24, пересекающиеся диапазоны и адресация «как получилось» годами копят проблемы, а потом взрываются при росте или слиянии компаний. Разбирают, почему двойной NAT не спасает, и как нормальная иерархия адресов помогает не превращать расширение сети в многонедельный квест. Серверная Админа | Zeroday | #Статья

🔥7

3 Oct 2026, 09:20 UTC≈2,360 views2 reactionsread 6 October 2026
Poll

Почему STP блокирует один из избыточных L2-путей?

  1. Чтобы выбрать кратчайший IP-маршрут11%
  2. Чтобы избежать Ethernet-петель77%
  3. Чтобы уменьшить размер ARP8%
  4. Чтобы распределить DHCP-запросы3%

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

❤2

2 Oct 2026, 11:38 UTC≈2,400 views11 reactionsread 6 October 2026
Video

👋 Привет, сетевой друг! Ещё три функции MikroTik, которые легко пропустить, пока не столкнёшься с конкретной задачей. 🟣Connection Tracking Helpers - когда роутер понимает протокол RouterOS умеет подключать helpers для некоторых протоколов, где одного IP/порта недостаточно, чтобы нормально отслеживать соединения. Например, FTP может открывать дополнительные соединения для передачи данных. Helper анализирует управляю…

👍6❤4🔥1

2 Oct 2026, 07:00 UTC≈2,090 views0 reactionsread 6 October 2026
Advertisementerid 2VtzqvEduELPhoto

Для тех, кто работает с Kubernetes и облачной инфраструктурой, в октябре намечается отличный повод выбраться из рабочих чатов и встретиться офлайн 👀 Обсудим: – как пройти путь от бизнес-требования к ядру Linux – как дать агенту управление кластером вашей инфраструктуры – как в MWS Cloud Platform доставляют системный софт в managed K8s – мультитенантность в Kubernetes-платформе — «Проект вместо namespace» – как работ…

1 Oct 2026, 15:52 UTC≈1,890 views12 reactionsread 6 October 2026
Photo

👋 Привет, сетевой друг! Сегодня про UUCP - протокол и набор утилит, через которые Unix-машины десятилетиями обменивались файлами, почтой и командами задолго до привычного нам интернета. 🟣Название расшифровывается как Unix-to-Unix Copy. Изначально идея была максимально простой: одна машина звонит другой по модему, устанавливает соединение и передаёт задания. Никаких постоянных TCP-соединений. Машины могли вообще не …

👍6🔥4❤2

30 Sept 2026, 12:25 UTC≈1,870 views14 reactionsread 6 October 2026
Video

👋 Привет, сетевой друг! Давай разберём несколько TCP-флагов и состояний, которые особенно полезны, когда смотришь трафик в Wireshark и пытаешься понять, где именно всё сломалось. 🟣SYN без SYN-ACK Клиент отправляет Client → Server SYN Client → Server SYN Client → Server SYN а ответа нет. Это ещё не значит «сервер лежит». SYN мог потеряться, его мог отбросить файрвол, либо обратный маршрут сломан. Поэтому сле…

🔥10❤4

29 Sept 2026, 09:24 UTC≈1,960 views4 reactionsread 6 October 2026
Photo

👋 Привет, сетевой друг! Сегодня про webcensus - инструмент для довольно специфичной задачи: найти один и тот же URL-путь сразу на огромном количестве сайтов. 🟣Например, хочется понять, кто вообще публикует /.well-known/security.txt, robots.txt, ads.txt или sitemap.xml. Перебирать сайты по одному здесь явно не вариант. 🟣webcensus собирает это в конвейер из нескольких этапов: список доменов ↓ DNS ↓ …

👍4

28 Sept 2026, 14:06 UTC≈2,460 viewsread 6 October 2026
Photo

Почему SAML снова и снова ломается на одном и том же месте? SAML больше 20 лет отвечает за корпоративный SSO, но исследователи до сих пор находят способы обходить его защиту. В статье разбирают, как XML-комментарии, особенности парсеров и канонизация позволяют подменять подписанные данные так, что проверка проходит, а приложение получает уже другое содержимое. 🟣Разбирают пять проблем протокола: сложность XML, канон…

26 Sept 2026, 06:25 UTC≈3,030 views38 reactionsread 6 October 2026
Photo

👨‍💻Серверная Админа | #мем

💯21😭12😁3❤2

25 Sept 2026, 14:59 UTC≈2,870 views12 reactionsread 6 October 2026
Photo

👋 Привет, сетевой друг! Сегодня про Ethernet, который мы привыкли воспринимать как обычный кабельный LAN. Но за ним давно стоит целый набор технологий, которые позволяют гонять трафик на десятки и сотни гигабит. 🟣Сначала был 10BASE-T: В классическом Ethernet по витой паре использовались 10 Мбит/с и обычная схема с хабами. Несколько устройств делили один collision domain и решали, кто сейчас может передавать, через …

👍7💘4🔥1

24 Sept 2026, 15:31 UTC≈2,360 views8 reactionsread 6 October 2026
Video

👋 Привет, сетевой друг! Собрал три способа прокачать защиту MikroTik - особенно если роутеров уже несколько и хочется меньше ручной работы… 🟣Автоматически обновлять блок-листы через RouterOS API + Python: Когда роутеров десятки, заходить на каждый и вручную добавлять подозрительные IP - сомнительное удовольствие. Через API можно централизованно обновлять address-list и быстро распространять блокировки на весь парк:…

👍4❤3💘1

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

Polls

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

3 Oct 2026, 09:20 UTCAnonymous Quiz731 voters

Почему STP блокирует один из избыточных L2-путей?

  1. Чтобы выбрать кратчайший IP-маршрут11%
  2. Чтобы избежать Ethernet-петель77%
  3. Чтобы уменьшить размер ARP8%
  4. Чтобы распределить DHCP-запросы3%

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

12 Sept 2026, 14:30 UTCAnonymous Quiz604 voters

Маршрутизатор получает маршрут по OSPF и такой же префикс по eBGP. Какой маршрут обычно попадёт в RIB?

  1. OSPF, потому что IGP всегда приоритетнее34%
  2. eBGP, потому что его AD ниже29%
  3. OSPF, если его metric ниже25%
  4. Выбирается случайно при равных prefix length12%

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

23 Aug 2026, 11:51 UTCAnonymous Quiz627 voters

Какой протокол используется для управления подписками на IPv6 multicast-группы?

  1. IGMP38%
  2. MLD23%
  3. PIM-SM22%
  4. RSVP17%

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

22 Aug 2026, 14:17 UTCAnonymous Quiz471 voters

Что произойдёт с iBGP без Route Reflector?

  1. Все маршруты станут eBGP35%
  2. Потребуется full mesh39%
  3. OSPF создаст соседства16%
  4. MED станет обязательным9%

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

25 Jul 2026, 09:00 UTCAnonymous Quiz577 voters

Что проверяет механизм ASLR?

  1. Права пользователей19%
  2. Случайное размещение памяти39%
  3. Сетевые соединения27%
  4. Целостность файлов15%

Shares as published. 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 73 most recent posts we hold, published 20 July 2026 to 6 October 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.

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

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.

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.

Admin Guides | Сисадмин
@admguides · 11,960
#1
infosec
@it_secur · 62,254
#2
Social Engineering
@Social_engineering · 124,999
#3
Network Admin
@networkadm · 12,361
#4
ZeroDay | Кибербезопасность
@cybersec_academy · 42,827
#5
Сетевик Джонни // Network Admin
@iscode · 5,787
#6
ServerAdmin.ru
@srv_admin · 32,593
#7
BashMaster
@bash_help · 8,853
#8
Не хакинг, а ИБ
@searchack · 18,204
#9
Белый хакер
@bezopasno_soft · 29,634
#10
Bash Days | Linux | DevOps
@bashdays · 23,640
#11
Типичный Сисадмин
@sysodmins · 38,258
#12
S.E.Reborn
@S_E_Reborn · 22,399
#13
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,522
#14
Лига сисадминов
@sysodmins_league · 13,279
#15
IT-KB 🤖
@ITKB_channel · 7,997
#16
Архив Безопасника
@secure_archive · 10,977
#17
Системный администратор
@i_odmin · 26,681
#18
Kali Linux
@linuxkalii · 55,481
#19
NetworkAdmin.ru
@networkadminru · 4,704
#20
no system is safe // cybersec
@nsis_cybersec · 21,516
#21
Linux
@linux_sup · 7,429
#22
S.E.Book
@S_E_Book · 23,139
#23
INSPECTOR | OSINT
@it_fullstak · 10,926
#24
Типичный Сисадмин
@tipsysdmin · 6,287
#25
Linux / Линукс
@linux_gram · 13,704
#26
CyberINS // Лаборатория ИБешника
@cyberins · 11,609
#27
Похек
@poxek · 16,928
#28
Life-Hack - Хакер
@haccking · 63,140
#29
DevOps School | Linux, InfoSec, ИБ
@devops_sc · 14,824
#30
Linux для чайника
@os_linux_ru · 19,602
#31
Системный администратор - Сетевые технологии - Компьютерная помощь
@sysadmin1 · 8,348
#32
Системный Администратор (Сисадмин)
@sysadminof · 14,288
#33
Linux Academy
@linuxacademiya · 28,459
#34
WindowsITPro - winitpro.ru
@winitpro_ru · 9,267
#35
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,450
#36
📚Системный Администратор (RTFM)
@IT_obrazovach · 6,714
#37
Пост Лукацкого
@alukatsky · 37,955
#38
DevOps
@i_DevOps · 8,820
#39
IT-Мемасы от Эникея
@itmemas · 10,028
#40
DevOps MemOps
@devops_memops · 6,340
#41
Linux Education
@linux_education · 11,106
#42
[PYTHON:TODAY]
@python2day · 63,715
#43
LinuxCamp | DevOps
@linuxcamp_tg · 13,582
#44
DevOps
@DevOPSitsec · 23,671
#45
Rick Academy — Хакинг и Кибербезопасность
@RickAcademy · 2,621
#46
IT Portal
@IT_Portal · 99,777
#47
Бункер Хакера
@book_academ · 21,410
#48
infosecurity
@tg_infosec · 26,761
#49
Mr. Robot
@elliot_cybersec · 38,849
#50
Записки Безопасника
@infosec_globe · 18,057
#51
SecurityLab.ru
@SecLabNews · 84,790
#52
Network Quiz
@network_quiz · 7,254
#53
Лаборатория хакера
@lab_hack · 25,611
#54
Codeby
@codeby_sec · 37,047
#55
Записки IT специалиста
@interface31 · 8,993
#56
MikroTik-сэнсэй
@mikrotik_sensei · 19,556
#57
Сетевой архитектор
@net_arch · 7,428
#58
linkmeup
@linkmeup_podcast · 17,446
#59
PyLinux - Всё о Linux, Python и IT
@pylinux0 · 11,043
#60
Арсенал Безопасника
@arsenal_security · 15,167
#61
SecAtor
@true_secator · 41,782
#62
Open Source
@open_source_friend · 52,333
#63
Пакет Безопасности
@package_security · 33,048
#64
White Hat
@kind_hack · 12,028
#65
ИБ Книга | Библиотека ИБ
@itbook_library · 15,974
#66
Useful Tools | Linux | GitOps | DevOps
@gitgate · 6,780
#67
RECURA | Программирование & IT
@recura_tech · 14,657 (as read 12 September 2026)
#68
Zabbix Recipes
@zabbix_ru · 3,629
#69
Хакер — Xakep.RU
@xakep_ru · 39,722
#70
Чёрный Треугольник
@black_triangle_tg · 63,815
#71
Архив Программиста
@storage_it · 8,723
#72
Russian OSINT
@Russian_OSINT · 47,997
#73
GitHub Community
@github · 155,595
#74
Утечки информации
@dataleak · 118,872
#75
Хабр
@habr_com · 132,847
#76
DevOps | Вопросы собесов
@easy_devops · 5,574
#77
Programmer & IT Memes
@itmemes · 122,995
#78
InfoSec Community
@infosec_tg · 10,330
#79
PRO:PENTEST
@pro_pentest · 10,127
#80
Мониторим ИТ
@monitorim_it · 8,534
#81
Вакансии в ИБ | infosec
@infosec_work · 15,847
#82
Эксплойт
@exploitex · 2,048,192
#83
Бэкдор
@whackdoor · 1,586,239
#84
Physics.Math.Code
@physics_lib · 146,792
#85

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

ZeroDay | Кибербезопасность
@cybersec_academy · 42,827
Telegram ranks this channel #8 of 70 here — alongside 69 others — read 29 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,522
Telegram ranks this channel #12 of 85 here — alongside 84 others — read 13 September 2026
Linux для чайника
@os_linux_ru · 19,602
Telegram ranks this channel #16 of 87 here — alongside 86 others — read 1 October 2026
Книги для Системного Администратора
@i_odmin_book · 18,737
Telegram ranks this channel #18 of 83 here — alongside 82 others — read 5 October 2026
Белый хакер
@bezopasno_soft · 29,634
Telegram ranks this channel #19 of 78 here — alongside 77 others — read 8 September 2026
MikroTik-сэнсэй
@mikrotik_sensei · 19,556
Telegram ranks this channel #20 of 92 here — alongside 91 others — read 1 October 2026
Системный администратор
@i_odmin · 26,681
Telegram ranks this channel #20 of 89 here — alongside 88 others — read 12 September 2026
ServerAdmin.ru
@srv_admin · 32,593
Telegram ranks this channel #20 of 96 here — alongside 95 others — read 5 September 2026
Bash Days | Linux | DevOps
@bashdays · 23,640
Telegram ranks this channel #22 of 94 here — alongside 93 others — read 18 September 2026
Типичный Сисадмин
@sysodmins · 38,258
Telegram ranks this channel #24 of 93 here — alongside 92 others — read 31 August 2026
Kali Linux
@linuxkalii · 55,481
Telegram ranks this channel #25 of 89 here — alongside 88 others — read 23 August 2026
infosec
@it_secur · 62,254
Telegram ranks this channel #27 of 81 here — alongside 80 others — read 22 August 2026
Linux Academy
@linuxacademiya · 28,459
Telegram ranks this channel #28 of 84 here — alongside 83 others — read 9 September 2026
S.E.Reborn
@S_E_Reborn · 22,399
Telegram ranks this channel #32 of 66 here — alongside 65 others — read 20 September 2026
no system is safe // cybersec
@nsis_cybersec · 21,516
Telegram ranks this channel #33 of 71 here — alongside 70 others — read 23 September 2026
S.E.Book
@S_E_Book · 23,139
Telegram ranks this channel #33 of 64 here — alongside 63 others — read 19 September 2026
Social Engineering
@Social_engineering · 124,999
Telegram ranks this channel #33 of 82 here — alongside 81 others — read 13 August 2026
Этичный Хакер
@hack_less · 240,669
Telegram ranks this channel #35 of 81 here — alongside 80 others — read 12 August 2026
Device
@device24 · 21,474
Telegram ranks this channel #40 of 52 here — alongside 51 others — read 23 September 2026
Selectel
@Selectel · 63,091
Telegram ranks this channel #40 of 96 here — alongside 95 others — read 21 August 2026
Windows Club | КДЧ
@pcTeapot · 39,539
Telegram ranks this channel #41 of 53 here — alongside 52 others — read 30 August 2026
Mr. Robot
@elliot_cybersec · 38,849
Telegram ranks this channel #44 of 70 here — alongside 69 others — read 31 August 2026
Бункер Хакера
@book_academ · 21,410
Telegram ranks this channel #45 of 72 here — alongside 71 others — read 23 September 2026
remontka.pro ✅
@remontka_pro · 26,206
Telegram ranks this channel #50 of 77 here — alongside 76 others — read 13 September 2026

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

“Серверная Админа | Компьютерные сети” (@school_network), 26,560 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/school_network.

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.