Обучающий канал по ОС Linux & Windows для начинающих и действующих администраторов.
Админ, реклама: @Ak_Mihail
Биржа: https://telega.in/c/admguides
РКН: https://kurl.ru/nQejS
Created
Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 88% 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
49 measurements spanning 89 days, net +214. 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 11,794–12,072 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)
Subscribers
Change
3 Nov 2026, 23:06
12,040
+5
3 Nov 2026, 02:09
12,035
+1
2 Nov 2026, 05:37
12,034
-2
1 Nov 2026, 08:34
12,036
+6
31 Oct 2026, 09:46
12,030
-2
30 Oct 2026, 09:26
12,032
+7
29 Oct 2026, 07:04
12,025
-1
28 Oct 2026, 06:58
12,026
+2
27 Oct 2026, 09:01
12,024
+1
25 Oct 2026, 11:38
12,023
+7
24 Oct 2026, 09:40
12,016
+7
23 Oct 2026, 11:11
12,009
+8
22 Oct 2026, 10:14
12,001
+14
19 Oct 2026, 21:04
11,987
+3
18 Oct 2026, 18:57
11,984
+7
17 Oct 2026, 17:31
11,977
+3
16 Oct 2026, 15:39
11,974
+2
15 Oct 2026, 14:56
11,972
-1
13 Oct 2026, 01:40
11,973
+20
8 Oct 2026, 16:55
11,953
first reading
Engagement
91 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 55 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
10.3%
avg views ÷ 12,040 subscribers
Avg views / post
1,240
24 posts measured
Reaction rate
0.794%
reactions ÷ views · ER floor
Posts in window
24
of 91 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
Window
Rolling 30 days · latest post in window 5 November 2026
Posts held
91 (28 July 2026 – 5 November 2026)
Views total
29,723
Reactions total
236
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
5 Nov 2026, 07:08 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,830
Videos
≈24
Links
≈599
Lifetime counters from Telegram’s own channel header, read 5 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
4s
Average length
4s
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
856 reactions across 90 posts, in 20 distinct kinds. The most used accounts for 39.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
341
39.8%
👍
211
24.6%
🔥
123
14.4%
😁
76
8.88%
🤣
31
3.62%
🤡
22
2.57%
😢
14
1.64%
👎
7
0.818%
💯
6
0.701%
👏
5
0.584%
🥴
4
0.467%
✍
3
0.35%
🤔
3
0.35%
🦄
3
0.35%
🤝
2
0.234%
☃
1
0.117%
💊
1
0.117%
🗿
1
0.117%
😐
1
0.117%
🙈
1
0.117%
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 90 of the 91 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 856 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 91 most recent posts we hold, published 28 July 2026 to 5 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.
Advertising
Ad load
4.40%
4 of 91 posts carry an ad marker
Regulatory tokens
4
posts carrying an erid · 4 distinct tokens
Median views · ads
1,290
over 4 measured posts
Median views · rest
1,380
over 87 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
2VtzqvzpKL7
1
17 August 2026
17 August 2026
2VtzqwNqfP1
1
10 August 2026
10 August 2026
2VtzqxV761Z
1
28 August 2026
28 August 2026
2W5zFHmzPUd
1
23 October 2026
23 October 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 91 most recent posts we hold, published 28 July 2026 to 5 November 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
Telegram’s own ‘edited’ marker: 0 of 24 posts held from the last 30 days (0%) 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).
Последовательное vs случайное чтение
Два приложения читают одинаковый объём данных с одного SSD. Но первое получает сотни МБ/с, а второе работает заметно медленнее.
Причина может быть не в размере данных, а в порядке обращений к ним. Проверим это через fio.
⏺Создаём тестовый файл
Сначала запишем 2 ГиБ данных:
fio —name=prepare —filename=/mnt/test.bin \
—rw=write —bs=1M —size=2G \
—direct=1 —end_fsync=1
…
Microsoft добавила сисадминам работы из-за смены часовых поясов в Канаде
После отмены сезонного перевода часов в ряде регионов Канады возникли проблемы с Outlook и Exchange Online: существующие встречи не адаптируются автоматически.
Исправлять их приходится вручную, причём изменить событие с участниками может только организатор.
Одному администратору понадобился PowerShell-скрипт примерно на 900 строк для корректи…
Как запустить сервис без доступа к сети
Допустим, у вас есть приложение, которое обрабатывает локальные файлы и вообще не должно обращаться в интернет. Можно настроить firewall, но systemd позволяет ограничить сетевой доступ непосредственно для сервиса. Причём двумя разными механизмами.
⏺PrivateNetwork: отдельное сетевое пространство
Добавим в unit-файл:
[Service]
PrivateNetwork=yes
systemd создаст для сервиса о…
docker bridge vs host network: где теряется производительность и появляются «странные» лаги
Контейнер работает стабильно, но при нагрузке появляются задержки, нестабильные ответы или разница между локальными и внешними запросами. Часто это не приложение, а тип сети контейнера.
В bridge-сети Docker добавляет слой: виртуальный интерфейс, NAT и iptables. Трафик проходит через bridge и трансляцию адресов, что даёт допо…
💬 Вопрос на собеседовании для сисадмина
Давайте разберем один из частых вопросов, который может быть задан на собеседовании и как на него отвечать.
❓Вопрос: Почему Linux-сервер может перестать создавать новые файлы, хотя на диске ещё достаточно свободного места?
✅Ответ: Причина может быть в исчерпании inode - структур файловой системы, которые хранят метаданные файлов и каталогов.
В файловых системах вроде ext4 к…
Dentry shrinker: как Linux освобождает память, занятую путями к файлам
Допустим, вы запустили find по каталогу с миллионами файлов. Команда давно завершилась, но память, занятая ядром, заметно выросла.
Дело может быть в dentry cache - кэше, который Linux использует для поиска файлов по именам.
⏺Почему кэш растёт
При обходе каталогов ядро создаёт структуры dentry. Они связывают имена с объектами файловой системы и…
Как дать сервису отдельную файловую систему
Иногда приложению нужен доступ только к нескольким каталогам, но при запуске оно видит почти всю файловую систему сервера.
В systemd можно создать для сервиса отдельное файловое окружение без полноценного контейнера. Для этого пригодятся TemporaryFileSystem и BindPaths.
⏺Создаём временный каталог
Допустим, приложение записывает промежуточные файлы в /var/cache/myapp.
До…
💬 Вопрос на собеседовании для DevOps-инженера
Давайте разберем один из частых вопросов, который может быть задан на собеседовании и как на него отвечать.
❓Вопрос: Что такое TCP BBR (Bottleneck Bandwidth and Round-trip propagation time) и зачем он нужен?
✅Ответ: TCP BBR - это алгоритм управления перегрузкой в TCP, разработанный Google. В отличие от классических алгоритмов (Reno, Cubic), которые регулируют скорость …
chroot vs pivot_root: два способа сменить корень Linux
Обе команды позволяют процессу увидеть другой каталог как /. Но работают они по-разному, и заменить одну другой получается далеко не всегда.
⏺chroot - меняем точку отсчёта
chroot() изменяет корневой каталог, относительно которого процесс разрешает абсолютные пути.
Например:
sudo chroot /srv/rootfs /bin/sh
Теперь /etc для оболочки означает /srv/rootfs/etc на…
❤9👍4
Showing the 12 most recent of 91 posts we hold for @admguides. 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 5 posts on @admguides 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
13 August 2026
Most recent seen missing
29 August 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
0
Polls
The 6 most recent of 9 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.
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 91 most recent posts we hold, published 28 July 2026 to 5 November 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 1 registered channel — 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.
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.
Секреты сисадмина | DevOps, Linux, SRE @sysadmin_library · 25,740 Telegram ranks this channel #1 of 85 here — alongside 84 others — read 13 September 2026
Серверная Админа | Компьютерные сети @school_network · 26,442 Telegram ranks this channel #1 of 85 here — alongside 84 others — read 12 September 2026
Bash Days | Linux | DevOps @bashdays · 23,629 Telegram ranks this channel #3 of 94 here — alongside 93 others — read 18 September 2026
Termux, please @termuxplz0x41 · 32,440 Telegram ranks this channel #3 of 54 here — alongside 53 others — read 4 September 2026
Linux Academy @linuxacademiya · 28,654 Telegram ranks this channel #5 of 84 here — alongside 83 others — read 9 September 2026
ServerAdmin.ru @srv_admin · 32,704 Telegram ranks this channel #5 of 96 here — alongside 95 others — read 5 September 2026
Kali Linux @linuxkalii · 55,818 Telegram ranks this channel #5 of 89 here — alongside 88 others — read 23 August 2026
Системный администратор @i_odmin · 26,723 Telegram ranks this channel #6 of 89 here — alongside 88 others — read 12 September 2026
Книги для Системного Администратора @i_odmin_book · 18,772 Telegram ranks this channel #7 of 83 here — alongside 82 others — read 5 October 2026
Linux для чайника @os_linux_ru · 19,542 Telegram ranks this channel #7 of 87 here — alongside 86 others — read 1 October 2026
Типичный Сисадмин @sysodmins · 40,494 Telegram ranks this channel #7 of 93 here — alongside 92 others — read 31 August 2026
ZeroDay | Кибербезопасность @cybersec_academy · 42,664 Telegram ranks this channel #7 of 70 here — alongside 69 others — read 29 August 2026
Open Source @open_source_friend · 52,605 Telegram ranks this channel #7 of 87 here — alongside 86 others — read 24 August 2026
Белый хакер @bezopasno_soft · 29,633 Telegram ranks this channel #9 of 78 here — alongside 77 others — read 8 September 2026
Windows Community @wind_community · 40,893 Telegram ranks this channel #9 of 74 here — alongside 73 others — read 29 August 2026
Windows Club | КДЧ @pcTeapot · 39,441 Telegram ranks this channel #10 of 53 here — alongside 52 others — read 30 August 2026
MikroTik-сэнсэй @mikrotik_sensei · 19,657 Telegram ranks this channel #12 of 92 here — alongside 91 others — read 1 October 2026
no system is safe // cybersec @nsis_cybersec · 21,224 Telegram ranks this channel #12 of 71 here — alongside 70 others — read 23 September 2026
infosec @it_secur · 63,299 Telegram ranks this channel #12 of 81 here — alongside 80 others — read 22 August 2026
ДЕВОПСИНА | DevOps | Linux @devopsina · 23,574 Telegram ranks this channel #13 of 90 here — alongside 89 others — read 18 September 2026
S.E.Book @S_E_Book · 23,094 Telegram ranks this channel #14 of 64 here — alongside 63 others — read 19 September 2026
Selectel @Selectel · 62,482 Telegram ranks this channel #14 of 96 here — alongside 95 others — read 21 August 2026
InfoSec Portal @cybersecinform · 20,005 Telegram ranks this channel #17 of 75 here — alongside 74 others — read 2 October 2026
DevOps @DevOPSitsec · 23,865 Telegram ranks this channel #18 of 90 here — alongside 89 others — read 18 September 2026
This channel appears in 50 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 3 November 2026 — this
entry's latest reading, not the date you are reading this.
“Admin Guides | Сисадмин” (@admguides), 12,040 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/admguides.
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.