Наши дорогие близкие! Спасибо огромное за поддержку нашей деятельности ❤️❤️❤️ https://pay.cloudtips.ru/p/f2a9c1d8

Channel
Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
57,501subscribers
+152 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 | -1002237387180 |
|---|---|
| Type | Channel |
| Username | @lpr1_Belgorod_alarm |
| Description | MAX: https://max.ru/join/FDb4xA3Vlf08CzD9GoZRucPqSoMPdls9SfZ-AQXM9sA Чат-бот: @treugolniklnr_bot Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 Реклама: @Lpr1reklama РКН: https://clck.ru/3P6MX8 |
| 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 | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/lpr1_Belgorod_alarm |
Topic
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 76% 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 |
|---|---|---|
| 17 Sept 2026, 02:55 | 57,501 | -18 |
| 15 Sept 2026, 01:01 | 57,519 | +6 |
| 13 Sept 2026, 11:36 | 57,513 | +13 |
| 11 Sept 2026, 16:00 | 57,500 | -19 |
| 9 Sept 2026, 01:58 | 57,519 | -18 |
| 5 Sept 2026, 21:01 | 57,537 | -1 |
| 3 Sept 2026, 19:20 | 57,538 | -8 |
| 2 Sept 2026, 14:24 | 57,546 | -4 |
| 1 Sept 2026, 14:08 | 57,550 | +3 |
| 31 Aug 2026, 16:38 | 57,547 | +13 |
| 30 Aug 2026, 16:08 | 57,534 | -4 |
| 29 Aug 2026, 15:58 | 57,538 | +7 |
| 28 Aug 2026, 15:45 | 57,531 | +10 |
| 27 Aug 2026, 13:13 | 57,521 | +2 |
| 26 Aug 2026, 14:54 | 57,519 | +2 |
| 25 Aug 2026, 11:33 | 57,517 | -3 |
| 24 Aug 2026, 10:24 | 57,520 | -23 |
| 22 Aug 2026, 20:44 | 57,543 | +46 |
| 21 Aug 2026, 08:34 | 57,497 | -9 |
| 20 Aug 2026, 11:24 | 57,506 | first reading |
Engagement
1,804 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 104 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.25%
- avg views ÷ 57,501 subscribers
- Avg views / post
- 4,750
- 1,077 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1,077
- of 1,804 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 23 September 2026 |
|---|---|
| Posts held | 1,804 (5 August 2026 – 23 September 2026) |
| Views total | 5,110,436 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 18: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
- ≈2,080
- Videos
- ≈1,840
- Links
- ≈3,960
Lifetime counters from Telegram’s own channel header, read 23 September 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
- 4s
Measured directly from 48 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
Шебекино Тревога по БПЛА Хорнет
Курская область и близлежащие Авиационная ракетная бомбовая опасность
Курская область и близлежащие Отбой Авиационной ракетной бомбовой опасности
Курская область и близлежащие Авиационная ракетная бомбовая опасность
Красная яруга Тревога по БПЛА Белгородская область
Ясные зори, Черемошное Белгородский район Тревога по БПЛА
За минувшие сутки ВСУ 150 раз атаковали территорию Белгородской области Совершены удары по Алексеевскому, Белгородскому, Борисовскому, Валуйскому, Волоконовскому, Грайворонскому, Губкинскому, Красногвардейскому, Краснояружскому, Новооскольскому, Ракитянскому, Чернянскому и Шебекинскому округам. Противник произвёл 14 обстрелов с применением артиллерии, авиации и реактивных систем залпового огня. Также 6 раз сбрасыва…
ОТБОЙ ОПАСНОСТИ АТАКИ БПЛА в г. Белгороде, Борисовском, Валуйском, Волоконовском, Ракитянском, Алексеевском, Ровеньском, Вейделевском, Новооскольском, Красненском, Ивнянском, Прохоровском, Красногвардейском и Чернянском МО
Шебекино Тревога по БПЛА
Курская, Брянская, Орловская, Воронежская, Белгородская область Отбой ракетной опасности
Курская область и ближайшие, ракетная опасность
Showing the 12 most recent of 1,804 posts we hold for @lpr1_Belgorod_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 11 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.
@lpr1_Bryansk_alarm · 44,1865 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,2495 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 51,9295 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,5614 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3744 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 196,8903 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,5172 postsЛуганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,9742 postsLpr 1
@lpr1_treugolnik · 933,0151 postРадар.ру | Ростовская область ( обстрелы, БПЛА, ракеты, сводки )
@radar_ru_rostov · 4,8471 postГРАЖДАНСКАЯ БЕЗОПАСНОСТЬ 🇷🇺
@svoi_dobro · 6001 post
Names
Channels on the register whose handles appear in this channel's posts.
@lpr1_Bryansk_alarm · 44,1863 postsРеспублика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm · 196,8903 postsХарьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,0393 postsХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,5173 postsКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,5613 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,2493 postsЛуганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,9743 postsОрловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,4423 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 51,9293 postsВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3743 postsLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 155,4593 postsБелгородская область оповещения, тревоги
@Belgorod_Lpr1 · 2552 postsБрянская область оповещения,тревоги
@Brynsk_Lpr1 · 2322 postsРеспублика Крым оповещения, тревоги
@Crime_Lpr1 · 6362 postsХерсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 912 postsКраснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 4492 postsКурская область оповещения и тревоги.
@Kursk_Lpr1 · 572 postsЛуганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 2152 postsLpr 1
@lpr1_treugolnik · 933,0152 postsОрловская область оповещения, тревоги.
@Orlov_Lpr1 · 352 postsРостовская область тревоги, оповещения.
@Rostov_Lpr1 · 2492 postsLPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 1702 postsВоронежская область, оповещения,тревоги.
@Voronezh_lpr1 · 642 postsОперштаб Белгородской области
@operativno31 · 15,1971 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@mfoto31 · 45,952
Telegram ranks this channel #11 of 66 here — alongside 65 others — read 27 August 2026
@vvgladkov · 414,183
Telegram ranks this channel #11 of 87 here — alongside 86 others — read 10 August 2026
@bbbelgorod · 49,116
Telegram ranks this channel #12 of 88 here — alongside 87 others — read 26 August 2026
@belgorodc400 · 49,567
Telegram ranks this channel #13 of 83 here — alongside 82 others — read 25 August 2026
@zhest_belgorod · 591,426
Telegram ranks this channel #14 of 75 here — alongside 74 others — read 8 August 2026
@avto_belgorod31 · 25,583
Telegram ranks this channel #15 of 83 here — alongside 82 others — read 14 September 2026
@stroitel_online_31 · 26,843
Telegram ranks this channel #16 of 33 here — alongside 32 others — read 11 September 2026
@club_shebekino · 48,980
Telegram ranks this channel #18 of 59 here — alongside 58 others — read 26 August 2026
@bel31online · 46,004
Telegram ranks this channel #20 of 82 here — alongside 81 others — read 27 August 2026
@fonartv · 26,787
Telegram ranks this channel #22 of 88 here — alongside 87 others — read 11 September 2026
@belgorod_informant · 22,532
Telegram ranks this channel #23 of 82 here — alongside 81 others — read 20 September 2026
@r31belgorod · 31,467
Telegram ranks this channel #24 of 81 here — alongside 80 others — read 10 September 2026
@belgorod_life · 27,857
Telegram ranks this channel #27 of 70 here — alongside 69 others — read 10 September 2026
@rschs_prigranichie · 28,170
Telegram ranks this channel #43 of 73 here — alongside 72 others — read 9 September 2026
@XNRRussia · 25,274
Telegram ranks this channel #58 of 82 here — alongside 81 others — read 14 September 2026
This channel appears in 15 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Белгородская область оповещения, тревоги” (@lpr1_Belgorod_alarm), 57,501 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/lpr1_Belgorod_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.