Channel
@vasily_s_orlov
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3,921subscribers
-11 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001380146465 |
|---|---|
| Type | Channel |
| Username | @vasily_s_orlov |
| Created | 24 August 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/vasily_s_orlov |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 00:14 | 3,921 | -1 |
| 26 Aug 2026, 03:47 | 3,922 | -1 |
| 19 Aug 2026, 00:02 | 3,923 | -3 |
| 15 Aug 2026, 15:14 | 3,926 | -1 |
| 12 Aug 2026, 02:55 | 3,927 | -3 |
| 9 Aug 2026, 05:51 | 3,930 | -2 |
| 6 Aug 2026, 04:21 | 3,932 | no change |
| 5 Aug 2026, 22:45 | 3,932 | first reading |
8 posts held, back to 31 December 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof 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 8 posts for this entry, the most recent from 3 March 2022. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
Сейчас всем не до безопасности на дорогах и не до ДТП. Но все-таки выложу видео, над которым работал в последнее время, и которое закончил монтировать сегодня. В нем разбираю сложное и неоднозначное ДТП из Альметьевска. Девушку-водителя одной из машин могут несправедливо признать виновной. Скоро будет суд. Так что приглашаю к просмотру тех, кто хочет отвлечься от происходящего и посмотреть материал про ДТП. https://…
Кошмар, который сейчас происходит невозможно описать словами. Это преступление, которое совершает безумный и совершенно оторванный от реальности человек. Это настоящая катастрофа, которая обрушилась на наши две страны. Я против этого. Расхлебывать все это придется годами. #нетвойне
Photo, posted without a caption
Также выкладываю полные материалы аварии из московского района Солнцево:
Недавно блогер Стас Асафьев выпустил у себя на канале документальный фильм о ДТП и о том, чему на не научили в автошколах. В своем новом видео я хочу обсудить этот фильм Стаса, а также дополнить его информацией со своей стороны. https://youtu.be/DN7kgmDObQQ
Что нужно будет делать: - Разрабатывать новый и поддерживать текущий функционал сайта(классификация ДТП, карточки ДТП, отображение ДТП на карте и т.п.) - Работать надо будет непосредственно со мной. Я глубоко погружен в техническую часть проекта, часть кода пишу самостоятельно, а ревью делаю для всего кода проекта. - Я отвечаю за постановку задачи, за наполнение данными, а также частично за работу с базой данных.…
Ищем php-программиста на оплачиваемую работу для развития функционала сайта https://orlov-dtp.ru/. Далее подробное описание вакансии:
Photo, posted without a caption
Showing the 8 most recent of 8 posts we hold for @vasily_s_orlov. 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.
Citation-graph rank — 1,308,534 of 1,625,954entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Василий Орлов” (@vasily_s_orlov), 3,921 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/vasily_s_orlov.
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.