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

Channel

Республика Крым, Севастополь Оповещения, тревоги

@lpr1_Crimea_Alarm

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

196,890subscribers

+989 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
TypeChannel
Username@lpr1_Crimea_Alarm
DescriptionMAX: https://max.ru/join/DOoizVuiuVLm-zeEMPCItWCODPhdCmN4T2M6o5qoN7g Чат-бот: @treugolniklnr_bot Реклама @Lpr1reklama Благодарность: https://pay.cloudtips.ru/p/f2a9c1d8 РКН: https://clck.ru/3MFjLp
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 live18 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.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

195,901197,441196,6716 August 2026 — 195,901 subscribers6 August 2026 — 195,901 subscribers7 August 2026 — 196,047 subscribers7 August 2026 — 196,183 subscribers8 August 2026 — 196,318 subscribers9 August 2026 — 196,271 subscribers10 August 2026 — 196,360 subscribers11 August 2026 — 196,462 subscribers12 August 2026 — 196,809 subscribers14 August 2026 — 196,956 subscribers15 August 2026 — 197,069 subscribers16 August 2026 — 197,037 subscribers17 August 2026 — 196,983 subscribers18 August 2026 — 197,026 subscribers19 August 2026 — 197,161 subscribers20 August 2026 — 197,226 subscribers22 August 2026 — 197,239 subscribers23 August 2026 — 197,276 subscribers25 August 2026 — 197,234 subscribers26 August 2026 — 197,217 subscribers27 August 2026 — 197,207 subscribers28 August 2026 — 197,427 subscribers29 August 2026 — 197,441 subscribers30 August 2026 — 197,406 subscribers31 August 2026 — 197,429 subscribers1 September 2026 — 197,427 subscribers2 September 2026 — 197,384 subscribers3 September 2026 — 197,366 subscribers4 September 2026 — 197,298 subscribers7 September 2026 — 197,149 subscribers10 September 2026 — 197,202 subscribers12 September 2026 — 197,109 subscribers14 September 2026 — 197,060 subscribers16 September 2026 — 196,990 subscribers18 September 2026 — 196,890 subscribers196,8906 August 202618 September 2026
35 measurements spanning 44 days, net +989. 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 195,670–197,672 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
18 Sept 2026, 18:19196,890-100
16 Sept 2026, 08:58196,990-70
14 Sept 2026, 13:39197,060-49
12 Sept 2026, 23:00197,109-93
10 Sept 2026, 21:02197,202+53
7 Sept 2026, 20:56197,149-149
4 Sept 2026, 22:38197,298-68
3 Sept 2026, 09:17197,366-18
2 Sept 2026, 00:34197,384-43
1 Sept 2026, 01:07197,427-2
31 Aug 2026, 01:14197,429+23
30 Aug 2026, 03:35197,406-35
29 Aug 2026, 06:06197,441+14
28 Aug 2026, 03:33197,427+220
27 Aug 2026, 01:35197,207-10
26 Aug 2026, 01:23197,217-17
25 Aug 2026, 03:25197,234-42
23 Aug 2026, 20:57197,276+37
22 Aug 2026, 07:58197,239+13
20 Aug 2026, 22:54197,226first reading

Engagement

1,954 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 100 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.20%
avg views ÷ 196,890 subscribers
Avg views / post
10,200
1,149 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1,149
of 1,954 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 23 September 2026
Posts held1,954 (6 August 202623 September 2026)
Views total11,769,918
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 19:37 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,400
Videos
1,440
Links
658

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 47s
Average length
23s

Measured directly from 10 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

23 Sept 2026, 19:25 UTC≈5,030 viewsread 23 September 2026

Севастополь и близлежащие Тревога по БПЛА сохраняется

23 Sept 2026, 19:24 UTC≈6,040 viewsread 23 September 2026

Сары-Баш Алексеевка и близлежащие Опасность по БПЛА Республика Крым

23 Sept 2026, 19:14 UTC≈8,050 viewsread 23 September 2026

Кача Бельбек и близлежащие Меры безопасности при БПЛА

23 Sept 2026, 19:13 UTC≈8,050 viewsread 23 September 2026

