✈️ Борт Ту-22м3 в районі Криму. Загроза пусків Х-22/32 у напрямку Одещини. monitoring ua🇺🇦

Channel
МОНІТОРИНГ UA🇺🇦
@monitoring_ua1
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
4,132subscribers
-39 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001203958437 |
|---|---|
| Type | Channel |
| Username | @monitoring_ua1 |
| Created | 28 March 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/monitoring_ua1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 17:54 | 4,132 | -4 |
| 30 Aug 2026, 16:01 | 4,136 | -6 |
| 27 Aug 2026, 09:58 | 4,142 | -8 |
| 24 Aug 2026, 07:12 | 4,150 | -5 |
| 21 Aug 2026, 01:32 | 4,155 | -5 |
| 17 Aug 2026, 22:03 | 4,160 | -3 |
| 14 Aug 2026, 19:45 | 4,163 | -4 |
| 10 Aug 2026, 23:48 | 4,167 | -3 |
| 8 Aug 2026, 06:37 | 4,170 | -1 |
| 7 Aug 2026, 12:33 | 4,171 | no change |
| 7 Aug 2026, 12:20 | 4,171 | first reading |
Engagement
27 posts held, back to 5 August 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 4 pages 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 27 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
33 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 12 | 36.4% | |
| 🔥 | 8 | 24.2% | |
| ❤ | 6 | 18.2% | |
| 🤝 | 2 | 6.06% | |
| 🤬 | 2 | 6.06% | |
| 👎 | 1 | 3.03% | |
| 🤔 | 1 | 3.03% | |
| 🤮 | 1 | 3.03% |
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 16 of the 27 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 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 5 August 2026 to 8 August 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.
Recent posts
🇺🇦 У ніч на 08.08.26, згідно зі звітом Повітряних Сил, Силами оборони було знищено з числа запущених засобів ураження: ☄ 0/6 балістичних ракет 9м723 «Іскандер-М» (ОТРК «Іскандер») / РМ-48У (ЗРК С-300/С-400); ⚠️ 135/151 ударних, імітаційних та розвідувальних БпЛА. Всього знешкоджено 89,4% БпЛА. Всього знешкоджено 0% ракетного озброєння. monitoring ua🇺🇦
👍2
💥Сизранський НПЗ — уражено. Добрий ранок 👋 monitoring ua🇺🇦
👍2
🟨 Ймовірність комбінованої атаки на низькому рівні. Стратегічна авіація не активна. Одинарні ударні БпЛА у повітряному просторі України. Ймовірні додаткові запуски груп вподовж ночі для атаки міст на Півдні та Сході (Суми, Харків, Запоріжжя, Дніпро, Одеса). Балістичні загрози на ніч стабільно на середньому рівні. Флот без активності. monitoring ua🇺🇦
⚡️понад 300 добрих дронів полетіли на окуповані території та росію. Зранку очікуємо на гарні новини 🤏🏻 monitoring ua🇺🇦
❤2
⚡️Усі підводні човни на морській базі «Рибачий» у Тихому океані були накриті сітками для захисту від FPV-дронів. Також сітками закрили кораблі та катери. monitoring ua🇺🇦
🤔1
🟢 Відбій ракетної загрози. monitoring ua🇺🇦
✈️ Зліт МіГ-31К ВПС рф. МіГ-31К — носій гіперзвукової аеробалістичної ракети Х-47м2 комплексу "Кинджал", яка становить загрозу для всіх регіонів країни. monitoring ua🇺🇦
Одеса. Ракетою вдарили у стадіон "Чорноморець". Сильні пошкодження. monitoring ua🇺🇦
💥 Одеса вибухи, дорозвідка. monitoring ua🇺🇦
‼️ 3х реактивних БпЛА у напрямку Одеса / порт
3 ракети "Бандероль" на Одесу! monitoring ua🇺🇦
Showing the 12 most recent of 27 posts we hold for @monitoring_ua1. 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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“МОНІТОРИНГ UA🇺🇦” (@monitoring_ua1), 4,132 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/monitoring_ua1.
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.