Telegram RegisterThe public register of Telegram
Telegram profile photo for Network Admin

Channel

Network Admin

@networkadm

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

12,351subscribers

-75 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-1001898919043
TypeChannel
Username@networkadm
DescriptionОбучающий канал по сетевому и системному администрированию. Сотрудничество: @dad_admin Биржа: https://telega.in/c/networkadm РКН: https://bit.ly/4ioc61C
CreatedBetween 1 November 2022 and 31 July 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/networkadm

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 11 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 the other topics.

Growth

12,35112,43912,3957 August 2026 — 12,426 subscribers7 August 2026 — 12,426 subscribers10 August 2026 — 12,421 subscribers11 August 2026 — 12,418 subscribers13 August 2026 — 12,417 subscribers14 August 2026 — 12,413 subscribers16 August 2026 — 12,412 subscribers17 August 2026 — 12,410 subscribers18 August 2026 — 12,407 subscribers19 August 2026 — 12,409 subscribers22 August 2026 — 12,432 subscribers23 August 2026 — 12,439 subscribers25 August 2026 — 12,437 subscribers26 August 2026 — 12,438 subscribers26 August 2026 — 12,430 subscribers28 August 2026 — 12,429 subscribers29 August 2026 — 12,426 subscribers30 August 2026 — 12,422 subscribers31 August 2026 — 12,419 subscribers1 September 2026 — 12,418 subscribers2 September 2026 — 12,415 subscribers3 September 2026 — 12,417 subscribers5 September 2026 — 12,411 subscribers8 September 2026 — 12,415 subscribers11 September 2026 — 12,409 subscribers13 September 2026 — 12,404 subscribers14 September 2026 — 12,401 subscribers16 September 2026 — 12,397 subscribers19 September 2026 — 12,394 subscribers25 September 2026 — 12,380 subscribers4 October 2026 — 12,361 subscribers8 October 2026 — 12,392 subscribers12 October 2026 — 12,383 subscribers14 October 2026 — 12,379 subscribers15 October 2026 — 12,377 subscribers16 October 2026 — 12,378 subscribers17 October 2026 — 12,379 subscribers18 October 2026 — 12,378 subscribers19 October 2026 — 12,380 subscribers20 October 2026 — 12,379 subscribers21 October 2026 — 12,377 subscribers22 October 2026 — 12,378 subscribers24 October 2026 — 12,374 subscribers25 October 2026 — 12,370 subscribers27 October 2026 — 12,371 subscribers29 October 2026 — 12,368 subscribers29 October 2026 — 12,370 subscribers30 October 2026 — 12,367 subscribers31 October 2026 — 12,365 subscribers2 November 2026 — 12,360 subscribers3 November 2026 — 12,354 subscribers5 November 2026 — 12,352 subscribers6 November 2026 — 12,353 subscribers7 November 2026 — 12,355 subscribers9 November 2026 — 12,353 subscribers11 November 2026 — 12,351 subscribers7 August 202611 November 2026
56 measurements spanning 96 days, net -75. 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 12,338–12,452 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
11 Nov 2026, 02:1912,351-2
9 Nov 2026, 13:1812,353-2
7 Nov 2026, 03:1712,355+2
6 Nov 2026, 03:3012,353+1
5 Nov 2026, 05:5112,352-2
3 Nov 2026, 02:0612,354-6
2 Nov 2026, 00:4012,360-5
31 Oct 2026, 21:4412,365-2
30 Oct 2026, 23:2612,367-3
29 Oct 2026, 22:4812,370+2
29 Oct 2026, 00:5712,368-3
27 Oct 2026, 21:1112,371+1
25 Oct 2026, 21:4812,370-4
24 Oct 2026, 22:1812,374-4
22 Oct 2026, 20:3512,378+1
21 Oct 2026, 15:4012,377-2
20 Oct 2026, 08:5512,379-1
19 Oct 2026, 08:5112,380+2
18 Oct 2026, 07:2812,378-1
17 Oct 2026, 10:2912,379first reading

Engagement

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

ERR · 30 days
14.3%
avg views ÷ 12,351 subscribers
Avg views / post
1,760
24 posts measured
Reaction rate
0.279%
reactions ÷ views · ER floor
Posts in window
24
of 66 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 11 November 2026
Posts held66 (15 July 2026 – 11 November 2026)
Views total42,314
Reactions total118
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 20:47 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,160
Videos
≈14
Links
≈1,180

Lifetime counters from Telegram’s own channel header, read 11 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
10m 23s
Average length
10m 23s

Measured directly from 1 video 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

414 reactions across 66 posts, in 11 distinct kinds. The most used accounts for 61.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍25461.4%
❤8119.6%
😁358.45%
🎉184.35%
🔥184.35%
❤‍🔥20.483%
👻20.483%
🗿10.242%
😱10.242%
🤔10.242%
🥰10.242%

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

Measured over the 66 most recent posts we hold, published 15 July 2026 to 11 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 24 posts held from the last 30 days (4.17%) 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).

11 Nov 2026, 08:35 UTC754 views2 reactionsread 11 November 2026
Photo