От Орловки в направлении Кача Фиксация БПЛА Севастополь

23 Sept 2026, 19:12 UTC≈8,050 viewsread 23 September 2026
Forwarded from @lpr1_treugolnik

От Качи в сторону Бельбека Тревога по БПЛА

23 Sept 2026, 19:11 UTC≈21,200 viewsread 23 September 2026

Керченский полуостров, Ленинский район на юг тревога по БПЛА в направлении примерно Чауда

23 Sept 2026, 19:07 UTC≈8,060 viewsread 23 September 2026
Forwarded from @lpr1_treugolnik

Раздольненский район Республика Крым Опасность по БПЛА

23 Sept 2026, 19:05 UTC≈9,060 viewsread 23 September 2026
Forwarded from @lpr1_treugolnik

Бельбек и близлежащие Тревога по БПЛА-матке со сбросами ФПВ

23 Sept 2026, 19:04 UTC≈9,060 viewsread 23 September 2026
Forwarded from @lpr1_treugolnik

Андреевка Кача и близлежащие Республика Крым Опасность по БПЛА

23 Sept 2026, 19:01 UTC≈9,070 viewsread 23 September 2026

Вилино Угловое И далее в направлении Севастополь Тревога по БПЛА сохраняется

23 Sept 2026, 18:56 UTC≈9,070 viewsread 23 September 2026
Forwarded from @lpr1_treugolnik

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

23 Sept 2026, 18:54 UTC≈9,060 viewsread 23 September 2026
Forwarded from @lpr1_treugolnik

Севастополь, ЮБК Опасность по БПЛА

Showing the 12 most recent of 1,954 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.

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 14 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 · 57,501
3 posts
Брянская область оповещения и тревоги
@lpr1_Bryansk_alarm · 44,186
3 posts
Харьковская область РФ тревоги, оповещения о воздушной опасности
@lpr1_Kharkov_alarm · 1,039
3 posts
Херсонская область РФ, Запорожская область РФ оповещения, тревоги
@lpr1_Kherson_alarm · 27,517
3 posts
Краснодарский Край оповещения, тревоги
@lpr1_Krasnodar_alarm · 97,561
3 posts
Курская область оповещения и тревоги
@lpr1_Kursk_alarm · 25,249
3 posts
Луганская Донецкая Народные Республики оповещения, тревоги
@lpr1_LDPR_alarm · 36,974
3 posts
Орловская область оповещения, тревоги
@lpr1_Orlov_alarm · 5,442
3 posts
Ростовская область тревоги оповещения
@lpr1_Rostov_alarm · 51,929
3 posts
Воронежская область, оповещения, тревоги
@lpr1_Voronezh_alarm · 11,374
3 posts
LPR оповещения, тревоги, отмены режима тревог
@LPRalarm · 155,459
3 posts
Белгородская область оповещения, тревоги
@Belgorod_Lpr1 · 255
2 posts
Брянская область оповещения,тревоги
@Brynsk_Lpr1 · 232
2 posts
Республика Крым оповещения, тревоги
@Crime_Lpr1 · 636
2 posts
Херсонская область РФ оповещения, тревоги
@Kherson_Lpr1 · 91
2 posts
Краснодарский край оповещения,тревоги.
@Krasnodar_Lpr1 · 449
2 posts
Курская область оповещения и тревоги.
@Kursk_Lpr1 · 57
2 posts
Луганская Донецкая Народная Республика оповещения, тревоги
@LDPR_Lpr1 · 215
2 posts
Lpr 1
@lpr1_treugolnik · 933,015
2 posts
Орловская область оповещения, тревоги.
@Orlov_Lpr1 · 35
2 posts
Ростовская область тревоги, оповещения.
@Rostov_Lpr1 · 249
2 posts
LPR 1 Оповещения
@treugolnik_lpr1_lpr1 · 170
2 posts
Воронежская область, оповещения,тревоги.
@Voronezh_lpr1 · 64
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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Республика Крым, Севастополь Оповещения, тревоги” (@lpr1_Crimea_Alarm), 196,890 subscribers as measured 18 September 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.