Telegram RegisterThe public register of Telegram
Telegram profile photo for Брянская область оповещения и тревоги

Channel

Брянская область оповещения и тревоги

@lpr1_Bryansk_alarm

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

44,186subscribers

+671 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002246127755
TypeChannel
Username@lpr1_Bryansk_alarm
DescriptionMAX: https://max.ru/join/TVZX4MwEIC4hnIQHg7lksJorO3TqrHHmw1M8YIWE5Pc Чат-бот: @treugolniklnr_bot Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 Реклама: @Lpr1reklama РКН: https://clck.ru/3MFjDr
CreatedBetween 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/lpr1_Bryansk_alarm

Topic

Other / unclassifiable — 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 76% 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

43,51544,20043,857.56 August 2026 — 43,515 subscribers6 August 2026 — 43,515 subscribers6 August 2026 — 43,537 subscribers7 August 2026 — 43,559 subscribers8 August 2026 — 43,574 subscribers9 August 2026 — 43,579 subscribers10 August 2026 — 43,644 subscribers11 August 2026 — 43,665 subscribers12 August 2026 — 43,678 subscribers13 August 2026 — 43,686 subscribers14 August 2026 — 43,792 subscribers16 August 2026 — 43,817 subscribers17 August 2026 — 43,849 subscribers18 August 2026 — 43,871 subscribers19 August 2026 — 43,867 subscribers20 August 2026 — 43,878 subscribers22 August 2026 — 43,883 subscribers23 August 2026 — 43,893 subscribers25 August 2026 — 43,918 subscribers25 August 2026 — 43,923 subscribers26 August 2026 — 43,924 subscribers27 August 2026 — 43,939 subscribers29 August 2026 — 43,956 subscribers30 August 2026 — 44,015 subscribers31 August 2026 — 44,024 subscribers1 September 2026 — 44,040 subscribers2 September 2026 — 44,032 subscribers4 September 2026 — 44,045 subscribers6 September 2026 — 44,051 subscribers9 September 2026 — 44,107 subscribers12 September 2026 — 44,200 subscribers13 September 2026 — 44,193 subscribers15 September 2026 — 44,177 subscribers17 September 2026 — 44,186 subscribers44,1866 August 202617 September 2026
34 measurements spanning 43 days, net +671. 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 43,412–44,303 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
17 Sept 2026, 13:5644,186+9
15 Sept 2026, 09:5644,177-16
13 Sept 2026, 21:3644,193-7
12 Sept 2026, 03:1744,200+93
9 Sept 2026, 20:3544,107+56
6 Sept 2026, 10:5644,051+6
4 Sept 2026, 02:2244,045+13
2 Sept 2026, 19:3644,032-8
1 Sept 2026, 19:5344,040+16
31 Aug 2026, 18:2544,024+9
30 Aug 2026, 20:1944,015+59
29 Aug 2026, 20:1743,956+17
27 Aug 2026, 19:5743,939+15
26 Aug 2026, 20:2543,924+1
25 Aug 2026, 23:2543,923+5
25 Aug 2026, 02:4643,918+25
23 Aug 2026, 16:1343,893+10
22 Aug 2026, 01:4643,883+5
20 Aug 2026, 20:2243,878+11
19 Aug 2026, 16:5443,867first reading

Engagement

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

ERR · 30 days
6.99%
avg views ÷ 44,186 subscribers
Avg views / post
3,090
915 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
915
of 1,656 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 24 September 2026
Posts held1,656 (5 August 2026 – 24 September 2026)
Views total2,826,981
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 22:13 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
806
Videos
681
Links
400

Lifetime counters from Telegram’s own channel header, read 24 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
6m 09s
Average length
26s

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

24 Sept 2026, 20:50 UTC≈1,410 viewsread 24 September 2026

Брянск и близлежащие Тревога по БПЛА сохраняется Соблюдайте меры безопасности Брянская область

24 Sept 2026, 20:47 UTC≈1,390 viewsread 24 September 2026
Forwarded from @lpr1_treugolnik

Бежица и близлежащие тревога по БПЛА Брянская область

24 Sept 2026, 20:36 UTC≈1,810 viewsread 24 September 2026

Дятьковский район Брянская область Тревога по БПЛА сохраняется И далее в тыловые регионы

24 Sept 2026, 20:30 UTC≈2,040 viewsread 24 September 2026

Жуковский МО Тревога по БПЛА Брянская область

24 Sept 2026, 20:30 UTC≈1,770 viewsread 24 September 2026
Forwarded from @lpr1_treugolnik

Брянская область, продолжаются массовые фиксации БПЛА от Гг, тревога по БПЛА сохраняется

24 Sept 2026, 20:23 UTC≈2,110 viewsread 24 September 2026

Дятьковский район Брянская область Тревога по БПЛА сохраняется

24 Sept 2026, 20:11 UTC≈2,380 viewsread 24 September 2026

Сельцо Брянск Бежица И близлежащие Тревога по БПЛА сохраняется Соблюдайте меры безопасности Брянская область

24 Sept 2026, 20:10 UTC≈2,120 viewsread 24 September 2026
Forwarded from @lpr1_treugolnik

Брянская, Курская, Белгородская область, тревога по БПЛА сохраняется, продолжаются фиксации БПЛА от Гг.

24 Sept 2026, 20:01 UTC≈2,440 viewsread 24 September 2026

Брянск и близлежащие Тревога по БПЛА Брянская область

24 Sept 2026, 19:54 UTC≈2,550 viewsread 24 September 2026

Погарский район Почепский район И далее в тыл Тревога по БПЛА Брянская область

24 Sept 2026, 19:40 UTC≈2,760 viewsread 24 September 2026

Суземка и близлежащие Тревога по БПЛА от ГГ Брянская область

24 Sept 2026, 19:28 UTC≈2,740 viewsread 24 September 2026
Forwarded from @lpr1_treugolnik

Погарский район опасность по реактивным бпла Брянская область

Showing the 12 most recent of 1,656 posts we hold for @lpr1_Bryansk_alarm. 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 12 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.

Names

Channels on the register whose handles appear in this channel's posts.

Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,501
5 posts
Республика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 196,890
5 posts
Харьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,039
5 posts
Херсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,522
5 posts
Краснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,561
5 posts
Курская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,249
5 posts
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,974
5 posts
Орловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,442
5 posts
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 51,929
5 posts
Воронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,374
5 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 155,320
5 posts
Lpr 1
@lpr1_treugolnik · 933,015
4 posts
Белгородская область оповещения, тревоги
@Belgorod_Lpr1 · 255
3 posts
Брянская область оповещения,тревоги
@Brynsk_Lpr1 · 232
3 posts
Республика Крым оповещения, тревоги
@Crime_Lpr1 · 636
3 posts
Херсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 91
3 posts
Краснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 449
3 posts
Курская область оповещения и тревоги.
@Kursk_Lpr1 · 57
3 posts
Луганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 215
3 posts
Орловская область оповещения, тревоги.
@Orlov_Lpr1 · 35
3 posts
Ростовская область тревоги, оповещения.
@Rostov_Lpr1 · 249
3 posts
LPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 170
3 posts
Воронежская область, оповещения,тревоги.
@Voronezh_lpr1 · 64
3 posts

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

“Брянская область оповещения и тревоги” (@lpr1_Bryansk_alarm), 44,186 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/lpr1_Bryansk_alarm.

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.