Telegram RegisterThe public register of Telegram
Telegram profile photo for Угроза БПЛА СПБ

Channel

Угроза БПЛА СПБ

@UgrozaBplaSpb

On this record: Growth · Engagement · Posts · Cite this entry

241subscribers

+19 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003275922627
TypeChannel
Username@UgrozaBplaSpb
CreatedBetween 1 October 2025 and 28 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/UgrozaBplaSpb

Growth

222241231.57 August 2026 — 222 subscribers8 August 2026 — 222 subscribers16 August 2026 — 238 subscribers24 August 2026 — 241 subscribers7 August 202624 August 2026
4 measurements spanning 17 days, net +19. 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 219–244 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 13:59241+3
16 Aug 2026, 20:09238+16
8 Aug 2026, 10:32222no change
7 Aug 2026, 19:22222first reading

Engagement

20 posts held, back to 24 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
107.1%
avg views ÷ 241 subscribers
Avg views / post
258
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 20 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 4 August 2026
Posts held20 (24 July 20264 August 2026)
Views total2,323
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:32 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.

Recent posts

4 Aug 2026, 04:17 UTC276 viewsread 8 August 2026

Сильный пожар на складе «Wildberries» под Санкт-Петербургом, Красный Бор после атаки БПЛА. ⏺ Угроза БПЛА СПБ

4 Aug 2026, 04:15 UTC274 viewsread 8 August 2026

Ленинградская область Отбой опасности по БПЛА ⏺ Угроза БПЛА СПБ

4 Aug 2026, 03:10 UTC218 viewsread 8 August 2026

Станция Слудицы, Гатчинский район, Ленинградская область Пролёт от 2 БПЛА в сторону Вырицы ⏺ Угроза БПЛА СПБ

4 Aug 2026, 03:10 UTC231 viewsread 8 August 2026

Кириши и близлежащие Ленинградская область Опасность по БПЛА ⏺ Угроза БПЛА СПБ

4 Aug 2026, 03:10 UTC250 viewsread 8 August 2026

Санкт-Петербург Опасность по БПЛА ⏺ Угроза БПЛА СПБ

4 Aug 2026, 03:10 UTC279 viewsread 8 August 2026

Тосненский район Ленинградская область Меры безопасности ⏺ Угроза БПЛА СПБ

4 Aug 2026, 03:10 UTC285 viewsread 8 August 2026

Тосненский район Ленинградская область Работа ПВО по БПЛА Меры безопасности ⏺ Угроза БПЛА СПБ

4 Aug 2026, 03:10 UTC284 viewsread 8 August 2026

Над территорией Ленинградской области сбиты 15 БПЛА Работа ПВО по БПЛА продолжается ⏺ Угроза БПЛА СПБ

4 Aug 2026, 01:21 UTC226 viewsread 8 August 2026

Ленинградская область - внимание по БПЛА ⏺ Угроза БПЛА СПБ

28 Jul 2026, 06:30 UTC478 viewsread 8 August 2026

Ленинградская область Отбой опасности по БПЛА ⏺ Угроза БПЛА СПБ

28 Jul 2026, 04:57 UTC455 viewsread 8 August 2026

Ленинградская область Опасность по БПЛА ⏺ Угроза БПЛА СПБ

28 Jul 2026, 04:57 UTC469 viewsread 8 August 2026

Волосово, Ленинградская область - пролёт БПЛА в сторону Усть-Луга. ⏺ Угроза БПЛА СПБ

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

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

“Угроза БПЛА СПБ” (@UgrozaBplaSpb), 241 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/UgrozaBplaSpb.

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.