Channel
@D4_Moscow
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
198subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004386619944 |
|---|---|
| Type | Channel |
| Username | @D4_Moscow |
| Description | Неофициальное сообщество про МЦД-4 (Калужско-Нижегородский диаметр), здесь вы увидите посты, связанные с этими направлениями (опоздания, изменения в графике движения и т. д.) Предложить новость/купить спонсорство/сотрудничество: @D4_Moscow_Bot |
| Created | Between 1 June 2026 and 30 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/D4_Moscow |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:34 | 198 | no change |
| 7 Aug 2026, 19:43 | 198 | first reading |
20 posts held, back to 30 July 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.
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. It is computed over the 19 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (30 July 2026 – 8 August 2026) |
| Views total | 7,361 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 11:34 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 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 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.
46 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 23.9% | |
| custom 5327994672574916994 | 6 | 13.0% | |
| custom 5395436748727660802 | 5 | 10.9% | |
| custom 5456271039170363072 | 5 | 10.9% | |
| ❤🔥 | 4 | 8.70% | |
| 😁 | 4 | 8.70% | |
| custom 5199963578676846236 | 2 | 4.35% | |
| custom 5213265663623205060 | 2 | 4.35% | |
| 👍 | 2 | 4.35% | |
| 🥱 | 2 | 4.35% | |
| custom 5318778819513950243 | 1 | 2.17% | |
| 😱 | 1 | 2.17% | |
| 🥰 | 1 | 2.17% |
Custom emoji. 6 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 July 2026 to 8 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
‼️Пассажиры МЦД-4 и Горьковского направления! ⏰ С 14 по 16 и с 28 по 30 августа будет существенно изменено расписание поездов МЦД-4 и Горьковского направления. ❌ Значительная часть поездов проследует измененным расписанием, ряд поездов будет отменен или сокращен от/до ст. Нижегородская, Площадь трех вокзалов и других станции. ‼️Обращаем Ваше внимание, что изменения в расписании будут распространяться и на пиковый …
Спокойной ночи 🌛! 4️⃣ МЦД-4 | Прислать новость? Сотрудничество?
❤3
Московские пассажиры назвали ЭП2Д «Корольком» Поезда ЭП2Д и ЭП2ДМ, работающие на Московских центральных диаметрах и Ярославском направлении, получили новое название – «Королек». Такое имя выбрали участники голосования на портале «Активный гражданин», в котором приняли участие более 136 тысяч человек, сообщил мэр Москвы Сергей Собянин. Ранее РЖД уже подвели итоги собственного голосования и присвоили этим же поездам …
🥱2
😕😕😕😕 Снова "Иволга" во Владимире ЭГЭ2Тв-090, которая стала последней "Иволгой 4.0", сейчас проходит испытания на участке от Москвы до Владимира для тестирования нового тормозного оборудования, а вернее отечественных блоков дисковых тормозов. 😕 Поездок состоится несколько, в том числе стоит ожидать обкатку и ровно через неделю, а выбор места для проведения испытаний, вероятно, основывается на том, что значительная ч…
❤🔥4
😕 🚆 Ночные приключения на D4, случившиеся из-за неисправности электропоезда. 😕 За 40 минут до полуночи «Сарай смерти» за номером ЭД4М-0458 расписанием 6843 Захарово — Апрелевка решил «умереть» по платформе Матвеевская. С 23:20 было остановлено движение по 1 пути от Москвы-Сортировочной (Минской) — Очаково на Апрелевку на неопределенное время. В итоге поезда 7409 и 6841, вышедшие на перегон за 6843, были задержаны б…
🔞 ОСТОРОЖНО МАТ! Будни пассажиров МЦД4! 4️⃣ МЦД-4 | Прислать новость? Сотрудничество?
❤2😱1
😕😕😕😕 МЦД поедет еще дальше? Московские центральные диаметры хотят продлить за пределы Подмосковья — в планах Тульская, Владимирская, Ярославская области и другие соседние регионы. О таких планах рассказал мэр Москвы Сергей Собянин. По его словам, проект сможет сделать поездки удобнее для 30+ миллионов жителей Центральной России. Если планы реализуют, добраться до столицы и обратно станет проще и быстрее. 4️⃣ МЦД-4 …
😁3
💧 Пассажирам электричек бесплатно раздают воду на московских вокзалах из-за жары Получить воду можно с 14:00 до 17:00 на Белорусском, Казанском, Киевском, Курском, Павелецком, Савеловском и Ярославском вокзалах, а также на станциях МЦД Тушинская и Площади трёх вокзалов. 4️⃣ МЦД-4 | Прислать новость? Сотрудничество?
👍2
Причина сбоя: 😕 Поезд №6743 Крутое - Лесной Городок остановился на перегоне Павловский Посад - Фрязево из-за неисправности ЭП2Д-0018, что спровоцировало временную приостановку движения по 1 пути на Москву. Пассажиров высадили на остановочном пункте Казанское, а электричку вызволили вспомогательным локомотивом. 😕😕😕😕😕😕😕 В 15:50 движение возобновили, несколько поездов отменили, а опоздания составляют около часа. 4️⃣ …
custom 54562710391703630725custom 53279946725749169942
🚆 Возобновлено движение поездов дальнего пригорода Нижегородского направления на участке Павловский Посад — Фрязево по 1 пути (на Москву). Ожидаются задержки электропоездов на Москву / Апрелевку и обратно по обороту, а также сокращения маршрутов и внеплановые отмены. 4️⃣ МЦД-4 | Прислать новость? Сотрудничество?
custom 52132656636232050601
❌🚆 Нет движения поездов дальнего пригорода Нижегородского направления на участке Павловский посад — Фрязево по 1 пути (на Москву). Ожидаются задержки электропоездов на Москву / Апрелевку и обратно по обороту, а также сокращения маршрутов и внеплановые отмены. 4️⃣ МЦД-4 | Прислать новость? Сотрудничество?
custom 51999635786768462361
😕🔥😕😕 ВОЗГОРАНИЕ ЭД4М -137 в Калужской области 😕 Электричка ЭД4М-0137, следующая поездом №6135 Калуга-1 - Сухиничи-Главные, к моменту следования по перегону Бабынино - Кудринская постепенно набрала 13 минут опоздания, после чего на станции пришлось задержаться для осмотра состава. После проверки было выявлено задымление подвагонного оборудования моторного вагона 06, далее пассажиров высадили. Для их вывоза с Калуги …
❤4
Showing the 12 most recent of 20 posts we hold for @D4_Moscow. 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 — 851,136 of 1,160,990entries 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.
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 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“МЦД-4 | Апрелевка-Железнодорожная” (@D4_Moscow), 198 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/D4_Moscow.
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.