Telegram RegisterThe public register of Telegram
Telegram profile photo for Луганская Донецкая Народные Республики оповещения, тревоги

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
TypeChannel
Username@lpr1_LDPR_alarm
DescriptionMAX: https://max.ru/join/bL2xNkbH4VezLWjJG2u5dVqLuXhiqm_7oxsjX9oJPKE Чат-бот: @treugolniklnr_bot Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 Реклама: @Lpr1reklama РКН: https://clck.ru/3MFjHR
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.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

36,04837,50136,774.56 August 2026 — 36,048 subscribers6 August 2026 — 36,048 subscribers6 August 2026 — 36,049 subscribers7 August 2026 — 36,060 subscribers8 August 2026 — 36,075 subscribers9 August 2026 — 36,068 subscribers10 August 2026 — 36,090 subscribers11 August 2026 — 36,089 subscribers12 August 2026 — 36,168 subscribers13 August 2026 — 36,217 subscribers14 August 2026 — 36,310 subscribers16 August 2026 — 36,313 subscribers17 August 2026 — 36,315 subscribers18 August 2026 — 36,320 subscribers19 August 2026 — 36,367 subscribers20 August 2026 — 36,384 subscribers22 August 2026 — 36,395 subscribers23 August 2026 — 36,406 subscribers25 August 2026 — 36,455 subscribers26 August 2026 — 36,489 subscribers27 August 2026 — 36,561 subscribers28 August 2026 — 36,615 subscribers29 August 2026 — 36,658 subscribers30 August 2026 — 36,648 subscribers31 August 2026 — 36,723 subscribers1 September 2026 — 36,758 subscribers4 September 2026 — 36,844 subscribers6 September 2026 — 36,892 subscribers9 September 2026 — 36,930 subscribers13 September 2026 — 36,937 subscribers15 September 2026 — 36,948 subscribers17 September 2026 — 36,974 subscribers27 September 2026 — 37,078 subscribers4 October 2026 — 37,161 subscribers9 October 2026 — 37,191 subscribers13 October 2026 — 37,268 subscribers14 October 2026 — 37,250 subscribers15 October 2026 — 37,235 subscribers16 October 2026 — 37,220 subscribers17 October 2026 — 37,214 subscribers18 October 2026 — 37,207 subscribers19 October 2026 — 37,203 subscribers20 October 2026 — 37,243 subscribers21 October 2026 — 37,289 subscribers22 October 2026 — 37,381 subscribers24 October 2026 — 37,442 subscribers25 October 2026 — 37,476 subscribers26 October 2026 — 37,501 subscribers27 October 2026 — 37,492 subscribers29 October 2026 — 37,488 subscribers30 October 2026 — 37,475 subscribers31 October 2026 — 37,466 subscribers1 November 2026 — 37,452 subscribers2 November 2026 — 37,459 subscribers3 November 2026 — 37,453 subscribers4 November 2026 — 37,458 subscribers5 November 2026 — 37,450 subscribers6 November 2026 — 37,435 subscribers7 November 2026 — 37,430 subscribers8 November 2026 — 37,425 subscribers37,4256 August 20268 November 2026
60 measurements spanning 94 days, net +1,377. 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 35,830–37,719 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
8 Nov 2026, 10:5937,425-5
7 Nov 2026, 08:5637,430-5
6 Nov 2026, 12:0837,435-15
5 Nov 2026, 10:1637,450-8
4 Nov 2026, 09:1937,458+5
3 Nov 2026, 10:5937,453-6
2 Nov 2026, 07:1837,459+7
1 Nov 2026, 08:3537,452-14
31 Oct 2026, 07:4837,466-9
30 Oct 2026, 06:0037,475-13
29 Oct 2026, 05:4837,488-4
27 Oct 2026, 03:2637,492-9
26 Oct 2026, 04:3737,501+25
25 Oct 2026, 03:4037,476+34
24 Oct 2026, 00:0637,442+61
22 Oct 2026, 23:1637,381+92
21 Oct 2026, 22:1637,289+46
20 Oct 2026, 16:3037,243+40
19 Oct 2026, 16:0737,203-4
18 Oct 2026, 17:4637,207first 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held3,455 (5 August 2026 – 8 November 2026)
Views total2,840,823
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 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).

