События на МЖД и за её пределами
По рекламе и остальным вопросам: @MironovZbc
Ваш контент @Electrichkalive_bot
РКН №5220516434
ВК: https://vk.com/elektrichki_moskva
За материалы от подписчиков канал ответственности не несет 18+
Created
13 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
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 20 August 2026 and assigned it the closest of 31 fixed categories, at 64% 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 the other topics.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
63 measurements spanning 96 days, net +324. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 63,373–64,068 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)
Subscribers
Change
10 Nov 2026, 06:28
63,798
+13
8 Nov 2026, 20:56
63,785
-22
7 Nov 2026, 11:06
63,807
-8
6 Nov 2026, 10:15
63,815
-19
5 Nov 2026, 13:38
63,834
-13
4 Nov 2026, 10:19
63,847
-7
3 Nov 2026, 13:19
63,854
-12
2 Nov 2026, 13:39
63,866
-22
1 Nov 2026, 12:20
63,888
-21
31 Oct 2026, 12:35
63,909
+13
30 Oct 2026, 11:47
63,896
-21
29 Oct 2026, 11:07
63,917
+41
28 Oct 2026, 10:55
63,876
-15
27 Oct 2026, 07:39
63,891
+12
26 Oct 2026, 07:16
63,879
+7
25 Oct 2026, 05:57
63,872
+3
24 Oct 2026, 08:20
63,869
-4
23 Oct 2026, 11:40
63,873
-9
22 Oct 2026, 11:57
63,882
-5
21 Oct 2026, 06:48
63,887
first reading
Engagement
192 posts held, back to 1 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 222 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
30.8%
avg views ÷ 63,798 subscribers
Avg views / post
19,700
34 posts measured
Reaction rate
0.942%
reactions ÷ views · ER floor
Posts in window
34
of 192 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 10 November 2026
Posts held
192 (1 August 2026 – 10 November 2026)
Views total
668,870
Reactions total
6,302
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Nov 2026, 19:20 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.
What this channel posts
Photos
≈6,870
Videos
≈3,500
Links
≈5,590
Lifetime counters from Telegram’s own channel header, read 10 November 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.
Video runtime
24m 45s
Average length
22s
Measured directly from 69 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.
Reaction mix
30,434 reactions across 191 posts, in 50 distinct kinds. The most used accounts for 23.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
7,212
23.7%
😡
5,595
18.4%
👍
2,830
9.30%
🤯
1,866
6.13%
💊
1,856
6.10%
😱
1,801
5.92%
😢
1,284
4.22%
🔥
1,206
3.96%
❤🔥
824
2.71%
🤪
805
2.65%
😨
638
2.10%
🕊
450
1.48%
🤔
390
1.28%
🙏
381
1.25%
💔
295
0.969%
😭
262
0.861%
👏
251
0.825%
🥰
251
0.825%
🫡
224
0.736%
🌚
220
0.723%
30 further kinds
1,793
5.89%
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 192 of the 192 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 30,515 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 192 most recent posts we hold, published 1 August 2026 to 10 November 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.
Telegram Stars
Stars received
17
across the posts below
Posts paid on
15
of 192 we hold a reading for · 8%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @electrichki. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 192 most recent posts we hold for this entry, published 1 August 2026 to 10 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 9 of 34 posts held from the last 30 days (26.5%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
❗️Небольшой сбой на Горьковском направлении.
📆 Сегодня на перегоне Павловский Посад — Фрязево произошла остановка одиночного тепловоза.
🔜 Около 14:00 по I пути остановился локомотив. Точная причина остановки пока неизвестна.
🚂 Локомотивная бригада вызвала вспомогательный тепловоз для оказания помощи.
🔜 Около 16:00 движение по I пути было восстановлено.
⚠️ В результате неисправности тепловоза были зафиксированы т…
🚃 В Бутово на МЦД-2 замечена ЭП2Д из будущего!
😏 Получается, ЭП2Д будут курсировать как минимум до 2043 года. 🔮
Похоже, эти поезда ещё долго не собираются уходить на покой! 👍
Подслушано электрички Москвы
😆Найдено электрички Москвы
🇷🇺 ПЭМ в MAX
🇷🇺 Электрички Live
💙 ПЭМ в ВК
😌Предложить свою новость
🦌 Время сбрасывать рога наступило не только у северных оленей, но и у местных ЭП2Д! 😁
🍂 Осень для наших электропоездов наступает по-своему! 🚆
Подслушано электрички Москвы
😆Найдено электрички Москвы
🇷🇺 ПЭМ в MAX
🇷🇺 Электрички Live
💙 ПЭМ в ВК
😌Предложить свою новость
❗️ Сбой на Ярославском направлении.
🐶 Электропоезд ЭД4М-0159 сообщением Балакирево — Москва Ярославская (поезд № 6305) следует с задержкой.
⏱ Опоздание составляет до 20 минут.
📍 Причина задержки — пропуск пассажирского поезда на станции Сергиев Посад.
☑ Задержек остальных поездов, следующих в сторону Москвы, не наблюдается.
Подслушано электрички Москвы
😆Найдено электрички Москвы
🇷🇺 ПЭМ в MAX
🇷🇺 Электрички Live
💙…
❗️🫎 Наезд на лося на Казанском направлении!
⏰ Сегодня около 16:50 электропоезд ЭД4М-0193, следовавший по маршруту «Черусти — Москва Казанская» (поезд № 6841), совершил наезд на лося.
📍 Инцидент произошёл на перегоне Гжель — Овражки.
⏱️ В результате происшествия на данный момент поезд задерживается до 50 минут.
🐶 После случившегося электропоезд доехал до Овражек и на данный момент находится по станции.
Подслуша…
😳 Не совсем понятно, что произошло и за что человека так сильно толкнули, что он буквально вылетел с платформы…
👨🦽 К сожалению, что было дальше — неизвестно. Очень надеемся, что он не получил серьёзных травм и с ним всё хорошо 🙏
🤔 А тому, кто толкнул человека, стоит задуматься о последствиях своих действий. Прежде чем что-то сделать, нужно включать голову! ⚠️
❗️Одно необдуманное действие может обернуться настояще…
❗️Сбой на МЦД-2: наезд на человека
🤩 На перегоне Тушино — Подмосковная, по второму главному пути, под электропоезд ЭП2Д-0034 «РЭКС», следовавший по маршруту Шаховская — Люблино (поезд № 7152/7151), попал мужчина.
👨 Благодаря своевременной реакции машиниста, применившего экстренное торможение, мужчина остался жив.
⏱ Задержка поездов составила до 25 минут.
⚠️ Уважаемые пассажиры! Будьте внимательны и осторожны на ж…
💍 Ретро-электричка СР3-1668 замечена на ВНИИЖТ!
🗓 Сегодня, 07.11.2026, на Экспериментальном кольце ВНИИЖТ целый день курсировал настоящий железнодорожный раритет — электропоезд СР3-1668!
▶️ Как сообщает наш подписчик, на территории института проходили съёмки фильма. К сожалению, какой именно фильм снимали, не известно. 🎥
📖 Немного истории
🇱🇻 Электропоезда серии СР3 — настоящая классика советского пригородного соо…
🚞 В Клину установили первую 700-тонную балку для ВСМ Москва — Санкт-Петербург
✔️ В Клину успешно провели тестовый монтаж первой железобетонной мостовой балки для высокоскоростной железнодорожной магистрали (ВСМ).
🏗️ Масштабы конструкции впечатляют:
🔹 Масса пролёта — 700 тонн.
🔹 Длина — более 32 метров.
🔹 Монтаж выполнен над автомобильной дорогой.
Об этом сообщили в пресс-службе РЖД.
🚅 Строительство ВСМ продолжает…
❗️ Зажатие человека на станции Лесной Городок Киевского направления МЖД.
🚅 Электропоезд «Иволга» ЭГЭ2ТВ-059, следовавший по маршруту Железнодорожная — Апрелевка (поезд № 7579), находился на 1-м пути.
⚠️ Между первым вагоном электропоезда и пассажирской платформой оказался зажат человек.
🚑 На место происшествия была вызвана бригада скорой медицинской помощи.
Информация о состоянии и дальнейшей судьбе пострадавшего…
❗️На МЦД-3 изменится расписание поездов: интервалы увеличат, последние рейсы отменят раньше
В предстоящие выходные, 7 и 8 ноября, пассажиров МЦД-3 ждут изменения в расписании.
⚠️Что изменится:
🔹 В отдельные периоды интервалы движения поездов увеличат до 20 минут.
🔹 На станции Митьково интервал может достигать 30 минут.
🔹 Сократится время работы поездов на участке Зеленоград-Крюково — Ипподром.
🔹 Последние поезд…
❗️ Вандализм на Ярославском направлении!
Вернёмся к теме вандализма на Ярославском направлении.
ЦППК старается радовать пассажиров, выпуская красивые поезда с тематической оклейкой и необычным оформлением. Но, к сожалению, вандалам, похоже, совершенно безразличны старания компании. 😡
📸 Очередной пример — изуродованная тематическая «Иволга», посвящённая 20-летию ЦППК. Пострадал состав № 077.
🚅 Сейчас поезд следует…
😡209❤30😱30💊8🔥8🤔3🤪3😍2
Showing the 12 most recent of 192 posts we hold for @electrichki. 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.
Posts edited after publishing
@electrichki edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
12 August 2026
Most recent edit
30 September 2026
Posts recorded as deleted after publishing
We recorded 35 posts on @electrichki as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
7 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
31 hours
Seen missing in the last 30 days
11
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 19 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.
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.
Channels Telegram recommends alongside this one
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.
РМТМ | «Развитие Метрополитена и Транспорта Москвы» @razvitie_metro_msk · 15,888#1
Read from Telegram’s recommendation API, most recently 21 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.
Appears in Telegram’s recommendations for other channels
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.
Дептранс. Оперативно @DtOperativno · 113,307 Telegram ranks this channel #3 of 91 here — alongside 90 others — read 14 August 2026
PRO МЕТРО @pro_metro · 54,117 Telegram ranks this channel #4 of 82 here — alongside 81 others — read 24 August 2026
Подслушано Метро Москвы @pmmgo1 · 84,098 Telegram ranks this channel #6 of 86 here — alongside 85 others — read 18 August 2026
Телеграмма РЖД @telerzd · 68,011 Telegram ranks this channel #7 of 93 here — alongside 92 others — read 20 August 2026
Раменское @ramenskoe24 · 69,343 Telegram ranks this channel #20 of 35 here — alongside 34 others — read 20 August 2026
Подольск @podolsk24life · 54,537 Telegram ranks this channel #24 of 40 here — alongside 39 others — read 23 August 2026
Глаз Москвы • Новости @glaz_moscow · 93,311 Telegram ranks this channel #35 of 91 here — alongside 90 others — read 16 August 2026
Балашиха Life 💛 @balashikha_life · 52,134 Telegram ranks this channel #38 of 56 here — alongside 55 others — read 27 August 2026
Дептранс Москвы @DtRoad · 142,235 Telegram ranks this channel #41 of 92 here — alongside 91 others — read 12 August 2026
Мои Люберцы ®️ @myluber · 109,341 Telegram ranks this channel #51 of 66 here — alongside 65 others — read 15 August 2026
ДТП и ЧП МОСКВА и МО @dtp777 · 140,782 Telegram ranks this channel #66 of 88 here — alongside 87 others — read 13 August 2026
Я❤️Москву @ilove_moscow · 106,377 Telegram ranks this channel #70 of 88 here — alongside 87 others — read 14 August 2026
Моя Москва @moscow_smi · 115,956 Telegram ranks this channel #71 of 76 here — alongside 75 others — read 14 August 2026
Наша колея 1520 @NashaKoleya · 45,701 Telegram ranks this channel #80 of 93 here — alongside 92 others — read 25 August 2026
This channel appears in 14 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Referenced elsewhere
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
One Wikipedia article names 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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Подслушано электрички Москвы” (@electrichki), 63,798 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/electrichki.
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.