Telegram RegisterThe public register of Telegram
Telegram profile photo for 112 Официальный канал оповещений Липецкой области

Channel

112 Официальный канал оповещений Липецкой области

@opas22201

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

395subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003480830049
TypeChannel
Username@opas22201
CreatedBetween 1 November 2025 and 29 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/opas22201

Topic

Local community — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

3953993977 August 2026 — 399 subscribers8 August 2026 — 399 subscribers15 August 2026 — 398 subscribers24 August 2026 — 395 subscribers9 September 2026 — 399 subscribers3 October 2026 — 396 subscribers12 October 2026 — 395 subscribers7 August 202612 October 2026
7 measurements spanning 66 days, net -4. 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 394–400 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 16:11395-1
3 Oct 2026, 02:16396-3
9 Sept 2026, 07:36399+4
24 Aug 2026, 08:03395-3
15 Aug 2026, 19:28398-1
8 Aug 2026, 05:49399no change
7 Aug 2026, 17:49399first reading

Engagement

20 posts held, back to 29 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

69 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 59.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4159.4%
👀913.0%
👍57.25%
🔥45.80%
🎄22.90%
👏22.90%
🤣22.90%
🥰22.90%
😁11.45%
🫡11.45%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 16 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 69 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 29 November 2025 to 2 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Aug 2026, 09:53 UTCviews —

112 Официальный канал оповещений Липецкой области pinned «Уважаемые жители Липецкой области! В связи с тем, что данный канал был утерян службами, был создан новый, который действует уже несколько месяцев. 112 Оповещения Липецкой области - https://t.me/lipsignals»

2 Aug 2026, 09:53 UTC138 viewsread 8 August 2026

Уважаемые жители Липецкой области! В связи с тем, что данный канал был утерян службами, был создан новый, который действует уже несколько месяцев. 112 Оповещения Липецкой области - https://t.me/lipsignals

31 Jul 2026, 13:19 UTCviews —

112 Официальный канал оповещений Липецкой области pinned Deleted message

30 May 2026, 00:31 UTCviews —

112 Официальный канал оповещений Липецкой области pinned Deleted message

2 Dec 2025, 06:37 UTC≈3,920 views37 reactionsread 8 August 2026

🟡 Объявлен желтый уровень "Воздушная опасность" по Липецкой области.

❤18👀9👍4🔥2🥰2👏1😁1

2 Dec 2025, 03:00 UTC≈3,690 views7 reactionsread 8 August 2026

🟢Отбой желтого уровня "Воздушной опасности" для Липецкой области.

❤4👍1👏1🔥1

2 Dec 2025, 02:30 UTC≈3,580 views2 reactionsread 8 August 2026

🟡Отбой «Красного уровня-Угроза атаки БПЛА». Сохраняется «Желтый уровень-Воздушная опасность» на территории Липецкой области.

❤2

1 Dec 2025, 22:24 UTC≈3,460 views3 reactionsread 8 August 2026

🔴Объявлен красный уровень "Угроза атаки БПЛА" для Липецкой области.

❤1🔥1🤣1

1 Dec 2025, 21:48 UTC≈3,320 views1 reactionsread 8 August 2026

🔴Объявлен красный уровень "Угроза атаки БПЛА" для г. Елец, Елецкого МО, Долгоруковского МО, Становлянского МО, Измалковского МО.

❤1

1 Dec 2025, 21:18 UTC≈2,980 views4 reactionsread 8 August 2026

🟡 Объявлен желтый уровень "Воздушная опасность" по Липецкой области.

❤4

1 Dec 2025, 02:21 UTC≈2,650 views1 reactionsread 8 August 2026

🟢Отбой желтого уровня "Воздушной опасности" для Липецкой области.

❤1

30 Nov 2025, 23:56 UTC≈2,430 views1 reactionsread 8 August 2026

🟡Отбой «Красного уровня-Угроза атаки БПЛА». по ранее введенным районам. Сохраняется «Желтый уровень-Воздушная опасность» на территории Липецкой области

❤1

Showing the 12 most recent of 20 posts we hold for @opas22201. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“112 Официальный канал оповещений Липецкой области” (@opas22201), 395 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/opas22201.

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.