Telegram RegisterThe public register of Telegram
Telegram profile photo for Моя Москва | Радар

Channel

Моя Москва | Радар

@myMoscow_radar

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

10,011subscribers

-405 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002510728449
TypeChannel
Username@myMoscow_radar
DescriptionИнформационный источник, созданный для оперативного оповещения населения о воздушных угрозах на территории Москвы 🤝🏻 Сотрудничество - @m1khailromanov и @kkardashyan
CreatedBetween 1 February 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/myMoscow_radar

Topic

International news — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 the other topics.

Growth

10,01110,41610,213.57 August 2026 — 10,416 subscribers7 August 2026 — 10,416 subscribers8 August 2026 — 10,415 subscribers9 August 2026 — 10,400 subscribers10 August 2026 — 10,394 subscribers11 August 2026 — 10,383 subscribers12 August 2026 — 10,375 subscribers14 August 2026 — 10,361 subscribers15 August 2026 — 10,353 subscribers16 August 2026 — 10,355 subscribers17 August 2026 — 10,345 subscribers18 August 2026 — 10,357 subscribers19 August 2026 — 10,358 subscribers20 August 2026 — 10,356 subscribers21 August 2026 — 10,349 subscribers23 August 2026 — 10,340 subscribers25 August 2026 — 10,336 subscribers26 August 2026 — 10,330 subscribers27 August 2026 — 10,326 subscribers28 August 2026 — 10,321 subscribers29 August 2026 — 10,313 subscribers30 August 2026 — 10,312 subscribers31 August 2026 — 10,308 subscribers1 September 2026 — 10,291 subscribers2 September 2026 — 10,284 subscribers3 September 2026 — 10,273 subscribers5 September 2026 — 10,276 subscribers8 September 2026 — 10,267 subscribers11 September 2026 — 10,244 subscribers13 September 2026 — 10,236 subscribers14 September 2026 — 10,224 subscribers16 September 2026 — 10,207 subscribers19 September 2026 — 10,191 subscribers25 September 2026 — 10,189 subscribers4 October 2026 — 10,141 subscribers8 October 2026 — 10,137 subscribers13 October 2026 — 10,127 subscribers14 October 2026 — 10,117 subscribers15 October 2026 — 10,114 subscribers16 October 2026 — 10,113 subscribers17 October 2026 — 10,109 subscribers19 October 2026 — 10,098 subscribers20 October 2026 — 10,095 subscribers21 October 2026 — 10,087 subscribers22 October 2026 — 10,078 subscribers23 October 2026 — 10,086 subscribers24 October 2026 — 10,077 subscribers25 October 2026 — 10,072 subscribers26 October 2026 — 10,068 subscribers27 October 2026 — 10,069 subscribers28 October 2026 — 10,065 subscribers29 October 2026 — 10,059 subscribers30 October 2026 — 10,056 subscribers31 October 2026 — 10,049 subscribers1 November 2026 — 10,044 subscribers2 November 2026 — 10,038 subscribers3 November 2026 — 10,024 subscribers4 November 2026 — 10,022 subscribers5 November 2026 — 10,011 subscribers7 August 20265 November 2026
59 measurements spanning 90 days, net -405. 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 9,950–10,477 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
5 Nov 2026, 17:2510,011-11
4 Nov 2026, 16:5910,022-2
3 Nov 2026, 16:5810,024-14
2 Nov 2026, 15:4910,038-6
1 Nov 2026, 14:5610,044-5
31 Oct 2026, 15:0610,049-7
30 Oct 2026, 14:3610,056-3
29 Oct 2026, 17:3010,059-6
28 Oct 2026, 19:5910,065-4
27 Oct 2026, 17:4910,069+1
26 Oct 2026, 16:1810,068-4
25 Oct 2026, 17:5910,072-5
24 Oct 2026, 20:0710,077-9
23 Oct 2026, 17:2010,086+8
22 Oct 2026, 19:5110,078-9
21 Oct 2026, 19:2710,087-8
20 Oct 2026, 12:3110,095-3
19 Oct 2026, 11:5110,098-11
17 Oct 2026, 15:4510,109-4
16 Oct 2026, 16:3710,113first reading

Engagement

266 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 43 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.19%
avg views ÷ 10,011 subscribers
Avg views / post
620
64 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
64
of 266 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held266 (5 August 2026 – 6 November 2026)
Views total39,688
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 09:01 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈13
Videos
≈11
Links
≈7,670

Lifetime counters from Telegram’s own channel header, read 6 November 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

Telegram’s own ‘edited’ marker: 0 of 64 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 06:00 UTC288 viewsread 6 November 2026

За прошедшую ночь силами противовоздушной обороны было уничтожено 142 БПЛА над территориями Курской, Белгородской, Тульской, Орловской, Ростовской, Астраханской областей, Московского региона, Краснодарского края, Республики Крым и над акваториями Черного и Азовского морей. 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

6 Nov 2026, 03:30 UTC480 viewsread 6 November 2026

Московская область Отбой опасности по БПЛА 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

6 Nov 2026, 01:09 UTC532 viewsread 6 November 2026

МО Истра Московская область Отбой опасности по БПЛА На территории региона опасность сохраняется 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 23:57 UTC573 viewsread 6 November 2026

ГО Домодедово Московская область Работа ПВО по БПЛА Меры безопасности 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 23:21 UTC568 viewsread 6 November 2026

МО Истра Московская область Опасность по БПЛА 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 22:45 UTC592 viewsread 6 November 2026

ГО Домодедово Московская область Работа ПВО по БПЛА 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 22:39 UTC587 viewsread 6 November 2026

Московская область Опасность по БПЛА 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 12:15 UTC763 viewsread 6 November 2026

На данный момент по обстановке тихо При возникновении непосредственной угрозы оповестим немедленно. Берегите себя и своих близких! 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 08:00 UTC827 viewsread 6 November 2026

За ночь средствами ПВО было уничтожено 496 БПЛА над Астраханской, Белгородской, Брянской, Волгоградской, Воронежской, Курской, Нижегородской, Орловской, Ростовской, Рязанской, Тамбовской, Тульской областей, Московского региона, Краснодарского края, Республики Крым и над акваториями Азовского и Черного морей. 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 06:21 UTC814 viewsread 6 November 2026

Московская область Отбой опасности по БПЛА 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

5 Nov 2026, 02:18 UTC866 viewsread 6 November 2026

МО Истра ГО Клин Московская область Опасность по БПЛА 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

4 Nov 2026, 21:42 UTC912 viewsread 6 November 2026

ГО Клин МО Истра Московская область Отбой опасности по БПЛА На территории региона опасность сохраняется 📲 Наш канал в МАХ - ❗️Моя Москва | Радар

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

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

“Моя Москва | Радар” (@myMoscow_radar), 10,011 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/myMoscow_radar.

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.