Channel
@DtOperativno
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
113,531subscribers
+218 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001031559169 |
|---|---|
| Type | Channel |
| Username | @DtOperativno |
| Description | Оперативная информация обо всем, что происходит в московском транспорте. Официальный канал Дептранса Для запросов СМИ 24/7: +7 925 072-19-33, Информационный центр Транспортного комплекса Москвы. Регистрация в перечне РКН: https://clck.ru/3F7rAe |
| Created | 24 February 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/DtOperativno |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 10:16 | 113,531 | +370 |
| 6 Sept 2026, 01:39 | 113,161 | +52 |
| 3 Sept 2026, 19:58 | 113,109 | +13 |
| 2 Sept 2026, 08:14 | 113,096 | -12 |
| 1 Sept 2026, 11:47 | 113,108 | -7 |
| 31 Aug 2026, 09:13 | 113,115 | +24 |
| 30 Aug 2026, 11:19 | 113,091 | +35 |
| 29 Aug 2026, 07:43 | 113,056 | -12 |
| 28 Aug 2026, 08:53 | 113,068 | -22 |
| 27 Aug 2026, 11:12 | 113,090 | +5 |
| 26 Aug 2026, 10:33 | 113,085 | -19 |
| 25 Aug 2026, 10:33 | 113,104 | -15 |
| 24 Aug 2026, 12:28 | 113,119 | -17 |
| 22 Aug 2026, 17:02 | 113,136 | -34 |
| 21 Aug 2026, 06:27 | 113,170 | -21 |
| 20 Aug 2026, 09:42 | 113,191 | -14 |
| 19 Aug 2026, 09:54 | 113,205 | -15 |
| 18 Aug 2026, 11:03 | 113,220 | -10 |
| 17 Aug 2026, 09:58 | 113,230 | -22 |
| 15 Aug 2026, 15:27 | 113,252 | first reading |
529 posts held, back to 4 August 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 73 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 10 September 2026 |
|---|---|
| Posts held | 529 (4 August 2026 – 10 September 2026) |
| Views total | 3,645,740 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 05:17 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 10 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 41 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.
Доброе утро! Сегодня в городе солнечно и тепло. В вечерний разъезд возможны затруднения движения в центре города, на ТТК, МКАД и вылетных магистралях по направлению в область. Не отвлекайтесь на телефон во время движения. Хорошего дня!
Движение на внешней стороне 30 км МКАД восстановлено.
В городе вечерний разъезд, а также временные локальные перекрытия в центре. По возможности для поездок используйте метро. Сейчас временно закрыто движение: 🔹 На Тверской улице перед Моховой улицей. 🔹 На Боровицкой площади. 🔹 На Москворецкой набережной перед Китайгородским проездом. Если вы на авто, то рекомендуем строить маршрут заранее и сверяться с навигатором.
❗️На внешней стороне 30 км МКАД (в районе съезда №30В) произошло возгорание автомобиля. На месте работают оперативные службы города. Обстоятельства произошедшего и информация о пострадавших уточняются. Движение по внешней стороне МКАД перекрыто. Пожалуйста, выбирайте пути объезда.
C 12 cентября меняются остановки у метро «Планерная» для пригородных маршрутов проекта «Москва — область»: 🔹 У маршрута 1383 переносится посадка на остановку 1Р, режим работы маршрута будет продлен до 23:30. 🔹 У маршрутов 1383 и 1971 добавляется остановка «Метро «Планерная» 1J.
ЦОДД: переносится дата изменения схемы движения на Шелепихинской набережной в Пресненском районе. С 10 сентября временный разворот в районе Шелепихинского шоссе по-прежнему будет доступен. О новой дате изменений сообщим дополнительно. Следите за актуальной информацией в телеграм-канале «Дептранс. Оперативно». Будьте внимательны и заранее планируйте маршрут с учетом изменений.
Сегодня в Текстильщиках на западном (Остаповском) путепроводе открыли двустороннее движение. Теперь при движении с МСД и внешней стороны ТТК можно воспользоваться новым разворотом и проехать в промзону и в северную часть Текстильщиков. Это второй этап новой схемы движения в районе. Благодаря изменениям: 🔹 движение между ТТК и Люблинской улицей будет распределяться равномернее 🔹 улучшатся условия для движения авто…
Сегодня около 8:31 на Мичуринском проспекте, у дома 80, произошло ДТП с участием двух автомобилей и электробуса 793, который стоял на остановке. В электробусе пострадавших нет. Подробности происшествия устанавливают сотрудники Госавтоинспекции.
Доброе утро! В городе заметно потеплело. По прогнозам синоптиков, сегодня будет облачно с прояснениями. Просим водителей следить за самочувствием в поездке. При первых признаках усталости или недомогания за рулем — прекратите движение и остановитесь в безопасном месте. Хорошего и бодрого дня 💚
Движение открыто.
Движение временно закрыто: 🔹 На Большом Каменном мосту по направлению в центр. 🔹 На Тверской улице по направлению в центр. 🔹 На Кремлевской набережной в центр.
Сегодня около 13:56 на Дмитровском шоссе, в районе д. 49, произошло ДТП с участием легкового и грузового автомобилей. Момент ДТП.
Showing the 12 most recent of 529 posts we hold for @DtOperativno. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 221 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 102 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
5 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Дептранс. Оперативно” (@DtOperativno), 113,531 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/DtOperativno.
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.