Спасибо огромное ❤️❤️❤️ https://pay.cloudtips.ru/p/f2a9c1d8

Channel
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
37,078subscribers
+1,030 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 | 27 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 27 September 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 21:36 | 37,078 | +104 |
| 17 Sept 2026, 17:37 | 36,974 | +26 |
| 15 Sept 2026, 15:56 | 36,948 | +11 |
| 13 Sept 2026, 22:01 | 36,937 | +7 |
| 9 Sept 2026, 20:57 | 36,930 | +38 |
| 6 Sept 2026, 11:15 | 36,892 | +48 |
| 4 Sept 2026, 01:21 | 36,844 | +86 |
| 1 Sept 2026, 13:56 | 36,758 | +35 |
| 31 Aug 2026, 10:35 | 36,723 | +75 |
| 30 Aug 2026, 10:55 | 36,648 | -10 |
| 29 Aug 2026, 09:34 | 36,658 | +43 |
| 28 Aug 2026, 07:13 | 36,615 | +54 |
| 27 Aug 2026, 04:39 | 36,561 | +72 |
| 26 Aug 2026, 05:43 | 36,489 | +34 |
| 25 Aug 2026, 02:47 | 36,455 | +49 |
| 23 Aug 2026, 18:56 | 36,406 | +11 |
| 22 Aug 2026, 02:36 | 36,395 | +11 |
| 20 Aug 2026, 21:03 | 36,384 | +17 |
| 19 Aug 2026, 23:04 | 36,367 | +47 |
| 18 Aug 2026, 20:27 | 36,320 | first reading |
Engagement
1,982 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 102 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.68%
- avg views ÷ 37,078 subscribers
- Avg views / post
- 2,110
- 887 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 887
- of 1,982 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 2 October 2026 |
|---|---|
| Posts held | 1,982 (5 August 2026 – 2 October 2026) |
| Views total | 1,867,959 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Oct 2026, 04:14 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,730
- Videos
- ≈2,090
- Links
- ≈515
Lifetime counters from Telegram’s own channel header, read 2 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
- 3m 05s
- Average length
- 21s
Measured directly from 9 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
Горское и далее в направлении Счастье Тревога по БПЛА ЛНР
Петровка, Счастье ЛНР и близлежащие тревога по БПЛА и далее на Чертковский Тарасовский, Миллеровский район Ростовской области
Счастье и близлежащие Тревога по БПЛА И далее в направлении Луганск ЛНР
Белокуракинский МО ЛНР Тревога по БПЛА сохраняется
От Родаково и далее на Луганск Тревога по БПЛА ЛНР
Старобельск Старобельский МО Тревога по БПЛА ЛНР
Ровеньки ЛНР, Свердловск и близлежащие тревога по БПЛА И далее Новошахтинск, Гуково Донецк Ростовский
Новопсковский МО Белокуракинский МО Тревога по БПЛА от Сватово ЛНР .
Воронежская область Тревога по БПЛА от ЛНР, повторно
Старобельск и близлежащие Тревога по БПЛА от Сватово И далее в направлении Ростовской области
ЛНР. Угроза атаки БПЛА. В границах муниципальных округов: Краснодонский, Лутугинский, Славяносербский, и городов Луганск, Брянка, Кировск, Стаханов, Первомайск РСЧС 1:16
Showing the 12 most recent of 1,982 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.
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 13 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 · 139,95710 postsБрянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 44,3845 postsКурская область оповещения и тревоги
@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,2833 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,5222 postsLpr 1
@lpr1_treugolnik · 932,2271 postВОДИТЕЛЬ ЛНР | ЛУГАНСК АВТО
@lprdriver · 13,9681 postРадар.ру | Ростовская область ( обстрелы, БПЛА, ракеты, сводки )
@radar_ru_rostov · 4,8661 postГРАЖДАНСКАЯ БЕЗОПАСНОСТЬ 🇷🇺
@svoi_dobro · 5961 post
Names
Channels on the register whose handles appear in this channel's posts.
@PushilinDenis · 81,17310 postsПриходько РИК
@Prikhodko1970 · 145,8079 postsБелгородская область оповещения, тревоги
@Belgorod_Lpr1 · 2552 postsБрянская область оповещения,тревоги
@Brynsk_Lpr1 · 2202 postsРеспублика Крым оповещения, тревоги
@Crime_Lpr1 · 6362 postsХерсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 802 postsКраснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 4492 postsКурская область оповещения и тревоги.
@Kursk_Lpr1 · 532 postsЛуганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 2002 postsБелгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,4532 postsБрянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 44,3842 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 196,2832 postsХарьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,0372 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,5222 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,5422 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,2292 postsОрловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,4392 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,1832 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3982 postsLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 155,3202 postsОрловская область оповещения, тревоги.
@Orlov_Lpr1 · 352 postsРостовская область тревоги, оповещения.
@Rostov_Lpr1 · 2492 postsLPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 1662 postsВоронежская область, оповещения,тревоги.
@Voronezh_lpr1 · 642 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Луганская Донецкая Народные Республики оповещения, тревоги” (@lpr1_LDPR_alarm), 37,078 subscribers as measured 27 September 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.