Telegram RegisterThe public register of Telegram
Telegram profile photo for Admin Guides | Сисадмин

Channel

Admin Guides | Сисадмин

@admguides

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

11,926subscribers

+100 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-1001941038959
TypeChannel
Username@admguides
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/admguides

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 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 why it has no browse page of its own yet.

Growth

11,82611,92611,8767 August 2026 — 11,826 subscribers7 August 2026 — 11,826 subscribers8 August 2026 — 11,830 subscribers9 August 2026 — 11,832 subscribers10 August 2026 — 11,826 subscribers11 August 2026 — 11,828 subscribers12 August 2026 — 11,830 subscribers14 August 2026 — 11,832 subscribers17 August 2026 — 11,839 subscribers18 August 2026 — 11,840 subscribers19 August 2026 — 11,845 subscribers20 August 2026 — 11,849 subscribers21 August 2026 — 11,844 subscribers23 August 2026 — 11,843 subscribers24 August 2026 — 11,851 subscribers27 August 2026 — 11,855 subscribers29 August 2026 — 11,859 subscribers31 August 2026 — 11,865 subscribers1 September 2026 — 11,872 subscribers2 September 2026 — 11,876 subscribers3 September 2026 — 11,873 subscribers5 September 2026 — 11,883 subscribers8 September 2026 — 11,886 subscribers11 September 2026 — 11,901 subscribers13 September 2026 — 11,913 subscribers14 September 2026 — 11,921 subscribers18 September 2026 — 11,926 subscribers7 August 202618 September 2026
27 measurements spanning 42 days, net +100. 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,811–11,941 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
18 Sept 2026, 21:5811,926+5
14 Sept 2026, 16:1811,921+8
13 Sept 2026, 05:4011,913+12
11 Sept 2026, 09:3711,901+15
8 Sept 2026, 18:1811,886+3
5 Sept 2026, 10:0011,883+10
3 Sept 2026, 09:3511,873-3
2 Sept 2026, 02:1311,876+4
1 Sept 2026, 03:5811,872+7
31 Aug 2026, 00:0511,865+6
29 Aug 2026, 00:0611,859+4
27 Aug 2026, 22:1811,855+4
24 Aug 2026, 22:4711,851+8
23 Aug 2026, 11:2811,843-1
21 Aug 2026, 20:3611,844-5
20 Aug 2026, 17:1411,849+4
19 Aug 2026, 18:4211,845+5
18 Aug 2026, 16:4211,840+1
17 Aug 2026, 13:5811,839+7
14 Aug 2026, 22:2811,832first reading

Engagement

67 posts held, back to 28 July 2026the 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
9.87%
avg views ÷ 11,926 subscribers
Avg views / post
1,180
19 posts measured
Reaction rate
0.773%
reactions ÷ views · ER floor
Posts in window
19
of 67 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 held67 (28 July 20262 September 2026)
Views total22,367
Reactions total173
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 23:33 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
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

620 reactions across 66 posts, in 16 distinct kinds. The most used accounts for 39.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
24339.2%
👍16827.1%
🔥8513.7%
😁579.19%
🤣254.03%
🤡152.42%
👎71.13%
👏50.806%
💯40.645%
30.484%
🤔20.323%
🤝20.323%
💊10.161%
🗿10.161%
🙈10.161%
🥴10.161%

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

Measured over the 67 most recent posts we hold, published 28 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.

Advertising

Ad load
4.48%
3 of 67 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
1,290
over 3 measured posts
Median views · rest
1,420
over 64 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
2VtzqvzpKL7117 August 202617 August 2026
2VtzqwNqfP1110 August 202610 August 2026
2VtzqxV761Z128 August 202628 August 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 67 most recent posts we hold, published 28 July 2026 to 2 September 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

2 Sept 2026, 09:25 UTC465 views7 reactionsread 2 September 2026
Photo

lsblk -o +UUID,PARTUUID: когда UUID и PARTUUID ведут к разным объектам У диска и его раздела могут быть сразу несколько идентификаторов, и они не взаимозаменяемы Посмотрим их вместе: lsblk -o NAME,SIZE,FSTYPE,UUID,PARTUUID,MOUNTPOINTS Например: nvme0n1 ├─nvme0n1p1 vfat 7A3C-91F2 4f8a... /boot/efi └─nvme0n1p2 ext4 91c2... 8e21... / UUID относится к файловой системе PARTUUID относится к самому разделу в

👍43

2 Sept 2026, 05:05 UTC789 views4 reactionsread 2 September 2026
Photo

💬 Вопрос на собеседовании для сисадмина Давайте разберем один из частых вопросов, который может быть задан на собеседовании и как на него отвечать. ❓Вопрос: Что такое split-brain в кластере и почему он опасен? ✅Ответ: Split-brain - это состояние кластера, при котором его узлы теряют связь между собой, но несколько частей кластера продолжают считать себя активными и пытаются одновременно управлять одними и теми же

3👍1

1 Sept 2026, 09:20 UTC696 views3 reactionsread 2 September 2026
Photo

