Сергиев Посад Опасность по БПЛА от Александрова

Channel
Северо-восток МО. Радар
@severovostok_MO
On this record: Growth · Engagement · Posts · Citations · Cite this entry
21subscribers
+2 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 | -1003598323548 |
|---|---|
| Type | Channel |
| Username | @severovostok_MO |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/severovostok_MO |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 00:17 | 21 | -1 |
| 31 Aug 2026, 20:05 | 22 | +1 |
| 24 Aug 2026, 13:04 | 21 | +2 |
| 11 Aug 2026, 17:45 | 19 | no change |
| 7 Aug 2026, 18:39 | 19 | first reading |
Engagement
20 posts held, back to 3 June 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
Московская область Ракетная опасность
Пушкино, Московская область Меры предосторожности! Источник радар LPR
Московская область Внимание по ракетной опасности
Все наши ресурсы Радар Московской области - 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 Радар по Северо-западу Московской …
https://t.me/radar_msk1 ссылка на основной канал пока нет возможности писать в наши отдельные каналы на постоянной основе
Все наши отдельные каналы пока не работают Ссылка на основной канал https://t.me/radar_msk1 :
Московская область Отбой опасности по БПЛА
Московская область Ракетная опасность
Московская область Внимание по ракетной опасности
Ищем людей из Подмосковья для более точного оповещения, писать нам в бота - @RadarOS_bot Указать свой город/пгт или н.п. Города : Апрелевка Балашиха Белоозерский Бронницы Верея Видное Волоколамск Воскресенск Высоковск Голицыно Дедовск Дзержинский Дмитров Домодедово Дрезна Дубна Егорьевск Жуковский Зарайск Звенигород Ивантеевка Истра Кашира Клин Коломна Королев Котельники Красноармейск Красногорск Красноснозаводск Кр…
Московская область Ракетная опасность
Showing the 12 most recent of 20 posts we hold for @severovostok_MO. 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
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.
@radar_msk1 · 2,8954 postsОПБ. Новости по БПЛА
@novosti_bpla · 4422 postsВосток МО. Радар
@radar_vostokMO · 892 postsСеверо-запад МО. Радар
@radarsevero_zapadMO · 462 postsЮг МО. Радар
@radarug_MO · 1052 postsЮго-восток МО. Радар
@radarug_vostokMO · 772 postsЮго-Запад МО. Радар
@radarug_zapadMO · 292 postsСевер МО. Радар
@sevepMO · 772 postsПодмосковный
@novosti_podmoskovie · 571 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Северо-восток МО. Радар” (@severovostok_MO), 21 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/severovostok_MO.
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.