Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Саратов

Channel

Радар Саратов

@rada_saratov

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

255,143subscribers

-131 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002327302568
TypeChannel
Username@rada_saratov
DescriptionОбратная связь с нами - @Radarr_russiabot 🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию
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 live19 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/rada_saratov

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 95% 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

254,764255,513255,138.57 August 2026 — 255,274 subscribers8 August 2026 — 255,288 subscribers9 August 2026 — 255,287 subscribers10 August 2026 — 255,217 subscribers11 August 2026 — 255,167 subscribers12 August 2026 — 255,056 subscribers13 August 2026 — 254,944 subscribers14 August 2026 — 254,984 subscribers16 August 2026 — 255,222 subscribers17 August 2026 — 255,074 subscribers18 August 2026 — 255,033 subscribers19 August 2026 — 254,940 subscribers20 August 2026 — 254,869 subscribers22 August 2026 — 255,288 subscribers23 August 2026 — 255,221 subscribers25 August 2026 — 255,097 subscribers26 August 2026 — 254,979 subscribers27 August 2026 — 254,968 subscribers28 August 2026 — 255,276 subscribers29 August 2026 — 255,308 subscribers30 August 2026 — 255,253 subscribers31 August 2026 — 255,172 subscribers1 September 2026 — 255,070 subscribers2 September 2026 — 254,971 subscribers3 September 2026 — 254,906 subscribers5 September 2026 — 254,764 subscribers8 September 2026 — 255,083 subscribers11 September 2026 — 255,412 subscribers13 September 2026 — 255,513 subscribers14 September 2026 — 255,375 subscribers16 September 2026 — 255,353 subscribers19 September 2026 — 255,143 subscribers255,1437 August 202619 September 2026
32 measurements spanning 42 days, net -131. 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 254,652–255,625 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
19 Sept 2026, 00:39255,143-210
16 Sept 2026, 14:19255,353-22
14 Sept 2026, 17:58255,375-138
13 Sept 2026, 04:00255,513+101
11 Sept 2026, 03:56255,412+329
8 Sept 2026, 07:36255,083+319
5 Sept 2026, 04:41254,764-142
3 Sept 2026, 13:19254,906-65
2 Sept 2026, 10:26254,971-99
1 Sept 2026, 08:45255,070-102
31 Aug 2026, 05:44255,172-81
30 Aug 2026, 05:35255,253-55
29 Aug 2026, 02:44255,308+32
28 Aug 2026, 02:27255,276+308
27 Aug 2026, 00:27254,968-11
26 Aug 2026, 02:08254,979-118
25 Aug 2026, 01:25255,097-124
23 Aug 2026, 13:07255,221-67
22 Aug 2026, 02:27255,288+419
20 Aug 2026, 21:46254,869first reading

Engagement

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

ERR · 30 days
15.4%
avg views ÷ 255,143 subscribers
Avg views / post
39,300
239 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
239
of 382 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 23 September 2026
Posts held382 (6 August 202623 September 2026)
Views total9,401,660
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 08:29 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

Photos
47
Videos
34
Links
976

Lifetime counters from Telegram’s own channel header, read 23 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3m 12s
Average length
14s

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

23 Sept 2026, 05:55 UTC≈10,500 viewsread 23 September 2026

За прошедшую ночь силами противовоздушной обороны было уничтожено 514 БПЛА над территориями Белгородской, Курской, Брянской, Воронежской, Орловской, Калужской, Липецкой, Тамбовской, Рязанской, Нижегородской, Смоленской, Саратовской, Самарской, Ульяновской, Ростовской областей, Краснодарского края, республиками Крым, Башкортостан, Татарстан, над акваториями Азовского и Черного морей. ❗️Радар Саратов - @rada_saratov 🌐

23 Sept 2026, 02:49 UTC≈18,600 viewsread 23 September 2026

Саратовская область Отбой опасности по БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

23 Sept 2026, 02:13 UTC≈20,100 viewsread 23 September 2026

Краснокутский район Саратовская область Фиксация БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

23 Sept 2026, 00:59 UTC≈20,700 viewsread 23 September 2026

Ровенский район Саратовская область Фиксация от 4 БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

23 Sept 2026, 00:06 UTC≈20,900 viewsread 23 September 2026

Красноармейский район Саратовская область Фиксация БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 22:55 UTC≈21,200 viewsread 23 September 2026

Калининский район Саратовская область Фиксация от 2 БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 22:11 UTC≈21,500 viewsread 23 September 2026

Саратовский район Екатериновский район Саратовская область Фиксации БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:42 UTC≈22,400 viewsread 23 September 2026

Аткарский район Самойловский район Саратовская область Фиксации БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:04 UTC≈23,800 viewsread 23 September 2026

Ртищевский район Саратовская область Фиксация БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 20:51 UTC≈24,700 viewsread 23 September 2026

Аркадакский район Саратовская область Фиксация БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 20:35 UTC≈25,700 viewsread 23 September 2026

Аркадакский район Саратовская область Фиксация группы БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 20:26 UTC≈26,100 viewsread 23 September 2026

Балашовский район Саратовская область Фиксация от 3 БПЛА ❗️Радар Саратов - @rada_saratov 🌐 Обход белых списков - @Internet_Boost_bot

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

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

“Радар Саратов” (@rada_saratov), 255,143 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/rada_saratov.

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.