opensnoop: кто постоянно открывает файлы Бывает приложение начинает тормозить из-за огромного количества файловых операций, хотя CPU и диск выглядят нормально Например, процесс может тысячи раз в секунду проверять один и тот же отсутствующий файл, конфигурацию или каталог opensnoop позволяет увидеть эти обращения непосредственно на уровне syscall open, openat и openat2 ⏺Смотрим, кто открывает файлы opensnoop В в

2🔥1

1 Sept 2026, 05:05 UTC913 views2 reactionsread 2 September 2026
Photo

Только 2% запросов к git.kernel.org приходят от людей Инфраструктура kernel.org обрабатывает около 6 млн запросов в день, но лишь 2% из них считаются запросами реальных пользователей. Остальные создают боты и скрапперы. Они перебирают старые коммиты и ветки, отправляя миллиарды запросов вместо обычного git clone. При этом используют миллионы случайных IP из домашних и мобильных сетей, поэтому блокировка по IP почти

2

31 Aug 2026, 11:40 UTC934 views2 reactionsread 2 September 2026
Photo

lsof +L1: почему удалённый файл продолжает занимать место Бывает, что файл уже удалили, а df продолжает показывать занятое место Причина в том, что процесс всё ещё держит файл открытым Находим такие файлы lsof +L1 Например: java 4217 app 12w REG 8,1 21474836480 /var/log/app.log (deleted) Файл больше не виден в каталоге, но его inode и блоки всё ещё принадлежат процессу java Почему rm не освобождает мес

1👍1

31 Aug 2026, 05:05 UTC≈1,120 views21 reactionsread 2 September 2026
Photo

Photo, posted without a caption

🔥15💯42

28 Aug 2026, 10:20 UTC≈1,330 views16 reactionsread 2 September 2026
Photo

systemctl cat: как найти реальную конфигурацию сервиса, когда файл выглядит нормально Иногда открываешь unit-файл и не находишь параметр, который явно влияет на работу сервиса. Причина в том, что systemd собирает конфигурацию не только из основного файла. ⏺Смотрим итоговую конфигурацию systemctl cat nginx.service Команда покажет основной unit и применённые drop-in конфигурации. Например: /etc/systemd/system/ng

8👍8

28 Aug 2026, 08:20 UTC≈1,290 views1 reactionsread 2 September 2026
Advertisementerid 2VtzqxV761ZPhoto

MinIO больше не развивается Патчи безопасности не выпускают, Обновления и железо не тестируют. Если у вас петабайты данных в S3-хранилище — это уже не гипотетический риск, а вопрос времени. 3 сентября на вебинаре разберем, как перенести данные из устаревшего хранилища (на примере MinIO) в другое S3-совместимое — без остановки сервиса. Что будет: — что переносится при миграции: объекты, версии, ACL, bucket-policy,

🔥1

28 Aug 2026, 05:05 UTC≈1,270 views14 reactionsread 2 September 2026
Photo

💬 Вопрос на собеседовании для DevOps-инженера Давайте разберем один из частых вопросов, который может быть задан на собеседовании и как на него отвечать. ❓Вопрос: Что такое file descriptor leak и как его обнаружить в Linux? ✅Ответ: File descriptor leak - это ситуация, когда процесс открывает файлы, сокеты, pipes или другие ресурсы, но не закрывает их после использования. Со временем количество открытых дескрипторо

9👍5

27 Aug 2026, 09:40 UTC≈1,070 views13 reactionsread 2 September 2026
Photo

Transient units: сервисы, которых вообще нет в /etc/systemd/system Не каждый systemd unit существует как файл на диске. Transient unit создаётся прямо во время работы системы и может появиться без собственного файла в /etc/systemd/system Например: systemd-run --unit=backup-now /usr/local/bin/backup.sh После этого появляется unit: systemctl status backup-now.service Но поиск файла ничего не даст: find /etc/sys

🔥85

27 Aug 2026, 05:05 UTC≈1,280 views22 reactionsread 2 September 2026
Photo

Photo, posted without a caption

😁157

26 Aug 2026, 09:35 UTC≈1,130 views8 reactionsread 2 September 2026
Photo

tc filter: когда пакет меняется ещё до выхода из интерфейса Иногда маршрут выбран правильно, firewall ничего не блокирует, но трафик всё равно уходит не таким, каким его отправляет приложение. Между сетевым стеком и интерфейсом пакет может пройти через tc — Traffic Control Смотрим, есть ли вообще правила tc filter show dev eth0 Если используется ingress: tc filter show dev eth0 ingress На современных системах

6👍2

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

Polls

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

26 Aug 2026, 05:05 UTCAnonymous Quiz302 voters

Что может скрывать реальное потребление памяти контейнером?

  1. Page cache68%
  2. Hostname3%
  3. File capabilities19%
  4. DNS cache11%

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

20 Aug 2026, 05:05 UTCAnonymous Quiz281 voters

