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 · Citations · Telegram's recommendations · Cite this entry

12,380subscribers

-46 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
CreatedBetween 1 November 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 25 September 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 why it has no browse page of its own yet.

Growth

12,38012,43912,409.57 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 subscribers7 August 202625 September 2026
30 measurements spanning 49 days, net -46. 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,371–12,448 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
25 Sept 2026, 08:0012,380-14
19 Sept 2026, 00:2012,394-3
16 Sept 2026, 16:4012,397-4
14 Sept 2026, 16:5612,401-3
13 Sept 2026, 02:1512,404-5
11 Sept 2026, 04:4112,409-6
8 Sept 2026, 07:5712,415+4
5 Sept 2026, 03:0012,411-6
3 Sept 2026, 09:1312,417+2
2 Sept 2026, 01:4212,415-3
1 Sept 2026, 01:4612,418-1
31 Aug 2026, 02:2412,419-3
30 Aug 2026, 03:1812,422-4
29 Aug 2026, 01:2512,426-3
28 Aug 2026, 02:3512,429-1
26 Aug 2026, 23:5212,430-8
26 Aug 2026, 02:4312,438+1
25 Aug 2026, 02:0812,437-2
23 Aug 2026, 17:5712,439+7
22 Aug 2026, 00:1812,432first reading

Engagement

39 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 50 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.87%
avg views ÷ 12,380 subscribers
Avg views / post
851
3 posts measured
Reaction rate
0.431%
reactions ÷ views · ER floor
Posts in window
3
of 39 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 2 September 2026
Posts held39 (15 July 2026 – 2 September 2026)
Views total2,553
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 21:57 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

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

254 reactions across 39 posts, in 9 distinct kinds. The most used accounts for 52.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍13252.0%
❤7328.7%
🎉187.09%
🔥135.12%
😁135.12%
❤‍🔥20.787%
😱10.394%
🤔10.394%
🥰10.394%

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

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

Recent posts

2 Sept 2026, 09:25 UTC690 views2 reactionsread 2 September 2026
Photo

Почему BGP может выбрать более длинный путь В BGP легко представить выбор маршрута как простое правило: меньше AS в пути - лучше. Но AS-path length - только один из атрибутов, которые участвуют в best-path selection. Например, маршрутизатор получил: 10.10.10.0/24 peer A: AS_PATH 64501 64502 peer B: AS_PATH 64503 64504 64505 На первый взгляд BGP должен выбрать A. Но если у маршрута от B выше LOCAL_PREF, он мож…

👍2

1 Sept 2026, 09:15 UTC823 views4 reactionsread 2 September 2026
Photo

Как локальный трафик может вообще не попадать на физический интерфейс Если приложение обращается к IP, который Linux считает своим локальным адресом, пакет не отправляется на физический интерфейс. Например, на сервере: eth0 → 10.0.0.10/24 Приложение выполняет: curl http://10.0.0.10:8080 Интуитивно кажется, что будет: application ↓ eth0 ↓ switch ↓ eth0 ↓ server Но Linux сначала проверяет destin…

🔥4

31 Aug 2026, 14:47 UTC≈1,040 views5 reactionsread 2 September 2026
Photo

📂Gratuitous ARP меняет ARP-кэш без единого ARP-запроса Обычно ARP работает так: Host A → Who has 10.0.0.10? Host B → 10.0.0.10 is aa:bb:cc:dd:ee:ff Но устройство может само отправить ARP-пакет, не дожидаясь никакого запроса. Это и есть Gratuitous ARP. Например, виртуальный IP переезжает: до: 10.0.0.10 → aa:aa:aa:aa:aa:aa после: 10.0.0.10 → bb:bb:bb:bb:bb:bb Новое устройство отправляет объявление: 10.0.0.10 …

❤4👍1

28 Aug 2026, 09:32 UTC≈1,630 views4 reactionsread 2 September 2026
Photo

Большой RX ring не всегда делает сеть быстрее У сетевой карты есть очереди, куда складываются входящие пакеты, пока драйвер не успел их обработать. При burst-трафике большой ring действительно может помочь пережить кратковременный всплеск: NIC → RX ring → driver → kernel Но бесконечной очереди не бывает. Если CPU стабильно обрабатывает, например, 500 тыс. пакетов/с, а приходит 700 тыс.: 500k → 700k → 900k → ...…

