Telegram RegisterThe public register of Telegram

Channel

ZloyTapochek's InfoSec

@ZTsInfoSec

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

29subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002162001984
TypeChannel
Username@ZTsInfoSec
DescriptionНа этом канале будут статьи, материалы и разные полезности по ИБ
Created21 December 2024measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/ZTsInfoSec

Growth

298 August 2026 — 29 subscribers11 August 2026 — 29 subscribers8 August 202611 August 2026
2 measurements spanning 3 days. 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 28–30 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:3129no change
8 Aug 2026, 00:2529first reading

Engagement

16 posts held, back to 21 December 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
58.6%
avg views ÷ 29 subscribers
Avg views / post
17.0
1 post measured
Reaction rate
29.4%
reactions ÷ views · ER floor
Posts in window
1
of 16 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 5 August 2026
Posts held16 (21 December 20245 August 2026)
Views total17
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 05:31 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
Links
11

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

79 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 44.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3544.3%
🔥1822.8%
🍌911.4%
👾56.33%
custom 540440887527945877845.06%
custom 540451958235648005622.53%
👍22.53%
🆒11.27%
👎11.27%
🙏11.27%
🥰11.27%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 16 most recent posts we hold, published 21 December 2024 to 5 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.

Recent posts

5 Aug 2026, 12:24 UTC17 views5 reactionsread 11 August 2026

Написал небольшой гайд по клонированию виртуальных машин в Proxmox с использованием Cloud-Init. Статья получилась очень подробной и простой. За критикой или вопросами - добро пожаловать в комментарии☕️ А сама статья тут: [тык] 🔖

3🔥1custom 54044088752794587781

18 Mar 2026, 05:59 UTC143 views7 reactionsread 11 August 2026
Forwarded from @kubCTFPhoto

KUBSTU CTF - пройдет онлайн! CTF организован на базе Кубанского государственного технологического университета (КубГТУ) на факультете Информационных технологий и кибербезопасности (ФИТК) командой Capybaras. 36-часовое соревнование (формат task-based), где участники смогут проверить свои навыки в различных областях информационной безопасности, решая захватывающие задачи и находя уязвимости в разных сценариях. План

2🔥2🍌1👎1custom 54045195823564800561

18 Mar 2026, 05:59 UTC151 views6 reactionsread 11 August 2026

А мы тут CTF свой делаем 👀

3🔥2custom 54045195823564800561

28 Feb 2026, 15:12 UTC181 views5 reactionsread 11 August 2026

👋 На днях решил переделать свою базу знаний 🗿Obsidian в сторону Ever Green заметок. И в процессе копятся мини-статьи по самым базовым вещам. Одну из таких сегодня представлю. Долго решался: постить или нет, как раз-таки из-за "базовизны", но в мире, где 👩‍💻StackOverflow умирает, считаю, что краткая и по делу статься всегда в тему👀 Сегодня поговорим про 🤟 Создание systemd сервиса

🔥32

12 Jan 2026, 08:39 UTC333 views5 reactionsread 11 August 2026

Немного поговорим про сканеры😠 В DevSecOps есть несколько их типов. ✍️Записывай: 🟣Secret Scanner - Анализирует исходных код и ищет известные патерны секретов. API ключи и тд и тп. Может быть применен как на этапе MR, так и на этапе отправки кода в репозиторий Talisman GitLeaks TruffleHog 🔴SAST - Анализирует исходный код на наличие уязвимостей в коде. Строит дерево зависимостей и находит такие вещи как SQL-инъекции

5

31 Dec 2025, 11:26 UTC190 views4 reactionsread 11 August 2026

Всем привет👋 Хочется поздравить всех с наступающим Новым Годом🎄 Канал был создан в декабре прошлого года(его др я благополучно пропустил😬), но за это время я сделал много выводов и решил, в каком направлении я хочу развивать этот канал. Сейчас очень много мусора в Интернете и плодить его я не вижу смысла. Так что на канале будут статьи написанные и проверенные на практике исключительно мной (именно по это причине п

3🍌1

3 Nov 2025, 21:39 UTC255 views7 reactionsread 11 August 2026

Прошу прощения за столь долгое отсутствие😇 Навалилось все: работа, учеба, работа, активности, CTF и тд и тп🔥 Но сейчас не об этом. Сегодня мы поговорим про "Домашний" Compute Cloud | Или как создавать машинки в Hyper-V без ошибок и с Cloud-Init. Статья небольшая, но главное не она, а то, что побудило меня ее написать. Что именно? Ответ в данном репозитории: [тык] Пока я писал статью по использованию ArgoCD и Vault

3🔥3👍1

5 Jun 2025, 13:56 UTC391 views12 reactionsread 11 August 2026

Поговорим про Templates для Ansible Roles В статье вы узнаете: 🐥Как с помощью templates Ansible прятать чувствительную информацию А также вспомните: 🐥Что такое Ansible 🐥Что такое Ansible Playbooks 🐥Что такое Ansible Roles 🐥Что такое Ansible Module

🔥5custom 540440887527945877832👾1🥰1

4 Mar 2025, 10:02 UTC565 views1 reactionsread 11 August 2026

Наткнулся на полезный ресурс, который представляет собой агрегацию многих популярных инструментов для OSINT. Вашему вниманию OSINT Framework - [ссылка] #osint #ресурс

🙏1

4 Feb 2025, 18:59 UTC565 views6 reactionsread 11 August 2026

Что ж, сессия закрыта, теперь можно вернуться к статьям. В качестве извинений за долгое отсутствие подготовил большую статью. Не будем тянуть время и сегодня поговорим про DevSecOps. Jenkins with Bandit

🍌4👍1🔥1

1 Jan 2025, 10:42 UTC469 views6 reactionsread 11 August 2026

В прекрасный январский день нет ничего лучше, чем прочитать новую статью под кружечку чая, кофе или какао☕️ Сегодня поговорим про DevSecOps. Bandit

3🍌2👾1

Showing the 12 most recent of 16 posts we hold for @ZTsInfoSec. 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

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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“ZloyTapochek's InfoSec” (@ZTsInfoSec), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ZTsInfoSec.

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.