28 Jul 2026, 12:15 UTC84 viewsread 9 August 2026
Раменское Бронницы Жуковский Опасность по БПЛА
Channel
Юго-восток МО. Радар
@radarug_vostokMO
On this record: Growth · Engagement · Posts · Citations · Cite this entry
77subscribers
-6 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 | -1003657983915 |
|---|---|
| Type | Channel |
| Username | @radarug_vostokMO |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 13 September 2026 |
| On Telegram | t.me/radarug_vostokMO |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 18:17 | 77 | -3 |
| 22 Aug 2026, 01:36 | 80 | -2 |
| 15 Aug 2026, 02:37 | 82 | -1 |
| 9 Aug 2026, 17:47 | 83 | no change |
| 7 Aug 2026, 19:37 | 83 | first reading |
Engagement
20 posts held, back to 28 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.
Recent posts
28 Jul 2026, 12:15 UTC86 viewsread 9 August 2026
ГО Воскресенск Московская область Фиксация БПЛА
28 Jul 2026, 11:30 UTC94 viewsread 9 August 2026
Все наши ресурсы Радар Московской области - https://t.me/radar_msk1 Новостной канал - https://t.me/novosti_bpla Радар по востоку Московской области - https://t.me/radar_vostokMO Радар по югу Московской области - https://t.me/radarug_MO Радар по Юго-востоку Московской области - https://t.me/radarug_vostokMO Радар по Юго-Западу Московской области - https://t.me/radarug_zapadMO Радар по Северо-западу Московской …
28 Jul 2026, 09:16 UTC78 viewsread 9 August 2026
ГО Коломна Московская область Работа ПВО по БПЛА Меры безопасности
28 Jul 2026, 08:16 UTC78 viewsread 9 August 2026
ГО Бронницы Московская область Работа ПВО по БПЛА Меры безопасности
28 Jul 2026, 08:08 UTC75 viewsread 9 August 2026
ГО Коломна Московская область Работа ПВО по БПЛА Меры безопасности
28 Jul 2026, 04:45 UTC78 viewsread 9 August 2026
ГО Зарайск Московская область Фиксация БПЛА
28 Jul 2026, 02:48 UTC79 viewsread 9 August 2026
Домодедово Чехов Подольск Воскресенск Раменское Бронницы Меры безопасности остаются
28 Jul 2026, 02:31 UTC75 viewsread 9 August 2026
Воскресенск/Бронницы Еще БПЛА к вам
28 Jul 2026, 02:27 UTC75 viewsread 9 August 2026
Раменское Бронницы Воскресенск Меры безопасности
28 Jul 2026, 02:26 UTC68 viewsread 9 August 2026
ГО Воскресенск Московская область Продолжается работа ПВО по БПЛА Меры безопасности
28 Jul 2026, 02:26 UTC62 viewsread 9 August 2026
Воскресенск го Возможно пролёт БПЛА
Showing the 12 most recent of 20 posts we hold for @radarug_vostokMO. 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.
Mentions
Named by 6 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.
Names
Channels on the register whose handles appear in this channel's posts.
ОПБ. Новости по БПЛА
@novosti_bpla · 4421 postПодмосковный
@novosti_podmoskovie · 571 postРадар Москва | Подмосковье
@radar_msk1 · 2,8951 postВосток МО. Радар
@radar_vostokMO · 891 postСеверо-запад МО. Радар
@radarsevero_zapadMO · 461 postЮг МО. Радар
@radarug_MO · 1051 postЮго-Запад МО. Радар
@radarug_zapadMO · 291 postСевер МО. Радар
@sevepMO · 771 postСеверо-восток МО. Радар
@severovostok_MO · 211 post
@novosti_bpla · 4421 postПодмосковный
@novosti_podmoskovie · 571 postРадар Москва | Подмосковье
@radar_msk1 · 2,8951 postВосток МО. Радар
@radar_vostokMO · 891 postСеверо-запад МО. Радар
@radarsevero_zapadMO · 461 postЮг МО. Радар
@radarug_MO · 1051 postЮго-Запад МО. Радар
@radarug_zapadMO · 291 postСевер МО. Радар
@sevepMO · 771 postСеверо-восток МО. Радар
@severovostok_MO · 211 post
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Юго-восток МО. Радар” (@radarug_vostokMO), 77 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/radarug_vostokMO.
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.