Telegram RegisterThe public register of Telegram
Telegram profile photo for РАДАР БПЛА

Channel

РАДАР БПЛА

@radar_tmb

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

9,498subscribers

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

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

9,4989,6189,5587 August 2026 — 9,618 subscribers8 August 2026 — 9,616 subscribers11 August 2026 — 9,600 subscribers15 August 2026 — 9,574 subscribers18 August 2026 — 9,577 subscribers22 August 2026 — 9,574 subscribers25 August 2026 — 9,569 subscribers28 August 2026 — 9,575 subscribers31 August 2026 — 9,559 subscribers3 September 2026 — 9,542 subscribers8 September 2026 — 9,522 subscribers12 September 2026 — 9,515 subscribers17 September 2026 — 9,498 subscribers7 August 202617 September 2026
13 measurements spanning 41 days, net -120. 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,480–9,636 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 07:569,498-17
12 Sept 2026, 23:599,515-7
8 Sept 2026, 15:389,522-20
3 Sept 2026, 04:399,542-17
31 Aug 2026, 05:579,559-16
28 Aug 2026, 01:539,575+6
25 Aug 2026, 05:539,569-5
22 Aug 2026, 06:389,574-3
18 Aug 2026, 15:129,577+3
15 Aug 2026, 10:269,574-26
11 Aug 2026, 19:139,600-16
8 Aug 2026, 11:129,616-2
7 Aug 2026, 17:019,618first reading

Engagement

475 posts held, back to 7 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 34 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.76%
avg views ÷ 9,498 subscribers
Avg views / post
357
91 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
91
of 475 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 29 August 2026
Posts held475 (7 August 2026 – 29 August 2026)
Views total32,459
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 05:54 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

Video runtime
1m 33s
Average length
23s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

29 Aug 2026, 05:40 UTC40 viewsread 29 August 2026

⚡️⚡️За ночь средствами ПВО было уничтожено 313 БПЛА над Белгородской, Брянской, Воронежской, Калужской, Курской, Липецкой, Ростовской, Тульской областей, Московского региона, Краснодарского края, Республики Крым, Республики Татарстан и над акваториями Азовского и Черного морей. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 04:50 UTC84 viewsread 29 August 2026

Отбой опасности БПЛА по всем ранее объявленным регионам. Опасность сохраняется в Брянской, Тульской, Московской областей. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 03:00 UTC153 viewsread 29 August 2026

Отбой ракетной опасности по всем ранее объявленным регионам. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 02:05 UTC173 viewsread 29 August 2026

Свердловская область - ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 02:00 UTC172 viewsread 29 August 2026

Оренбургская область - ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 02:00 UTC171 viewsread 29 August 2026

Республика Удмуртия Пермский край Кировская область Ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 01:50 UTC169 viewsread 29 August 2026

Республика Татарстан - опасность БПЛА. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 01:20 UTC192 viewsread 29 August 2026

Самарская область Республика Башкортостан Ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 01:20 UTC187 viewsread 29 August 2026

Ульяновская область Республика Чувашия Республика Татарстан Республика Марий Эл Ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 01:20 UTC179 viewsread 29 August 2026

Липецкая область Тамбовская область Нижегородская область Ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 01:20 UTC176 viewsread 29 August 2026

Волгоградская область Саратовская область Пензенская область Республика Мордовия Ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

29 Aug 2026, 01:20 UTC164 viewsread 29 August 2026

Воронежская область - ракетная опасность. РАДАР БПЛА | ПОДПИСАТЬСЯ

Showing the 12 most recent of 475 posts we hold for @radar_tmb. 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_tmb), 9,498 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_tmb.

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.