Channel
@OWASP_ZHYTOMYR_OFFICIAL
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
81subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001382422591 |
|---|---|
| Type | Channel |
| Username | @OWASP_ZHYTOMYR_OFFICIAL |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 10 September 2026 |
| On Telegram | t.me/OWASP_ZHYTOMYR_OFFICIAL |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 05:06 | 81 | -1 |
| 9 Aug 2026, 18:02 | 82 | no change |
| 7 Aug 2026, 22:52 | 82 | first reading |
20 posts held, back to 25 February 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 18 December 2023. An engagement rate over an empty window would be a number about nothing.
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.
23 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 56.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 56.5% | |
| 👍 | 5 | 21.7% | |
| 🤩 | 3 | 13.0% | |
| 👎 | 1 | 4.35% | |
| 🤬 | 1 | 4.35% |
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 6 of the 20 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 February 2022 to 18 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Не можемо не поділитись з вами ☝️ Велика кількість tips & tricks у пошуку вразливостей. Самі типи вразливостей зручно розбиті по папочкам. https://github.com/Az0x7/vulnerability-Checklist
👍1
Signed Bohdan
Чим ще зайнятись в неділю ввечорі, як не пробігтись по питаннячкам щоб перевірити себе https://tib3rius.com/interview-questions.html
Signed Bohdan
Powerful weapon in the wrong hands: https://thehackernews.com/2023/11/offensive-and-defensive-ai-lets-chatgpt.html
Signed Bohdan
Просто не можемо не поділитись, бо це підпал 🔥 https://www.youtube.com/watch?v=H3VBtRPvvE4&t=1s
👍1
Signed Bohdan
Рубрика: “Неможливо не поділитись” В одночас і цікава і дратівлива штука Хто до яково рівня дійшов? https://neal.fun/password-game/
👍2❤1🤬1
Signed Bohdan
Державна служба спеціального зв’язку та захисту інформації запрошує молодь взяти участь у всеукраїнських командних змаганнях із кібербезпеки UA30CTF, які відбудуться 22 квітня у форматі онлайн. Для участі потрібно сформувати команду (до п’яти осіб разом із капітаном) та зареєструватися. Є бажаючі ?)) Писати ➡️ @adfgjy
Signed Bohdan
Погоджуєтесь? Можемо поділитись думками в нашому @OWASP_ZHYTOMYR_CHAT
Signed Bohdan
Друзі, вітаємо вас! Спостергаємо непогану активність і зацікавленість людей в сфері кібер безпеки. Багато запитують “як допомагати, де підвчитись?” Маємо чудовий Security study plan https://github.com/jassics/security-study-plan Будемо раді обговоренням в нашому OWASP чатику @OWASP_ZHYTOMYR_CHAT
❤3🤩3
Signed Bohdan
З новим роком! Сильні люди вільного міста, бажаємо вам лише найкращого 😇
❤8👎1
Signed Bohdan
Шановне товариство! Плекаю надії на те, що всі в безпеці! Від імені OWASP Zhytomyr просимо пробачення, що пропали з інфопростору. Причини пояснювати не будемо, а от ситуацію мємо намір покращити! 🇺🇦 Тож принесли вам цікавого матеріалу: https://www.youtube.com/watch?v=Yjogm9ejcPQ
❤1👍1
Ще одна надважлива політична та безпекова перемога! Україна стає учасником-контрибутором Об'єднаного центру передових технологій з кібероборони НАТО!
Обращаюсь к российским айтишникам. У вас забирают лучшие года жизни.
Showing the 12 most recent of 20 posts we hold for @OWASP_ZHYTOMYR_OFFICIAL. 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.
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.
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.
@OWASP_ZHYTOMYR_OFFICIAL named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“OWASP_ZHYTOMYR_OFFICIAL” (@OWASP_ZHYTOMYR_OFFICIAL), 81 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/OWASP_ZHYTOMYR_OFFICIAL.
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.