Telegram RegisterThe public register of Telegram
Telegram profile photo for Локатор России

Channel

Локатор России

@locatorru

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

239,876subscribers

+29,543 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1002242116325
TypeChannel
Username@locatorru
DescriptionМы в MAX — https://max.ru/locatorru Поддержать — https://pay.cloudtips.ru/p/45774fc7
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/locatorru

Topic

National news — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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

210,333239,946225,139.56 August 2026 — 210,333 subscribers7 August 2026 — 210,787 subscribers8 August 2026 — 211,674 subscribers9 August 2026 — 212,065 subscribers10 August 2026 — 212,749 subscribers11 August 2026 — 213,293 subscribers12 August 2026 — 213,566 subscribers13 August 2026 — 213,857 subscribers15 August 2026 — 214,786 subscribers16 August 2026 — 215,788 subscribers17 August 2026 — 215,805 subscribers18 August 2026 — 218,400 subscribers19 August 2026 — 219,382 subscribers21 August 2026 — 219,680 subscribers22 August 2026 — 220,092 subscribers24 August 2026 — 221,489 subscribers25 August 2026 — 221,679 subscribers26 August 2026 — 221,992 subscribers27 August 2026 — 222,268 subscribers28 August 2026 — 222,763 subscribers29 August 2026 — 222,831 subscribers30 August 2026 — 223,362 subscribers31 August 2026 — 223,429 subscribers1 September 2026 — 223,593 subscribers2 September 2026 — 223,541 subscribers3 September 2026 — 223,787 subscribers5 September 2026 — 223,812 subscribers9 September 2026 — 223,826 subscribers11 September 2026 — 224,739 subscribers13 September 2026 — 224,840 subscribers15 September 2026 — 224,961 subscribers17 September 2026 — 225,663 subscribers19 September 2026 — 225,830 subscribers26 September 2026 — 227,508 subscribers4 October 2026 — 228,176 subscribers9 October 2026 — 228,735 subscribers13 October 2026 — 230,951 subscribers14 October 2026 — 231,079 subscribers15 October 2026 — 232,760 subscribers16 October 2026 — 233,586 subscribers17 October 2026 — 234,089 subscribers19 October 2026 — 236,484 subscribers19 October 2026 — 236,749 subscribers21 October 2026 — 237,301 subscribers22 October 2026 — 237,737 subscribers23 October 2026 — 237,715 subscribers24 October 2026 — 238,002 subscribers25 October 2026 — 238,153 subscribers26 October 2026 — 238,327 subscribers27 October 2026 — 238,585 subscribers28 October 2026 — 238,876 subscribers29 October 2026 — 239,034 subscribers30 October 2026 — 239,252 subscribers31 October 2026 — 239,223 subscribers1 November 2026 — 239,320 subscribers2 November 2026 — 239,313 subscribers3 November 2026 — 239,709 subscribers4 November 2026 — 239,946 subscribers5 November 2026 — 239,876 subscribers239,8766 August 20265 November 2026
59 measurements spanning 91 days, net +29,543. 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 205,891–244,388 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
5 Nov 2026, 10:56239,876-70
4 Nov 2026, 09:44239,946+237
3 Nov 2026, 08:30239,709+396
2 Nov 2026, 10:25239,313-7
1 Nov 2026, 09:16239,320+97
31 Oct 2026, 06:55239,223-29
30 Oct 2026, 06:31239,252+218
29 Oct 2026, 04:18239,034+158
28 Oct 2026, 03:59238,876+291
27 Oct 2026, 01:55238,585+258
26 Oct 2026, 02:58238,327+174
25 Oct 2026, 05:25238,153+151
24 Oct 2026, 04:06238,002+287
23 Oct 2026, 04:16237,715-22
22 Oct 2026, 04:01237,737+436
21 Oct 2026, 00:11237,301+552
19 Oct 2026, 22:04236,749+265
19 Oct 2026, 00:05236,484+2,395
17 Oct 2026, 21:18234,089+503
16 Oct 2026, 20:54233,586first reading

Engagement

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

ERR · 30 days
4.14%
avg views ÷ 239,876 subscribers
Avg views / post
9,930
1,193 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1,193
of 3,692 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 5 November 2026
Posts held3,692 (6 August 2026 – 5 November 2026)
Views total11,848,492
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 13:54 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
3
Videos
1
Links
5

Lifetime counters from Telegram’s own channel header, read 5 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.

Recent posts

Telegram’s own ‘edited’ marker: 6 of 1,193 posts held from the last 30 days (0.503%) 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).

5 Nov 2026, 13:40 UTC≈2,030 viewsread 5 November 2026

Ростовская область - отбой опасности по БПЛА. 📡Локатор России - @locatorru

5 Nov 2026, 09:49 UTC≈10,600 viewsread 5 November 2026

Сельцо и близлежащие, Брянская область - опасность по БПЛА. 📡Локатор России - @locatorru

5 Nov 2026, 09:43 UTC≈11,200 viewsread 5 November 2026

Ростовская область - опасность по БПЛА по югу. 📡Локатор России - @locatorru

5 Nov 2026, 09:42 UTC≈11,400 viewsread 5 November 2026

Чертково, Миллерово, Тарасовский, Матвеев Курган, Куйбышево, Лысогорка, Новошахтинск, Шахты, Красный Сулин, Гуково, Лиховской, Донецк, Каменск-Шахтинский, Ростовская область - опасность по БПЛА. 📡Локатор России - @locatorru

5 Nov 2026, 09:41 UTC≈11,400 viewsread 5 November 2026

Курская область - отбой ракетной опасности! 📡Локатор России - @locatorru

5 Nov 2026, 09:41 UTC≈11,200 viewsread 5 November 2026

Ростовская область - опасность по БПЛА по северу. 📡Локатор России - @locatorru

5 Nov 2026, 09:38 UTC≈10,900 viewsread 5 November 2026

Курская область - ракетная опасность! 📡Локатор России - @locatorru

5 Nov 2026, 09:34 UTC≈10,500 viewsread 5 November 2026

Титовка, Шебекинский район, Белгородская область - обстрел. г.Шебекино, меры безопасности от Титовка. 📡Локатор России - @locatorru

5 Nov 2026, 09:27 UTC≈9,870 viewsread 5 November 2026

🫡Помочь нашей команде можно через сервис Т-Банк(оплата по СБП) https://pay.cloudtips.ru/p/45774fc7 За последнее время нам помогают единицы. 🙏 📡Локатор России - @locatorru

5 Nov 2026, 09:24 UTC≈9,140 viewsread 5 November 2026

Приграничные районы Курской области, Брянской области, Белгородской области - опасность по БПЛА. Активность FPV-дронов на высоком уровне. 📡Локатор России - @locatorru

5 Nov 2026, 09:21 UTC≈10,000 viewsread 5 November 2026
Photo

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

5 Nov 2026, 08:58 UTC≈9,570 viewsread 5 November 2026

Ростовская область - отбой ракетной опасности! 📡Локатор России - @locatorru

Showing the 12 most recent of 3,692 posts we hold for @locatorru. 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

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 32 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Локатор России” (@locatorru), 239,876 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/locatorru.

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.