Офіційний канал 5 окремої штурмової Київської бригади (5 ОШБр / в.ч. А4010)
😎 Долучитися https://5brigade.army/
🤝 Допомогти https://5brigade.org/
📲 Гаряча лінія рекрутингу:
+38 (095) 946 93 64
[email protected]
Created
3 May 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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
25 measurements spanning 91 days, net +81. 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 7,698–7,839 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)
Subscribers
Change
4 Nov 2026, 23:26
7,799
-4
1 Nov 2026, 17:19
7,803
+2
29 Oct 2026, 20:19
7,801
-9
26 Oct 2026, 18:45
7,810
-13
23 Oct 2026, 22:55
7,823
+6
21 Oct 2026, 06:06
7,817
-4
17 Oct 2026, 17:12
7,821
+5
15 Oct 2026, 01:47
7,816
-4
12 Oct 2026, 06:01
7,820
+6
5 Oct 2026, 22:56
7,814
-9
28 Sept 2026, 15:56
7,823
+6
18 Sept 2026, 15:37
7,817
+3
14 Sept 2026, 05:19
7,814
+2
10 Sept 2026, 16:18
7,812
-1
5 Sept 2026, 17:19
7,813
+56
1 Sept 2026, 09:25
7,757
-18
29 Aug 2026, 05:35
7,775
-6
25 Aug 2026, 22:43
7,781
-4
23 Aug 2026, 05:24
7,785
+40
16 Aug 2026, 03:34
7,745
first reading
Engagement
44 posts held, back to 15 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 26 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
43.6%
avg views ÷ 7,799 subscribers
Avg views / post
3,400
12 posts measured
Reaction rate
3.12%
reactions ÷ views · ER floor
Posts in window
12
of 44 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
44 (15 July 2026 – 5 November 2026)
Views total
40,840
Reactions total
1,273
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Nov 2026, 00:20 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
952
Videos
703
Links
652
Lifetime counters from Telegram’s own channel header, read 7 November 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.
Video runtime
35m 02s
Average length
1m 31s
Measured directly from 23 videos 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
4,374 reactions across 43 posts, in 14 distinct kinds. The most used accounts for 33.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,457
33.3%
👍
1,166
26.7%
🫡
648
14.8%
🔥
603
13.8%
custom 5438571934210082705
294
6.72%
💔
54
1.23%
⚡
48
1.10%
🙏
47
1.07%
🤝
25
0.572%
😈
12
0.274%
👏
7
0.16%
🤩
7
0.16%
😎
4
0.091%
💯
2
0.046%
Custom emoji. One row above is a 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 count beside it is Telegram’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 44 of the 44 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 4,478 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 44 most recent posts we hold, published 15 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.
Telegram Stars
Stars received
14
across the posts below
Posts paid on
6
of 44 we hold a reading for · 14%
Most on one post
7
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @fifthbrUA. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 44 most recent posts we hold for this entry, published 15 July 2026 to 5 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 12 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).
⚡️ DARTS! SHOT! HIT!
У нашому дартсі немає права на промах. Замість ігрових мішеней – ворожий тил, укриття та техніка. Замість розваги – бойова робота.
Виявити. Націлилися. Уразити.
Кожен точний middle strike – це результат майстерності, холодного розрахунку та злагодженої роботи воїнів 5 штурмової бригади.
Наша ціль – знищення противника. Наш результат – точні влучання!
🫡 3 листопада – День інженерних військ України!
Вони прокладають шлях нашим штурмовикам і перетворюють українську землю на смертельну пастку для окупантів.
Їхня зброя – знання, точний розрахунок, вибухівка та сталеві нерви.
Вітаємо воїнів інженерних підрозділів 5 окремої штурмової Київської бригади та всіх військових інженерів Збройних Сил України!
Там, де потрібно пройти – ви відкриваєте шлях. Там, де ворог нама…
⚡️ Тижневий ТОП-10 влучань по піхоті противника від 5 штурмової бригади
Окупанти намагаються просуватися і ховатися в укриттях. Але наші бійці продовжують виявляти та уражати ворожу піхоту, не даючи противнику реалізувати свої плани.
⚔️ 5 штурмова. Б'ємо ворога. Захищаємо Україну!
🇺🇦 27 жовтня – День української писемності та мови
Ми захищаємо не лише українську землю, а й право залишатися собою. Сьогодні наша мова – це символ свободи, ідентичності та незламності. Те, що ворог століттями прагне знищити.
Ми стоїмо на передовій, щоб українське слово вільно звучало на своїй землі, а наші діти зростали у вільній країні та ніколи не боялися говорити рідною. Кожен метр звільненої території – це бо…
🇺🇦 Гаряча лінія патронатної служби 5 штурмової бригади
Ми завжди на зв’язку, щоб підтримати військовослужбовців та їхні сім’ї у вирішенні важливих питань!
Наші основні напрямки:
✅ Реєстрація звернень та швидкий зворотний зв’язок з підрозділами.
✅ Допомога з оформленням медичних і правових документів.
✅ Підтримка родин поранених, зниклих безвісти, полонених чи загиблих.
✅ Консультації щодо медичних установ, центрів …
⚡️ Нічна робота операторів БПЛА
Мінування шляхів і логістика – щоденна робота підрозділу безпілотних систем 5 штурмової бригади. Бійці дистанційно встановлюють міни та підтримують бойову готовність позицій, щоб стримувати просування противника.
Підготовка до роботи починається задовго до вильоту: потрібно перевірити обладнання, підготувати дрони, антени й батареї. А дістатися на позицію та працювати там стає дедалі…
⚡️ Робота важких бомберів 5 штурмової бригади
За кожним вильотом стоїть робота цілої команди. Військовослужбовці готують техніку, перевіряють її справність, ремонтують, тестують і вдосконалюють – щоб важкі бомбери були готові до виконання завдань.
Це постійна робота: від підготовки до перевірки результату. Бо ефективність у небі починається на землі – з фаховості, уважності та злагодженості команди.
🫡 Важкі бомбер…
⚡️ Ворогу не сховатися
Воїни 5 штурмової бригади виявляють і знищують противника в укриттях, бліндажах, на ворожих позиціях і в норах.
Жодне укриття не гарантує ворогу безпеки. Бойова робота триває.
⚡️ Твої навички потрібні в 5 штурмовій бригаді
5 штурмова бригада запрошує до своїх лав мотивованих людей, готових діяти, розвиватися та посилювати Сили оборони України.
Шукаємо фахівців різного профілю: від бойових посад до забезпечення, ІТ, медицини, зв’язку, БПЛА, НРК і РЕБ. Твій досвід стане у пригоді, а навички — перевагою.
Як долучитися до команди?
🔹 За контрактом «18–24» — для молоді, яка хоче пройти служб…
⚡️ НРК-камікадзе – десант просто в тил ворога
Важкий дрон доставив наземний роботизований комплекс у тил ворожих позицій. НРК подолав маршрут, де були міни та нерозірвані боєприпаси, і дістався укриття, в якому перебував противник.
Завдання виконано – укриття знищено разом із ворогом усередині.
🫡 Технології, точність і злагоджена робота – 5 штурмова бригада.
🇺🇦 12 жовтня — День військового капелана
На фронті віра стає опорою, що допомагає не втрачати надію та триматися разом. Військовий капелан — це людина, з якою можна поговорити про найважливіше, знайти розраду й відчути духовну підтримку. Капелани поруч із нашими захисниками у хвилини тиші й у найважчі часи — з молитвою, добрим словом і щирою турботою.
Дякуємо військовим капеланам за відданість і служіння. Нехай вір…
🫡 11 жовтня – День фахівців логістичного забезпечення Збройних Сил України
Пальне, техніка, боєприпаси, спорядження — за своєчасним забезпеченням підрозділів стоїть злагоджена робота логістів. Вони планують, доставляють, ремонтують і знаходять рішення там, де від цього залежить виконання завдань.
Дякуємо логістам 5 штурмової бригади за професійність, витримку та надійність. Ваша робота — важлива частина спільного р…
👍47❤21🫡18🤝2custom 54385719342100827052⚡1
Showing the 12 most recent of 44 posts we hold for @fifthbrUA. 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 edited after publishing
@fifthbrUA edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
12 August 2026
Most recent edit
12 August 2026
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 23 registered channels — 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.
СКЕЛЯ 425 @skala425 · 19,087 Telegram ranks this channel #25 of 84 here — alongside 83 others — read 2 October 2026
24 ОМБр імені короля Данила @official24ombr · 21,038 Telegram ranks this channel #29 of 87 here — alongside 86 others — read 27 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Referenced elsewhere
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
5th Assault Brigade(en.wikipedia.org) “…counteroffensive]]
***[[Battle of Chasiv Yar]]
{{tree list/end}}
| website = [https://t.me/s/fifthbrUA Official Telegram channel]
| commander1 = Col. [[Oleksandr Yakovenko…” read 1 November 2026
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 4 November 2026 — this
entry's latest reading, not the date you are reading this.
“5 ОКРЕМА ШТУРМОВА КИЇВСЬКА БРИГАДА” (@fifthbrUA), 7,799 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/fifthbrUA.
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.