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

Channel

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

@lpr1_Kursk_alarm

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

25,147subscribers

-80 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002236355955
TypeChannel
Username@lpr1_Kursk_alarm
DescriptionЧат-бот приема информации: @treugolniklnr_bot Благодарность админам: https://pay.cloudtips.ru/p/f2a9c1d8 Менеджер по рекламе @Lpr1reklama РКН: https://clck.ru/3MFjAw
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/lpr1_Kursk_alarm

Topic

National news — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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

25,14725,25825,202.57 August 2026 — 25,227 subscribers7 August 2026 — 25,227 subscribers7 August 2026 — 25,240 subscribers9 August 2026 — 25,248 subscribers10 August 2026 — 25,251 subscribers11 August 2026 — 25,238 subscribers12 August 2026 — 25,231 subscribers13 August 2026 — 25,237 subscribers14 August 2026 — 25,236 subscribers15 August 2026 — 25,232 subscribers17 August 2026 — 25,226 subscribers18 August 2026 — 25,229 subscribers19 August 2026 — 25,227 subscribers20 August 2026 — 25,225 subscribers21 August 2026 — 25,221 subscribers22 August 2026 — 25,209 subscribers24 August 2026 — 25,210 subscribers25 August 2026 — 25,207 subscribers28 August 2026 — 25,205 subscribers29 August 2026 — 25,199 subscribers30 August 2026 — 25,190 subscribers31 August 2026 — 25,193 subscribers1 September 2026 — 25,203 subscribers2 September 2026 — 25,206 subscribers4 September 2026 — 25,204 subscribers6 September 2026 — 25,201 subscribers9 September 2026 — 25,224 subscribers11 September 2026 — 25,256 subscribers13 September 2026 — 25,258 subscribers15 September 2026 — 25,254 subscribers17 September 2026 — 25,249 subscribers26 September 2026 — 25,229 subscribers4 October 2026 — 25,199 subscribers13 October 2026 — 25,217 subscribers14 October 2026 — 25,212 subscribers15 October 2026 — 25,210 subscribers16 October 2026 — 25,203 subscribers17 October 2026 — 25,212 subscribers18 October 2026 — 25,200 subscribers21 October 2026 — 25,207 subscribers22 October 2026 — 25,203 subscribers23 October 2026 — 25,204 subscribers24 October 2026 — 25,197 subscribers25 October 2026 — 25,207 subscribers26 October 2026 — 25,216 subscribers28 October 2026 — 25,211 subscribers29 October 2026 — 25,209 subscribers30 October 2026 — 25,205 subscribers31 October 2026 — 25,201 subscribers1 November 2026 — 25,195 subscribers2 November 2026 — 25,201 subscribers4 November 2026 — 25,186 subscribers5 November 2026 — 25,176 subscribers6 November 2026 — 25,169 subscribers7 November 2026 — 25,166 subscribers8 November 2026 — 25,153 subscribers10 November 2026 — 25,147 subscribers7 August 202610 November 2026
57 measurements spanning 95 days, net -80. 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 25,130–25,275 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
10 Nov 2026, 08:4825,147-6
8 Nov 2026, 22:2025,153-13
7 Nov 2026, 12:2225,166-3
6 Nov 2026, 10:4725,169-7
5 Nov 2026, 11:4525,176-10
4 Nov 2026, 12:0425,186-15
2 Nov 2026, 10:4725,201+6
1 Nov 2026, 08:2825,195-6
31 Oct 2026, 07:0925,201-4
30 Oct 2026, 08:0625,205-4
29 Oct 2026, 04:3125,209-2
28 Oct 2026, 01:5625,211-5
26 Oct 2026, 22:4525,216+9
25 Oct 2026, 19:5525,207+10
24 Oct 2026, 19:1625,197-7
23 Oct 2026, 21:2725,204+1
22 Oct 2026, 23:5625,203-4
21 Oct 2026, 22:5625,207+7
18 Oct 2026, 16:5425,200-12
17 Oct 2026, 14:5525,212first reading

Engagement

