Пятихатки, Бондариевка, Корсунь ДНР Дорога Пантелеймоновна - Енакиево И близлежащие Опасность по БПЛА и возможным сбросам с БПЛА

Channel
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry
37,425subscribers
+1,377 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 | -1002228985332 |
|---|---|
| Type | Channel |
| Username | @lpr1_LDPR_alarm |
| Description | MAX: https://max.ru/join/bL2xNkbH4VezLWjJG2u5dVqLuXhiqm_7oxsjX9oJPKE Чат-бот: @treugolniklnr_bot Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 Реклама: @Lpr1reklama РКН: https://clck.ru/3MFjHR |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/lpr1_LDPR_alarm |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 10:59 | 37,425 | -5 |
| 7 Nov 2026, 08:56 | 37,430 | -5 |
| 6 Nov 2026, 12:08 | 37,435 | -15 |
| 5 Nov 2026, 10:16 | 37,450 | -8 |
| 4 Nov 2026, 09:19 | 37,458 | +5 |
| 3 Nov 2026, 10:59 | 37,453 | -6 |
| 2 Nov 2026, 07:18 | 37,459 | +7 |
| 1 Nov 2026, 08:35 | 37,452 | -14 |
| 31 Oct 2026, 07:48 | 37,466 | -9 |
| 30 Oct 2026, 06:00 | 37,475 | -13 |
| 29 Oct 2026, 05:48 | 37,488 | -4 |
| 27 Oct 2026, 03:26 | 37,492 | -9 |
| 26 Oct 2026, 04:37 | 37,501 | +25 |
| 25 Oct 2026, 03:40 | 37,476 | +34 |
| 24 Oct 2026, 00:06 | 37,442 | +61 |
| 22 Oct 2026, 23:16 | 37,381 | +92 |
| 21 Oct 2026, 22:16 | 37,289 | +46 |
| 20 Oct 2026, 16:30 | 37,243 | +40 |
| 19 Oct 2026, 16:07 | 37,203 | -4 |
| 18 Oct 2026, 17:46 | 37,207 | first reading |
Engagement
3,455 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 177 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.52%
- avg views ÷ 37,425 subscribers
- Avg views / post
- 2,440
- 1,165 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1,165
- of 3,455 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 8 November 2026 |
|---|---|
| Posts held | 3,455 (5 August 2026 – 8 November 2026) |
| Views total | 2,840,823 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 23:21 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
- ≈1,760
- Videos
- ≈2,150
- Links
- ≈554
Lifetime counters from Telegram’s own channel header, read 8 November 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
- 1m 03s
- Average length
- 4s
Measured directly from 17 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
Telegram’s own ‘edited’ marker: 3 of 1,165 posts held from the last 30 days (0.258%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Новоайдар Счастье, Луганск и далее в направлении Миллеровский, Тарасовский, Каменский районы тревога по БПЛА
Светлодарск, Дебальцево и близлежащие Опасность по БПЛА ДНР
Донецк, Докучаевск, Старобешево, Моспино и близлежащие Опасность по БПЛА ДНР
Донецк и близлежащие Опасность по БПЛА ДНР
Пески, окраины Донецка Опасность ФПВ
Краснодон и далее в направлении Свердловск Тревога по БПЛА ЛНР Далее с возможным пролётом в сторону Ростовской области
Веселая Гора Счастье и близлежащие Тревога по БПЛА И далее в направлении Луганск ЛНР
Курахово и близлежащие на восток Опасность по БПЛА ДНР
Горловка и близлежащие Опасность по БПЛА и возможным ФПВ повторно, ещё фиксации ДНР
Старобельск и близлежащие Тревога по БПЛА ЛНР
От Покровки в направлении Свердловск БПЛА Хорнет ЛНР
Showing the 12 most recent of 3,455 posts we hold for @lpr1_LDPR_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.
Posts recorded as deleted after publishing
We recorded 1 post on @lpr1_LDPR_alarm as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 24 September 2026
- Most recent seen missing
- 24 September 2026
- Median time before seen missing
- 13 hours
- Seen missing in the last 30 days
- 0
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.
@lpr1_treugolnik · 932,0021,917 postsПриходько РИК
@Prikhodko1970 · 150,32014 postsПушилин Д.В.
@PushilinDenis · 80,60510 postsФакты военных преступлений Украины
@DNR_SCKK · 14,6224 postsLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 154,0043 postsКУПОЛ РОССИИ
@kupolrussia · 225,2011 post
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 15 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.
@mlnrlive · 142,54811 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,1536 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,2266 postsБрянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 45,8805 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,3995 postsБелгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,0144 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 194,3754 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,6854 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,7323 postsЛуганскИнформЦентр Z
@LIC_LPR · 49,6992 postsLpr 1
@lpr1_treugolnik · 932,0022 postsLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 154,0041 postВОДИТЕЛЬ ЛНР | ЛУГАНСК АВТО
@lprdriver · 14,0211 postРадар.ру | Ростовская область ( обстрелы, БПЛА, ракеты, сводки )
@radar_ru_rostov · 4,9631 postГРАЖДАНСКАЯ БЕЗОПАСНОСТЬ 🇷🇺
@svoi_dobro · 5911 post
Names
Channels on the register whose handles appear in this channel's posts.
@online_dnr_sckk · 25,68614 postsПриходько РИК
@Prikhodko1970 · 150,32013 postsПушилин Д.В.
@PushilinDenis · 80,60510 postsБелгородская область оповещения, тревоги
@Belgorod_Lpr1 · 2432 postsБрянская область оповещения,тревоги
@Brynsk_Lpr1 · 2032 postsРеспублика Крым оповещения, тревоги
@Crime_Lpr1 · 5872 postsХерсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 662 postsКраснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 4072 postsКурская область оповещения и тревоги.
@Kursk_Lpr1 · 502 postsЛуганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 1872 postsБелгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,0142 postsБрянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 45,8802 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 194,3752 postsХарьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,0282 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,7322 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,3992 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,1532 postsОрловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,5352 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,2262 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,6852 postsLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 154,0042 postsОрловская область оповещения, тревоги.
@Orlov_Lpr1 · 302 postsРостовская область тревоги, оповещения.
@Rostov_Lpr1 · 2272 postsLPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 1602 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Луганская Донецкая Народные Республики оповещения, тревоги” (@lpr1_LDPR_alarm), 37,425 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/lpr1_LDPR_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.