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

Channel

Воронежская область, оповещения, тревоги

@lpr1_Voronezh_alarm

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

11,674subscribers

+413 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-1002250260946
TypeChannel
Username@lpr1_Voronezh_alarm
DescriptionMAX: https://max.ru/join/pvwYeO2fRto6m6MLvs2pituMfdDHmVzUqVlHVionQmU Регистрация канала в РКН: № 7541864389 Чат-бот приема информации: @treugolniklnr_bot
CreatedBetween 1 September 2024 and 31 January 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/lpr1_Voronezh_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 11 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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

11,26111,69211,476.57 August 2026 — 11,261 subscribers7 August 2026 — 11,263 subscribers8 August 2026 — 11,266 subscribers9 August 2026 — 11,269 subscribers11 August 2026 — 11,273 subscribers11 August 2026 — 11,276 subscribers12 August 2026 — 11,306 subscribers14 August 2026 — 11,313 subscribers15 August 2026 — 11,312 subscribers16 August 2026 — 11,316 subscribers17 August 2026 — 11,311 subscribers18 August 2026 — 11,307 subscribers20 August 2026 — 11,309 subscribers21 August 2026 — 11,314 subscribers22 August 2026 — 11,315 subscribers24 August 2026 — 11,311 subscribers25 August 2026 — 11,314 subscribers26 August 2026 — 11,312 subscribers27 August 2026 — 11,313 subscribers28 August 2026 — 11,315 subscribers29 August 2026 — 11,310 subscribers30 August 2026 — 11,321 subscribers31 August 2026 — 11,352 subscribers1 September 2026 — 11,375 subscribers2 September 2026 — 11,379 subscribers3 September 2026 — 11,383 subscribers4 September 2026 — 11,377 subscribers8 September 2026 — 11,367 subscribers10 September 2026 — 11,371 subscribers13 September 2026 — 11,375 subscribers14 September 2026 — 11,373 subscribers16 September 2026 — 11,370 subscribers19 September 2026 — 11,374 subscribers25 September 2026 — 11,398 subscribers4 October 2026 — 11,481 subscribers8 October 2026 — 11,462 subscribers13 October 2026 — 11,457 subscribers14 October 2026 — 11,458 subscribers15 October 2026 — 11,457 subscribers18 October 2026 — 11,460 subscribers19 October 2026 — 11,456 subscribers20 October 2026 — 11,464 subscribers21 October 2026 — 11,471 subscribers22 October 2026 — 11,477 subscribers23 October 2026 — 11,557 subscribers24 October 2026 — 11,553 subscribers25 October 2026 — 11,561 subscribers26 October 2026 — 11,618 subscribers27 October 2026 — 11,639 subscribers28 October 2026 — 11,660 subscribers29 October 2026 — 11,677 subscribers30 October 2026 — 11,687 subscribers31 October 2026 — 11,689 subscribers1 November 2026 — 11,686 subscribers2 November 2026 — 11,684 subscribers4 November 2026 — 11,692 subscribers5 November 2026 — 11,690 subscribers6 November 2026 — 11,686 subscribers7 November 2026 — 11,685 subscribers9 November 2026 — 11,674 subscribers11,6747 August 20269 November 2026
60 measurements spanning 94 days, net +413. 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 11,196–11,757 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
9 Nov 2026, 15:0911,674-11
7 Nov 2026, 06:0811,685-1
6 Nov 2026, 06:2011,686-4
5 Nov 2026, 07:3111,690-2
4 Nov 2026, 06:3911,692+8
2 Nov 2026, 08:2911,684-2
1 Nov 2026, 11:4711,686-3
31 Oct 2026, 13:4911,689+2
30 Oct 2026, 16:2811,687+10
29 Oct 2026, 16:4611,677+17
28 Oct 2026, 16:4111,660+21
27 Oct 2026, 16:2911,639+21
26 Oct 2026, 16:3811,618+57
25 Oct 2026, 18:0011,561+8
24 Oct 2026, 19:3911,553-4
23 Oct 2026, 20:4811,557+80
22 Oct 2026, 22:2111,477+6
21 Oct 2026, 19:3811,471+7
20 Oct 2026, 16:3911,464+8
19 Oct 2026, 13:2711,456first reading

Engagement

587 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 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.4%
avg views ÷ 11,674 subscribers
Avg views / post
1,450
169 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
169
of 587 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 held587 (6 August 2026 – 10 November 2026)
Views total245,532
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 20:28 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
448
Videos
470
Links
183

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. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
13m 34s
Average length
26s

Measured directly from 31 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: 0 of 169 posts held from the last 30 days (0%) 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, 19:38 UTC500 viewsread 10 November 2026

Старооскольский район Белгородская область Тревога по БПЛА И далее в направлении Воронежской области

10 Nov 2026, 18:26 UTC916 viewsread 10 November 2026

Марковский МО ЛНР Тревога по БПЛА И далее в направлении Воронежской области

10 Nov 2026, 18:17 UTC934 viewsread 10 November 2026

Богучарский район Кантемировский район Тревога по БПЛА Воронежская область

10 Nov 2026, 18:12 UTC≈1,000 viewsread 10 November 2026

Воронежская область Опасность по БПЛА

10 Nov 2026, 11:49 UTC≈1,380 viewsread 10 November 2026

Отбой ракетной опасности по Фламинго ЛНР Ростовская область Воронежская область Тамбовская область Астраханская область Республика Мордовия Оренбургская область

10 Nov 2026, 11:25 UTC≈1,570 viewsread 10 November 2026

Ракетная опасность по объявленным регионам в связи с фиксацией Фламинго над территорией ЛНР

10 Nov 2026, 11:18 UTC≈1,620 viewsread 10 November 2026

Воронежская область Ракетная опасность

10 Nov 2026, 03:30 UTC≈1,740 viewsread 10 November 2026

Воронежская область, отбой опасности БПЛА

9 Nov 2026, 18:56 UTC≈1,890 viewsread 10 November 2026

Харьковская область РФ в направлении Белгородской, Воронежской области многочисленные фиксации БПЛА

9 Nov 2026, 18:56 UTC≈1,860 viewsread 10 November 2026

Воронежская область Тревога по БПЛА

9 Nov 2026, 18:18 UTC≈1,810 viewsread 10 November 2026

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

9 Nov 2026, 18:12 UTC≈1,840 viewsread 10 November 2026

ЛДНР, Ростовская область отбой ракетной тревоги Воронежская область, Краснодарский край отбой внимания по ракетам от ЛДНР

Showing the 12 most recent of 587 posts we hold for @lpr1_Voronezh_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 edited after publishing

@lpr1_Voronezh_alarm edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 August 2026
Most recent edit
15 August 2026

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.

Names

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

Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 56,977
4 posts
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 45,868
4 posts
Республика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 194,263
4 posts
Харьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,027
4 posts
Херсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,725
4 posts
Краснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,317
4 posts
Курская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,147
4 posts
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 37,414
4 posts
Орловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,535
4 posts
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 52,192
4 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 153,946
4 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

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

“Воронежская область, оповещения, тревоги” (@lpr1_Voronezh_alarm), 11,674 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/lpr1_Voronezh_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.