Климово опасность по БПЛА Дартс и ФПВ Брянская область

Channel
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
44,384subscribers
+869 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 |
|---|---|
| Type | Channel |
| Username | @lpr1_Bryansk_alarm |
| Description | MAX: https://max.ru/join/TVZX4MwEIC4hnIQHg7lksJorO3TqrHHmw1M8YIWE5Pc Чат-бот: @treugolniklnr_bot Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 Реклама: @Lpr1reklama РКН: https://clck.ru/3MFjDr |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 11:17 | 44,384 | +198 |
| 17 Sept 2026, 13:56 | 44,186 | +9 |
| 15 Sept 2026, 09:56 | 44,177 | -16 |
| 13 Sept 2026, 21:36 | 44,193 | -7 |
| 12 Sept 2026, 03:17 | 44,200 | +93 |
| 9 Sept 2026, 20:35 | 44,107 | +56 |
| 6 Sept 2026, 10:56 | 44,051 | +6 |
| 4 Sept 2026, 02:22 | 44,045 | +13 |
| 2 Sept 2026, 19:36 | 44,032 | -8 |
| 1 Sept 2026, 19:53 | 44,040 | +16 |
| 31 Aug 2026, 18:25 | 44,024 | +9 |
| 30 Aug 2026, 20:19 | 44,015 | +59 |
| 29 Aug 2026, 20:17 | 43,956 | +17 |
| 27 Aug 2026, 19:57 | 43,939 | +15 |
| 26 Aug 2026, 20:25 | 43,924 | +1 |
| 25 Aug 2026, 23:25 | 43,923 | +5 |
| 25 Aug 2026, 02:46 | 43,918 | +25 |
| 23 Aug 2026, 16:13 | 43,893 | +10 |
| 22 Aug 2026, 01:46 | 43,883 | +5 |
| 20 Aug 2026, 20:22 | 43,878 | first reading |
Engagement
1,727 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 112 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.90%
- avg views ÷ 44,384 subscribers
- Avg views / post
- 3,060
- 914 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 914
- of 1,727 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.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 1,727 (5 August 2026 – 27 September 2026) |
| Views total | 2,797,230 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 11:55 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
- 807
- Videos
- 682
- Links
- 400
Lifetime counters from Telegram’s own channel header, read 27 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 10s
- Average length
- 25s
Measured directly from 15 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
Брянская область Опасность по БПЛА в том числе реактивные БПЛА
Брянская область Калужская область, Орловская область от Брянской области опасность по реактивным БПЛА
Чубковичи опасность по ФПВ
От ГГ группа ФПВ на Белую Березку в центр
Климово опасность по ФПВ
Наши дорогие близкие! Спасибо огромное за поддержку нашей деятельности. Без Вашей помощи нам было бы невозможно выполнять задачу ❤️❤️❤️ https://pay.cloudtips.ru/p/f2a9c1d8
Климово Стародубский район Погарский район и близлежащие опасность БПЛА Брянская область
Отбой авиационной ракетной опасности по всем ранее обьявленым
Климово Брянская область тревога по БПЛА Дартс
Климово и близлежащие тревога по ФПВ
Стародубский район и далее в тыл Опасность по БПЛА Брянская область
Showing the 12 most recent of 1,727 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
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 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.
Named by
Channels on the register whose posts name this channel's handle.
@lpr1_Kursk_alarm · 25,2295 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,1835 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,5424 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3984 postsБелгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,4533 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 196,8903 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,5222 postsЛуганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,9742 postsLpr 1
@lpr1_treugolnik · 932,2271 postМониторинг Мигалки
@migalka_monitoring · 4541 postРадар.ру | Ростовская область ( обстрелы, БПЛА, ракеты, сводки )
@radar_ru_rostov · 4,8471 postГРАЖДАНСКАЯ БЕЗОПАСНОСТЬ 🇷🇺
@svoi_dobro · 6001 post
Names
Channels on the register whose handles appear in this channel's posts.
@lpr1_Belgorod_alarm · 57,4535 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 196,8905 postsХарьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,0395 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,5225 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,5425 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,2295 postsЛуганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,9745 postsОрловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,4425 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,1835 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3985 postsLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 155,3205 postsLpr 1
@lpr1_treugolnik · 932,2274 postsБелгородская область оповещения, тревоги
@Belgorod_Lpr1 · 2553 postsБрянская область оповещения,тревоги
@Brynsk_Lpr1 · 2323 postsРеспублика Крым оповещения, тревоги
@Crime_Lpr1 · 6363 postsХерсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 803 postsКраснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 4493 postsКурская область оповещения и тревоги.
@Kursk_Lpr1 · 573 postsЛуганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 2153 postsОрловская область оповещения, тревоги.
@Orlov_Lpr1 · 353 postsРостовская область тревоги, оповещения.
@Rostov_Lpr1 · 2493 postsLPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 1703 postsВоронежская область, оповещения,тревоги.
@Voronezh_lpr1 · 643 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Брянская область оповещения и тревоги” (@lpr1_Bryansk_alarm), 44,384 subscribers as measured 26 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.