Telegram RegisterThe public register of Telegram
Telegram profile photo for 181 Обстановка | Тревоги и опасности ЛНР

Channel

181 Обстановка | Тревоги и опасности ЛНР

@radar_lnr

On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

11,081subscribers

+4,183 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-1004367049127
TypeChannel
Username@radar_lnr
CreatedBetween 1 June 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held19
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/radar_lnr

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

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

6,89811,0818,989.57 August 2026 — 6,898 subscribers7 August 2026 — 6,898 subscribers10 August 2026 — 7,133 subscribers12 August 2026 — 7,552 subscribers16 August 2026 — 7,915 subscribers19 August 2026 — 8,056 subscribers22 August 2026 — 8,278 subscribers25 August 2026 — 9,311 subscribers28 August 2026 — 9,893 subscribers1 September 2026 — 10,067 subscribers2 September 2026 — 10,103 subscribers2 September 2026 — 10,193 subscribers4 September 2026 — 10,691 subscribers6 September 2026 — 10,855 subscribers9 September 2026 — 10,924 subscribers12 September 2026 — 10,975 subscribers13 September 2026 — 10,995 subscribers15 September 2026 — 11,007 subscribers17 September 2026 — 11,081 subscribers7 August 202617 September 2026
19 measurements spanning 41 days, net +4,183. 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 6,271–11,708 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 11:0011,081+74
15 Sept 2026, 13:1911,007+12
13 Sept 2026, 22:2010,995+20
12 Sept 2026, 05:0210,975+51
9 Sept 2026, 20:5710,924+69
6 Sept 2026, 16:5710,855+164
4 Sept 2026, 08:3810,691+498
2 Sept 2026, 22:5510,193+90
2 Sept 2026, 00:1810,103+36
1 Sept 2026, 00:4710,067+174
28 Aug 2026, 15:539,893+582
25 Aug 2026, 20:089,311+1,033
22 Aug 2026, 23:438,278+222
19 Aug 2026, 20:478,056+141
16 Aug 2026, 14:587,915+363
12 Aug 2026, 23:167,552+419
10 Aug 2026, 06:057,133+235
7 Aug 2026, 13:276,898no change
7 Aug 2026, 12:326,898first reading

Engagement

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

ERR · 30 days
29.1%
avg views ÷ 11,081 subscribers
Avg views / post
3,230
125 posts measured
Reaction rate
0.588%
reactions ÷ views · ER floor
Posts in window
125
of 278 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 29 August 2026
Posts held278 (5 August 202629 August 2026)
Views total403,248
Reactions total2,370
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 04:51 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

Video runtime
15m 00s
Average length
53s

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.

Reaction mix

5,672 reactions across 278 posts, in 10 distinct kinds. The most used accounts for 87.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏4,97387.7%
🤬2834.99%
2113.72%
😱711.25%
😢460.811%
👍300.529%
🤯280.494%
👎190.335%
💯90.159%
🤝20.035%

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

Measured over the 278 most recent posts we hold, published 5 August 2026 to 29 August 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.

Telegram Stars

Stars received
13
across the posts below
Posts paid on
7
of 278 we hold a reading for · 3%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @radar_lnr. 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 278 most recent posts we hold for this entry, published 5 August 2026 to 29 August 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.

Recent posts

29 Aug 2026, 04:10 UTC773 views4 reactionsread 29 August 2026

ЛНР. Угроза атаки БПЛА. В границах муниципальных округов: Краснодонский, Лутугинский, Славяносербский, и городов Луганск, Брянка, Кировск, Стаханов, Первомайск 07:05 РСЧС Радар ЛНР🟢Чат | Обратная связь

🙏4

29 Aug 2026, 03:59 UTC930 views6 reactionsread 29 August 2026

От Алчевска фиксации БПЛА в сторону Луганска Меры безопасности Радар ЛНР 🟢 Чат | Обратная связь

🙏6

28 Aug 2026, 20:46 UTC≈2,720 views19 reactionsread 29 August 2026