Что может объяснить высокий %steal на виртуальной машине?

  1. Гостевая ОС ждёт CPU гипервизора68%
  2. Гость потерял сетевой маршрут7%
  3. Закончились inode22%
  4. Сломался NTP3%

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

14 Aug 2026, 05:05 UTCAnonymous Quiz281 voters

Что может вызвать резкий рост context switches?

  1. Частая конкуренция потоков59%
  2. Увеличение MTU13%
  3. Ошибка DNS11%
  4. Большой inode17%

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

10 Aug 2026, 05:05 UTCAnonymous Quiz313 voters

Почему высокий load average не обязательно означает высокую загрузку CPU?

  1. Load считает только ядра CPU24%
  2. Load учитывает процессы в I/O68%
  3. Load зависит только от RAM4%
  4. Load показывает сетевой трафик4%

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

5 Aug 2026, 05:05 UTCAnonymous Quiz357 voters

Что произойдёт, если изменить vm.swappiness в Linux?

  1. Изменится размер RAM7%
  2. Изменится агрессивность использования swap86%
  3. Изменится скорость CPU3%
  4. Изменится размер файловой системы5%

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

30 Jul 2026, 05:05 UTCAnonymous Quiz304 voters

После настройки keepalived оба узла стали MASTER одновременно:

  1. У узлов одинаковый приоритет52%
  2. Версия VRRP разная4%
  3. VRRP пакеты не доходят между узлами33%
  4. Preempt не настроен12%

Shares as published, totalling 101%. 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 67 most recent posts we hold, published 28 July 2026 to 2 September 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.

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.

Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,649
Telegram ranks this channel #1 of 85 here — alongside 84 others — read 13 September 2026
Серверная Админа | Компьютерные сети
@school_network · 26,624
Telegram ranks this channel #1 of 85 here — alongside 84 others — read 12 September 2026
Bash Days | Linux | DevOps
@bashdays · 23,674
Telegram ranks this channel #3 of 94 here — alongside 93 others — read 18 September 2026
Termux, please
@termuxplz0x41 · 32,763
Telegram ranks this channel #3 of 54 here — alongside 53 others — read 4 September 2026
Linux Academy
@linuxacademiya · 28,422
Telegram ranks this channel #5 of 84 here — alongside 83 others — read 9 September 2026
ServerAdmin.ru
@srv_admin · 32,537
Telegram ranks this channel #5 of 96 here — alongside 95 others — read 5 September 2026
Kali Linux
@linuxkalii · 55,349
Telegram ranks this channel #5 of 89 here — alongside 88 others — read 23 August 2026
Системный администратор
@i_odmin · 26,662
Telegram ranks this channel #6 of 89 here — alongside 88 others — read 12 September 2026
Типичный Сисадмин
@sysodmins · 38,088
Telegram ranks this channel #7 of 93 here — alongside 92 others — read 31 August 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
Telegram ranks this channel #7 of 70 here — alongside 69 others — read 29 August 2026
Open Source
@open_source_friend · 52,224
Telegram ranks this channel #7 of 87 here — alongside 86 others — read 24 August 2026
Белый хакер
@bezopasno_soft · 29,706
Telegram ranks this channel #9 of 78 here — alongside 77 others — read 8 September 2026
Windows Community
@wind_community · 41,313
Telegram ranks this channel #9 of 74 here — alongside 73 others — read 29 August 2026
Windows Club | КДЧ
@pcTeapot · 39,659
Telegram ranks this channel #10 of 53 here — alongside 52 others — read 30 August 2026
infosec
@it_secur · 61,761
Telegram ranks this channel #12 of 81 here — alongside 80 others — read 22 August 2026
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,562
Telegram ranks this channel #13 of 90 here — alongside 89 others — read 18 September 2026
S.E.Book
@S_E_Book · 23,170
Telegram ranks this channel #14 of 64 here — alongside 63 others — read 19 September 2026
Selectel
@Selectel · 63,289
Telegram ranks this channel #14 of 96 here — alongside 95 others — read 21 August 2026
DevOps
@DevOPSitsec · 23,663
Telegram ranks this channel #18 of 90 here — alongside 89 others — read 18 September 2026
infosecurity
@tg_infosec · 26,786
Telegram ranks this channel #21 of 74 here — alongside 73 others — read 11 September 2026
1С Hacks | Бухгалтерия и Учёт
@secrets_1C · 45,901
Telegram ranks this channel #23 of 79 here — alongside 78 others — read 27 August 2026
DevOps by REBRAIN
@rebrain_devops · 28,890
Telegram ranks this channel #24 of 94 here — alongside 93 others — read 9 September 2026
Базы данных | Access, SQL, Big Data
@databases_secrets · 30,034
Telegram ranks this channel #31 of 82 here — alongside 81 others — read 7 September 2026
Social Engineering
@Social_engineering · 125,008
Telegram ranks this channel #31 of 82 here — alongside 81 others — read 13 August 2026

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

“Admin Guides | Сисадмин” (@admguides), 11,926 subscribers as measured 18 September 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.