Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Тамбов

Channel

Радар Тамбов

@radar_tambov

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

19,213subscribers

+548 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-1002496301341
TypeChannel
Username@radar_tambov
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 live18 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/radar_tambov

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 81% 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

18,66219,21318,937.57 August 2026 — 18,665 subscribers7 August 2026 — 18,662 subscribers8 August 2026 — 18,723 subscribers9 August 2026 — 18,766 subscribers10 August 2026 — 18,776 subscribers11 August 2026 — 18,773 subscribers12 August 2026 — 18,772 subscribers13 August 2026 — 18,763 subscribers14 August 2026 — 18,760 subscribers15 August 2026 — 18,769 subscribers17 August 2026 — 18,788 subscribers18 August 2026 — 18,877 subscribers19 August 2026 — 18,895 subscribers20 August 2026 — 18,939 subscribers21 August 2026 — 18,964 subscribers23 August 2026 — 18,972 subscribers25 August 2026 — 18,962 subscribers26 August 2026 — 19,025 subscribers27 August 2026 — 19,046 subscribers28 August 2026 — 19,061 subscribers28 August 2026 — 19,071 subscribers29 August 2026 — 19,082 subscribers30 August 2026 — 19,071 subscribers31 August 2026 — 19,098 subscribers1 September 2026 — 19,112 subscribers3 September 2026 — 19,145 subscribers4 September 2026 — 19,139 subscribers7 September 2026 — 19,134 subscribers10 September 2026 — 19,135 subscribers12 September 2026 — 19,156 subscribers14 September 2026 — 19,150 subscribers16 September 2026 — 19,208 subscribers18 September 2026 — 19,213 subscribers7 August 202618 September 2026
33 measurements spanning 42 days, net +548. 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 18,579–19,296 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
18 Sept 2026, 06:3719,213+5
16 Sept 2026, 04:0219,208+58
14 Sept 2026, 08:3819,150-6
12 Sept 2026, 20:3819,156+21
10 Sept 2026, 20:2019,135+1
7 Sept 2026, 16:3519,134-5
4 Sept 2026, 15:1719,139-6
3 Sept 2026, 00:2619,145+33
1 Sept 2026, 20:4819,112+14
31 Aug 2026, 19:2319,098+27
30 Aug 2026, 19:3319,071-11
29 Aug 2026, 21:5519,082+11
28 Aug 2026, 22:1719,071+10
28 Aug 2026, 00:2419,061+15
27 Aug 2026, 01:2419,046+21
26 Aug 2026, 02:3419,025+63
25 Aug 2026, 00:3918,962-10
23 Aug 2026, 09:1318,972+8
21 Aug 2026, 22:2618,964+25
20 Aug 2026, 14:3818,939first reading

Engagement

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

ERR · 30 days
26.5%
avg views ÷ 19,213 subscribers
Avg views / post
5,090
44 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
44
of 196 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 held196 (5 August 2026 – 3 September 2026)
Views total223,950
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 08:50 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
53s
Average length
11s

Measured directly from 5 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, 06:11 UTC≈1,350 viewsread 3 September 2026

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

3 Sept 2026, 04:13 UTC≈2,310 viewsread 3 September 2026

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

2 Sept 2026, 17:28 UTC≈3,700 viewsread 3 September 2026

С 08:00 до 20:00 силами противовоздушной обороны было уничтожено 238 БПЛА над территориями Брянской, Белгородской, Курской, Орловской, Тамбовской, Рязанской, Калужской, Воронежской, Липецкой, Тульской, Владимирской, Смоленской, Ростовской областей, Московского региона, Республики Крым и над акваторией Черного моря. ❗️Радар Тамбов - @radar_tambov 🌐 Обход белых списков - @Internet_Boost_bot

2 Sept 2026, 09:37 UTC≈4,500 viewsread 3 September 2026

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

2 Sept 2026, 08:33 UTC≈4,680 viewsread 3 September 2026

Котовск, Тамбовская область - меры предосторожности при БПЛА. ❗️Радар Тамбов - @radar_tambov 🌐 Обход белых списков - @Internet_Boost_bot

2 Sept 2026, 06:49 UTC≈4,580 viewsread 3 September 2026

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

2 Sept 2026, 06:11 UTC≈4,560 viewsread 3 September 2026

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

2 Sept 2026, 05:23 UTC≈4,540 viewsread 3 September 2026

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

2 Sept 2026, 02:41 UTC≈4,680 viewsread 3 September 2026

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

2 Sept 2026, 02:41 UTC≈4,460 viewsread 3 September 2026

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

2 Sept 2026, 02:17 UTC≈4,340 viewsread 3 September 2026

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

1 Sept 2026, 05:13 UTC≈4,480 viewsread 3 September 2026

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

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Радар Тамбов” (@radar_tambov), 19,213 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/radar_tambov.

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.