Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар.ру | Липецкая область ( обстрелы, БПЛА, ракеты, сводки )

Channel

Радар.ру | Липецкая область ( обстрелы, БПЛА, ракеты, сводки )

@radar_ru_lipetsk

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

18,748subscribers

-457 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-1002299347087
TypeChannel
Username@radar_ru_lipetsk
DescriptionОповещение населения и самые оперативные новости региона на нашем канале 🙏
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/radar_ru_lipetsk

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

18,74819,20518,976.57 August 2026 — 19,205 subscribers7 August 2026 — 19,204 subscribers9 August 2026 — 19,196 subscribers10 August 2026 — 19,191 subscribers11 August 2026 — 19,185 subscribers12 August 2026 — 19,178 subscribers13 August 2026 — 19,165 subscribers15 August 2026 — 19,161 subscribers16 August 2026 — 19,146 subscribers17 August 2026 — 19,138 subscribers18 August 2026 — 19,135 subscribers19 August 2026 — 19,122 subscribers20 August 2026 — 19,118 subscribers21 August 2026 — 19,108 subscribers23 August 2026 — 19,097 subscribers24 August 2026 — 19,084 subscribers25 August 2026 — 19,076 subscribers26 August 2026 — 19,071 subscribers27 August 2026 — 19,065 subscribers29 August 2026 — 19,063 subscribers30 August 2026 — 19,060 subscribers31 August 2026 — 19,052 subscribers1 September 2026 — 19,049 subscribers2 September 2026 — 19,045 subscribers4 September 2026 — 19,086 subscribers6 September 2026 — 19,085 subscribers9 September 2026 — 19,086 subscribers12 September 2026 — 19,070 subscribers14 September 2026 — 19,059 subscribers15 September 2026 — 19,052 subscribers17 September 2026 — 19,037 subscribers27 September 2026 — 18,980 subscribers4 October 2026 — 18,924 subscribers9 October 2026 — 18,900 subscribers13 October 2026 — 18,877 subscribers14 October 2026 — 18,862 subscribers15 October 2026 — 18,861 subscribers16 October 2026 — 18,855 subscribers17 October 2026 — 18,847 subscribers18 October 2026 — 18,842 subscribers19 October 2026 — 18,832 subscribers20 October 2026 — 18,819 subscribers21 October 2026 — 18,804 subscribers23 October 2026 — 18,820 subscribers24 October 2026 — 18,821 subscribers26 October 2026 — 18,811 subscribers28 October 2026 — 18,806 subscribers29 October 2026 — 18,801 subscribers30 October 2026 — 18,787 subscribers31 October 2026 — 18,786 subscribers1 November 2026 — 18,790 subscribers2 November 2026 — 18,799 subscribers3 November 2026 — 18,793 subscribers4 November 2026 — 18,786 subscribers4 November 2026 — 18,771 subscribers6 November 2026 — 18,752 subscribers7 November 2026 — 18,748 subscribers7 August 20267 November 2026
57 measurements spanning 92 days, net -457. 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 18,679–19,274 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
7 Nov 2026, 02:1918,748-4
6 Nov 2026, 02:2018,752-19
4 Nov 2026, 23:3518,771-15
4 Nov 2026, 01:5118,786-7
3 Nov 2026, 02:2918,793-6
2 Nov 2026, 02:3718,799+9
1 Nov 2026, 02:4918,790+4
31 Oct 2026, 01:1118,786-1
30 Oct 2026, 04:2918,787-14
29 Oct 2026, 05:3118,801-5
28 Oct 2026, 06:1918,806-5
26 Oct 2026, 08:0618,811-10
24 Oct 2026, 04:2818,821+1
23 Oct 2026, 01:4818,820+16
21 Oct 2026, 22:2818,804-15
20 Oct 2026, 16:5618,819-13
19 Oct 2026, 17:3818,832-10
18 Oct 2026, 14:3118,842-5
17 Oct 2026, 15:2918,847-8
16 Oct 2026, 14:5418,855first reading

Engagement

