Channel
@sluhmetroplus
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
751subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002875280722 |
|---|---|
| Type | Channel |
| Username | @sluhmetroplus |
| Description | Интересные новости кратко. Разборы. Критика Прислать новость: @prpmmcdbot Реклама, связь с редакцией: @reklama_pmmcd_bot Основной канал: @sluhmetro |
| Created | Between 1 June 2025 and 30 September 2025— 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/sluhmetroplus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:01 | 751 | no change |
| 7 Aug 2026, 17:58 | 751 | first reading |
14 posts held, back to 10 June 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.
| Window | Rolling 30 days · latest post in window 16 July 2026 |
|---|---|
| Posts held | 14 (10 June 2026 – 16 July 2026) |
| Views total | 316 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 02:01 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 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.
171 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 32.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5294358537412035472 | 55 | 32.2% | |
| custom 5291873611068489808 | 46 | 26.9% | |
| 😱 | 41 | 24.0% | |
| custom 5443095372291403318 | 24 | 14.0% | |
| 🤣 | 4 | 2.34% | |
| 🤯 | 1 | 0.585% |
Custom emoji. 3 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 13 of the 14 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 171reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 10 June 2026 to 16 July 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.
По предварительным данным, восстановление канала может занять неделю и более — и это при раскладе принятия решения о разблокировке. @monk, @durov, @durov_russia и @Telegram. Призываем вас о помощи, мы не совершали нарушений в @sluhmetro.
😱12
➡️ Мы создали резервный канал — @sluhmetroo. Там будем информировать о ситуации с каналом.
😱10
☄️☄️☄️ Думаем, что вы заметили, что пропал наш основной канал! Причина неизвестна, мы уже пытаемся восстановить к нему доступ.
😱17
⚡️ Теперь мы связали всю нашу сетку в единое сообщество! Это позволило новое обновление. Теперь вам достаточно нажать на иконку любого нашего канала в общем списке и будет возможно сразу в любой другой наш канал/чат. ➕ Подписаться на ПММЦД+ | Наши каналы
custom 544309537229140331813
Posted without readable text
🟨 В Московском метро заметили белую лисичку ➕ Подписаться на ПММЦД+ | Наши каналы
custom 529187361106848980810custom 54430953722914033181
👀 Хотите быть в курсе новостей о российском общественном транспорте? Тогда присоединяйтесь к нашему каналу «Транспорт РФ»! Ежедневно мы публикуем множество актуальных новостей, интересных фактов и инсайдерской информации, которые помогут вам быть в курсе всех событий. 🤩 Транспорт РФ | 💙 Мы во ВКонтакте
custom 52918736110684898085
🔈 Вещь, которая, к сожалению, не пошла в Московском метро — звук перед объявлением станции Его тестировали в 2022 году в поездах «Москва» и «Москва 2020», когда только появился аудиобренд Московского транспорта. Позже его убрали из-за «создания акустического мусора», так как лишний звук мешает при интервалах в 90 секунд. Но все же он был хорош. Например, если пассажир едет в наушниках, то звуковой сигнал мог отвле…
custom 529435853741203547219custom 54430953722914033182
🦌 Страшное крушение на станции Купавна 5 сентября 1975 года. Обычные плановые работы на съезде 2/4. Но из-за халатности пострадал не только состав и вагоны, но и люди. • Предыстория Для промывки электропривода требовалось отключить оба стрелочных перевода. В 10:30 было получено разрешение, и их отключили. Поэтому стрелки теперь можно было переводить только вручную, при этом сохранилась возможность пользования сигна…
custom 529435853741203547213😱2🤯1
🎉 Мы начинаем новый конкурс с интересными призами! Для участия необходимо подписаться на: 1. @sluhmetro 2. @sluhmetroplus 3. @TransMoscowChannel Призы: 1. Значок «Иволги 0.0» — в честь начала разработки первой телеграм-галереи 2. Случайный значок 3. Карта метро и ЖД Москвы 4. 5 префиксов в нашем чате 🍀 Итоги подведем 5 июля в 20:00. Удачи!
custom 52918736110684898089custom 54430953722914033185
🪣 ЭД4МКу – для чего нужен был изначально? Начнем с расшифровки: ЭД4МКу – Электропоезд Демиховский 4-й Модернизированный Комфортабельный улучшенный • Для чего и когда создавали? Всего было построенно 2 экспереремертальных состава (0151 и 0153). Они предзначались для перевозок на не более 700 км. Салон был более комфортным и в одном из вагонов был маленький ресторан. Также, там были впервые установленны прислонно-сдв…
custom 529187361106848980815custom 54430953722914033183
💍❓ Почему некоторые участки БМО неоднократно перестраивали? Выглядит как какая-то бессмыслица. Зачем один и тот же участок постоянно строить заново? На то есть причины: • Спрямление трассы. Из-за особенного рельефа путь имел резкие повороты и не совсем идеальный профиль, а в грузовом движении резкий поворот очень опасен, поэтому часть участков спрямили. • «Отвязка» от узловых станций: ранее было много узловых стан…
custom 52918736110684898086
Showing the 12 most recent of 14 posts we hold for @sluhmetroplus. 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 — 370,667 of 1,350,102entries 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.
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.
@sluhmetroplus named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“ПММЦД+” (@sluhmetroplus), 751 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/sluhmetroplus.
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.