🟢🟢🟢🟢🟢🟢Отбой «Ракетная опасность» по Липецкой области. 👉 Подписаться | Написать нам | Max
🙏7👎2🤣2🤬2

Channel
@lipetska4
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
65,673subscribers
+6,149 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001674168982 |
|---|---|
| Type | Channel |
| Username | @lipetska4 |
| Description | Лучший канал о Липецкой области. Много эксклюзива, быстрые новости! По вопросам рекламы, предложить новость или пожаловаться на участников наших чатов: @lipetska4bot |
| 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 | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/lipetska4 |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 7 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @lipetska4/35664 · this entry9 Aug 2026, 08:46 UTC | @ryazplus/70089 Aug 2026, 08:47 UTC | 1.00 | 72 seconds |
| @lipetska4/35982 · this entry22 Aug 2026, 12:44 UTC | @ryazplus/716022 Aug 2026, 13:53 UTC | 1.00 | 70 minutes |
| @lipetska4/36050 · this entry25 Aug 2026, 15:13 UTC | @ryazplus/719825 Aug 2026, 19:34 UTC | 1.00 | 4.3 hours |
| @lipetska4/36082 · this entry26 Aug 2026, 18:50 UTC | @ryazplus/721326 Aug 2026, 18:51 UTC | 1.00 | under a minute |
| @lipetska4/36157 · this entry30 Aug 2026, 09:00 UTC | @ryazplus/724530 Aug 2026, 10:18 UTC | 1.00 | 78 minutes |
| @lipetska4/36159 · this entry30 Aug 2026, 11:18 UTC | @ryazplus/724730 Aug 2026, 12:40 UTC | 1.00 | 82 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ryazplus | 63 (8/8 hand-verifiable sample passed) | 1.00 | 81 minutes | this entry (63–0) |
| @lipetsktop1 | 13 (8/8 hand-verifiable sample passed) | 0.96 | 70 minutes | @lipetsktop1 (8–5) |
| @msk_live | 7 (7/7 hand-verifiable sample passed) | 0.91 | 2.5 hours | @msk_live (7–0) |
| @live_piter | 7 (7/7 hand-verifiable sample passed) | 0.91 | 2.5 hours | @live_piter (7–0) |
| @yartop12 | 6 (6/6 hand-verifiable sample passed) | 0.97 | 71 minutes | @yartop12 (5–1) |
| @lipetsk_24 | 5 (5/5 hand-verifiable sample passed) | 0.90 | 21 hours | this entry (5–0) |
| @moscowplus | 5 (5/5 hand-verifiable sample passed) | 0.90 | 59 minutes | @moscowplus (5–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 32 of the 32 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 1,367 comparable posts for this entry, running 6 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @lipetska4 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 00:45 | 65,673 | -45 |
| 9 Nov 2026, 06:57 | 65,718 | -23 |
| 7 Nov 2026, 22:15 | 65,741 | -13 |
| 6 Nov 2026, 23:37 | 65,754 | -7 |
| 6 Nov 2026, 03:06 | 65,761 | -15 |
| 5 Nov 2026, 02:26 | 65,776 | -28 |
| 3 Nov 2026, 23:19 | 65,804 | +14 |
| 2 Nov 2026, 20:38 | 65,790 | +27 |
| 1 Nov 2026, 22:26 | 65,763 | +4 |
| 1 Nov 2026, 01:38 | 65,759 | +25 |
| 31 Oct 2026, 04:51 | 65,734 | -27 |
| 30 Oct 2026, 03:08 | 65,761 | -25 |
| 29 Oct 2026, 04:41 | 65,786 | +77 |
| 28 Oct 2026, 04:00 | 65,709 | +377 |
| 27 Oct 2026, 06:58 | 65,332 | +46 |
| 26 Oct 2026, 09:45 | 65,286 | +429 |
| 25 Oct 2026, 12:29 | 64,857 | +2,140 |
| 24 Oct 2026, 10:16 | 62,717 | +150 |
| 23 Oct 2026, 07:15 | 62,567 | +590 |
| 22 Oct 2026, 07:49 | 61,977 | first reading |
1,802 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 197 pages of 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 10 November 2026 |
|---|---|
| Posts held | 1,802 (6 August 2026 – 10 November 2026) |
| Views total | 4,570,308 |
| Reactions total | 41,193 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 02:08 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 96 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.
73,216 reactions across 1,000 posts, in 16 distinct kinds. The most used accounts for 19.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 14,151 | 19.3% | |
| 👍 | 9,767 | 13.3% | |
| 🤣 | 9,437 | 12.9% | |
| ❤ | 7,925 | 10.8% | |
| 👎 | 6,918 | 9.45% | |
| 😱 | 6,800 | 9.29% | |
| 🤬 | 6,702 | 9.15% | |
| 🤮 | 4,814 | 6.58% | |
| 😭 | 1,605 | 2.19% | |
| 🙏 | 1,487 | 2.03% | |
| 🗿 | 1,435 | 1.96% | |
| 🕊 | 594 | 0.811% | |
| 🥰 | 531 | 0.725% | |
| 🤔 | 474 | 0.647% | |
| 🤝 | 327 | 0.447% | |
| 🫡 | 249 | 0.34% |
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 1,000 of the 1,000 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 73,216 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 12 September 2026 to 10 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lipetska4. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 12 September 2026 to 10 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
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.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 12 September 2026 to 10 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.
Telegram’s own ‘edited’ marker: 70 of 582 posts held from the last 30 days (12.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).
🟢🟢🟢🟢🟢🟢Отбой «Ракетная опасность» по Липецкой области. 👉 Подписаться | Написать нам | Max
🙏7👎2🤣2🤬2
🔴🔴🔴🔴🔴🔴 Объявлена «Ракетная опасность» по Липецкой области. 👉 Подписаться | Написать нам | Max
😱15🤬7🤮6🥰6👍2
🏠 Плановое отключение воды и света произойдет в Липецке 11 ноября. Подробнее смотрите — в карточках. 👉 Подписаться | Написать нам | Max
🤬8🤣3❤2👍1😱1
💁♂️ Бросать резко пить опасно для ментального здоровья, — наркологи. В таком случае есть риск получить другую зависимость — например, стать лудоманом, геймером или трудоголиком. После отказа от спиртного человек ищет другие способы быстро справиться с тревогой, скукой или неприятными переживаниями. И тогда на помощь приходит новая зависимость. 👉 Подписаться | Написать нам | Max
🤮13❤5🤡4👍3🥰2🫡2
🗣 Переговоры в Абу-Даби были продуктивными, но многое еще предстоит сделать, — Рубио. Предстоит проделать большую работу. Это не похоже на то, что что-то может быть решено в ближайшие 24 часа. 👉 Подписаться | Написать нам | Max
🤮16🤡15👍7🤣4😱3
⚡️ Делегации России, США и Украины завершили первый день переговоров в Абу-Даби — они длились почти четыре часа. 👉 Подписаться | Написать нам | Max
🤣31❤10🤡6🤮4😱2
🎄 В Госдуме предложили сократить новогодние каникулы. Там считают, что 11 дней отдыха слишком много, поэтому часть выходных нужно перенести на май. 👉 Подписаться | Написать нам | Max
👎162🤡80👍28🤬16🤣8😭2❤1
❗️Ключевая ставка останется двузначной весь 2027 год — ЦБ РФ. Сейчас ключевая ставка 14%. 👉 Подписаться | Написать нам | Max
🤡31🤣8🤮5👍4🤝3🙏3🥰1
🎅У Комсомольского пруда сегодня утром рабочие предприятия «Липецкгорсвет» смонтировали светящиеся конструкции «С Новым годом» и «Свечи». 👉 Подписаться | Написать нам | Max
❤27🤡17🤮4👍3🥰2😱1
🤒 Заболеваемость гриппом растет в России — доля выявленных вирусов гриппа выросла почти в 3 раза за 3 недели Сейчас в стране еженедельно регистрируют до 600 тысяч случаев ОРВИ, гриппа и COVID-19. 👉 Подписаться | Написать нам | Max
❤9🤮4🤣3🥰2😱2👍1
🤲 В Воловском округе Липецкой области накрыли нарколабораторию, изъяли около 60 кг наркотиков. Полицейские задержали троих жителей Воронежской области: 46-летнего организатора и супружескую пару — 37-летняя женщина и её 33-летний муж. В ходе обыска обнаружены оборудование, вещества и упаковочные материалы. Изъятая смесь содержит производное N-метилэфедрона. По версии следствия, наркотики планировали распространять ч…
😱32👍6🤮5😭5❤4
⚡️В Липецкой области возникла путаница с ограничениями на бензин — в министерстве не подтвердили их введение. В министерстве заявили, что официального документа о введении ограничений на липецких АЗС пока нет. При этом сами заправочные сети могут устанавливать лимиты на отпуск топлива по собственному усмотрению. Таким образом, введение единых ограничений по всей области пока официально не подтверждено. Но на отдельн…
🤡53🤬12❤5😱4👎2🤮2👍1🤣1
Showing the 12 most recent of 1,802 posts we hold for @lipetska4. 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.
@lipetska4 edited 21 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 2 posts on @lipetska4 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.
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.
Named by 6 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 22 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
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.
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.
“Липецкач • Новости Липецка” (@lipetska4), 65,673 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/lipetska4.
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.