Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Энгельс

Channel

Радар Энгельс

@radar_engels

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

26,888subscribers

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

Topic

Local community — 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 83% 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

26,85226,95326,902.57 August 2026 — 26,953 subscribers7 August 2026 — 26,953 subscribers8 August 2026 — 26,952 subscribers9 August 2026 — 26,942 subscribers10 August 2026 — 26,931 subscribers11 August 2026 — 26,917 subscribers12 August 2026 — 26,911 subscribers13 August 2026 — 26,906 subscribers15 August 2026 — 26,909 subscribers16 August 2026 — 26,900 subscribers17 August 2026 — 26,885 subscribers18 August 2026 — 26,882 subscribers19 August 2026 — 26,867 subscribers21 August 2026 — 26,852 subscribers22 August 2026 — 26,884 subscribers24 August 2026 — 26,879 subscribers25 August 2026 — 26,878 subscribers26 August 2026 — 26,866 subscribers27 August 2026 — 26,872 subscribers28 August 2026 — 26,901 subscribers29 August 2026 — 26,924 subscribers30 August 2026 — 26,927 subscribers31 August 2026 — 26,924 subscribers1 September 2026 — 26,914 subscribers2 September 2026 — 26,900 subscribers3 September 2026 — 26,898 subscribers4 September 2026 — 26,883 subscribers7 September 2026 — 26,868 subscribers10 September 2026 — 26,928 subscribers12 September 2026 — 26,945 subscribers14 September 2026 — 26,931 subscribers15 September 2026 — 26,920 subscribers18 September 2026 — 26,888 subscribers26,8887 August 202618 September 2026
33 measurements spanning 41 days, net -65. 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 26,837–26,968 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, 03:1526,888-32
15 Sept 2026, 23:3926,920-11
14 Sept 2026, 06:1826,931-14
12 Sept 2026, 18:0126,945+17
10 Sept 2026, 17:5826,928+60
7 Sept 2026, 15:1726,868-15
4 Sept 2026, 20:0126,883-15
3 Sept 2026, 06:3426,898-2
2 Sept 2026, 02:1726,900-14
1 Sept 2026, 05:2526,914-10
31 Aug 2026, 05:1626,924-3
30 Aug 2026, 08:4526,927+3
29 Aug 2026, 07:1626,924+23
28 Aug 2026, 04:2526,901+29
27 Aug 2026, 06:0726,872+6
26 Aug 2026, 07:1126,866-12
25 Aug 2026, 04:5426,878-1
24 Aug 2026, 01:5626,879-5
22 Aug 2026, 08:1726,884+32
21 Aug 2026, 00:1326,852first reading

Engagement

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

ERR · 30 days
14.5%
avg views ÷ 26,888 subscribers
Avg views / post
3,890
70 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
70
of 136 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 held136 (5 August 20263 September 2026)
Views total272,338
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11:07 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
11s
Average length
11s

Measured directly from 1 video 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:36 UTC928 viewsread 3 September 2026

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

3 Sept 2026, 00:51 UTC≈1,790 viewsread 3 September 2026

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

2 Sept 2026, 02:19 UTC≈2,990 viewsread 3 September 2026

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

2 Sept 2026, 00:56 UTC≈3,010 viewsread 3 September 2026

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

1 Sept 2026, 08:11 UTC≈3,410 viewsread 3 September 2026

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

1 Sept 2026, 05:14 UTC≈3,100 viewsread 3 September 2026

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

31 Aug 2026, 19:19 UTC≈3,300 viewsread 3 September 2026

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

31 Aug 2026, 07:59 UTC≈3,350 viewsread 3 September 2026

Фиксаций над нашим воздушным пространством не наблюдаем В случае возникновения угрозы незамедлительно сообщим! ❗️Радар Энгельс - @radar_engels 🌐 Обход белых списков - @Internet_Boost_bot

31 Aug 2026, 06:07 UTC≈3,160 viewsread 3 September 2026

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

31 Aug 2026, 02:59 UTC≈3,200 viewsread 3 September 2026

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

30 Aug 2026, 20:44 UTC≈3,420 viewsread 3 September 2026

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

30 Aug 2026, 10:12 UTC≈3,940 viewsread 3 September 2026

Саратовская область - ракетная опасность от Ростовской области. ❗️Радар Энгельс - @radar_engels 🌐 Обход белых списков - @Internet_Boost_bot

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

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 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.

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_engels), 26,888 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/radar_engels.

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.