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

Channel

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

@UgrozaBplaSpb

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

1,392subscribers

+1,170 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

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

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

2221,415818.57 August 2026 — 222 subscribers8 August 2026 — 222 subscribers16 August 2026 — 238 subscribers24 August 2026 — 241 subscribers31 August 2026 — 247 subscribers10 September 2026 — 256 subscribers18 September 2026 — 258 subscribers3 October 2026 — 250 subscribers13 October 2026 — 245 subscribers21 October 2026 — 1,352 subscribers24 October 2026 — 1,379 subscribers27 October 2026 — 1,401 subscribers30 October 2026 — 1,413 subscribers2 November 2026 — 1,415 subscribers5 November 2026 — 1,412 subscribers8 November 2026 — 1,410 subscribers13 November 2026 — 1,401 subscribers18 November 2026 — 1,392 subscribers1,3927 August 202618 November 2026
18 measurements spanning 103 days, net +1,170. 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 43–1,594 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 18:081,392-9
13 Nov 2026, 14:071,401-9
8 Nov 2026, 17:571,410-2
5 Nov 2026, 04:301,412-3
2 Nov 2026, 13:361,415+2
30 Oct 2026, 10:471,413+12
27 Oct 2026, 01:181,401+22
24 Oct 2026, 11:081,379+27
21 Oct 2026, 09:061,352+1,107
13 Oct 2026, 13:09245-5
3 Oct 2026, 20:14250-8
18 Sept 2026, 03:57258+2
10 Sept 2026, 03:40256+9
31 Aug 2026, 20:06247+6
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 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

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

“Угроза БПЛА СПБ” (@UgrozaBplaSpb), 1,392 subscribers as measured 18 November 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.