25 Feb 2022, 09:30 UTC≈5,370 viewsread 6 August 2026
Движение на Люблинско-Дмитровской линии (10) осуществляется в соответствии с графиком. — Московское метро (@MetroOperativno) 12:29:27, Feb 25, 2022
Channel
Metro Operativno
@metroOperativnos
On this record: Growth · Engagement · Posts · Citations · Cite this entry
298subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001357867919 |
|---|---|
| Type | Channel |
| Username | @metroOperativnos |
| Created | 19 June 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 20 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/metroOperativnos |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 18:36 | 298 | -3 |
| 6 Aug 2026, 22:32 | 301 | no change |
| 6 Aug 2026, 12:09 | 301 | first reading |
Engagement
20 posts held, back to 10 February 2022 — 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 25 February 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
25 Feb 2022, 09:17 UTC≈5,370 viewsread 6 August 2026
Движение на Люблинско-Дмитровской линии (10) восстановлено и вводится в график. — Московское метро (@MetroOperativno) 12:16:33, Feb 25, 2022
25 Feb 2022, 09:03 UTC≈5,420 viewsread 6 August 2026
На Люблинско-Дмитровской линии (10) нет движения поездов от станции «Селигерская» до «Петровско-Разумовской» из-за человека на пути. В обратном направлении поезда следуют с увеличенными интервалами. — Московское метро (@MetroOperativno) 12:03:39, Feb 25, 2022
22 Feb 2022, 07:24 UTC≈5,230 viewsread 6 August 2026
Движение на Арбатско-Покровской линии (3) осуществляется в соответствии с графиком. — Московское метро (@MetroOperativno) 10:24:13, Feb 22, 2022
22 Feb 2022, 07:07 UTC≈4,380 viewsread 6 August 2026
Движение на Арбатско-Покровской линии (3) вводится в график. — Московское метро (@MetroOperativno) 10:06:38, Feb 22, 2022
22 Feb 2022, 07:00 UTC≈3,630 viewsread 6 August 2026
На восточном участке Арбатско-Покровской линии (3) временно увеличены интервалы движения поездов для проверки состава. — Московское метро (@MetroOperativno) 09:59:39, Feb 22, 2022
22 Feb 2022, 05:01 UTC≈3,000 viewsread 6 August 2026
Движение на Большой кольцевой линии (11) осуществляется в соответствии с графиком. — Московское метро (@MetroOperativno) 08:00:19, Feb 22, 2022
22 Feb 2022, 04:22 UTC≈2,480 viewsread 6 August 2026
Движение на Большой кольцевой линии (11) вводится в график. — Московское метро (@MetroOperativno) 07:22:18, Feb 22, 2022
22 Feb 2022, 04:04 UTC≈2,040 viewsread 6 August 2026
На Большой кольцевой линии (11) временно увеличены интервалы движения поездов для проверки инфраструктуры на технической ветке в депо. — Московское метро (@MetroOperativno) 07:03:31, Feb 22, 2022
13 Feb 2022, 17:45 UTC≈1,740 viewsread 6 August 2026
Движение на Кольцевой линии (5) осуществляется в соответствии с графиком. — Московское метро (@MetroOperativno) 20:44:54, Feb 13, 2022
13 Feb 2022, 17:38 UTC≈1,580 viewsread 6 August 2026
Движение на Кольцевой линии (5) по направлению против часовой восстановлено и вводится в график. — Московское метро (@MetroOperativno) 20:38:36, Feb 13, 2022
13 Feb 2022, 17:30 UTC≈1,260 viewsread 6 August 2026
На Кольцевой линии (5) по направлению против часовой нет движения поездов из-за человека на пути. Для проезда, пожалуйста, пользуйтесь поездами в направлении по часовой и радиальными линиями. — Московское метро (@MetroOperativno) 20:29:30, Feb 13, 2022
Showing the 12 most recent of 20 posts we hold for @metroOperativnos. 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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Metro Operativno” (@metroOperativnos), 298 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/metroOperativnos.
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.