1,729 posts held, back to 6 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 168 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.43%
avg views ÷ 25,147 subscribers
Avg views / post
1,360
695 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
695
of 1,729 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 10 November 2026
Posts held1,729 (6 August 2026 – 10 November 2026)
Views total948,299
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 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
≈1,020
Videos
≈1,300
Links
≈380

Lifetime counters from Telegram’s own channel header, read 10 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
3m 23s
Average length
8s

Measured directly from 26 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: 1 of 695 posts held from the last 30 days (0.144%) 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).

10 Nov 2026, 11:35 UTC155 viewsread 10 November 2026

Обоянский, Солнцевский, Курский районы опасность по БПЛА

10 Nov 2026, 11:20 UTC269 viewsread 10 November 2026

Обоянь и близлежащие Курской области Опасность по БПЛА

10 Nov 2026, 11:15 UTC300 viewsread 10 November 2026

Отбой авиационно ракетно бомбовой опасности по всем раннее объявленным

10 Nov 2026, 11:12 UTC368 viewsread 10 November 2026

Рыльск опасность по ФПВ от Хомутовки сохраняется, есть ещё фиксация

10 Nov 2026, 10:56 UTC403 viewsread 10 November 2026

Дорогие наши друзья! Огромное Вам спасибо за поддержку нашей деятельности! Мы никогда не получали какого-либо финансирования, кроме Вашей помощи, и существуем исключительно благодаря Вам. Желающие выразить благодарность и поддержку могут перейти по ссылке: 👇👇👇 https://pay.cloudtips.ru/p/f2a9c1d8 ❤️❤️❤️ Ещё раз огромное спасибо!

10 Nov 2026, 09:49 UTC558 viewsread 10 November 2026

Курская область и близлежащие Авиационно ракетно бомбовая опасность

10 Nov 2026, 09:48 UTC566 viewsread 10 November 2026

Обоянь и близлежащие Опасность по БПЛА Курская область

10 Nov 2026, 08:42 UTC712 viewsread 10 November 2026

Большой каменец Курская область Опасность по БПЛА

10 Nov 2026, 08:36 UTC739 viewsread 10 November 2026

Любостань Сторожевое и близлежащие Курская область Опасность по БПЛА

10 Nov 2026, 07:58 UTC828 viewsread 10 November 2026

Суджа и близлежащие Курская область Опасность по БПЛА

10 Nov 2026, 07:48 UTC862 viewsread 10 November 2026

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

10 Nov 2026, 07:28 UTC894 viewsread 10 November 2026

Большое Солдатское и близлежащие Курская область Опасность по БПЛА

Showing the 12 most recent of 1,729 posts we hold for @lpr1_Kursk_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 34 posts on @lpr1_Kursk_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
8 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
15 hours
Seen missing in the last 30 days
8

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 · 56,977
6 posts
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 45,868
6 posts
Республика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 194,263
6 posts
Харьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,027
6 posts
Херсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,725
6 posts
Краснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,317
6 posts
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 37,414
6 posts
Орловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,535
6 posts
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,192
6 posts
Воронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,674
6 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 153,946
6 posts
Lpr 1
@lpr1_treugolnik · 931,786
3 posts
Белгородская область оповещения, тревоги
@Belgorod_Lpr1 · 240
2 posts
Брянская область оповещения,тревоги
@Brynsk_Lpr1 · 203
2 posts
Республика Крым оповещения, тревоги
@Crime_Lpr1 · 587
2 posts
Херсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 66
2 posts
Краснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 403
2 posts
Курская область оповещения и тревоги.
@Kursk_Lpr1 · 50
2 posts
Луганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 185
2 posts
Орловская область оповещения, тревоги.
@Orlov_Lpr1 · 29
2 posts
Ростовская область тревоги, оповещения.
@Rostov_Lpr1 · 223
2 posts
LPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 160
2 posts
Воронежская область, оповещения,тревоги.
@Voronezh_lpr1 · 58
2 posts
Александр Хинштейн
@Hinshtein · 213,096
1 post

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

“Курская область оповещения и тревоги” (@lpr1_Kursk_alarm), 25,147 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/lpr1_Kursk_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.