Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар.ру | Курская область ( обстрелы, БПЛА, ракеты, сводки )

Channel

Радар.ру | Курская область ( обстрелы, БПЛА, ракеты, сводки )

@radar_ru_kursk

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

1,008subscribers

+64 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-1002271587616
TypeChannel
Username@radar_ru_kursk
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/radar_ru_kursk

Topic

National 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

9441,0089767 August 2026 — 944 subscribers8 August 2026 — 944 subscribers8 August 2026 — 947 subscribers15 August 2026 — 952 subscribers21 August 2026 — 958 subscribers28 August 2026 — 971 subscribers5 September 2026 — 983 subscribers13 September 2026 — 1,000 subscribers17 September 2026 — 1,008 subscribers7 August 202617 September 2026
9 measurements spanning 41 days, net +64. 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 934–1,018 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 05:571,008+8
13 Sept 2026, 05:571,000+17
5 Sept 2026, 09:37983+12
28 Aug 2026, 09:57971+13
21 Aug 2026, 08:15958+6
15 Aug 2026, 01:13952+5
8 Aug 2026, 09:05947+3
8 Aug 2026, 00:49944no change
7 Aug 2026, 13:41944first 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, 23:58 UTC14 viewsread 8 August 2026

Курская область Орловская область Брянская область Отбой ракетной опасности 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 22:50 UTC38 viewsread 8 August 2026

Курская область Ракетная опасность 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 22:41 UTC42 viewsread 8 August 2026

Пристень, Обоянь, Солнцево и близлежащие Курская область Тревога по БпЛА 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 21:43 UTC54 viewsread 8 August 2026

Трояново -Студенок Тревога по БПЛА Курская область И далее на Орловскую область 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 21:34 UTC53 viewsread 8 August 2026

Железногорский район Курская область Тревога по БПЛА Сохраняется 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 21:31 UTC48 viewsread 8 August 2026

Хомутовка Курская область Тревога по БПЛА И далее на Орловскую область 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 21:09 UTC51 viewsread 8 August 2026

Курская область Тревога по БПЛА сохраняется 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 20:53 UTC55 viewsread 8 August 2026

Продолжаются фиксации БПЛА через Белгородскую область Курскую область Воронежскую область И далее в тыл Тыловым регионам приготовиться к объявлению опасности по БПЛА Не игнорируйте тревоги 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 20:47 UTC49 viewsread 8 August 2026

Курск и близлежащие Тревога по БПЛА Курская область 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 20:08 UTC50 viewsread 8 August 2026

Коренево и далее в направлении Рыльск, Хомутовка, Железногорск, Восточная часть Брянской области на Орловскую область и далее в тыловые регионы фиксации БПЛА 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 16:22 UTC56 viewsread 8 August 2026

🟢 Курская область: внимание! Отбой ракетной опасности. 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

7 Aug 2026, 16:19 UTC55 viewsread 8 August 2026

⚠️ Курская область: ракетная опасность! Если вы находитесь дома, необходимо укрыться в помещениях без окон со сплошными стенами: в коридоре, ванной, кладовой. Если вы находитесь на улице — зайдите в ближайшее здание или подходящее укрытие. 🎯Радар.ру | Курск - @radar_ru_kursk 🎯Радар.ру | Курск - @radar_ru_kursk

Showing the 12 most recent of 20 posts we hold for @radar_ru_kursk. 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 1 registered channel — 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.

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_ru_kursk), 1,008 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_ru_kursk.

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.