Telegram RegisterThe public register of Telegram
Telegram profile photo for Липецк · Важно и Срочно

Channel

Липецк · Важно и Срочно

@chp48dtp

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

14,117subscribers

-233 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-1001238019985
TypeChannel
Username@chp48dtp
DescriptionКоротко о главном в Липецке. Все ключевые события, происшествия, сводки в одной ленте По рекламе: @chp48dtpbot Реклама через биржу: https://telega.in/c/chp48dtp
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/chp48dtp

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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

14,11714,35014,233.57 August 2026 — 14,350 subscribers7 August 2026 — 14,348 subscribers8 August 2026 — 14,347 subscribers10 August 2026 — 14,346 subscribers11 August 2026 — 14,345 subscribers11 August 2026 — 14,339 subscribers12 August 2026 — 14,346 subscribers14 August 2026 — 14,344 subscribers15 August 2026 — 14,338 subscribers17 August 2026 — 14,335 subscribers18 August 2026 — 14,338 subscribers19 August 2026 — 14,335 subscribers20 August 2026 — 14,334 subscribers21 August 2026 — 14,329 subscribers23 August 2026 — 14,325 subscribers24 August 2026 — 14,322 subscribers25 August 2026 — 14,319 subscribers26 August 2026 — 14,321 subscribers27 August 2026 — 14,319 subscribers28 August 2026 — 14,320 subscribers29 August 2026 — 14,316 subscribers30 August 2026 — 14,298 subscribers31 August 2026 — 14,295 subscribers1 September 2026 — 14,290 subscribers2 September 2026 — 14,291 subscribers6 September 2026 — 14,289 subscribers9 September 2026 — 14,282 subscribers11 September 2026 — 14,280 subscribers13 September 2026 — 14,268 subscribers15 September 2026 — 14,267 subscribers17 September 2026 — 14,256 subscribers26 September 2026 — 14,218 subscribers4 October 2026 — 14,188 subscribers9 October 2026 — 14,178 subscribers13 October 2026 — 14,163 subscribers14 October 2026 — 14,158 subscribers15 October 2026 — 14,159 subscribers16 October 2026 — 14,147 subscribers18 October 2026 — 14,146 subscribers19 October 2026 — 14,147 subscribers20 October 2026 — 14,143 subscribers21 October 2026 — 14,140 subscribers22 October 2026 — 14,131 subscribers23 October 2026 — 14,127 subscribers24 October 2026 — 14,128 subscribers25 October 2026 — 14,132 subscribers26 October 2026 — 14,134 subscribers27 October 2026 — 14,131 subscribers28 October 2026 — 14,143 subscribers29 October 2026 — 14,141 subscribers30 October 2026 — 14,144 subscribers31 October 2026 — 14,142 subscribers1 November 2026 — 14,141 subscribers2 November 2026 — 14,140 subscribers3 November 2026 — 14,138 subscribers4 November 2026 — 14,128 subscribers7 November 2026 — 14,129 subscribers8 November 2026 — 14,125 subscribers10 November 2026 — 14,124 subscribers11 November 2026 — 14,117 subscribers7 August 202611 November 2026
60 measurements spanning 96 days, net -233. 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 14,082–14,385 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
11 Nov 2026, 23:1614,117-7
10 Nov 2026, 00:0614,124-1
8 Nov 2026, 13:4514,125-4
7 Nov 2026, 04:0614,129+1
4 Nov 2026, 01:4714,128-10
3 Nov 2026, 02:4814,138-2
2 Nov 2026, 03:2914,140-1
1 Nov 2026, 06:1114,141-1
31 Oct 2026, 04:1014,142-2
30 Oct 2026, 05:5914,144+3
29 Oct 2026, 08:4914,141-2
28 Oct 2026, 09:3114,143+12
27 Oct 2026, 12:3614,131-3
26 Oct 2026, 13:2714,134+2
25 Oct 2026, 12:4614,132+4
24 Oct 2026, 14:3014,128+1
23 Oct 2026, 13:1014,127-4
22 Oct 2026, 15:3614,131-9
21 Oct 2026, 11:0614,140-3
20 Oct 2026, 11:1914,143first reading

Engagement

538 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 75 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.25%
avg views ÷ 14,117 subscribers
Avg views / post
459
183 posts measured
Reaction rate
0.545%
reactions ÷ views · ER floor
Posts in window
183
of 538 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 88 of 183 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held538 (6 August 2026 – 14 November 2026)
Views total84,084
Reactions total227
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 20:53 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
≈37,900
Videos
≈13,300
Links
≈8,190