👍4

27 Aug 2026, 09:31 UTC≈1,610 views7 reactionsread 2 September 2026
Photo

Сетевой пакет может потеряться ещё внутри NIC В tcpdump нет пакета - легко сделать вывод, что он не пришёл на сервер. Но между физическим портом и tcpdump находится сама сетевой карта. У NIC есть собственные RX ring buffers. Драйвер забирает из них дескрипторы и передаёт полученные данные ядру. При перегрузке очередь может не успеть обработать входящие пакеты: NIC ↓ RX ring ↓ driver ↓ kernel ↓ tcpdump Если п…

👍5❤2

26 Aug 2026, 11:10 UTC≈1,530 views6 reactionsread 2 September 2026
Photo

📂 Linux bridge учит MAC-адреса почти как обычный коммутатор Когда Linux работает как bridge, он не просто механически пересылает Ethernet-кадры между интерфейсами. У него есть собственная forwarding database - FDB. Когда кадр приходит на bridge, ядро смотрит на его source MAC и запоминает, откуда он пришёл: aa:bb:cc:dd:ee:01 → eth0 aa:bb:cc:dd:ee:02 → eth1 Посмотреть таблицу можно: bridge fdb show После этого …

👍6

25 Aug 2026, 10:20 UTC≈1,410 views5 reactionsread 2 September 2026
Photo

Пакет можно отбросить до создания skb Обычно сетевой пакет проходит довольно длинный путь внутри Linux: NIC → driver → skb → network stack → socket → application Но skb создаётся не в самом начале. XDP может выполнить программу прямо на раннем этапе обработки пакета, когда драйвер уже получил его из NIC, но обычный sk_buff ещё не создан. Поэтому решение можно принять буквально на входе: NIC ↓ driver ↓ XDP ├─…

👍3❤2

24 Aug 2026, 10:15 UTC≈1,500 views6 reactionsread 2 September 2026
Photo

Почему ss показывает тысячи соединений, а netstat - другую картину На одном сервере можно запустить: ss -ant и получить тысячи TCP-соединений, а затем: netstat -ant и увидеть совсем другое количество. Это не обязательно означает, что один из инструментов врёт. ss работает через современный интерфейс ядра Linux - NETLINK_INET_DIAG. Ядро отдаёт ему информацию о сокетах напрямую, поэтому ss может получать состояние…

👍6

21 Aug 2026, 09:35 UTC≈2,100 views6 reactionsread 2 September 2026
Photo

Один VLAN может проходить через несколько коммутаторов без единого L3-интерфейса VLAN не привязан к конкретному коммутатору. Если между устройствами настроен trunk, один и тот же broadcast domain может растянуться через несколько физических узлов. Например: PC ── SW1 ══ SW2 ══ SW3 ── Server VLAN 30 VLAN 30 VLAN 30 На trunk-портах кадр VLAN 30 идёт с тегом 802.1Q. Проверка на Linux: ip -d link show et…

❤6

20 Aug 2026, 09:10 UTC≈2,180 views12 reactionsread 2 September 2026
Photo

Ping 1 мс не всегда означает, что сеть работает быстро (но почему?) Можно получить RTT в 1–2 мс и при этом иметь очень плохую передачу данных. ping проверяет только время прохождения ICMP-пакета туда и обратно. Он почти ничего не говорит о том, сколько пакетов реально теряется, насколько забит канал и что происходит с TCP при передаче. Например, при потере даже небольшого процента TCP-пакетов скорость может резко …

👍8❤4

19 Aug 2026, 09:32 UTC≈2,010 views6 reactionsread 2 September 2026
Photo

Почему TCP-порт 443 - это не обязательно один TCP-порт? Когда говорят «сервер слушает 443 порт», легко представить один socket, который принимает все HTTPS-соединения. Но TCP идентифицирует соединение не только по порту назначения. Для него важна комбинация: src IP + src port + dst IP + dst port Например, сервер слушает: 10.0.0.10:443 А клиенты создают: 10.0.1.20:49152 → 10.0.0.10:443 10.0.1.21:49153 → 10.0.0…

