Telegram RegisterThe public register of Telegram
Telegram profile photo for РАДАР ЮГ НЕБО Ростов Краснодар | ЛПР Тревоги БПЛА МОНИТОРИНГ

Channel

РАДАР ЮГ НЕБО Ростов Краснодар | ЛПР Тревоги БПЛА МОНИТОРИНГ

@radar_yog

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

984subscribers

+365 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-1003551722710
TypeChannel
Username@radar_yog
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live2 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/radar_yog

Topic

Other / unclassifiable — 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 61% 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

619984801.57 August 2026 — 619 subscribers8 August 2026 — 619 subscribers8 August 2026 — 624 subscribers15 August 2026 — 650 subscribers23 August 2026 — 695 subscribers29 August 2026 — 793 subscribers8 September 2026 — 846 subscribers16 September 2026 — 898 subscribers2 October 2026 — 984 subscribers7 August 20262 October 2026
9 measurements spanning 56 days, net +365. 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 564–1,039 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 06:17984+86
16 Sept 2026, 11:57898+52
8 Sept 2026, 09:19846+53
29 Aug 2026, 05:45793+98
23 Aug 2026, 05:04695+45
15 Aug 2026, 01:56650+26
8 Aug 2026, 18:03624+5
8 Aug 2026, 03:02619no change
7 Aug 2026, 18:12619first reading

Engagement

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

Recent posts

8 Aug 2026, 02:59 UTC1 viewsread 8 August 2026

Отбой опасности по БПЛА 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:47 UTC4 viewsread 8 August 2026

Между Пчелиное, Красноселовка Фиксация БПЛА в направлении Приветное, Рыбачье Республика Крым 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:23 UTC8 viewsread 8 August 2026

Ахтырский и далее на Краснодар Тревога по БПЛА Краснодарский край 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:19 UTC9 viewsread 8 August 2026

Краснодарский край Республика Адыгея Отбой ракетной опасности 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:19 UTC9 viewsread 8 August 2026

Орджоникидзе Феодосия Коктебель и близлежащие Опасность по БПЛА Республика Крым 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:11 UTC10 viewsread 8 August 2026

Советский район Республика Крым Тревога по БПЛА, повторно 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:11 UTC9 viewsread 8 August 2026

Афипский район Краснодарский край Продолжается работа ПВО 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:07 UTC10 viewsread 8 August 2026

Краснодарский край Опасность по БПЛА сохраняется 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 02:03 UTC10 viewsread 8 August 2026

Керченский полуостров Керчь и близлежащие Опасность по БПЛА Республика Крым 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 01:59 UTC11 viewsread 8 August 2026

Азовское Михайловка Нижнегорский и близлежащие Опасность по БПЛА Республика Крым 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 01:51 UTC14 viewsread 8 August 2026

Красная Поляна Черноморское и близлежащие Опасность по БПЛА Республика Крым 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

8 Aug 2026, 01:47 UTC15 viewsread 8 August 2026

От Инкермана в направлении Балаклавской ТЭС фиксация БПЛА Севастополь 📡 Радар ЮГ в MAX Радар в Telegram - t.me/radar_yog

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

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

“РАДАР ЮГ НЕБО Ростов Краснодар | ЛПР Тревоги БПЛА МОНИТОРИНГ” (@radar_yog), 984 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/radar_yog.

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.