Channel
@barakholka48
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
8,356subscribers
-35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001631688482 |
|---|---|
| Type | Channel |
| Username | @barakholka48 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/barakholka48 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:03 | 8,356 | -10 |
| 10 Aug 2026, 13:03 | 8,366 | -21 |
| 7 Aug 2026, 22:10 | 8,387 | -4 |
| 7 Aug 2026, 12:32 | 8,391 | no change |
| 7 Aug 2026, 12:20 | 8,391 | first reading |
26 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 12 pagesof Telegram’s post history, 20 posts per page.
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 12 August 2026 |
|---|---|
| Posts held | 26 (31 July 2026 – 12 August 2026) |
| Views total | 17,045 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:28 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.
Measured directly from 7 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.
Губернатор о бензине в регионе: «Ситуация с бензином напряженная. В ближайшую неделю-две серьёзного улучшения ожидать не стоит. На сутки региону отводится определённый объем топлива. Он заканчивается — ждём следующей поставки. Поэтому и режим «чёт-нечёт» сейчас ситуацию не изменит. Если можете сократить поездки – сократите. Если можете не доливать 10 литров до полного бака — человек, который приедет на заправку уж…
Необычный голос маленькой полярной совы попал на видео в Липецком зоопарке
Двое молодых людей попытались переплыть реку Воронеж в Липецке и едва не попали в беду. Парни отправились вплавь со стороны набережной, но в какой-то момент поняли, что не рассчитали свои силы и самостоятельно добраться до берега не смогут. На помощь пришли спасатели.
Что по пробкам у АЗС?
❗️ВНИМАНИЕ, ТРЕВОГА❗️ По всем регионам России производят массивные атаки. Российские ПВО за сутки сбивают ТЮСЯЧИ дронов. Всем настоятельно рекомендуем следить за ситуацией в специальных каналах вашего города! КАНАЛЫ РАБОТАЮТ ДАЖЕ БЕЗ МОБИЛЬНОЙ СВЯЗИ. Убедительная просьба, найти свой город и подписаться: Москва 24/7 Питер 24/7 Абакан 24/7 Архангельск 24/7 Астрахань 24/7 Балашиха 24/7 Барнаул 24/7 Благовещенск 24/7…
Мэр Михаил Щербаков: волонтёры вернутся на заправки Липецка. «Принял решение вновь вывести волонтёров на заправки. Они будут помогать там, где сейчас особенно большая нагрузка, и регулировать движение автомобилей. Мы уже проходили через такую ситуацию и знаем, что эта помощь действительно работает. Хочу попросить автомобилистов о простом – давайте с пониманием относиться друг к другу. Если у автомобиля топливный бак…
Труп 71-летней женщины нашли в болоте на окраине села Гудово Добровского округа. Обстоятельства ее гибели еще устанавливаются.
🚲 В Липецке столкнулись самокатчик и электровелосипедист. ДТП произошло на улице Яна Берзина. В результате столкновения водитель самоката получил травмы. Его доставили в больницу. Обстоятельства аварии и состояние пострадавшего уточняются.
Два человека погибли в серьёзном ДТП под Липецком. Авария произошла на 32-м километре трассы А-133. Столкнулись Renault и Mercedes. Водитель и пассажир Renault погибли на месте. Ещё несколько человек получили травмы и были доставлены в больницу. Среди пострадавших есть дети. На месте работали сотрудники полиции и следователи. Причины и обстоятельства аварии устанавливаются.
Трактор наехал на 53-летнего мужчину в селе Завальное Усманского округа От многочисленных травм головы, причиненных навесной косилкой, пострадавший скончался на месте. Его тело обнаружили сельчане. Трактором управлял 70-летний пенсионер, который скрылся с места преступления. Проводятся экспертизы и следственные действия.
Автомат Калашникова появится на стене дома в Ельце
В Ссёлках в колодце нашли тело 57-летнего мужчины Сейчас сотрудники четвёртого отдела полиции устанавливают причины и обстоятельства произошедшего. По предварительным данным, признаков криминального характера в смерти мужчины не обнаружено.
Showing the 12 most recent of 26 posts we hold for @barakholka48. 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 — 1,370,007 of 1,480,688entries 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.
Named by 1 registered channel — 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.
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.
@barakholka48 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.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Новости Липецка” (@barakholka48), 8,356 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/barakholka48.
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.