Публикуем кадры работы оперативных служб на местах сегодняшней ночной вражеской атаки на регион В Орле под удар попали помещения предприятий.

Channel
Новости Орел
@barakholka57
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
11,716subscribers
-310 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001417925274 |
|---|---|
| Type | Channel |
| Username | @barakholka57 |
| Description | Лента всех событий: новости, происшествия, ЧП, ДТП По всем вопросам: BROKER6.t.me наша сетка: @barakholkaTG |
| Created | 7 February 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/barakholka57 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 7 Nov 2026, 08:17 | 11,716 | -5 |
| 6 Nov 2026, 10:37 | 11,721 | -3 |
| 5 Nov 2026, 09:46 | 11,724 | -4 |
| 4 Nov 2026, 06:36 | 11,728 | +1 |
| 3 Nov 2026, 06:29 | 11,727 | -10 |
| 2 Nov 2026, 03:09 | 11,737 | -4 |
| 1 Nov 2026, 02:18 | 11,741 | -2 |
| 31 Oct 2026, 03:10 | 11,743 | +1 |
| 29 Oct 2026, 01:08 | 11,742 | -1 |
| 26 Oct 2026, 20:07 | 11,743 | -2 |
| 25 Oct 2026, 21:56 | 11,745 | -2 |
| 24 Oct 2026, 20:37 | 11,747 | +11 |
| 23 Oct 2026, 23:50 | 11,736 | +20 |
| 22 Oct 2026, 20:57 | 11,716 | -4 |
| 21 Oct 2026, 18:41 | 11,720 | -1 |
| 20 Oct 2026, 15:10 | 11,721 | -6 |
| 19 Oct 2026, 14:30 | 11,727 | -3 |
| 18 Oct 2026, 17:49 | 11,730 | -2 |
| 17 Oct 2026, 15:16 | 11,732 | -3 |
| 16 Oct 2026, 17:20 | 11,735 | first reading |
Engagement
113 posts held, back to 31 July 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 59 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.1%
- avg views ÷ 11,716 subscribers
- Avg views / post
- 1,180
- 29 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 29
- of 113 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 7 November 2026 |
|---|---|
| Posts held | 113 (31 July 2026 – 7 November 2026) |
| Views total | 34,352 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 20:10 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
- ≈4,690
- Videos
- ≈2,020
- Links
- ≈444
Lifetime counters from Telegram’s own channel header, read 7 November 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
- 15m 50s
- Average length
- 56s
Measured directly from 17 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
Telegram’s own ‘edited’ marker: 7 of 29 posts held from the last 30 days (24.1%) 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).
Стало известно, какими ракетами атаковали Орловщину По официальной информации Минобороны РФ, удар по региону был нанесен крылатыми ракетами «Нептун». Напомним, город уже подвергался обстрелам с применением этого типа вооружения — ранее атаки также были направлены на объекты коммунальной инфраструктуры.
Силами ПВО над территорией региона уничтожены 3 ракеты и 2 БПЛА. В результате атаки частично повреждены склады и производственные площадки коммерческих предприятий в областном центре, а также 3 частных дома в муниципалитетах области. Пострадавших нет. Все очаги возгорания ликвидированы, на объектах работают оперативные службы и правоохранительные органы. Ведутся работы по устранению последствий.
В Орловской области пьяного электросамокатчика оштрафовали на 2 тысячи за неповиновение полиции Выяснилось, что мужчина, будучи сильно пьяным, ехал на электросамокате по центру проезжей части, виляя из стороны в сторону. Полицейские предложили мужчине пройти в служебный автомобиль. Однако он грубо отказался, размахивал руками и пытался уйти
В Орле ловили пьяных подростков и хулиганов Полицейские вместе с отрядом «Сармат» проверили места массового отдыха и пресекли девять правонарушений. Составили пять протоколов за распитие алкоголя в запрещённых местах и один – на родителя пьяного несовершеннолетнего. ⠀
В Орле введут запрет на продажу табака возле школ 🚬 В радиусе 100 метров от учебных заведений нельзя будет продавать сигареты, вейпы и кальяны.
В Орловской области задержали пятерых за публикацию видео удара по заводу Кадры попали на украинские ресурсы, используемые в информационной войне против России. К нарушителям применят меры вплоть до уголовной ответственности. Один из задержанных услышал взрыв, снял поражённый объект из окна и выложил видео в соцсетях в формате «сторис». Позже он удалил запись, пожалел о поступке и пообещал так больше не делать.
Блогер сняла обзор на Мценск 👀 Девушка отметила продуманность местных жителей и показала некоторые легендарные локации. В комментариях горожане поддержали автора ролика и подтвердили, что город «по-своему прекрасен».
В Орле начали привлекать к ответственности авторов роликов с последствиями атак ВСУ Административное дело завели на орловчанина, который выложил в Сеть кадры атаки на завод в Орле. Парень снял ролик из окна своей квартиры и выложил контент в открытый доступ. Теперь орловчанину предстоит оплатить штраф.
В МЧС рассказали подробности о ликвидации пожара на территории орловского маслозавода Сообщение о возгорании поступило в 22:27. Пламя было видно издалека, существовала угроза перехода огня на соседние здания. На месте работали 43 сотрудника и 12 единиц спецтехники. Распространение огня остановили. По предварительным данным, пострадавших нет.
Камеры выдали орловчанина, который украл три велосипеда В Железнодорожном районе из подъезда пропали два взрослых и один подростковый велосипеды. Записи с камер помогли полиции выйти на 48-летнего мужчину Два велосипеда нашли у его знакомого, поиски третьего продолжаются. Возбуждено уголовное дело
Пять комплексов фото-видеофиксации в новых антивандальных ящиках установили на дорогах Орловской области 📸 Вот адреса: - автодорога Р-92 Калуга – Перемышль – Белёв – Орел, 198 км (Орловский муниципальный округ); - автодорога Р-120 Орел – Брянск – Смоленск – Граница с Республикой Беларусь, 16 км (Урицкий район); - автодорога Р-120 Орел – Брянск – Смоленск – Граница с Республикой Беларусь, 10 км (Орловский муниципа…
Showing the 12 most recent of 113 posts we hold for @barakholka57. 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 3 posts on @barakholka57 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
- 20 August 2026
- Most recent seen missing
- 27 August 2026
- Median time before seen missing
- 3 days
- Seen missing in the last 30 days
- 0
Mentions
Named by 2 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.
@abknlive · 75 posts🚧ДТП АРХАНГЕЛЬСКА🚧
@arhangelsklive · 145 postsAstrakhan.live Лайк
@Astrakhanlive · 115 postsБарнаул лайв
@barnaullive · 1105 postsХАБАРОВСКlive
@habarovsklive · 145 postsИркутск live
@irkutsklive · 265 postsКалининград | все обо всем 🌆
@kaliningradLive · 625 postsKazan
@kazanlive · 195 postsКУРСК (БЕЗ ОПОВЕЩЕНИЙ) Школьная жизнь
@kurskLIVE · 395 postsЛипецк LIVE
@lipetsklive · 1,4935 postsМагнитогорск лайв
@magnitogorsklive · 95 postsНижний Новгород лайв
@nizhnynovlive · 245 postsНовоалтайск Live ДТП и ЧС
@novoaltaisklive · 185 postsНВКЗ
@novokuznetsklive · 115 postsНОВОРОССИЯ
@novorussialive · 275 postsNskLive
@NovosibirskLIVE · 165 postsПермь LIVE
@permlive · 125 postsПетрозаводск Live
@petrozavodsklive · 2615 postsАндрей Савельев
@razvitie · 7375 postsSAHALIN LIVE
@SAHALINLIVE · 105 postsПыльный Сратов
@saratovlive · 2,0985 postsСтаврополь LIVE
@Stavropollive · 605 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.
Handles this channel named that no longer answer
- Dead references
- 38
- 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
- 38
- vacant every time we have ever looked
@barakholka57 named 38 handles 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 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 2026
named in 8 posts, 8 August 2026 – 6 November 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.
@zhest_orel_57 · 32,315
Telegram ranks this channel #9 of 41 here — alongside 40 others — read 5 September 2026
@orel_vkurse · 46,330
Telegram ranks this channel #9 of 20 here — alongside 19 others — read 27 August 2026
@gorodorel57 · 103,681
Telegram ranks this channel #10 of 38 here — alongside 37 others — read 19 August 2026
@orel_smi · 76,746
Telegram ranks this channel #10 of 32 here — alongside 31 others — read 19 August 2026
@orelsvodka · 19,838
Telegram ranks this channel #12 of 36 here — alongside 35 others — read 30 September 2026
@reg57orel · 22,987
Telegram ranks this channel #14 of 40 here — alongside 39 others — read 19 September 2026
@Orel_nov · 22,292
Telegram ranks this channel #15 of 74 here — alongside 73 others — read 25 September 2026
@orel_tut · 26,178
Telegram ranks this channel #15 of 77 here — alongside 76 others — read 25 September 2026
@Orel_podslushal · 36,562
Telegram ranks this channel #24 of 60 here — alongside 59 others — read 25 September 2026
@Klychkov_Andrey · 66,506
Telegram ranks this channel #30 of 58 here — alongside 57 others — read 20 August 2026
@vzor57 · 20,800
Telegram ranks this channel #55 of 93 here — alongside 92 others — read 25 September 2026
This channel appears in 11 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Новости Орел” (@barakholka57), 11,716 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/barakholka57.
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.