Для оперативного информирования гражданского населения приглашаем к сотрудничеству представителей МОГ, ПВН, сил ПВО, расчётов РЛС, подразделений ДРЛО, а также специалистов пунктов сбора и обработки радиолокационной информации. Также будем рады сотрудничеству с представителями экстренных и спасательных служб, местных администраций, официальных пресс-служб, энергетических и коммунальных организаций, располагающих подт

🙏133👍3

28 Aug 2026, 19:09 UTC≈3,580 views28 reactionsread 29 August 2026

Роскошное, Луганск и близлежащие Опасность по БПЛА Радар ЛНР 🟢 Чат | Обратная связь

🙏28

28 Aug 2026, 19:02 UTC≈3,670 views30 reactionsread 29 August 2026

Повторно тревога от РСЧС 22:00 В границах муниципальных округов: Краснодонский, Лутугинский, Славяносербский, и городов Луганск, Брянка, Кировск, Стаханов, Первомайск Радар ЛНР 🟢 Чат | Обратная связь

🙏30

28 Aug 2026, 18:30 UTC≈4,010 views34 reactionsread 29 August 2026

ЛНР. Угроза атаки БПЛА. В границах муниципальных округов: Краснодонский, Лутугинский, Славяносербский, и городов Луганск, Брянка, Кировск, Стаханов, Первомайск 21:30 РСЧС Радар ЛНР 🟢 Чат | Обратная связь

🙏34

28 Aug 2026, 15:16 UTC≈3,220 views11 reactionsread 29 August 2026
Forwarded from @obstanovkalnrPhoto

❗️ В Рубежном света может не быть ещё несколько дней В администрации предупредили, что после массированной атаки БПЛА на энергетический комплекс электроснабжение пока не восстановлено. Все силы сейчас направлены на ремонт, однако работы могут занять несколько дней ➡️ Отдельно по воде: 29 августа с 12:00 до 15:00 в городе будет осуществляться подача воды Жителям лучше воспользоваться этим временем и сделать необход

🤬72🤯2

28 Aug 2026, 14:15 UTC≈3,160 views21 reactionsread 29 August 2026
Forwarded from @obstanovkalnrPhoto

❗️ После ночной атаки на энергосистему проблемы с водой сохраняются сразу в нескольких городах ЛНР Ситуация везде разная: где-то воду сегодня вообще не дадут, где-то её подают по временному графику, а в некоторых городах организовали подвоз Что известно на данный момент ❔ ➖ Кировск и село Березовское — 28 августа подача воды не планируется из-за отсутствия поступления воды в резервуары ➖ Старобельский округ — воду

🙏76😢4👎2🤬2

28 Aug 2026, 13:18 UTC≈3,930 views17 reactionsread 29 August 2026

Первомайск, Алчевск и близлежащие Опасность по БПЛА Радар ЛНР 🟢 Чат | Обратная связь

🙏17

28 Aug 2026, 08:53 UTC≈4,750 views19 reactionsread 29 August 2026

ЛНР Отбой ракетной опасности Радар ЛНР 🟢 Чат | Обратная связь

🙏17🤯2

28 Aug 2026, 08:43 UTC≈4,810 views12 reactionsread 29 August 2026
Video

ЛНР Ракетная опасность Радар ЛНР 🟢 Чат | Обратная связь

🙏10😱2

28 Aug 2026, 08:30 UTC≈3,280 views15 reactionsread 29 August 2026
Forwarded from @obstanovkalnrPhoto

❗️ Ночью энергетический комплекс ЛНР подвергся массированной атаке БПЛА, — Пасечник По словам главы республики, системы ПВО и мобильные огневые группы несколько часов отражали налёт, но некоторым дронам удалось нанести удары Из-за этого в ряде городов и районов ЛНР до сих пор нет света. Медицинские и социально значимые объекты работают от резервных источников питания Угроза повторной атаки сохраняется, поэтому рем

🙏9🤬32🤝1

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 3 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.

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.

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

“181 Обстановка | Тревоги и опасности ЛНР” (@radar_lnr), 11,081 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_lnr.

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.