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

Channel

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

@radar_ru_krasnodar

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

3,394subscribers

+130 since we began measuring on 7 August 2026

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

Register entry

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

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

3,2643,3943,3297 August 2026 — 3,264 subscribers8 August 2026 — 3,267 subscribers11 August 2026 — 3,297 subscribers14 August 2026 — 3,312 subscribers17 August 2026 — 3,301 subscribers20 August 2026 — 3,304 subscribers23 August 2026 — 3,302 subscribers26 August 2026 — 3,311 subscribers29 August 2026 — 3,318 subscribers31 August 2026 — 3,312 subscribers4 September 2026 — 3,319 subscribers9 September 2026 — 3,327 subscribers12 September 2026 — 3,347 subscribers17 September 2026 — 3,394 subscribers7 August 202617 September 2026
14 measurements spanning 41 days, net +130. 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 3,245–3,414 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 02:373,394+47
12 Sept 2026, 16:593,347+20
9 Sept 2026, 01:203,327+8
4 Sept 2026, 02:183,319+7
31 Aug 2026, 18:483,312-6
29 Aug 2026, 03:253,318+7
26 Aug 2026, 07:093,311+9
23 Aug 2026, 11:543,302-2
20 Aug 2026, 08:133,304+3
17 Aug 2026, 11:443,301-11
14 Aug 2026, 04:183,312+15
11 Aug 2026, 02:523,297+30
8 Aug 2026, 07:203,267+3
7 Aug 2026, 13:473,264first reading

Engagement

37 posts held, back to 7 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 2 pages 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 37 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:27 UTC24 viewsread 7 August 2026

Ст. Марьяновская И далее в направлении Ильский, Афипский Тревога по БПЛА Особое внимание НПЗ Краснодарский край 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 23:25 UTC29 viewsread 7 August 2026

Экстренная информация РСЧС: БЕСПИЛОТНАЯ ОПАСНОСТЬ на территории муниципальных образований: Туапсинский округ, муниципальный округ г. Анапа, г. Новороссийск, г. Геленджик, Темрюкский, Крымский, Абинский, Северский районы. 08.08.2026. 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 23:19 UTC35 viewsread 7 August 2026

Ильский Афипский и близлежащие Краснодарский край Тревога по БПЛА 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 23:14 UTC37 viewsread 7 August 2026

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

7 Aug 2026, 22:40 UTC41 viewsread 7 August 2026

Чушка Таманский залив и близлежащие Тревога по БПЛА Краснодарский край 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 19:55 UTC172 viewsread 7 August 2026

Все южные районы Ростовская область, Ростов на Дону Северные районы Краснодарского края от Ростовской области и Азовского моря Опасность по БПЛА 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 19:47 UTC181 viewsread 7 August 2026

Авиационная ракетная бомбовая опасность ЛДНР, Запорожская область РФ Возможны пуски Штормов в указанном направлении и далее на Ростовскую область, Краснодарский край, восток Крыма 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 19:46 UTC178 viewsread 7 August 2026

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

7 Aug 2026, 16:38 UTC225 viewsread 7 August 2026

Керченский пролив с Чёрного моря, суда на рейде в Керченский пролив с Чёрного моря, п. Волна, Керченский полуостров прибрежная зона Черного моря, Причерноморье Краснодарский край Анапа и близлежащие Тревога по БЭК 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 15:54 UTC247 viewsread 7 August 2026

Геленджик и близлежащие опасность по БПЛА 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 15:50 UTC211 viewsread 7 August 2026

Суда на рейде Новороссийск Тревога по БПЛА Срочно принять меры безопасности Краснодарский край 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

7 Aug 2026, 15:40 UTC212 viewsread 7 August 2026

Мысхако Кабардинка Новороссийск и близлежащие Принять меры безопасности Краснодарский край 🎯Радар.ру | Краснодарский край - @radar_ru_krasnodar

Showing the 12 most recent of 37 posts we hold for @radar_ru_krasnodar. 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_krasnodar), 3,394 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_ru_krasnodar.

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.