Channel
@chapaevtrans
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
60subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003557149788 |
|---|---|
| Type | Channel |
| Username | @chapaevtrans |
| Description | Канал о транспорте Петербурга. Больше, чем просто маршруты, схемы, подвижной состав. Налаживаем связь с городом, пассажирами и любителями Для личных сообщений: @Mihail7787 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/chapaevtrans |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 05:30 | 60 | no change |
| 10 Aug 2026, 01:46 | 60 | first reading |
17 posts held, back to 27 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 page of 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 17 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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 1 video 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.
54 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 57.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 57.4% | |
| ❤🔥 | 6 | 11.1% | |
| 💘 | 5 | 9.26% | |
| 💔 | 4 | 7.41% | |
| 🔥 | 2 | 3.70% | |
| 🕊 | 2 | 3.70% | |
| 😭 | 2 | 3.70% | |
| 👏 | 1 | 1.85% | |
| 🙏 | 1 | 1.85% |
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 15 of the 17 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 27 June 2026 to 9 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.
Однажды электрички вернутся на вокзал. Убирать их с Московского вокзала навсегда – одна из самых разрушительных и недальновидных идей. Московский вокзал исторически был идеальным распределительным хабом: пассажиры попадали напрямую в деловой и исторический центр города, имея доступ сразу к двум линиям метро и десяткам маршрутов НОТ. ВСМ – важный инфраструктурный проект. Но жертвовать ради него ежедневным массовым п…
❤1👏1💔1
Photo, posted without a caption
💔2
Сохранить «Ижавиа»: регион не должен расплачиваться за ошибки руководства Ситуация, которая сейчас разворачивается вокруг региональной авиации Удмуртии, вызывает искреннее недоумение. Казалось бы, в наше время игнорировать требования Росавиации и пренебрегать стандартами безопасности – преступление. Но факт остается фактом: управленческие просчеты поставили под удар важный для региона актив. И здесь очень важно раз…
🙏1
Когда официальные транспортные порталы молчат в тряпочку, мы не стесняемся и пытаемся разобраться в каждой тонкости сами. Исторические здания сносят, дома двигают, поезда отменяют: во что ВСМ превращает Петербург
24 июля жители юга Петербурга столкнулись с очередным транспортным коллапсом. После ночной атаки сами знаете чего на логистические комплексы, движение по Московскому шоссе – одной из ключевых магистралей, связывающих город с Пушкином, Колпино и Ленинградской областью – оказалось полностью заблокировано. Информация о перекрытии появилась около 7:30 утра. Водителей разворачивали без объяснений причин происходящего. Хо…
❤2
https://dzen.ru/a/al9nTdVlSA96-0ww
❤2💘2❤🔥1
Под Петербургом этим летом работают сразу шесть проходческих щитов – для города это исторический рекорд. От первых щитов под Темзой и советской копии Markham до сегодняшнего метростроя, который работает уже не ради показателей, а ради метро там, где оно действительно нужно людям. Здесь же и про мировой рекорд скорости, который до сих пор держит Ленинград, и про Москву, которая попала с Книгу рекордов Гинесса! https…
❤1
Кто-то плачет по метро на Ржевке, а эти ребята будут плакать без метро ещё очень долго https://dzen.ru/a/akuaHNuqyiEz8LCC
❤1
⚡️В Белгородской области разворачивается транспортная война между жителями, ОЭМК и городскими властями. Цена вопроса – выживание уникального скоростного трамвая, который уже несколько лет душат административными решениями. 5️⃣Ещё год назад трамваи ходили каждые 5 минут в час пик, исправно и бесперебойно подвозя тысячи сотрудников ОЭМК. 📉 В 2025 году, владелец линии (сам комбинат) решает, что нужно экономить, поэтом…
❤3
день прощания волховстроевского направления с Московским вокзалом настал
😭2💔1
File, posted without a caption
❤4
⚡️С 5 утра 28 июня начинается ремонт на Невском проспекте Учитывайте это при планировании своих поездок
❤5
Showing the 12 most recent of 17 posts we hold for @chapaevtrans. 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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Транспорт честно | Михаил Чапаев” (@chapaevtrans), 60 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/chapaevtrans.
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.