Channel
@russian_sos
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002479635331 |
|---|---|
| Type | Channel |
| Username | @russian_sos |
| Created | 23 October 2024 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/russian_sos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 23:16 | 4 | -1 |
| 16 Aug 2026, 17:05 | 5 | +1 |
| 13 Aug 2026, 04:17 | 4 | no change |
| 8 Aug 2026, 00:30 | 4 | first reading |
4 posts held, back to 23 October 2024 — 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 4 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
💬 В Telegram запустили лицензионную игру @JetTon ➕ Без регистрации и ВПН, можно играть прямо в мессенджере ➕ Бонус до 175 000 рублей + 200 Фриспинов новым игрокам ➕ Возможность пополнения любой криптовалютой (BTC/Ton/USDT) и фиатом - картами ➕ Моментальный вывод выигрыша без ограничений ➕ Проекту доверяют уже более 3.5 млн игроков Переходи по кнопке и получи приветственный бонус 👇
Channel created
Showing the 4 most recent of 4 posts we hold for @russian_sos. 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.
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.
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.
“russian_sos” (@russian_sos), 4 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/russian_sos.
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.