Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Сочи(Адлер, Лазаревское, Сириус)

Channel

Радар Сочи(Адлер, Лазаревское, Сириус)

@radar_sochiii

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

66,522subscribers

+821 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002743590568
TypeChannel
Username@radar_sochiii
DescriptionОбратная связь с нами - @Radarr_russiabot 🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/radar_sochiii

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 9 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 why it has no browse page of its own yet.

Growth

65,62866,64866,1387 August 2026 — 65,701 subscribers7 August 2026 — 65,701 subscribers7 August 2026 — 65,693 subscribers8 August 2026 — 65,719 subscribers9 August 2026 — 65,737 subscribers10 August 2026 — 65,739 subscribers11 August 2026 — 65,697 subscribers13 August 2026 — 65,732 subscribers14 August 2026 — 66,114 subscribers15 August 2026 — 66,316 subscribers16 August 2026 — 66,343 subscribers17 August 2026 — 66,360 subscribers19 August 2026 — 66,458 subscribers20 August 2026 — 66,411 subscribers21 August 2026 — 66,330 subscribers22 August 2026 — 66,312 subscribers24 August 2026 — 66,435 subscribers25 August 2026 — 66,310 subscribers26 August 2026 — 66,210 subscribers27 August 2026 — 66,080 subscribers28 August 2026 — 65,979 subscribers29 August 2026 — 65,924 subscribers30 August 2026 — 65,827 subscribers31 August 2026 — 65,710 subscribers1 September 2026 — 65,628 subscribers2 September 2026 — 65,695 subscribers3 September 2026 — 65,694 subscribers6 September 2026 — 66,397 subscribers9 September 2026 — 66,316 subscribers11 September 2026 — 66,539 subscribers13 September 2026 — 66,462 subscribers15 September 2026 — 66,648 subscribers17 September 2026 — 66,522 subscribers66,5227 August 202617 September 2026
33 measurements spanning 41 days, net +821. 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 65,475–66,801 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
17 Sept 2026, 06:4066,522-126
15 Sept 2026, 06:3966,648+186
13 Sept 2026, 17:1966,462-77
11 Sept 2026, 21:2266,539+223
9 Sept 2026, 08:5966,316-81
6 Sept 2026, 00:2066,397+703
3 Sept 2026, 18:2265,694-1
2 Sept 2026, 11:2465,695+67
1 Sept 2026, 14:1665,628-82
31 Aug 2026, 13:3265,710-117
30 Aug 2026, 10:0665,827-97
29 Aug 2026, 12:1465,924-55
28 Aug 2026, 12:0465,979-101
27 Aug 2026, 09:4666,080-130
26 Aug 2026, 08:3266,210-100
25 Aug 2026, 09:3666,310-125
24 Aug 2026, 08:2966,435+123
22 Aug 2026, 12:4266,312-18
21 Aug 2026, 05:0366,330-81
20 Aug 2026, 03:1466,411first reading

Engagement

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

ERR · 30 days
15.9%
avg views ÷ 66,522 subscribers
Avg views / post
10,600
240 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
240
of 355 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 23 September 2026
Posts held355 (6 August 202623 September 2026)
Views total2,536,560
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 08:33 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
30
Videos
24
Links
989

Lifetime counters from Telegram’s own channel header, read 23 September 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 18s
Average length
20s

Measured directly from 10 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.

Advertising

Ad load
0.282%
1 of 355 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
8,560
over 1 measured post
Median views · rest
10,400
over 354 measured posts

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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFGF2kCH18 September 20268 September 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 355 most recent posts we hold, published 6 August 2026 to 23 September 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.

Recent posts

23 Sept 2026, 06:50 UTC≈2,370 viewsread 23 September 2026

Краснодарский край Отбой опасности по БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

23 Sept 2026, 05:58 UTC≈3,300 viewsread 23 September 2026

За прошедшую ночь силами противовоздушной обороны было уничтожено 514 БПЛА над территориями Белгородской, Курской, Брянской, Воронежской, Орловской, Калужской, Липецкой, Тамбовской, Рязанской, Нижегородской, Смоленской, Саратовской, Самарской, Ульяновской, Ростовской областей, Краснодарского края, республиками Крым, Башкортостан, Татарстан, над акваториями Азовского и Черного морей. ❗️Радар Сочи(Адлер, Лазаревское,

23 Sept 2026, 02:14 UTC≈5,410 viewsread 23 September 2026

Сочи Геленджик Туапсе Новороссийск и близлежащие Опасность по БПЛА Меры безопасности Краснодарский край ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

23 Sept 2026, 00:51 UTC≈5,480 viewsread 23 September 2026

Сириус и близлежащие Краснодарский край Работа ПВО по БПЛА Меры безопасности ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

23 Sept 2026, 00:11 UTC≈5,420 viewsread 23 September 2026

Сочи Краснодарский край Работа ПВО по БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 23:31 UTC≈5,590 viewsread 23 September 2026

Сириус и близлежащие Краснодарский край Работа ПВО по БПЛА Меры безопасности ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 22:40 UTC≈5,690 viewsread 23 September 2026

Сочи Краснодарский край Работа ПВО по БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:44 UTC≈6,540 viewsread 23 September 2026

Адлер Краснодарский край Работа ПВО по БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:43 UTC≈6,610 viewsread 23 September 2026

Сочи Краснодарский край Сбитие БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:36 UTC≈7,030 viewsread 23 September 2026

Сочи Геленджик Туапсе Новороссийск и близлежащие Опасность по БПЛА Принять меры безопасности Краснодарский край ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:35 UTC≈6,900 viewsread 23 September 2026

Сочи Краснодарский край Продолжается работа ПВО по БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

22 Sept 2026, 21:32 UTC≈6,780 viewsread 23 September 2026

Сочи Краснодарский край Работа ПВО по БПЛА ❗️Радар Сочи(Адлер, Лазаревское, Сириус) - @radar_sochiii 🌐 Обход белых списков - @Internet_Boost_bot

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

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

“Радар Сочи(Адлер, Лазаревское, Сириус)” (@radar_sochiii), 66,522 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/radar_sochiii.

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.