366 posts held, back to 5 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 77 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.55%
avg views ÷ 18,748 subscribers
Avg views / post
1,600
89 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
89
of 366 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 November 2026
Posts held366 (5 August 2026 – 7 November 2026)
Views total142,582
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 16:45 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
46
Videos
30
Links
29

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. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3m 51s
Average length
14s

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: 0 of 89 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).

7 Nov 2026, 11:51 UTC745 viewsread 7 November 2026

Автор ролика Максим П. утверждает, что девушка напала на него со шприцем. Ещё одна пострадавшая тоже говорит о броске со шприцем, однако сама Татьяна такой эпизод отрицает. Связать её с серией нашумевших уколов нельзя — в конце октября информацию об инцидентах официально не подтвердили. Знакомая девушки рассказала, что та ранее наблюдалась у психиатров и проходила лечение, сейчас периодически живёт у подруги и проси…

7 Nov 2026, 11:51 UTC768 viewsread 7 November 2026
Photo

⚠️ В московском метро пассажиры жалуются на агрессивную девушку, двое заявили об угрозе шприцем В соцсетях разошлось видео, где молодая девушка просит у пассажиров метро деньги. Под роликом десятки комментариев от людей, которые, по их словам, встречали её на разных ветках. Сценарий похож: Татьяна просит 300–400 рублей, а после отказа оскорбляет или ведёт себя агрессивно. Пассажирка Лейсан рассказала, что столкнула…

7 Nov 2026, 11:20 UTC781 viewsread 7 November 2026

❗️ Владимир Путин подтвердил, что 10 ноября в Абу-Даби начнутся переговоры РФ и Украины. Российскую делегацию возглавит Владимир Мединский, украинскую - Рустем Умеров.

7 Nov 2026, 10:50 UTC893 viewsread 7 November 2026
Photo

🔥 ЭКСПРЕСС НА 4 МАТЧА — КЭФФ 24.02 🇷🇺 Краснодар - ЦСКА 🇷🇺 🏴󠁧󠁢󠁥󠁮󠁧󠁿 Арсенал - Халл Сити 🏴󠁧󠁢󠁥󠁮󠁧󠁿 🇪🇸 Валенсия - Реал Мадрид 🇪🇸 🇮🇹 Рома - Сассуоло 🇮🇹 4 матча → Одна ставка → ПРИБЫЛЬ 2 402 000 Статистика за прошлый месяц: +27 | -3 Средний коэффицент прогнозов: 17.3 👉 ЗАБРАТЬ ЭТОТ ЭКСПРЕСС https://t.me/+Pru-5tQosi02ODJi

7 Nov 2026, 04:02 UTC≈1,120 viewsread 7 November 2026

Липецкая область Отбой опасности по БПЛА 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 23:40 UTC≈1,260 viewsread 7 November 2026

Липецкая область Отбой ракетной опасности 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 23:10 UTC≈1,320 viewsread 7 November 2026

Липецкая область Ракетная опасность 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 22:42 UTC≈1,370 viewsread 7 November 2026

Липецкая область Отбой ракетной опасности 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 22:14 UTC≈1,490 viewsread 7 November 2026

Елец, Липецк - ракетная опасность 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 22:00 UTC≈1,620 viewsread 7 November 2026

Липецк Липецкая область Меры безопасности 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 21:58 UTC≈1,570 viewsread 7 November 2026

Липецкая область Ракетная опасность 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

6 Nov 2026, 21:08 UTC≈1,860 viewsread 7 November 2026

Липецк Липецкая область Меры безопасности 🎯Радар.ру | Липецкая область - @radar_ru_lipetsk

Showing the 12 most recent of 366 posts we hold for @radar_ru_lipetsk. 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 12 posts on @radar_ru_lipetsk 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
10 August 2026
Most recent seen missing
6 November 2026
Median time before seen missing
28 hours
Seen missing in the last 30 days
1

Mentions

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.

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.

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.

“Радар.ру | Липецкая область ( обстрелы, БПЛА, ракеты, сводки )” (@radar_ru_lipetsk), 18,748 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/radar_ru_lipetsk.

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.