Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Брянск

Channel

Радар Брянск

@radar_bryanskk

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

41,094subscribers

-445 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002246809028
TypeChannel
Username@radar_bryanskk
DescriptionОбратная связь с нами - @Radarr_russiabot 🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию
CreatedBetween 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 October 2026
Measurements held52
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/radar_bryanskk

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 the other topics.

Growth

41,05541,54241,298.57 August 2026 — 41,539 subscribers7 August 2026 — 41,536 subscribers8 August 2026 — 41,542 subscribers9 August 2026 — 41,533 subscribers10 August 2026 — 41,528 subscribers11 August 2026 — 41,508 subscribers12 August 2026 — 41,490 subscribers14 August 2026 — 41,473 subscribers15 August 2026 — 41,541 subscribers18 August 2026 — 41,540 subscribers19 August 2026 — 41,529 subscribers20 August 2026 — 41,520 subscribers21 August 2026 — 41,508 subscribers22 August 2026 — 41,498 subscribers23 August 2026 — 41,488 subscribers25 August 2026 — 41,472 subscribers26 August 2026 — 41,460 subscribers27 August 2026 — 41,441 subscribers28 August 2026 — 41,434 subscribers29 August 2026 — 41,423 subscribers30 August 2026 — 41,442 subscribers31 August 2026 — 41,431 subscribers1 September 2026 — 41,423 subscribers2 September 2026 — 41,424 subscribers3 September 2026 — 41,409 subscribers4 September 2026 — 41,405 subscribers7 September 2026 — 41,393 subscribers10 September 2026 — 41,386 subscribers12 September 2026 — 41,367 subscribers14 September 2026 — 41,348 subscribers15 September 2026 — 41,318 subscribers17 September 2026 — 41,295 subscribers27 September 2026 — 41,196 subscribers4 October 2026 — 41,131 subscribers9 October 2026 — 41,098 subscribers13 October 2026 — 41,085 subscribers14 October 2026 — 41,075 subscribers15 October 2026 — 41,066 subscribers16 October 2026 — 41,055 subscribers17 October 2026 — 41,096 subscribers18 October 2026 — 41,114 subscribers19 October 2026 — 41,087 subscribers20 October 2026 — 41,088 subscribers21 October 2026 — 41,139 subscribers22 October 2026 — 41,128 subscribers23 October 2026 — 41,125 subscribers24 October 2026 — 41,117 subscribers25 October 2026 — 41,110 subscribers26 October 2026 — 41,079 subscribers27 October 2026 — 41,097 subscribers28 October 2026 — 41,098 subscribers30 October 2026 — 41,094 subscribers41,0947 August 202630 October 2026
52 measurements spanning 83 days, net -445. 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 40,982–41,615 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 52
Measured (UTC)SubscribersChange
30 Oct 2026, 00:0741,094-4
28 Oct 2026, 20:5041,098+1
27 Oct 2026, 16:2941,097+18
26 Oct 2026, 18:3941,079-31
25 Oct 2026, 15:5641,110-7
24 Oct 2026, 15:1841,117-8
23 Oct 2026, 14:0141,125-3
22 Oct 2026, 16:1941,128-11
21 Oct 2026, 12:0141,139+51
20 Oct 2026, 08:2041,088+1
19 Oct 2026, 08:5041,087-27
18 Oct 2026, 11:0441,114+18
17 Oct 2026, 14:3041,096+41
16 Oct 2026, 17:4541,055-11
15 Oct 2026, 20:5441,066-9
14 Oct 2026, 18:1041,075-10
13 Oct 2026, 09:1741,085-13
9 Oct 2026, 09:2141,098-33
4 Oct 2026, 23:3741,131-65
27 Sept 2026, 18:1941,196first reading

Engagement

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

ERR · 30 days
12.0%
avg views ÷ 41,094 subscribers
Avg views / post
4,940
166 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
166
of 451 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 30 October 2026
Posts held451 (4 August 2026 – 30 October 2026)
Views total820,520
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Oct 2026, 16: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

Photos
≈47
Videos
≈25
Links
≈1,250

Lifetime counters from Telegram’s own channel header, read 30 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 35s
Average length
22s

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

30 Oct 2026, 15:36 UTC≈1,050 viewsread 30 October 2026

Фиксаций над нашим воздушным пространством не наблюдаем В случае возникновения угрозы незамедлительно сообщим! ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

30 Oct 2026, 14:38 UTC≈1,530 viewsread 30 October 2026
Photo

🤫 Секретный способ обхода БЕЛЫХ СПИСКОВ Разработчики запустили антиглушилку с новым протоколом, которая обходит любые фильтры и не реагирует на блокировки – Ускоритель Интернета • 4к-видео и стримы грузят без задержек • Связь не обрывается даже во время пиковых нагрузок • Телеграм, Тикток и Ютуб летают как раньше 🎁 Начни с бесплатного теста на 3 дня, чтобы оценить разницу. Сейчас идет регистрация на 100 человек, …

30 Oct 2026, 08:32 UTC≈3,140 viewsread 30 October 2026

За прошедшую ночь и утро силами противовоздушной обороны было уничтожено 1043 БПЛА над территориями Белгородской, Брянской, Воронежской, Волгоградской, Курской, Калужской, Костромской, Орловской, Пензенской, Ростовской, Рязанской, Смоленской, Самарской, Саратовской, Тверской, Тульской, Ярославской областей, Московского региона и Республики Татарстан. ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.r…

30 Oct 2026, 07:59 UTC≈4,140 viewsread 30 October 2026

ВСУ сбросили взрывные устройства с дронов на три школы и 17 детских садов в Брянске. ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

30 Oct 2026, 03:53 UTC≈5,060 viewsread 30 October 2026

Брянская область Ракетная опасность ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 20:16 UTC≈5,580 viewsread 30 October 2026

Брянская область Отбой ракетной опасности ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 19:59 UTC≈5,740 viewsread 30 October 2026

Брянская область Ракетная опасность ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 17:52 UTC≈5,840 viewsread 30 October 2026

С 08:00 до 20:00 силами противовоздушной обороны было уничтожено 40 БПЛА над территориями Белгородской, Брянской, Курской, Орловской областей и Пермского края ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 17:11 UTC≈5,570 viewsread 30 October 2026

Брянская область Отбой ракетной опасности ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 16:29 UTC≈5,400 viewsread 30 October 2026

Брянская область Ракетная опасность ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 13:30 UTC≈5,280 viewsread 30 October 2026

Брянская область Отбой ракетной опасности ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

29 Oct 2026, 12:53 UTC≈5,150 viewsread 30 October 2026

Брянская область Ракетная опасность ❗️Радар Брянск - @radar_bryanskk 📲 Наш канал в МАХ - https://max.ru/join/radarrussiia

Showing the 12 most recent of 451 posts we hold for @radar_bryanskk. 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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“Радар Брянск” (@radar_bryanskk), 41,094 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/radar_bryanskk.

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.