Telegram RegisterThe public register of Telegram
Telegram profile photo for Радар Санкт-Петербург

Channel

Радар Санкт-Петербург

@radar_piter

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

52,052subscribers

+13,545 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-1002549707378
TypeChannel
Username@radar_piter
Description🔔Включите обязательно уведомления, чтобы получать точную и оперативную информацию. По рекламе: @ktoktoktoktooo
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/radar_piter

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

37,67452,21044,9427 August 2026 — 38,507 subscribers8 August 2026 — 38,494 subscribers9 August 2026 — 38,483 subscribers10 August 2026 — 38,459 subscribers11 August 2026 — 38,444 subscribers12 August 2026 — 38,423 subscribers13 August 2026 — 38,398 subscribers14 August 2026 — 38,388 subscribers16 August 2026 — 38,338 subscribers17 August 2026 — 38,290 subscribers18 August 2026 — 38,262 subscribers19 August 2026 — 38,232 subscribers20 August 2026 — 38,183 subscribers22 August 2026 — 38,181 subscribers24 August 2026 — 38,156 subscribers25 August 2026 — 38,128 subscribers26 August 2026 — 38,115 subscribers27 August 2026 — 38,098 subscribers28 August 2026 — 38,088 subscribers29 August 2026 — 38,082 subscribers30 August 2026 — 38,078 subscribers31 August 2026 — 38,179 subscribers1 September 2026 — 38,210 subscribers2 September 2026 — 38,231 subscribers3 September 2026 — 38,217 subscribers5 September 2026 — 38,204 subscribers9 September 2026 — 38,153 subscribers11 September 2026 — 38,104 subscribers13 September 2026 — 38,106 subscribers15 September 2026 — 38,068 subscribers17 September 2026 — 38,038 subscribers19 September 2026 — 38,068 subscribers26 September 2026 — 37,997 subscribers4 October 2026 — 37,923 subscribers9 October 2026 — 37,822 subscribers13 October 2026 — 37,756 subscribers14 October 2026 — 37,708 subscribers15 October 2026 — 37,674 subscribers16 October 2026 — 37,710 subscribers17 October 2026 — 37,715 subscribers18 October 2026 — 46,461 subscribers19 October 2026 — 47,783 subscribers20 October 2026 — 51,585 subscribers21 October 2026 — 52,023 subscribers22 October 2026 — 51,980 subscribers24 October 2026 — 51,999 subscribers25 October 2026 — 52,091 subscribers26 October 2026 — 52,200 subscribers27 October 2026 — 52,124 subscribers28 October 2026 — 52,182 subscribers29 October 2026 — 52,117 subscribers30 October 2026 — 52,095 subscribers31 October 2026 — 52,069 subscribers1 November 2026 — 52,072 subscribers2 November 2026 — 52,210 subscribers3 November 2026 — 52,119 subscribers4 November 2026 — 52,127 subscribers5 November 2026 — 52,052 subscribers52,0527 August 20265 November 2026
58 measurements spanning 90 days, net +13,545. 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 35,494–54,390 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
5 Nov 2026, 13:5152,052-75
4 Nov 2026, 12:3952,127+8
3 Nov 2026, 15:5452,119-91
2 Nov 2026, 12:5552,210+138
1 Nov 2026, 13:2152,072+3
31 Oct 2026, 10:3752,069-26
30 Oct 2026, 08:4452,095-22
29 Oct 2026, 11:0052,117-65
28 Oct 2026, 06:4652,182+58
27 Oct 2026, 05:5652,124-76
26 Oct 2026, 03:3752,200+109
25 Oct 2026, 06:0952,091+92
24 Oct 2026, 02:4051,999+19
22 Oct 2026, 23:1951,980-43
21 Oct 2026, 23:3852,023+438
20 Oct 2026, 16:5651,585+3,802
19 Oct 2026, 14:4447,783+1,322
18 Oct 2026, 17:0046,461+8,746
17 Oct 2026, 19:5837,715+5
16 Oct 2026, 18:3737,710first reading

Engagement

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

ERR · 30 days
34.1%
avg views ÷ 52,052 subscribers
Avg views / post
17,700
156 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
156
of 375 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 held375 (5 August 2026 – 5 November 2026)
Views total2,766,934
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 12:17 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
257
Videos
152
Links
332

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

Video runtime
4m 24s
Average length
22s

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

Recent posts

Telegram’s own ‘edited’ marker: 2 of 156 posts held from the last 30 days (1.28%) 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, 12:08 UTC≈8,880 viewsread 6 November 2026

