Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Самара

Channel

Радар Самара

@radar_samaraaa

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

20,546subscribers

-310 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002740131855
TypeChannel
Username@radar_samaraaa
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/radar_samaraaa

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

20,54620,86220,7047 August 2026 — 20,856 subscribers8 August 2026 — 20,862 subscribers9 August 2026 — 20,855 subscribers10 August 2026 — 20,846 subscribers11 August 2026 — 20,830 subscribers12 August 2026 — 20,831 subscribers13 August 2026 — 20,821 subscribers14 August 2026 — 20,799 subscribers16 August 2026 — 20,783 subscribers17 August 2026 — 20,765 subscribers18 August 2026 — 20,738 subscribers19 August 2026 — 20,726 subscribers20 August 2026 — 20,732 subscribers21 August 2026 — 20,733 subscribers22 August 2026 — 20,734 subscribers24 August 2026 — 20,729 subscribers25 August 2026 — 20,723 subscribers26 August 2026 — 20,709 subscribers27 August 2026 — 20,691 subscribers28 August 2026 — 20,681 subscribers29 August 2026 — 20,673 subscribers30 August 2026 — 20,667 subscribers31 August 2026 — 20,654 subscribers1 September 2026 — 20,663 subscribers2 September 2026 — 20,660 subscribers3 September 2026 — 20,652 subscribers5 September 2026 — 20,640 subscribers9 September 2026 — 20,624 subscribers11 September 2026 — 20,598 subscribers13 September 2026 — 20,585 subscribers14 September 2026 — 20,589 subscribers16 September 2026 — 20,577 subscribers19 September 2026 — 20,546 subscribers7 August 202619 September 2026
33 measurements spanning 43 days, net -310. 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 20,499–20,909 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 10:4120,546-31
16 Sept 2026, 21:0020,577-12
14 Sept 2026, 22:2020,589+4
13 Sept 2026, 08:5920,585-13
11 Sept 2026, 14:0120,598-26
9 Sept 2026, 00:5720,624-16
5 Sept 2026, 20:3920,640-12
3 Sept 2026, 15:3720,652-8
2 Sept 2026, 06:2520,660-3
1 Sept 2026, 06:3920,663+9
31 Aug 2026, 08:4420,654-13
30 Aug 2026, 05:2520,667-6
29 Aug 2026, 06:4620,673-8
28 Aug 2026, 09:3620,681-10
27 Aug 2026, 06:5420,691-18
26 Aug 2026, 05:4220,709-14
25 Aug 2026, 07:5220,723-6
24 Aug 2026, 08:2220,729-5
22 Aug 2026, 16:3320,734+1
21 Aug 2026, 06:3320,733first reading

Engagement

369 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.0%
avg views ÷ 20,546 subscribers
Avg views / post
2,680
87 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
87
of 369 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 3 September 2026
Posts held369 (6 August 20263 September 2026)
Views total233,258
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 18:24 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
5m 02s
Average length
19s

Measured directly from 16 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

3 Sept 2026, 17:20 UTC758 viewsread 3 September 2026

Пока по обстановке тихо, в случае появления угрозы незамедлительно сообщим Радар Самара | Подписаться

1 Sept 2026, 08:15 UTC≈3,160 viewsread 3 September 2026

За прошедшую ночь силами противовоздушной обороны было уничтожено 516 БПЛА над территориями Белгородской, Брянской, Волгоградской, Воронежской, Калужской, Курской, Ленинградской, Новгородской, Орловской, Псковской, Ростовской, Самарской, Саратовской, Смоленской, Тверской, Тульской и Ульяновской областей, Московского региона, Республики Крым и над акваторией Черного моря. Радар Самара | Подписаться

1 Sept 2026, 04:30 UTC≈3,680 viewsread 3 September 2026

Самарская область Отбой опасности по БПЛА Радар Самара | Подписаться

1 Sept 2026, 02:55 UTC≈4,270 viewsread 3 September 2026

Новокуйбышевск Самарская область Продолжается работа ПВО по БПЛА Меры безопасности Радар Самара | Подписаться

1 Sept 2026, 01:45 UTC≈4,400 viewsread 3 September 2026

Безенчукский район Самарская область Ещё фиксация БПЛА Радар Самара | Подписаться

1 Sept 2026, 01:40 UTC≈4,260 viewsread 3 September 2026

Чапаевск Самарская область Ещё фиксация БПЛА Готовность к сбитию Меры безопасности Радар Самара | Подписаться

1 Sept 2026, 01:30 UTC≈4,140 viewsread 3 September 2026

Чапаевск Самарская область Сбитие БПЛА Радар Самара | Подписаться

1 Sept 2026, 01:25 UTC≈4,020 viewsread 3 September 2026

Чапаевск Новокуйбышевск Самарская область Работа ПВО по БПЛА Радар Самара | Подписаться

1 Sept 2026, 01:20 UTC≈3,880 viewsread 3 September 2026

Кошкинский район Самарская область Фиксация БПЛА Радар Самара | Подписаться

1 Sept 2026, 01:20 UTC≈3,800 viewsread 3 September 2026

Безенчукский район Самарская область Продолжаются фиксации БПЛА Радар Самара | Подписаться

1 Sept 2026, 01:10 UTC≈3,700 viewsread 3 September 2026

Безенчукский район Самарская область Ещё фиксация 2 БПЛА Радар Самара | Подписаться

1 Sept 2026, 01:00 UTC≈3,600 viewsread 3 September 2026

Безенчукский район Самарская область Фиксация БПЛА Радар Самара | Подписаться

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 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.

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

“Радар Самара” (@radar_samaraaa), 20,546 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/radar_samaraaa.

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.