Channel
@boyovyy_sokil
On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry
507subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002363149346 |
|---|---|
| Type | Channel |
| Username | @boyovyy_sokil |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/boyovyy_sokil |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 04:38 | 507 | +7 |
| 29 Aug 2026, 02:05 | 500 | -48 |
| 21 Aug 2026, 07:52 | 548 | -2 |
| 14 Aug 2026, 13:07 | 550 | +5 |
| 8 Aug 2026, 03:47 | 545 | no change |
| 7 Aug 2026, 17:36 | 545 | first reading |
20 posts held, back to 7 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 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 28 July 2026. 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.
За попередньою інформацією, найближчим часом існує ймовірність застосування до 3 балістичних ракет середньої дальності по території України. Ймовірний район пусків — район м. Тебріз (Іран). Бойовий сокіл | Карта шахедів
Signed Cartel
Візуалізація пуску ракети Х-47М2 «Кинжал» з Ліпецької області та її руху до Староконстянтинова. Бойовий сокіл | Карта шахедів
Signed .
Поки що не маємо можливості інформувати, вибачте за незручності, до місяця такі справи( Бойовий сокіл | Карта шахедів
Signed Cartel
Також можливе оголошення балістичної загрози з Єйська Бойовий сокіл | Карта шахедів
Signed Cartel
Дніпропетровщина/Харківщина - уважно Бойовий сокіл | Карта шахедів
Signed Cartel
Загроза балістики з Таганрогу Бойовий сокіл | Карта шахедів
Signed Cartel
Не фіксую біля Пісочина Бойовий сокіл | Карта шахедів
Signed Cartel
На Пісочин Бойовий сокіл | Карта шахедів
Signed Cartel
Ще дві ракети, курс як в попередніх Бойовий сокіл | Карта шахедів
Signed Cartel
Дві ракети на Полтаву Бойовий сокіл | Карта шахедів
Signed Cartel
Ракета на Харків Бойовий сокіл | Карта шахедів
Signed Cartel
БПЛА на Світловодськ Бойовий сокіл | Карта шахедів
Signed Cartel
Showing the 12 most recent of 20 posts we hold for @boyovyy_sokil. 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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Бойовий Сокіл” (@boyovyy_sokil), 507 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/boyovyy_sokil.
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.