Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Кубани

Channel

Радар Кубани

@radarkubani

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

5,203subscribers

-71 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-1002242118025
TypeChannel
Username@radarkubani
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 live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/radarkubani

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

5,2035,2825,242.57 August 2026 — 5,274 subscribers7 August 2026 — 5,274 subscribers8 August 2026 — 5,278 subscribers11 August 2026 — 5,273 subscribers15 August 2026 — 5,282 subscribers18 August 2026 — 5,280 subscribers21 August 2026 — 5,275 subscribers24 August 2026 — 5,271 subscribers27 August 2026 — 5,258 subscribers30 August 2026 — 5,252 subscribers3 September 2026 — 5,237 subscribers7 September 2026 — 5,229 subscribers12 September 2026 — 5,215 subscribers16 September 2026 — 5,203 subscribers7 August 202616 September 2026
14 measurements spanning 39 days, net -71. 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 5,191–5,294 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 03:015,203-12
12 Sept 2026, 06:175,215-14
7 Sept 2026, 18:575,229-8
3 Sept 2026, 00:065,237-15
30 Aug 2026, 12:155,252-6
27 Aug 2026, 07:155,258-13
24 Aug 2026, 11:175,271-4
21 Aug 2026, 00:545,275-5
18 Aug 2026, 10:485,280-2
15 Aug 2026, 06:575,282+9
11 Aug 2026, 12:055,273-5
8 Aug 2026, 11:555,278+4
7 Aug 2026, 17:315,274no change
7 Aug 2026, 17:295,274first reading

Engagement

77 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 7 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 77 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Aug 2026, 02:45 UTC124 viewsread 12 August 2026

Геленджик Краснодарский край Сбитие БПЛА ❗️Радар Кубани - @radarkubani

12 Aug 2026, 02:30 UTC139 viewsread 12 August 2026

Новороссийск и близлежащие Краснодарский край Отбой опасности по БЭК ❗️Радар Кубани - @radarkubani

12 Aug 2026, 02:20 UTC148 viewsread 12 August 2026

Новороссийск, Геленджик Краснодарский край Продолжается работа ПВО по БПЛА Меры безопасности ❗️Радар Кубани - @radarkubani

12 Aug 2026, 02:00 UTC161 viewsread 12 August 2026

Новороссийск Геленджик Краснодарский край Работа ПВО по БПЛА Меры безопасности ❗️Радар Кубани - @radarkubani

12 Aug 2026, 01:45 UTC172 viewsread 12 August 2026

Новороссийск, Геленджик Краснодарский край Работа ПВО по БПЛА Меры безопасности Ракетная опасность ❗️Радар Кубани - @radarkubani

12 Aug 2026, 01:35 UTC135 viewsread 12 August 2026

Краснодарский край Ракетная опасность ❗️Радар Кубани - @radarkubani

12 Aug 2026, 01:00 UTC160 viewsread 12 August 2026

Новороссийск Краснодарский край Продолжается работа ПВО по БПЛА Меры безопасности Уйти с улиц ❗️Радар Кубани - @radarkubani

12 Aug 2026, 00:45 UTC174 viewsread 12 August 2026

Анапа, Новороссийск, Геленджик Краснодарский край Продолжается работа ПВО по БПЛА Меры безопасности ❗️Радар Кубани - @radarkubani

12 Aug 2026, 00:45 UTC171 viewsread 12 August 2026

Краснодарский край Отбой ракетной опасности ❗️Радар Кубани - @radarkubani

12 Aug 2026, 00:45 UTC172 viewsread 12 August 2026

Анапа Краснодарский край Работа ПВО по БПЛА Еще фиксации в вашем направлении Меры безопасности ❗️Радар Кубани - @radarkubani

12 Aug 2026, 00:40 UTC173 viewsread 12 August 2026

Геленджик Краснодарский край Работа ПВО по БПЛА Меры безопасности ❗️Радар Кубани - @radarkubani

12 Aug 2026, 00:15 UTC198 viewsread 12 August 2026

Новороссийск Геленджик Анапа Краснодарский край Работа ПВО по БПЛА Еще фиксации в вашем направлении ❗️Радар Кубани - @radarkubani

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

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

“Радар Кубани” (@radarkubani), 5,203 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/radarkubani.

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.