Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Москва | Подмосковье

Channel

Радар Москва | Подмосковье

@radar_msk1

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

2,895subscribers

+960 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003985243471
TypeChannel
Username@radar_msk1
CreatedBetween 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/radar_msk1

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,9352,8952,4157 August 2026 — 1,935 subscribers7 August 2026 — 1,935 subscribers8 August 2026 — 1,941 subscribers10 August 2026 — 1,971 subscribers13 August 2026 — 1,985 subscribers16 August 2026 — 2,129 subscribers20 August 2026 — 2,418 subscribers23 August 2026 — 2,471 subscribers26 August 2026 — 2,523 subscribers28 August 2026 — 2,535 subscribers1 September 2026 — 2,543 subscribers4 September 2026 — 2,817 subscribers9 September 2026 — 2,852 subscribers13 September 2026 — 2,877 subscribers17 September 2026 — 2,895 subscribers7 August 202617 September 2026
15 measurements spanning 40 days, net +960. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,791–3,039 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 06:582,895+18
13 Sept 2026, 15:562,877+25
9 Sept 2026, 22:002,852+35
4 Sept 2026, 23:422,817+274
1 Sept 2026, 01:462,543+8
28 Aug 2026, 23:042,535+12
26 Aug 2026, 02:152,523+52
23 Aug 2026, 11:092,471+53
20 Aug 2026, 06:172,418+289
16 Aug 2026, 21:232,129+144
13 Aug 2026, 08:251,985+14
10 Aug 2026, 18:341,971+30
8 Aug 2026, 03:011,941+6
7 Aug 2026, 20:461,935no change
7 Aug 2026, 19:161,935first reading

Engagement

20 posts held, back to 6 August 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 02:40 UTC879 viewsread 7 August 2026

Московская область Отбой опасности по БПЛА

6 Aug 2026, 23:39 UTC934 viewsread 7 August 2026

Го Наро-Фоминск Опасность по БПЛА

6 Aug 2026, 18:53 UTC≈1,030 viewsread 7 August 2026

Серебряные пруды Зарайск ГО Луховицы МО Коломна ГО Егорьевск МО Воскресенск ГО Опасность по БПЛА сохраняется, периодически появляются фиксации БПЛА от Рязанской области

6 Aug 2026, 15:49 UTC≈1,540 viewsread 7 August 2026

Опасность по БПЛА сохраняется для городов : Серпухов ГО Чехов МО Наро-Фоминск ГО Можайск ГО Серебрянные Пруды ГО Ступино ГО Кашира ГО Одинцово ГО Кубинка Руза ГО Солнечногорск ГО Клин ГО Истра ГО Волоколамск ГО Шаховская Коломна ГО Луховицы ГО Зарайск ГО Бронницы ГО Егорьевск МО Шатура МО Воскресенск ГО Орехово-Зуево ГО Павловский Посад ГО Богородский ГО

6 Aug 2026, 15:39 UTC828 viewsread 7 August 2026

Богородский ГО Опасность по БПЛА

6 Aug 2026, 15:34 UTC781 viewsread 7 August 2026

Го Павловский Посад Опасность по БПЛА

6 Aug 2026, 15:28 UTC930 viewsread 7 August 2026

Воскресенск Бронницы Раменское Жуковский Опасность по БПЛА

Showing the 12 most recent of 20 posts we hold for @radar_msk1. 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

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 7 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.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Радар Москва | Подмосковье” (@radar_msk1), 2,895 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_msk1.

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.