Telegram RegisterThe public register of Telegram
Telegram profile photo for РОДНОЙ ЛИПЕЦК | РАДАР

Channel

РОДНОЙ ЛИПЕЦК | РАДАР

@rodnoylipetsk

On this record: Topic · Growth · Engagement · Posts · Cite this entry

2,090subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002114766639
TypeChannel
Username@rodnoylipetsk
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/rodnoylipetsk

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.

Growth

2,0842,0922,0887 August 2026 — 2,092 subscribers7 August 2026 — 2,092 subscribers7 August 2026 — 2,091 subscribers10 August 2026 — 2,092 subscribers17 August 2026 — 2,091 subscribers23 August 2026 — 2,090 subscribers29 August 2026 — 2,092 subscribers1 September 2026 — 2,084 subscribers4 September 2026 — 2,091 subscribers10 September 2026 — 2,092 subscribers13 September 2026 — 2,086 subscribers18 September 2026 — 2,090 subscribers2,0907 August 202618 September 2026
12 measurements spanning 42 days, net -2. 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 2,083–2,093 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 02:592,090+4
13 Sept 2026, 13:582,086-6
10 Sept 2026, 03:172,092+1
4 Sept 2026, 22:392,091+7
1 Sept 2026, 14:362,084-8
29 Aug 2026, 13:142,092+2
23 Aug 2026, 12:562,090-1
17 Aug 2026, 11:382,091-1
10 Aug 2026, 14:352,092+1
7 Aug 2026, 16:542,091-1
7 Aug 2026, 14:482,092no change
7 Aug 2026, 14:302,092first reading

Engagement

20 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 07:48 UTC42 viewsread 7 August 2026

Фиксаций над нашим воздушным пространством не наблюдаем В случае возникновения угрозы незамедлительно сообщим! 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 20:33 UTC88 viewsread 7 August 2026

Измалковский район Липецкая область Фиксация БПЛА 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 19:57 UTC97 viewsread 7 August 2026

Лебедянский район Долгоруковский район Добринский район Липецкая область Фиксация БПЛА 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 19:46 UTC98 viewsread 7 August 2026

Задонский район Хлевенский район Липецкая область Фиксация БПЛА 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 19:02 UTC100 viewsread 7 August 2026

Усманский район Липецкая область Фиксация БПЛА 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 16:27 UTC113 viewsread 7 August 2026

Елец Елецкий МО Долгоруковский МО Становлянский МО Измайловский МО Задонский МО Тербунский МО Воловского МО Липецкая область Опасность по БПЛА 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 16:09 UTC112 viewsread 7 August 2026

Липецкая область Опасность по БПЛА Сохраняется 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 13:46 UTC111 viewsread 7 August 2026

За сутки силами ПВО было уничтожено 1155 БПЛА над российскими регионами 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 12:05 UTC110 viewsread 7 August 2026

❗️ Сотрудниками ФСБ России в Приморском крае задержаны двое подростков, которые по заданию украинских кураторов готовили теракт на объекте Росгвардии.

6 Aug 2026, 08:45 UTC113 viewsread 7 August 2026

⚡️Макрон командует Украине совершать теракты, призывая усилить давление на Россию — МИД РФ Франция должна знать, что её руководство лично участвует в террористической деятельности против женщин и детей.

6 Aug 2026, 07:08 UTC89 viewsread 7 August 2026

За ночь силами ПВО было уничтожено 605 БПЛА над российскими регионами. 🌐 🚨Родной Липецк - @rodnoylipetsk

6 Aug 2026, 06:46 UTC91 viewsread 7 August 2026

❗️ Специалисты МАИ совместно с учёными из МФТИ создали двигатель на криптоне малой мощности для низкоорбитальных спутников.

Showing the 12 most recent of 20 posts we hold for @rodnoylipetsk. 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.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“РОДНОЙ ЛИПЕЦК | РАДАР” (@rodnoylipetsk), 2,090 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/rodnoylipetsk.

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.