23 May 2026, 19:15 UTC43 viewsread 9 August 2026
💣 Просяна (Дніпропетровська обл.) Загроза застосування КАБів.
Channel
Military Universe
@monitorinukraine
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
109subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001907045814 |
|---|---|
| Type | Channel |
| Username | @monitorinukraine |
| Description | 🚀🛵 Автооповіщувальний канал який завчасно інформує про пуск, напрямок та кількість ворожих ракет та БпЛА і не тільки. 📮 Звʼязок з адміністрацією каналу @monitorinukrainebot Важливо: https://t.me/monitorinukraine/80340 |
| Created | Between 1 April 2023 and 31 October 2023— 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/monitorinukraine |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 07:46 | 109 | no change |
| 7 Aug 2026, 12:28 | 109 | first reading |
Engagement
20 posts held, back to 23 May 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 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 23 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈13,800
- Videos
- ≈152
- Links
- ≈7,680
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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
23 May 2026, 19:15 UTC43 viewsread 9 August 2026
💣 Краснопілля (Сумська обл.) Загроза застосування КАБів.
23 May 2026, 19:14 UTC44 viewsread 9 August 2026
Forwarded from @kpszsu
🚀Пуски керованих авіаційних бомб ворожою тактичною авіацією на Сумщину.
23 May 2026, 19:14 UTC44 viewsread 9 August 2026
💥 Околиці Києва - вибухи
23 May 2026, 19:14 UTC44 viewsread 9 August 2026
Сумщина: БпЛА курсом на Недригайлів Чернігівщина: БпЛА курсом на Семенівку Київщина: БпЛА курсом на Київ Полтавщина: БпЛА курсом на Комишню БпЛА курсом на Лохвицю БпЛА курсом на Заводське Харківщина: 10х БпЛА курсом на Златопіль 3х БпЛА курсом на Близнюки 6х БпЛА курсом на Лозову БпЛА курсом на Краснопавлівку 2х БпЛА курсом на Балаклію Дніпропетровщина: БпЛА курсом на Вербки 10х БпЛА курсом на Юріївку Миколаївщ…
23 May 2026, 19:12 UTC30 viewsread 9 August 2026
Forwarded from @kpszsu
🚀Пуски керованих авіаційних бомб ворожою тактичною авіацією на Дніпропетровщину.
23 May 2026, 19:08 UTC32 viewsread 9 August 2026
Київ: БпЛА курсом на Погреби Наш канал | Карта тривог
23 May 2026, 19:07 UTC31 viewsread 9 August 2026
Forwarded from @kpszsu
🛵 Київ - БпЛА в напрямку міста.
23 May 2026, 19:06 UTC32 viewsread 9 August 2026
Київ: БпЛА курсом на Троєщину Наш канал | Карта тривог
23 May 2026, 19:06 UTC31 viewsread 9 August 2026
Forwarded from @kpszsu
🛵Група БпЛА на півночі Чернігівщини курсом на Короп.
23 May 2026, 19:03 UTC33 viewsread 9 August 2026
~55 БПЛА в повітряному просторі України. Перебувайте в укритті!
23 May 2026, 19:03 UTC31 viewsread 9 August 2026
🛵Сумщина: →Кролевець/Чернігівщина; →Дубовʼязівка/Чернігівщина; →Глухів/Шостка. 🛵Чернігівщина: →Холми/Корюківка(2х). 🛵Київщина: →Бровари/Київ. 🛵Полтавщина: →Комишня/Миргород; →Заводське/Лохвиця (2х); →Лубни/Черкащина. 🛵Харківщина: →Барвінкове/Близнюки(18х). 🛵Дніпропетровщина: →Петропавлівка/Шахтарське(6х); →Широке/Інгулець(10х). 🛵Кіровоградщина: →Бобринець/Новоукраїнка. 🛵Миколаївщина: →Новий Буг/Кіровоградщина(…
Showing the 12 most recent of 20 posts we hold for @monitorinukraine. 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.
Mentions
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Military Universe” (@monitorinukraine), 109 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/monitorinukraine.
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.