На данный момент по обстановке тихо При возникновении непосредственной угрозы оповестим немедленно. Берегите себя и своих близких! Радар Санкт Петербург - @radar_piter | Мы в MAX

4 Nov 2026, 08:49 UTC≈13,000 viewsread 6 November 2026
Photo

💰 Компании урезают зарплаты без увольнений Работодатели экономят не за счёт сокращений: отменяют премии, урезают бонусы и переводят сотрудников на неполный день. Причина в том, что поиск и обучение новых работников обходятся дороже, чем сохранить текущих. Радар Санкт Петербург - @radar_piter | Мы в MAX

4 Nov 2026, 07:30 UTC≈13,600 viewsread 6 November 2026
Photo

Baкaнcия oт Пятepoчки: paзpeзaть цeнники нa дoмy, oплaтa 1.800 в чac Oплaтa: кaждый дeнь нa кapтy, вoзмoжнo oфициaльнoe тpyдoycтpoйcтвo Tpeбoвaния: oбpeзaть cтpoгo пo шaблoнy, oтвecтвeннocть, внимaтeльнocть Уcлoвия: 2-3 чaca в дeнь из дoмa, гибкий гpaфик Пo вceм вoпpocaм 👉🏼 @pyaterochka_rabota Для oткликa нa вaкaнcию нaжмитe кнoпкy нижe

3 Nov 2026, 16:14 UTC≈18,600 viewsread 6 November 2026

Ожидаем ближе к ночи массовый запуск БПЛА на всех направлениях, в том числе крылатых ракет Радар Санкт Петербург - @radar_piter | Мы в MAX

3 Nov 2026, 08:00 UTC≈17,800 viewsread 6 November 2026

Фиксаций над нашим воздушным пространством не наблюдаем В случае возникновения угрозы незамедлительно сообщим! Радар Санкт Петербург - @radar_piter | Мы в MAX

2 Nov 2026, 20:20 UTC≈19,900 viewsread 6 November 2026
Photo

⚡ Хакеры атаковали хостинг Beget — под угрозой сотни тысяч сайтов Компания официально подтвердила ночную атаку на свою инфраструктуру. Восстановление сервисов может затянуться. На хостинге размещено почти 15% действующих сайтов в зонах.ru,.рф и.su — около 500 тысяч ресурсов. Радар Санкт Петербург - @radar_piter | Мы в MAX

2 Nov 2026, 16:20 UTC≈15,500 viewsread 6 November 2026

Пока по обстановке тихо, в случае появления угрозы незамедлительно сообщим Радар Санкт Петербург - @radar_piter | Мы в MAX

2 Nov 2026, 14:07 UTC≈16,800 viewsread 6 November 2026
Photo

🚗 ДТП на КАД перед съездом на Шафировский собрало пробку 7,5 км Столкнулись легковушка и фургон: легковую смяло, фургон перевернулся. Пассажира такси зажало в салоне, его госпитализировали. По предварительным данным, у легковушки лопнуло колесо — машина встала в левом ряду, и в неё врезался фургон. Авария перекрыла две полосы внешнего кольца КАД. На месте работают экстренные службы. Радар Санкт Петербург - @radar…

2 Nov 2026, 08:00 UTC≈17,700 viewsread 6 November 2026

Фиксаций над нашим воздушным пространством не наблюдаем В случае возникновения угрозы незамедлительно сообщим! Радар Санкт Петербург - @radar_piter | Мы в MAX

1 Nov 2026, 18:54 UTC≈20,600 viewsread 6 November 2026

На данный момент по обстановке тихо При возникновении непосредственной угрозы оповестим немедленно. Берегите себя и своих близких! Радар Санкт Петербург - @radar_piter | Мы в MAX

1 Nov 2026, 15:00 UTC≈24,500 viewsread 6 November 2026

Ожидаем ближе к ночи массовый запуск БПЛА Радар Санкт Петербург - @radar_piter | Мы в MAX

30 Oct 2026, 15:38 UTC≈26,500 viewsread 6 November 2026

Фиксаций над нашим воздушным пространством не наблюдаем В случае возникновения угрозы незамедлительно сообщим! Радар Санкт Петербург - @radar_piter | Мы в MAX

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

Posts edited after publishing

@radar_piter edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
1 October 2026
Most recent edit
20 October 2026

Posts recorded as deleted after publishing

We recorded 69 posts on @radar_piter as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
9 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
23

Mentions

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

“Радар Санкт-Петербург” (@radar_piter), 52,052 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/radar_piter.

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.