БПЛА от Карьерное повернул в направлении Войково, Первомайское

Channel
Республика Крым, Севастополь Оповещения, тревоги
@lpr1_Crimea_Alarm
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
197,069subscribers
+1,168 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1002166201484 |
|---|---|
| Type | Channel |
| Username | @lpr1_Crimea_Alarm |
| Description | MAX: https://max.ru/join/DOoizVuiuVLm-zeEMPCItWCODPhdCmN4T2M6o5qoN7g Чат-бот: @treugolniklnr_bot Реклама @Lpr1reklama Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 РКН: https://clck.ru/3MFjLp |
| 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 | 15 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/lpr1_Crimea_Alarm |
Topic
Local community — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 15 Aug 2026, 11:16 | 197,069 | +113 |
| 14 Aug 2026, 01:47 | 196,956 | +147 |
| 12 Aug 2026, 21:58 | 196,809 | +347 |
| 11 Aug 2026, 20:12 | 196,462 | +102 |
| 10 Aug 2026, 18:07 | 196,360 | +89 |
| 9 Aug 2026, 19:11 | 196,271 | -47 |
| 8 Aug 2026, 22:11 | 196,318 | +135 |
| 7 Aug 2026, 23:44 | 196,183 | +136 |
| 7 Aug 2026, 00:34 | 196,047 | +146 |
| 6 Aug 2026, 01:30 | 195,901 | no change |
| 6 Aug 2026, 00:48 | 195,901 | first reading |
Engagement
458 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 24 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 4.93%
- avg views ÷ 197,069 subscribers
- Avg views / post
- 9,720
- 458 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 458
- of 458 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 16 August 2026 |
|---|---|
| Posts held | 458 (6 August 2026 – 16 August 2026) |
| Views total | 4,449,948 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 07:02 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,370
- Videos
- ≈1,370
- Links
- ≈604
Lifetime counters from Telegram’s own channel header, read 16 August 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
- 4m 35s
- Average length
- 46s
Measured directly from 6 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
БПЛА от Евпатории повернул на Охотниково, Саки, Новофедоровка
Карьерное от Евпатории и далее на Саки, Гвардейское тревога по БПЛА
Ромашкино - Колоски - север Евпатория тревога по БПЛА. И далее возможно в направлении Саки, Гвардейское
Новоозерное, Мирный, Витино, Штормовое, Молочное, Уютное, Заозёрное, Евпатория с запада Опасность по БПЛА
Евпатория и близлежащие Республика Крым Опасность по БПЛА Повторно
Дорогие наши близкие! Огромное Вам спасибо за поддержку нашей деятельности! ❤️❤️❤️ https://pay.cloudtips.ru/p/f2a9c1d8
От Евпатории на запад - Заозёрное, Молочное, Витино, Штормовое, Мирный, Новоозерное и далее Внимание по БПЛА
Евпатория Мойнаки и близлежащие Тревога по БПЛА сохраняется
г. Евпатория тревога по БПЛА. Меры безопасности
Авиагородок Евпатория и далее на запад - Уютное и близлежащие Внимание по БПЛА
Евпатория от Охотниково (севернее Саки) кругами БПЛА. Меры предосторожности
Showing the 12 most recent of 458 posts we hold for @lpr1_Crimea_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.
Citation-graph rank
Citation-graph rank — 12,885 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@LPRalarm · 156,1648 postsLpr 1
@lpr1_treugolnik · 928,3366 postsНовости Севастополя
@news_sev · 1,4654 postsТактическая медицина🤙
@hfjfbcjf · 591 postКУПОЛ РОССИИ
@kupolrussia · 214,2201 postlpr Крым | Тревога и отбои | атаки БПЛА, ракет и тд | оповещение граждан
@lprCrimea · 21 post
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.
@anonimniysevastopol · 1662 postsБрянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 43,8172 postsКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,2322 postsРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 50,9922 postsТревоги и оповещения
@sevasalert · 162 postsБелгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 57,4751 postКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 96,4941 postЛуганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,3131 postLpr 1
@lpr1_treugolnik · 928,3361 postВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3121 postМониторинг Мигалки
@migalka_monitoring · 3631 postРадар.ру | Ростовская область ( обстрелы, БПЛА, ракеты, сводки )
@radar_ru_rostov · 4,6631 postГРАЖДАНСКАЯ БЕЗОПАСНОСТЬ 🇷🇺
@svoi_dobro · 5991 post
Names
Channels on the register whose handles appear in this channel's posts.
@lpr1_Belgorod_alarm · 57,4751 postБрянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 43,8171 postХарьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,0461 postХерсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,3651 postКраснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 96,4941 postКурская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,2321 postЛуганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,3131 postОрловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,4081 postРостовская область тревоги оповещения
@lpr1_Rostov_alarm · 50,9921 postВоронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,3121 postLPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 156,1641 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Республика Крым, Севастополь Оповещения, тревоги” (@lpr1_Crimea_Alarm), 197,069 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/lpr1_Crimea_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.