4 measurements spanning 7 days, net +8. 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 2,206–2,217 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 20:44
2,216
+4
10 Aug 2026, 00:28
2,212
+5
6 Aug 2026, 21:06
2,207
-1
6 Aug 2026, 07:05
2,208
first reading
Engagement
12 posts held, back to 13 July 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
139.0%
avg views ÷ 2,216 subscribers
Avg views / post
3,080
1 post measured
Reaction rate
3.21%
reactions ÷ views · ER floor
Posts in window
1
of 12 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 23 July 2026
Posts held
12 (13 July 2024 – 23 July 2026)
Views total
3,080
Reactions total
99
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:51 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.
Reaction mix
1,178 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 44.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5449442513616121857
521
44.2%
custom 5330547699919888388
188
16.0%
😨
161
13.7%
custom 5215185140342334577
146
12.4%
custom 5210956306952758910
68
5.77%
🤔
44
3.74%
🕊
31
2.63%
custom 5460704463327074557
16
1.36%
🤬
3
0.255%
Custom emoji. 5 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 12 of the 12 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 1,178reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 13 July 2024 to 23 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.
Telegram Stars
Stars received
38
across the posts below
Posts paid on
6
of 12 we hold a reading for · 50%
Most on one post
20
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TrackMap. 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 12 most recent posts we hold for this entry, published 13 July 2024 to 23 July 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.
Где чаще ходят поезда?
🛞 / Релиз новой схемы
Отвлечёмся от темы метро, и устроим небольшой оффтоп на тему электричек)
Когда-то я задался вопросом, насколько вообще просто уехать на электричке с различных платформ, учитывая богатое путевое развитие центрального московского узла? Какие направления считаются самыми загруженными, и что происходит на них в разных частах?
Вдохновившись схемой «Тысяч пассажиров в метро»,…
Moscow Metro Track Map
🚇 v6.08 / Новые перспективные планы по строительству метро
Схема доступна для просмотра на trackmap.msk.ru
– Новые планы по строительству метро после 2030 года:
• Переименования проектных станций
• Бирюлёвская/Рокадная линия
• Продление Филёвской линии
• Актуализированы прочие планы на далёкую перспективу
– Переписан алгоритм сайта, теперь сайт стал легковеснее. Исправлена ошибка с от…
Moscow Metro Track Map
🚇 v5.37 / Открытие участка Троицкой линии (16) «Вавиловская» — «ЗИЛ»
Схема доступна для просмотра на trackmap.msk.ru
upd – v5.37a: Исправлены тупики на «ЗИЛе», прочие изменения
🚇 @trackmap
Moscow Metro Track Map
🚇 v5.32 / Открытие депо ТЧ-23 «Столбово»
Схема доступна для просмотра на trackmap.msk.ru
- Открытие депо ТЧ-23 Столбово
- Ещё раз скорректирована перспектива Троицкой линии (16)
- Прочие дополнения
🚇 @trackmap
🚇 🌐 Потихоньку продолжаю работать над сайтом 🤨
– Новый дизайн шапки!
Вместо единой шапки теперь у каждого элемента собственная подложка.
– Теперь схема точно должна нормально открываться через Safari на любых яблочных устройствах. Больше не должно быть проблемы с тем, что схема криво отображается, особенно на макбуках.
– Небольшие, но очень приятные улучшения
Сайт научился определять трекпад ноутбука, и будет плав…
В одном из сервисов для просмотра схемы метро выпустили московские схемы разных годов, довольно любопытно потыкать и построить маршруты
Ещё давно у меня была идея сделать такое же и для trackmap, но руки к сожалению так и не дошли, но когда-нибудь обязательно доделаю🤥
🥳 Тем не менее, поздравляю всех с 90-млетием Московского метрополитена! 🎉
Moscow Metro Track Map
🚇 v5.19 / Открытие корпуса «Южное» ТЧ-17 «Братеево»
Схема доступна для просмотра на trackmap.msk.ru
- Скорректированы планы Троицкой линии (16).
- Убраны отдалённые перспективы до появления обновлённых проектов.
- Внесено множество небольших исправлений.
Ожидаем ближайшего открытия нового корпуса «Братеево», и потихоньку дорабатываем схему 🙃
🚇 @trackmap
Moscow Metro Track Map (🔄)
🚇 v4.53 / Продление Троицкой линии до Новомосковской.
Схема доступна для просмотра на trackmap.msk.ru
- Схема увеличена по высоте
- Открытый участок Троицкой линии (16) до Новомосковской
- Добавлено проектируемое продление Бирюлёвской линии (18) до ЭКСПО и предполагаемое соединение с Рублёво-Архангельской линией (17).
- Имеющиеся проектируемые участки перерисованы в соответствии с обновлё…
Moscow Metro Track Map
🚇 v4.34 / с 5 сентября '24.
Схема доступна для просмотра на trackmap.msk.ru
- С начала сентября открывается станция "Потапово" Сокольнический линии (1) и пусковой участок Троицкой линии (16).
- Небольшие изменения, связанные со шрифтом названий станций.
Теперь вы можете поддержать меня напрямую через telegram, оставив звёздную реакцию, если вам нравится схема. Буду очень признателен! 🥰🙏
🚇 @…
🚇 После обновления сайта, какой способ и систему вы используете для просмотра схемы?
🤖🔗 Android — Сайт48%
🤖📁 Android — PDF/PNG Файлы49%
🍏🔗 iOS/iPadOS — Сайт16%
🍏📁iOS/iPadOS — PDF/PNG Файлы19%
📺🔗 MacOS/Windows/PC — Сайт24%
📺📁MacOS/Windows/PC — PDF/PNG Файлы22%
The shares total 178%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🚇 🖥 Обновление сайта!
На trackmap.msk.ru добавлено масштабирование двумя пальцами.
Масштабирование может выглядеть дёрганным, это связано с необходимостью точно подгонять схему пиксель в пиксель, чтобы она выглядела идеально. Чуть позже доработаю механизм приближения и подумаю над анимацией.
Теперь схема отображается на устройствах с браузером Safari, хоть и с костылями.
Если чуть подробнее — движок браузеров на iO…
Showing the 12 most recent of 12 posts we hold for @TrackMap. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
🚇 После обновления сайта, какой способ и систему вы используете для просмотра схемы?
🤖🔗 Android — Сайт48%
🤖📁 Android — PDF/PNG Файлы49%
🍏🔗 iOS/iPadOS — Сайт16%
🍏📁iOS/iPadOS — PDF/PNG Файлы19%
📺🔗 MacOS/Windows/PC — Сайт24%
📺📁MacOS/Windows/PC — PDF/PNG Файлы22%
The shares total 178%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 12 most recent posts we hold, published 13 July 2024 to 23 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 166,305 of 1,151,006entries 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.
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 2 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.
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
2 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.
Варшавская (станция метро, Москва)(ru.wikipedia.org) “…«[[Замоскворецкое (электродепо)|Замоскворецкое]]»{{Cite web |url=https://t.me/trackmap/75 |title=Telegram: Contact @trackmap<!-- Заголовок добавлен ботом…” read 9 August 2026
Кленовый бульвар (станция метро, Большая кольцевая линия)(ru.wikipedia.org) “…расположен [[Путевой съезд|пошёрстный съезд]]{{Cite web|url=https://t.me/s/trackmap|title=Moscow Metro Track Map|website=Telegram|access-date=202…” read 9 August 2026
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“Moscow Metro TrackMap” (@TrackMap), 2,216 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TrackMap.
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.