25 Feb 2025, 09:31 UTCviews —
⚠️Брянск, внимание!⚠️ pinned «По техническим причинам канал временно заморожен»
Channel
⚠️Брянск, внимание!⚠️
@Bryansk_warning
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 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 | -1002388288910 |
|---|---|
| Type | Channel |
| Username | @Bryansk_warning |
| Description | Публикуем исключительно сообщения о беспилотниках и ракетной опасности в Брянске и области. (Идёт тестирование: возможны сообщения не по теме.) |
| Created | Between 1 September 2024 and 22 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Bryansk_warning |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 14:50 | 3 | no change |
| 7 Aug 2026, 14:34 | 3 | first reading |
Engagement
20 posts held, back to 22 February 2025 — 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 25 February 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 318
Lifetime counters from Telegram’s own channel header, read 13 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.
Recent posts
25 Feb 2025, 09:31 UTC42 viewsread 13 August 2026
По техническим причинам канал временно заморожен
24 Feb 2025, 18:31 UTC43 viewsread 13 August 2026
🚨 Белая Берёзка Брянская область опасность по БПЛА @bryansk_tyt
24 Feb 2025, 12:49 UTC42 viewsread 13 August 2026
🚨 Отбой авиационной ракетной бомбовой опасности @bryansk_tyt
24 Feb 2025, 12:44 UTC42 viewsread 13 August 2026
🚨 Возможно реактивный БПЛА от Суземки в направлении Брасово @bryansk_tyt
24 Feb 2025, 12:16 UTC41 viewsread 13 August 2026
🚨Брянская область - внимание по единичным БПЛА. @bryansk_tyt
24 Feb 2025, 11:58 UTC40 viewsread 13 August 2026
🚨 Авиационная ракетная бомбовая опасность Брянская область @bryansk_tyt
24 Feb 2025, 09:21 UTC38 viewsread 13 August 2026
🚨 Брянская область Авиационная ракетная бомбовая опасность @bryansk_tyt
23 Feb 2025, 21:35 UTC28 viewsread 13 August 2026
🚨Массированный налёт БПЛА! В небе от 40 БПЛА. Группы БПЛА замечены над Брянской, Курской, Орловской, Белгородской и Воронежской областями. По направлению БПЛА движутся в тыл. Об опасности сообщим. @bryansk_tyt
23 Feb 2025, 20:53 UTC22 viewsread 13 August 2026
🚨 Брянская область Опасность по БПЛА @bryansk_tyt
23 Feb 2025, 20:44 UTC21 viewsread 13 August 2026
🚨 От Комаричи в сторону Орла Внимание по БПЛА @bryansk_tyt
23 Feb 2025, 20:35 UTC20 viewsread 13 August 2026
🚨 Брянская область Внимание по БПЛА @bryansk_tyt
Showing the 12 most recent of 20 posts we hold for @Bryansk_warning. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“⚠️Брянск, внимание!⚠️” (@Bryansk_warning), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Bryansk_warning.
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.