9 Apr 2026, 19:20 UTC≈1,050 viewsread 7 August 2026
ОТБОЙ ОПАСНОСТИ АТАКИ БПЛА Белгородском МО 22:19.
Channel
РСЧСки
@rscs31
On this record: Growth · Engagement · Posts · Cite this entry
2,873subscribers
-23 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 | -1001996969757 |
|---|---|
| Type | Channel |
| Username | @rscs31 |
| Created | Between 1 October 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/rscs31 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 22:25 | 2,873 | -5 |
| 24 Aug 2026, 23:15 | 2,878 | -7 |
| 21 Aug 2026, 04:03 | 2,885 | -1 |
| 18 Aug 2026, 07:03 | 2,886 | -4 |
| 14 Aug 2026, 21:57 | 2,890 | -6 |
| 7 Aug 2026, 13:31 | 2,896 | no change |
| 7 Aug 2026, 12:21 | 2,896 | first reading |
Engagement
20 posts held, back to 6 April 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 pageof 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 9 April 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
9 Apr 2026, 19:12 UTC≈1,050 viewsread 7 August 2026
ОПАСНОСТЬ АТАКИ БПЛА в Белгородском МО 22:10. Оставайтесь дома, не подходите к окнам или пройдите в укрытие.
9 Apr 2026, 18:27 UTC≈1,080 viewsread 7 August 2026
ОПАСНОСТЬ АТАКИ БПЛА в Алексеевском, Валуйском, Вейделевском, Волоконовском, Красненском, Красногвардейском, Новооскольском, Ровеньском, Чернянском МО 21:25. Оставайтесь дома, не подходите к окнам или пройдите в укрытие.
9 Apr 2026, 05:26 UTC≈1,100 viewsread 7 August 2026
ОТБОЙ ОПАСНОСТИ АТАКИ БПЛА в Ракитянском и Белгородском МО 08:25.
8 Apr 2026, 12:34 UTC≈1,100 viewsread 7 August 2026
ОТБОЙ РАКЕТНОЙ ОПАСНОСТИ в Белгородской области 15:33.
8 Apr 2026, 12:09 UTC≈1,050 viewsread 7 August 2026
РАКЕТНАЯ ОПАСНОСТЬ в Белгородской области 15:07. Спуститесь в подвальное помещение или подземное пространство.
8 Apr 2026, 11:52 UTC897 viewsread 7 August 2026
ОТБОЙ ОПАСНОСТИ АТАКИ БПЛА в городе Белгороде 14:51.
8 Apr 2026, 11:47 UTC853 viewsread 7 August 2026
ОПАСНОСТЬ АТАКИ БПЛА в г. Белгороде 14:45. Оставайтесь дома, не подходите к окнам или пройдите в укрытие.
8 Apr 2026, 11:33 UTC803 viewsread 7 August 2026
ОПАСНОСТЬ АТАКИ БПЛА в Белгородском МО 14:31. Оставайтесь дома, не подходите к окнам или пройдите в укрытие.
8 Apr 2026, 09:09 UTC796 viewsread 7 August 2026
ОПАСНОСТЬ АТАКИ БПЛА в Ракитянском МО 12:09. Оставайтесь дома, не подходите к окнам или пройдите в укрытие.
8 Apr 2026, 03:27 UTC863 viewsread 7 August 2026
ОТБОЙ ОПАСНОСТИ АТАКИ БПЛА Валуйском МО 06:26.
7 Apr 2026, 09:03 UTC920 viewsread 7 August 2026
ОТБОЙ ОПАСНОСТИ АТАКИ БПЛА Белгородском МО 12:02.
Showing the 12 most recent of 20 posts we hold for @rscs31. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“РСЧСки” (@rscs31), 2,873 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/rscs31.
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.