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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
19 measurements spanning 71 days, net +47. 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 7,380–7,451 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Oct 2026, 15:45
7,443
+3
14 Oct 2026, 21:47
7,440
+7
11 Oct 2026, 05:21
7,433
+5
4 Oct 2026, 20:01
7,428
+14
25 Sept 2026, 07:42
7,414
+8
15 Sept 2026, 11:57
7,406
+4
12 Sept 2026, 00:40
7,402
-2
7 Sept 2026, 13:17
7,404
+6
2 Sept 2026, 11:24
7,398
+2
30 Aug 2026, 16:34
7,396
+4
27 Aug 2026, 16:25
7,392
+1
24 Aug 2026, 13:44
7,391
+3
20 Aug 2026, 11:32
7,388
-3
17 Aug 2026, 11:38
7,391
+1
14 Aug 2026, 08:37
7,390
-6
11 Aug 2026, 02:38
7,396
-2
8 Aug 2026, 04:57
7,398
+2
7 Aug 2026, 11:45
7,396
no change
7 Aug 2026, 11:36
7,396
first reading
Engagement
27 posts held, back to 7 May 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 15 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 27 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
626 reactions across 27 posts, in 9 distinct kinds. The most used accounts for 58.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
368
58.8%
😁
101
16.1%
🔥
95
15.2%
👏
15
2.40%
🤯
15
2.40%
👎
11
1.76%
🤬
8
1.28%
😱
7
1.12%
🎉
6
0.958%
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 27 of the 27 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 626 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 7 May 2026 to 27 August 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
3.70%
1 of 27 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
5,240
over 1 measured post
Median views · rest
4,650
over 26 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
erid
Posts
First seen
Last seen
2VtzqxMMFzM
1
23 July 2026
23 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 27 most recent posts we hold, published 7 May 2026 to 27 August 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.
ГИБРИДНЫЕ ПОРТЫ В VLAN (ИЛИ ПРОСТОР ДЛЯ ФАНТАЗИИ)
Прежде всего скажу, что при определении того, что такое "гибридный порт", появляется простор для фантазии, т.к. в стандарте относительно него ничего не сказано. В общем смысле гибридный порт и тегированный порт – это одно и то же: может быть использовано более одного VLAN ID с тегированными кадрами и один VLAN ID с нетегированными кадрами. Далее каждый вендор трактуе…
ТЕГИРОВАННЫЕ ПОРТЫ В VLAN
Тегированный порт – порт, который принимает и отправляет тегированные кадры.
Тегированные порты (tagged) также известны как транк-порты (trunk).
Тегированные порты чаще всего используются для соединения промежуточных устройств, когда требуется по одной линии связи одновременно передавать кадры, относящиеся к разным VLAN. Таким образом возможна одновременная передача кадров, относящихся к…
НЕТЕГИРОВАННЫЕ ПОРТЫ ВО VLAN
Нетегированный порт – порт, который принимает и отправляет только нетегированные кадры, которые могут принадлежать только к одному VLAN ID.
Нетегированные порты (untagged) также известны как порты доступа (access port).
Нетегированные порты чаще всего используются для подключения конечных устройств. Но бывают и исключения.
На приведенной схеме нетегированными (access) портами являются…
СХЕМА ДЛЯ СЛЕДУЮЩЕГО ВОПРОСА
Между всеми устройствами, относящимися к любой одной и той же VLAN, есть связь друг с другом. Связь между устройствами из разных VLAN выполняется через маршрутизатор. На маршрутизаторе и коммутаторах настроено использование VLAN. Компьютеры отправляют нетегированные кадры, IP-телефоны отправляют тегированные кадры, любые устройства, находящиеся за беспроводными точками доступа, отправляю…
НАЗНАЧЕНИЕ VLAN
Смысл использования VLAN – это очень скучная тема. Есть три возможные причины:
*️⃣ Необходимо разделение по группам безопасности. Пример: отделить трафик одного отдела от трафика другого отдела.
*️⃣ Необходимо разделение по типам трафика. Пример: выделение IP-телефонии, видеонаблюдения и т.д. в отдельные VLAN'ы.
*️⃣ Необходимо ограничение широковещательного домена. Требуется в очень больших сетях.
…
АДМИНИСТРАТОРЫ, КОТОРЫЕ САМИ СЕБЕ ИЩУТ ПРОБЛЕМЫ
Очень часто сталкиваюсь с ситуациями, когда администраторы при выборе оборудования останавливают свой выбор не на том, что реально нужно, а на том, что подешевле. В то же время эти люди, как правило, осознают, что своим выбором они потенциально или даже гарантированно создадут себе проблемы. Более того, заказчик зачастую даже не догадывается, что выбор сделан не в поль…
1000BASE-T И ДУПЛЕКСНЫЙ СПОСОБ СВЯЗИ
Стандарт 1000BASE-T – самый распространенный стандарт для передачи данных по витой паре с помощью протокола Ethernet на скорости 1 Гбит/с.
При использовании стандарта 1000BASE-T в дуплексном режиме все четыре пары проводников одновременно используются и для передачи, и для приема. Сигналы формируются таким образом, чтобы не мешать друг другу при одновременном прохождении во встр…
При использовании стандарта 1000BASE-T в дуплексном режиме две пары проводников используются только для передачи данных, а другие две пары – только для приема. Уточнение: 1000BASE-T – самый распространенный стандарт для передачи данных по витой паре.
Утверждение правдиво51%
Утверждение ложно44%
Не знаю5%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
КОЛЛИЗИИ
Коллизия (collision) – это наложение друг на друга двух и более кадров, созданных разными отправителями.
Домен коллизий – это участок сети, в котором может произойти коллизия.
Надо учитывать, что домен коллизий и широковещательный домен – это не одно и то же. Часто встречал такое заблуждение. Поэтому и пишу о нем.
Коллизии возникают из-за того, что нельзя определить факт начала передачи данных другим устр…
👍24
Showing the 12 most recent of 27 posts we hold for @net_arch. 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 4 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.
При использовании стандарта 1000BASE-T в дуплексном режиме две пары проводников используются только для передачи данных, а другие две пары – только для приема. Уточнение: 1000BASE-T – самый распространенный стандарт для передачи данных по витой паре.
Утверждение правдиво51%
Утверждение ложно44%
Не знаю5%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
При скорости 1000 Мбит/с сколько Мбит данных будет передано за одну секунду при условии использования стандартных кадров формата Ethernet II?
Под «данными» я подразумеваю одноименное поле из поста выше. Речь идет про стандартные кадры.
От 547 до 97524%
От 600 до 99012%
От 834 до 95627%
От 300 до 90013%
Не знаю24%
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 27 most recent posts we hold, published 7 May 2026 to 27 August 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.
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.
MikroTik-сэнсэй @mikrotik_sensei · 19,634 Telegram ranks this channel #7 of 92 here — alongside 91 others — read 1 October 2026
Системный администратор @i_odmin · 26,713 Telegram ranks this channel #26 of 89 here — alongside 88 others — read 12 September 2026
ITDog @itdoginfo · 19,296 Telegram ranks this channel #42 of 87 here — alongside 86 others — read 2 October 2026
Типичный Сисадмин @sysodmins · 39,592 Telegram ranks this channel #56 of 93 here — alongside 92 others — read 31 August 2026
Серверная Админа | Компьютерные сети @school_network · 26,480 Telegram ranks this channel #58 of 85 here — alongside 84 others — read 12 September 2026
ServerAdmin.ru @srv_admin · 32,654 Telegram ranks this channel #58 of 96 here — alongside 95 others — read 5 September 2026
remontka.pro ✅ @remontka_pro · 26,255 Telegram ranks this channel #59 of 77 here — alongside 76 others — read 13 September 2026
Книги для Системного Администратора @i_odmin_book · 18,753 Telegram ranks this channel #67 of 83 here — alongside 82 others — read 5 October 2026
Секреты сисадмина | DevOps, Linux, SRE @sysadmin_library · 25,896 Telegram ranks this channel #68 of 85 here — alongside 84 others — read 13 September 2026
#энерголикбез @operby · 35,869 Telegram ranks this channel #73 of 85 here — alongside 84 others — read 2 September 2026
DevOps by REBRAIN @rebrain_devops · 28,837 Telegram ranks this channel #90 of 94 here — alongside 93 others — read 9 September 2026
Bash Days | Linux | DevOps @bashdays · 23,637 Telegram ranks this channel #91 of 94 here — alongside 93 others — read 18 September 2026
This channel appears in 12 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 17 October 2026 — this
entry's latest reading, not the date you are reading this.
“Сетевой архитектор” (@net_arch), 7,443 subscribers as measured 17 October 2026. Telegram Register, tgregister.com/channel/net_arch.
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.