Channel
@cyber_cossacks
On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
77subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001721444703 |
|---|---|
| Type | Channel |
| Username | @cyber_cossacks |
| Description | Диванні Кібервійська Збройних Сил України |
| Created | Between 1 December 2021 and 14 March 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cyber_cossacks |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 20:16 | 77 | no change |
| 7 Aug 2026, 04:44 | 77 | first reading |
20 posts held, back to 14 March 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 pageof 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 1 January 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Нещодавно в бєлгараде вибухнув склад боєприпасів, жителі міста панікують Розкидайте в чатах вброси про радіомітки, диверсантів, окупацію та заплановані ракетні удари Нехай свинособаки сьогодні не сплять)
ОГРОМНАЯ ПОДБОРКА С КАНАЛАМИ И ЧАТАМИ ПО БЕЛГОРОДУ! БОМБИМ! Новости: @belgorod01 – главный канал о городе, много эксклюзива @fonartv – телеграм хорошего белгородского СМИ @IABelRu – старейшее местное медиа в телеграме @kudagobelgorod – канал о том, куда пойти в Белгороде @belgorod_go31 – еще один канал еще одного белгородского СМИ Люди: @belgurban – канал об урбанистике в Белгороде @painseo – интересный канал белго…
Ви знаете що робити)👌 https://t.me/belgorod_protect
А ще долучайте більше людей, щоб встигати накидати більше гівна русні в коменти:)
Прохання: Покидайте @ya9am1 шаблонів для спаму (фото, відео, меми, повідомлення, на ваш смак) Ми зробимо підбірку, щоб було легше та швидше брати участь в рейдах (контрол-с контрол-v) Завтра о шостій рейдимо наступний чат
Перепрошую за затримку Ось вам канал, заходите в коменти під кожним постом і спамите максимум, поки вас не забанять) https://t.me/novostilivez
Кличте друзів, поширюйте канал Чим більше людей активно приєднаються до рейду, тим більше москальских срак ми пдпалимо😉
кіберкозацтво pinned «Рейд 29.03 18:00»
Рейд 29.03 18:00
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Поступила пропозиція зарейдити росіські чати фотками їхніх трупачків і будь-якими повідомленнями проти війни/про реальні втрати та події в Україні/про що завгодно, що відрізняється від їхніх парадигм на ваш смак Але зробити це потрібно сплановано та одночасно, бо окремо ніхуя не вийде Пропоную зробити це завтра о шостій годині Якщо вам такий формат подобається - продовжимо далі)
Showing the 12 most recent of 20 posts we hold for @cyber_cossacks. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Рейд 29.03 18:00
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 20 most recent posts we hold, published 14 March 2022 to 1 January 2024. 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.
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.
@cyber_cossacks named 7 handles 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“кіберкозацтво” (@cyber_cossacks), 77 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/cyber_cossacks.
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.