Incast: когда сотни серверов перегружают один порт В датацентре может возникнуть странная ситуация: сеть почти не загружена, но распределённое приложение периодически сталкивается с резкими задержками. Причина может быть в TCP Incast — эффекте, когда множество серверов одновременно отправляют данные одному получателю. ⏺Как возникает Incast? Допустим, приложение запрашивает данные сразу у 100 серверов. Каждый отпр…

👍2

10 Nov 2026, 08:35 UTC≈1,080 views5 reactionsread 11 November 2026
Photo

DNS over HTTPS vs DNS over TLS: что меняется для корпоративной сети Раньше администратор мог анализировать DNS-запросы сотрудников на UDP/53, блокировать нежелательные домены и выявлять подозрительную активность. Но с появлением шифрованного DNS привычная схема перестала быть такой надёжной. ⏺DNS over TLS (DoT) DNS-запросы передаются через отдельное TLS-соединение, обычно на TCP-порту 853. Это удобно для сетевог…

👍5

9 Nov 2026, 10:29 UTC≈1,170 views3 reactionsread 11 November 2026
Photo

Как узнать, что изменилось в сети перед аварией В 14:30 перестал работать один из VLAN. Интерфейсы UP, оборудование доступно, а в логах нет очевидных ошибок. Через полчаса выясняется, что незадолго до сбоя кто-то изменил конфигурацию trunk-порта. Чтобы не искать такие изменения вручную, используют Configuration Drift Detection. ⏺Сохраняем историю конфигураций Для этого подходит Oxidized - инструмент, который рег…

👍3

6 Nov 2026, 08:20 UTC≈1,600 views4 reactionsread 11 November 2026
Photo

TCAM переполнен: почему новая ACL не применяется Представим, что сетевой инженер добавил несколько правил ACL на коммутатор. Конфигурация сохранилась, ошибок в синтаксисе нет, но часть трафика продолжает проходить так, будто новых правил не существует. Одна из возможных причин - закончились ресурсы TCAM. ⏺Что такое TCAM? Ternary Content Addressable Memory - специальная память, которую коммутаторы используют для б…

👍4

5 Nov 2026, 08:25 UTC≈1,540 views2 reactionsread 11 November 2026
Photo

Маршруты правильные, но трафик идёт по кругу: как найти MPLS-ловушку В MPLS-сети может возникнуть ситуация, когда IP-маршрутизация выглядит исправной, но пакеты с метками зацикливаются между двумя LSR. Причина - несогласованность таблиц пересылки меток после изменения топологии. ⏺Сначала проверяем LFIB На Cisco IOS/IOS XE: show mpls forwarding-table Здесь видно, какую входящую метку маршрутизатор заменяет на вы…

👍2

4 Nov 2026, 08:20 UTC≈1,540 views3 reactionsread 11 November 2026
Photo

3 команды для диагностики нестабильного OSPF-соседства OSPF-соседство периодически переходит из Full в Down, а затем восстанавливается. При этом интерфейс остаётся UP, и обычный ping может не показывать проблем. На Cisco IOS/IOS XE причину можно искать через три команды. ⏺Проверяем состояние соседей show ip ospf neighbor detail Смотрим состояние соседства, Dead Timer, количество переходов между состояниями и вре…

👍3

3 Nov 2026, 11:15 UTC≈1,400 views5 reactionsread 11 November 2026
Photo

VLAN Translation: когда VLAN 100 превращается в VLAN 200 Представим, что две компании подключаются через сеть оператора. У первой используется VLAN 100, а у второй - VLAN 200. Нужно объединить их в один L2-сегмент, но менять VLAN на оборудовании клиентов никто не хочет. Для этого существует VLAN Translation - механизм переписывания VLAN-тегов прямо на коммутаторе. ⏺Как это работает? Коммутатор получает Ethernet-к…

👍5

2 Nov 2026, 08:40 UTC≈1,320 views4 reactionsread 11 November 2026
Photo

Проверка DNSSEC валидации через dig +dnssec, а не просто наличия настройки DNSSEC включён в конфиге резолвера, но это не значит что валидация реально работает. Резолвер может принимать неподписанные ответы, игнорировать сломанные подписи или вообще не проверять цепочку доверия. Проверяем поведение, а не настройку. Базовая проверка: резолвер возвращает AD флаг AD (Authentic Data) в ответе означает что резолвер про…

👍4

30 Oct 2026, 10:03 UTC≈1,830 views3 reactionsread 11 November 2026
Photo

Почему два коммутатора могут одновременно считать себя главным шлюзом В сети используется MLAG: два физических коммутатора объединены в логическую пару, а серверы подключены сразу к обоим через LACP. Всё работает нормально, пока между коммутаторами не пропадает служебное соединение — peer-link. ⏺Что происходит при разрыве? Через peer-link устройства обмениваются служебной информацией и синхронизируют часть состоя…

🔥3

29 Oct 2026, 12:17 UTC≈1,910 views3 reactionsread 11 November 2026
Photo

