Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Питер и Ленинградская область

Channel

Радар Питер и Ленинградская область

@radar_peterburg

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

152,780subscribers

+289 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002385745466
TypeChannel
Username@radar_peterburg
DescriptionОбратная связь с нами - @Radarr_russiabot 🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию
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 live15 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/radar_peterburg

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 9 August 2026 and assigned it the closest of 31 fixed categories, at 47% 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

152,248152,780152,5147 August 2026 — 152,491 subscribers7 August 2026 — 152,491 subscribers7 August 2026 — 152,500 subscribers8 August 2026 — 152,502 subscribers9 August 2026 — 152,446 subscribers10 August 2026 — 152,380 subscribers11 August 2026 — 152,355 subscribers12 August 2026 — 152,248 subscribers14 August 2026 — 152,473 subscribers15 August 2026 — 152,780 subscribers7 August 202615 August 2026
10 measurements spanning 8 days, net +289. 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 152,168–152,860 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 17:53152,780+307
14 Aug 2026, 03:56152,473+225
12 Aug 2026, 18:33152,248-107
11 Aug 2026, 16:17152,355-25
10 Aug 2026, 19:17152,380-66
9 Aug 2026, 21:31152,446-56
8 Aug 2026, 23:03152,502+2
7 Aug 2026, 22:08152,500+9
7 Aug 2026, 16:30152,491no change
7 Aug 2026, 16:26152,491first reading

Engagement

55 posts held, back to 4 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 26 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
34.9%
avg views ÷ 152,780 subscribers
Avg views / post
53,300
55 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
55
of 55 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 15 August 2026
Posts held55 (4 August 202615 August 2026)
Views total2,928,900
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 07:14 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
32
Videos
18
Links
503

Lifetime counters from Telegram’s own channel header, read 16 August 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
42s
Average length
11s

Measured directly from 4 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
1.82%
1 of 55 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
38,300
over 1 measured post
Median views · rest
51,400
over 54 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
2VtzquchFgf111 August 202611 August 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 55 most recent posts we hold, published 4 August 2026 to 15 August 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

15 Aug 2026, 07:38 UTC≈36,300 viewsread 16 August 2026

Ленинградская область Отбой опасности по БПЛА ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 06:00 UTC≈42,700 viewsread 16 August 2026

Кириши, Ленинградская область - отбой опасности по БПЛА. Переходим в режим внимание. ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 05:42 UTC≈45,600 viewsread 16 August 2026

Кириши Ленинградская область Работа ПВО по БПЛА Меры безопасности ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 05:36 UTC≈43,400 viewsread 16 August 2026

Кириши и близлежащие Ленинградская область Приготовиться к сбитию ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 05:30 UTC≈40,400 viewsread 16 August 2026

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

15 Aug 2026, 05:23 UTC≈37,900 viewsread 16 August 2026

В нескольких районах Ленинградской области идут сбития БПЛА. ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 05:15 UTC≈37,300 viewsread 16 August 2026

Кириши Ленинградская область Меры безопасности ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 05:11 UTC≈37,100 viewsread 16 August 2026

Киришский район Ленинградская область Фиксация от 3 БПЛА ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 04:56 UTC≈37,400 viewsread 16 August 2026

Волховский район Ленинградская область Фиксация БПЛА ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 04:55 UTC≈39,800 viewsread 16 August 2026

Тосненский район Ленинградская область Фиксация БПЛА ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 04:40 UTC≈40,500 viewsread 16 August 2026

Бокситогорский район Ленинградская область Фиксации БПЛА ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

15 Aug 2026, 02:45 UTC≈42,600 viewsread 16 August 2026

Ленинградская область Опасность по БПЛА ❗️Радар Питер и Ленинградская область - @radar_peterburg 🌐 Обход белых списков - @Internet_Boost_bot

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

Citation-graph rank

Citation-graph rank — 334,895 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

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

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 4 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.

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

“Радар Питер и Ленинградская область” (@radar_peterburg), 152,780 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/radar_peterburg.

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.