Lifetime counters from Telegram’s own channel header, read 14 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
30m 59s
Average length
39s

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

572 reactions across 237 posts, in 16 distinct kinds. The most used accounts for 22.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡12622.0%
❤11119.4%
👍8414.7%
🙏7813.6%
🤬518.92%
🔥498.57%
🤔264.55%
💩223.85%
🤯71.22%
👀40.699%
🕊40.699%
😎30.524%
⚡20.35%
👌20.35%
👏20.35%
💯10.175%

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 245 of the 538 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 572 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 538 most recent posts we hold, published 6 August 2026 to 14 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
2.23%
12 of 538 posts carry an ad marker
Regulatory tokens
12
posts carrying an erid · 6 distinct tokens
Median views · ads
381
over 12 measured posts
Median views · rest
430
over 526 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2Vtzqx8CnJo66 August 202630 August 2026
2VtzquyJjQa29 November 202613 November 2026
2Vtzqw9rQD8110 August 202610 August 2026
2VtzqwH9uGo126 August 202626 August 2026
2VtzqwZ6Y9q125 August 202625 August 2026
2VtzqwZ6apN110 November 202610 November 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 538 most recent posts we hold, published 6 August 2026 to 14 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: 2 of 183 posts held from the last 30 days (1.09%) 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).

14 Nov 2026, 20:45 UTC163 views12 reactionsread 14 November 2026

⚡️ Громко! Напомним, что в настоящий момент действует красный уровень опасности Вы слышали хлопок? 👍 — Да / 🔥 — Нет

👍10🔥2

14 Nov 2026, 19:44 UTC220 views2 reactionsread 14 November 2026

🚨 Сирена. Просьба сохранять спокойствие У вас слышно? 👍 — да / 🔥 — нет

👍2

14 Nov 2026, 17:53 UTC399 viewsread 14 November 2026

⚡️ Над Липецкой областью и другими регионами России сбили 39 беспилотников По данным Минобороны РФ, 14 ноября с 8:00 до 20:00 силы ПВО перехватили и уничтожили 39 украинских БПЛА. Беспилотники были сбиты над Липецкой, Белгородской, Брянской, Воронежской, Калужской, Курской, Орловской и Рязанской областями, Московским регионом и Крымом. Сколько именно беспилотников уничтожили над Липецкой областью, в сводке не уточ…

14 Nov 2026, 16:37 UTC337 views2 reactionsread 14 November 2026
Video

🚗 В Липецке парень забрался на капот и крышу чужой машины На улице Белянского камера видеонаблюдения сняла молодого человека, который решил прогуляться по припаркованному возле подъезда автомобилю. Сначала парень забрался на капот, а затем перебрался на крышу машины. Как сообщает GOROD48, владелец автомобиля заявил о повреждениях и теперь разыскивает незнакомца через соцсети. Мужчина предлагает ему самостоятельно…

🤬2

14 Nov 2026, 14:03 UTC349 views1 reactionsread 14 November 2026
Photo

🌿 Шесть кустов конопли нашли во дворе жителя Липецкого округа 42-летний мужчина выращивал запрещённые растения возле своего дома, а в гараже хранил готовый к употреблению наркотик. Как сообщили в региональном УМВД, во время обыска полицейские обнаружили шесть кустов конопли. Масса изъятого растения превысила 1,9 килограмма. Кроме того, в гараже нашли пластиковую банку с 13,1 грамма наркотического средства. Мужчина…

❤1

14 Nov 2026, 12:23 UTC353 views1 reactionsread 14 November 2026
Photo

🚧 На Интернациональной три месяца не закапывают яму у подъезда Жители дома №56 в Липецке жалуются на раскопанную территорию возле второго подъезда. По их словам, коммунальные работы начались ещё в августе, но последствия аварии до сих пор не устранены. С 11 августа жильцы оставались без горячей воды. Спустя три месяца её наконец вернули, однако возле дома так и осталась большая яма с открытыми трубами. Особое бесп…

❤1

14 Nov 2026, 10:25 UTC348 viewsread 14 November 2026
Photo