Как Ethernet временно останавливает передачу Представим, что сервер принимает трафик быстрее, чем успевает его обрабатывать. Буферы сетевой карты заполняются, и скоро начнутся потери пакетов. Но Ethernet умеет не только отбрасывать кадры. В некоторых сетях он может попросить соседнее устройство временно прекратить передачу. ⏺Как это работает? В стандарте IEEE 802.3x предусмотрены специальные PAUSE-кадры. Если вкл…

👍3

28 Oct 2026, 10:50 UTC≈1,800 views3 reactionsread 11 November 2026
Photo

4 команды для диагностики оптического линка в Linux Оптический интерфейс может оставаться UP, даже когда качество сигнала уже ухудшилось. Поэтому при нестабильной связи стоит проверить не только состояние порта, но и сам трансивер. ⏺Проверить параметры SFP-модуля ethtool -m eth0 Если модуль и драйвер поддерживают диагностику, увидим температуру, напряжение, мощность передатчика (Tx) и принимаемого сигнала (Rx). …

👍3

27 Oct 2026, 10:40 UTC≈1,630 views5 reactionsread 11 November 2026
Photo

Как проверить PoE-потребление без доступа к устройству IP-камера периодически перезагружается, хотя сетевой линк работает нормально. Причина может быть не в сети, а в питании через PoE. Чтобы это проверить, необязательно идти к камере с тестером. Управляемый PoE-коммутатор часто показывает параметры питания прямо через CLI. ⏺Смотрим общий бюджет PoE На Cisco Catalyst: show power inline Команда показывает доступ…

👍5

Showing the 12 most recent of 66 posts we hold for @networkadm. 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 recorded as deleted after publishing

We recorded 3 posts on @networkadm as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
19 August 2026
Most recent seen missing
28 August 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
0

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

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.

Серверная Админа | Компьютерные сети
@school_network · 26,411
Telegram ranks this channel #4 of 85 here — alongside 84 others — read 12 September 2026
Linux для чайника
@os_linux_ru · 19,526
Telegram ranks this channel #15 of 87 here — alongside 86 others — read 1 October 2026
Системный администратор
@i_odmin · 26,713
Telegram ranks this channel #22 of 89 here — alongside 88 others — read 12 September 2026
Книги для Системного Администратора
@i_odmin_book · 18,778
Telegram ranks this channel #23 of 83 here — alongside 82 others — read 5 October 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,588
Telegram ranks this channel #29 of 70 here — alongside 69 others — read 29 August 2026
Kali Linux
@linuxkalii · 55,900
Telegram ranks this channel #30 of 89 here — alongside 88 others — read 23 August 2026
MikroTik-сэнсэй
@mikrotik_sensei · 19,662
Telegram ranks this channel #32 of 92 here — alongside 91 others — read 1 October 2026
ServerAdmin.ru
@srv_admin · 32,701
Telegram ranks this channel #33 of 96 here — alongside 95 others — read 5 September 2026
S.E.Book
@S_E_Book · 23,090
Telegram ranks this channel #40 of 64 here — alongside 63 others — read 19 September 2026
InfoSec Portal
@cybersecinform · 20,042
Telegram ranks this channel #44 of 75 here — alongside 74 others — read 2 October 2026
no system is safe // cybersec
@nsis_cybersec · 21,166
Telegram ranks this channel #44 of 71 here — alongside 70 others — read 23 September 2026
infosec
@it_secur · 63,440
Telegram ranks this channel #44 of 81 here — alongside 80 others — read 22 August 2026
Mr. Robot
@elliot_cybersec · 38,905
Telegram ranks this channel #49 of 70 here — alongside 69 others — read 31 August 2026
Бункер Хакера
@book_academ · 21,293
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 23 September 2026
Этичный Хакер
@hack_less · 243,065
Telegram ranks this channel #52 of 81 here — alongside 80 others — read 12 August 2026
Лаборатория хакера
@lab_hack · 25,423
Telegram ranks this channel #60 of 71 here — alongside 70 others — read 14 September 2026
Типичный Сисадмин
@sysodmins · 40,818
Telegram ranks this channel #62 of 93 here — alongside 92 others — read 31 August 2026
Windows Community
@wind_community · 40,852
Telegram ranks this channel #62 of 74 here — alongside 73 others — read 29 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,689
Telegram ranks this channel #64 of 85 here — alongside 84 others — read 13 September 2026
Linux Academy
@linuxacademiya · 28,676
Telegram ranks this channel #65 of 84 here — alongside 83 others — read 9 September 2026
Белый хакер
@bezopasno_soft · 29,601
Telegram ranks this channel #74 of 78 here — alongside 77 others — read 8 September 2026
1С Hacks | Бухгалтерия и Учёт
@secrets_1C · 46,421
Telegram ranks this channel #75 of 79 here — alongside 78 others — read 27 August 2026
Базы данных | Access, SQL, Big Data
@databases_secrets · 30,000
Telegram ranks this channel #80 of 82 here — alongside 81 others — read 7 September 2026
Social Engineering
@Social_engineering · 124,696
Telegram ranks this channel #80 of 82 here — alongside 81 others — read 13 August 2026

This channel appears in 28 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.

“Network Admin” (@networkadm), 12,351 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/networkadm.

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.