👍6

18 Aug 2026, 13:20 UTC≈1,510 views3 reactionsread 2 September 2026
Photo

📂 Почему Linux иногда отбрасывает корректный пакет из-за rp_filter Ситуация выглядит странно: маршрут до сервера есть, интерфейс поднят, tcpdump показывает входящие пакеты, но соединение не устанавливается. Одна из причин - Reverse Path Filtering. 1️⃣Что происходит Linux получает пакет от 10.20.30.50 на eth1 и проверяет, через какой интерфейс он сам отправил бы трафик обратно к 10.20.30.50. Если маршрут указывае…

👍3

Showing the 12 most recent of 39 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.

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,588
Telegram ranks this channel #4 of 85 here — alongside 84 others — read 12 September 2026
Системный администратор
@i_odmin · 26,669
Telegram ranks this channel #22 of 89 here — alongside 88 others — read 12 September 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
Telegram ranks this channel #29 of 70 here — alongside 69 others — read 29 August 2026
Kali Linux
@linuxkalii · 55,412
Telegram ranks this channel #30 of 89 here — alongside 88 others — read 23 August 2026
ServerAdmin.ru
@srv_admin · 32,572
Telegram ranks this channel #33 of 96 here — alongside 95 others — read 5 September 2026
S.E.Book
@S_E_Book · 23,146
Telegram ranks this channel #40 of 64 here — alongside 63 others — read 19 September 2026
no system is safe // cybersec
@nsis_cybersec · 21,518
Telegram ranks this channel #44 of 71 here — alongside 70 others — read 23 September 2026
infosec
@it_secur · 61,761
Telegram ranks this channel #44 of 81 here — alongside 80 others — read 22 August 2026
Mr. Robot
@elliot_cybersec · 38,917
Telegram ranks this channel #49 of 70 here — alongside 69 others — read 31 August 2026
Бункер Хакера
@book_academ · 21,429
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 23 September 2026
Этичный Хакер
@hack_less · 233,911
Telegram ranks this channel #52 of 81 here — alongside 80 others — read 12 August 2026
Лаборатория хакера
@lab_hack · 25,556
Telegram ranks this channel #60 of 71 here — alongside 70 others — read 14 September 2026
Типичный Сисадмин
@sysodmins · 38,088
Telegram ranks this channel #62 of 93 here — alongside 92 others — read 31 August 2026
Windows Community
@wind_community · 41,313
Telegram ranks this channel #62 of 74 here — alongside 73 others — read 29 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,649
Telegram ranks this channel #64 of 85 here — alongside 84 others — read 13 September 2026
Linux Academy
@linuxacademiya · 28,434
Telegram ranks this channel #65 of 84 here — alongside 83 others — read 9 September 2026
Белый хакер
@bezopasno_soft · 29,706
Telegram ranks this channel #74 of 78 here — alongside 77 others — read 8 September 2026
1С Hacks | Бухгалтерия и Учёт
@secrets_1C · 45,901
Telegram ranks this channel #75 of 79 here — alongside 78 others — read 27 August 2026
Базы данных | Access, SQL, Big Data
@databases_secrets · 30,002
Telegram ranks this channel #80 of 82 here — alongside 81 others — read 7 September 2026
Social Engineering
@Social_engineering · 125,008
Telegram ranks this channel #80 of 82 here — alongside 81 others — read 13 August 2026
Bash Days | Linux | DevOps
@bashdays · 23,634
Telegram ranks this channel #88 of 94 here — alongside 93 others — read 18 September 2026
DevOps
@DevOPSitsec · 23,684
Telegram ranks this channel #90 of 90 here — alongside 89 others — read 18 September 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,637
Telegram ranks this channel #90 of 94 here — alongside 93 others — read 18 August 2026
DevOps by REBRAIN
@rebrain_devops · 28,873
Telegram ranks this channel #92 of 94 here — alongside 93 others — read 9 September 2026

This channel appears in 24 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 25 September 2026 — this entry's latest reading, not the date you are reading this.

“Network Admin” (@networkadm), 12,380 subscribers as measured 25 September 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.