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

Channel
ЧП ВОРОНЕЖ
@chp_vrn36
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
10,293subscribers
-180 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 | -1001351504388 |
|---|---|
| Type | Channel |
| Username | @chp_vrn36 |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/chp_vrn36 |
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 86% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 23:48 | 10,293 | -1 |
| 5 Nov 2026, 00:08 | 10,294 | -5 |
| 4 Nov 2026, 00:17 | 10,299 | -1 |
| 3 Nov 2026, 03:41 | 10,300 | -2 |
| 2 Nov 2026, 02:49 | 10,302 | -5 |
| 1 Nov 2026, 01:47 | 10,307 | -1 |
| 28 Oct 2026, 23:41 | 10,308 | -3 |
| 28 Oct 2026, 01:56 | 10,311 | -2 |
| 27 Oct 2026, 01:40 | 10,313 | +24 |
| 24 Oct 2026, 23:26 | 10,289 | -5 |
| 22 Oct 2026, 22:58 | 10,294 | +1 |
| 22 Oct 2026, 00:15 | 10,293 | -8 |
| 20 Oct 2026, 19:19 | 10,301 | -1 |
| 19 Oct 2026, 22:00 | 10,302 | -1 |
| 18 Oct 2026, 20:29 | 10,303 | -7 |
| 17 Oct 2026, 17:38 | 10,310 | -8 |
| 16 Oct 2026, 00:06 | 10,318 | -5 |
| 14 Oct 2026, 21:56 | 10,323 | +2 |
| 13 Oct 2026, 16:31 | 10,321 | -12 |
| 9 Oct 2026, 23:15 | 10,333 | first reading |
Engagement
493 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 45 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.81%
- avg views ÷ 10,293 subscribers
- Avg views / post
- 186
- 90 posts measured
- Reaction rate
- 0.222%
- reactions ÷ views · ER floor
- Posts in window
- 90
- of 493 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. It is computed over the 2 of 90 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 493 (6 August 2026 – 5 November 2026) |
| Views total | 16,729 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 20:48 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
- Video runtime
- 2m 59s
- Average length
- 18s
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.
Reaction mix
19 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 26.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 26.3% | |
| 👍 | 5 | 26.3% | |
| 🙏 | 3 | 15.8% | |
| 🤨 | 3 | 15.8% | |
| 🤡 | 2 | 10.5% | |
| ❤🔥 | 1 | 5.26% |
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 22 of the 493 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 493 most recent posts we hold, published 6 August 2026 to 5 November 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.
Advertising
- Ad load
- 0.203%
- 1 of 493 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 401
- over 1 measured post
- Median views · rest
- 221
- over 492 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFJ4UbPw | 1 | 14 August 2026 | 14 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 493 most recent posts we hold, published 6 August 2026 to 5 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 90 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).
Россошанский район Воронежская область Опасность по БПЛА @chp_vrn36
Острогожский район Лискинский район Нововоронеж и близлежащие Воронеж и близлежащие Воронежская область Опасность по БПЛА @chp_vrn36
Воронежская область Опасность по БПЛА @chp_vrn36
На данный момент по обстановке тихо При возникновении непосредственной угрозы оповестим немедленно. Берегите себя и своих близких! @chp_vrn36
За ночь средствами ПВО было уничтожено 496 БПЛА над Астраханской, Белгородской, Брянской, Волгоградской, Воронежской, Курской, Нижегородской, Орловской, Ростовской, Рязанской, Тамбовской, Тульской областей, Московского региона, Краснодарского края, Республики Крым и над акваториями Азовского и Черного морей. @chp_vrn36
Воронежская область Отбой опасности по БПЛА @chp_vrn36
Воронеж Каширский район Хохольский район Рамонский район Новоусманский район Семилукский район Воронежская область Отбой опасности по БПЛА На территории региона опасность сохраняется @chp_vrn36
Каменский район Павловский район Бутурлиновский район Борисоглебский район Калачеевский район Россошанский район Кантемировский район Богучарский район Воронежская область Отбой опасности по БПЛА На территории региона опасность сохраняется @chp_vrn36
Нововоронежский район Лискинский район Острогожский район Воронежская область Отбой опасности по БПЛА На территории региона опасность сохраняется @chp_vrn36
Бутурлиновский район Воронежская область Работа ПВО по БПЛА @chp_vrn36
Воронежская область По ранее указанным районам Продолжаются фиксации БПЛА @chp_vrn36
Showing the 12 most recent of 493 posts we hold for @chp_vrn36. 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 recorded as deleted after publishing
We recorded 1 post on @chp_vrn36 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 24 August 2026
- Most recent seen missing
- 24 August 2026
- Median time before seen missing
- 12 hours
- Seen missing in the last 30 days
- 0
Mentions
Named by 3 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.
Names
Channels on the register whose handles appear in this channel's posts.
@tonplay · 382,2363 postsUNSTOP VPN
@unstop_vpn_bot · 20,1882 postsSkiskimasssk
@abknlive · 71 post🚧ДТП АРХАНГЕЛЬСКА🚧
@arhangelsklive · 141 postAstrakhan.live Лайк
@Astrakhanlive · 111 postБарнаул лайв
@barnaullive · 1101 postИркутск live
@irkutsklive · 261 postКалининград | все обо всем 🌆
@kaliningradLive · 621 postKazan
@kazanlive · 191 postКУРСК (БЕЗ ОПОВЕЩЕНИЙ) Школьная жизнь
@kurskLIVE · 391 postЛипецк LIVE
@lipetsklive · 1,4911 postМагнитогорск лайв
@magnitogorsklive · 91 postНижний Новгород лайв
@nizhnynovlive · 241 postНовоалтайск Live ДТП и ЧС
@novoaltaisklive · 181 postНВКЗ
@novokuznetsklive · 111 postНОВОРОССИЯ
@novorussialive · 271 postNskLive
@NovosibirskLIVE · 161 postПермь LIVE
@permlive · 121 postПетрозаводск Live
@petrozavodsklive · 2611 postПовестка правды
@povestka_pravdy · 3301 postАндрей Савельев
@razvitie · 7361 postSAHALIN LIVE
@SAHALINLIVE · 101 postПыльный Сратов
@saratovlive · 2,1001 postСтаврополь LIVE
@Stavropollive · 601 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@chp_vrn36 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
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.
@tre_voronezh · 51,847
Telegram ranks this channel #27 of 48 here — alongside 47 others — read 25 August 2026
@vrinc · 64,321
Telegram ranks this channel #31 of 62 here — alongside 61 others — read 21 August 2026
@vrn36v · 70,228
Telegram ranks this channel #33 of 64 here — alongside 63 others — read 20 August 2026
@typicalvoronezh · 374,092
Telegram ranks this channel #34 of 66 here — alongside 65 others — read 10 August 2026
@zhest_voronezh_136 · 61,957
Telegram ranks this channel #36 of 66 here — alongside 65 others — read 22 August 2026
@bloknot_vrn · 64,717
Telegram ranks this channel #36 of 88 here — alongside 87 others — read 21 August 2026
@smi_voronezh · 208,729
Telegram ranks this channel #36 of 61 here — alongside 60 others — read 11 August 2026
@vrn01 · 72,867
Telegram ranks this channel #37 of 84 here — alongside 83 others — read 19 August 2026
@voronezh_r36 · 73,412
Telegram ranks this channel #39 of 80 here — alongside 79 others — read 19 August 2026
This channel appears in 9 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“ЧП ВОРОНЕЖ” (@chp_vrn36), 10,293 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/chp_vrn36.
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.