🎬 Приглашение в кино обошлось липчанину в 102 тысячи рублей 29-летний житель Липецка познакомился с девушкой на сайте знакомств. Во время переписки она предложила сходить в кино и прислала ссылку для покупки билетов в частный кинотеатр. Мужчина заплатил 24 тысячи рублей, но вскоре незнакомка сообщила, что не сможет прийти на свидание. Она посоветовала обратиться в техподдержку для возврата денег. Как сообщает GORO…

14 Nov 2026, 08:20 UTC397 views2 reactionsread 14 November 2026
Video

🩹 В Липецке блогер «полечил» подземный переход пластырями Необычный способ привлечь внимание к состоянию подземного перехода у Центрального рынка придумал липецкий блогер a_mrtslv. Молодой человек снял видео, на котором заклеивает повреждённые участки перехода обычными медицинскими пластырями. Ролик он подписал короткой фразой «Переходик, не болей». Таким образом блогер решил обратить внимание на проблемы благоус…

👍1💩1

14 Nov 2026, 07:05 UTC209 viewsread 14 November 2026
Video

🚨 После жалоб на нападения в Новолипецке 11-летнего школьника поставили на учёт Родители четверых подростков рассказали, что их детей с прошлой зимы преследовала компания из 10–15 сверстников. По словам взрослых, школьников били, требовали у них деньги и даже угрожали ножом. Как сообщает GOROD48, после очередного конфликта родители обратились в полицию, а затем история получила огласку благодаря общественнику Андре…

Showing the 12 most recent of 538 posts we hold for @chp48dtp. 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 2 posts on @chp48dtp 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
12 November 2026
Most recent seen missing
12 November 2026
Median time before seen missing
30 hours
Seen missing in the last 30 days
2

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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.

Инцидент Липецк
@incidentlipetsk · 23,134
Telegram ranks this channel #13 of 29 here — alongside 28 others — read 18 September 2026
Игорь Артамонов
@igor_artamonov48 · 184,352
Telegram ranks this channel #14 of 30 here — alongside 29 others — read 11 August 2026
Липецк №1
@lipetsk001 · 35,938
Telegram ranks this channel #15 of 36 here — alongside 35 others — read 1 September 2026
Липецк ЧП 48 — Новости
@myregion48 · 37,677
Telegram ranks this channel #15 of 40 here — alongside 39 others — read 31 August 2026
Липецк с огоньком
@lipetsktop1 · 50,184
Telegram ranks this channel #16 of 42 here — alongside 41 others — read 25 August 2026
Липецкач • Новости Липецка
@lipetska4 · 65,688
Telegram ranks this channel #16 of 26 here — alongside 25 others — read 22 August 2026
Gorod48 | Город48
@gorod48ru · 59,257
Telegram ranks this channel #17 of 50 here — alongside 49 others — read 22 August 2026
Липецкое Время Z
@lipetsktimez · 19,038
Telegram ranks this channel #18 of 56 here — alongside 55 others — read 3 October 2026
ЛипецкМедиа
@lipetskmediaru · 21,665
Telegram ranks this channel #19 of 44 here — alongside 43 others — read 22 September 2026
Жесть Липецк
@zhest_lipetsk_48 · 23,443
Telegram ranks this channel #19 of 27 here — alongside 26 others — read 18 September 2026
Новости Липецка и Области
@lipetsk_smi · 112,384
Telegram ranks this channel #19 of 27 here — alongside 26 others — read 14 August 2026
Липецкая область
@lipobl · 24,366
Telegram ranks this channel #21 of 68 here — alongside 67 others — read 15 September 2026
Весь Липецк
@Lipetsk7 · 82,796
Telegram ranks this channel #22 of 40 here — alongside 39 others — read 9 September 2026
Радар.ру • Питер По всей России | БПЛА • Приграничье
@radar_ru_russiaa · 113,322
Telegram ranks this channel #33 of 33 here — alongside 32 others — read 14 August 2026
Липтаун
@liptown · 30,965
Telegram ranks this channel #55 of 96 here — alongside 95 others — read 5 September 2026
Чернозем
@blackzemye · 18,701
Telegram ranks this channel #60 of 92 here — alongside 91 others — read 4 October 2026
Вакансии Липецк
@rabota_v_lipetskeu · 28,952
Telegram ranks this channel #69 of 89 here — alongside 88 others — read 6 September 2026

This channel appears in 17 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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Липецк · Важно и Срочно” (@chp48dtp), 14,117 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/chp48dtp.

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.