8 Nov 2026, 22:41 UTC411 viewsread 8 November 2026

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

8 Nov 2026, 21:29 UTC≈1,130 viewsread 8 November 2026

Новоайдар Счастье, Луганск и далее в направлении Миллеровский, Тарасовский, Каменский районы тревога по БПЛА

8 Nov 2026, 19:34 UTC≈2,550 viewsread 8 November 2026

Светлодарск, Дебальцево и близлежащие Опасность по БПЛА ДНР

8 Nov 2026, 19:32 UTC≈2,590 viewsread 8 November 2026

Донецк, Докучаевск, Старобешево, Моспино и близлежащие Опасность по БПЛА ДНР

8 Nov 2026, 19:22 UTC≈2,810 viewsread 8 November 2026

Донецк и близлежащие Опасность по БПЛА ДНР

8 Nov 2026, 19:02 UTC≈3,850 viewsread 8 November 2026

Пески, окраины Донецка Опасность ФПВ

8 Nov 2026, 18:50 UTC≈3,600 viewsread 8 November 2026

Краснодон и далее в направлении Свердловск Тревога по БПЛА ЛНР Далее с возможным пролётом в сторону Ростовской области

8 Nov 2026, 18:39 UTC≈3,610 viewsread 8 November 2026

Веселая Гора Счастье и близлежащие Тревога по БПЛА И далее в направлении Луганск ЛНР

8 Nov 2026, 18:32 UTC≈3,410 viewsread 8 November 2026

Курахово и близлежащие на восток Опасность по БПЛА ДНР

8 Nov 2026, 17:53 UTC≈3,590 viewsread 8 November 2026

Горловка и близлежащие Опасность по БПЛА и возможным ФПВ повторно, ещё фиксации ДНР

8 Nov 2026, 17:09 UTC≈3,950 viewsread 8 November 2026

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

8 Nov 2026, 17:08 UTC≈3,970 viewsread 8 November 2026

От Покровки в направлении Свердловск БПЛА Хорнет ЛНР

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

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.

МЛНР LIVE ЛУГАНСК | НОВОСТИ
@mlnrlive · 142,548
11 posts
Курская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,153
6 posts
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,226
6 posts
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 45,880
5 posts
Краснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,399
5 posts
Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,014
4 posts
Республика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 194,375
4 posts
Воронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,685
4 posts
Херсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,732
3 posts
ЛуганскИнформЦентр Z
@LIC_LPR · 49,699
2 posts
Lpr 1
@lpr1_treugolnik · 932,002
2 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 154,004
1 post
ВОДИТЕЛЬ ЛНР | ЛУГАНСК АВТО
@lprdriver · 14,021
1 post
Радар.ру | Ростовская область ( обстрелы, БПЛА, ракеты, сводки )
@radar_ru_rostov · 4,963
1 post
ГРАЖДАНСКАЯ БЕЗОПАСНОСТЬ 🇷🇺
@svoi_dobro · 591
1 post

Names

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

Online ДНР: атаки ВФУ
@online_dnr_sckk · 25,686
14 posts
Приходько РИК
@Prikhodko1970 · 150,320
13 posts
Пушилин Д.В.
@PushilinDenis · 80,605
10 posts
Белгородская область оповещения, тревоги
@Belgorod_Lpr1 · 243
2 posts
Брянская область оповещения,тревоги
@Brynsk_Lpr1 · 203
2 posts
Республика Крым оповещения, тревоги
@Crime_Lpr1 · 587
2 posts
Херсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 66
2 posts
Краснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 407
2 posts
Курская область оповещения и тревоги.
@Kursk_Lpr1 · 50
2 posts
Луганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 187
2 posts
Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,014
2 posts
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 45,880
2 posts
Республика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 194,375
2 posts
Харьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,028
2 posts
Херсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,732
2 posts
Краснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,399
2 posts
Курская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,153
2 posts
Орловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,535
2 posts
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,226
2 posts
Воронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,685
2 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 154,004
2 posts
Орловская область оповещения, тревоги.
@Orlov_Lpr1 · 30
2 posts
Ростовская область тревоги, оповещения.
@Rostov_Lpr1 · 227
2 posts
LPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 160
2 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.