Иволга 077 прибыла на Болшево в сторону Москвы, акт 22:09
❤1

Channel
@where_suburban_train
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
3,241subscribers
+84 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002224731616 |
|---|---|
| Type | Channel |
| Username | @where_suburban_train |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/where_suburban_train |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 15:51 | 3,241 | +17 |
| 8 Oct 2026, 04:42 | 3,224 | +17 |
| 2 Oct 2026, 00:17 | 3,207 | -2 |
| 16 Sept 2026, 18:16 | 3,209 | +30 |
| 8 Sept 2026, 10:01 | 3,179 | +3 |
| 2 Sept 2026, 20:24 | 3,176 | -3 |
| 27 Aug 2026, 22:03 | 3,179 | +2 |
| 24 Aug 2026, 12:46 | 3,177 | +1 |
| 20 Aug 2026, 10:02 | 3,176 | +5 |
| 17 Aug 2026, 12:44 | 3,171 | +1 |
| 14 Aug 2026, 03:39 | 3,170 | +9 |
| 11 Aug 2026, 03:26 | 3,161 | +2 |
| 8 Aug 2026, 00:02 | 3,159 | +2 |
| 7 Aug 2026, 16:32 | 3,157 | no change |
| 7 Aug 2026, 16:24 | 3,157 | first reading |
22 posts held, back to 6 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 2 pages 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 22 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
231 reactions across 22 posts, in 9 distinct kinds. The most used accounts for 19.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5379926792893140809 | 46 | 19.9% | |
| 🤯 | 39 | 16.9% | |
| ❤ | 36 | 15.6% | |
| custom 5379619225990107477 | 29 | 12.6% | |
| custom 5379938110131965042 | 24 | 10.4% | |
| custom 5380022798297105587 | 22 | 9.52% | |
| 👍 | 17 | 7.36% | |
| 🤔 | 15 | 6.49% | |
| 🔥 | 3 | 1.30% |
Custom emoji. 4 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 are Telegram’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 22 of the 22 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 231 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 6 August 2026 to 7 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.
Иволга 077 прибыла на Болшево в сторону Москвы, акт 22:09
❤1
Эп2дм-277 отправилась с Орехово Зуево следует до поклонной 19:39
👍9custom 53796192259901074773❤1
ЭГЭ2Тв 020 "Первейшая Иволга 4.0" с Выхино на Ипподром рейсом №7435 Актуально на 17:05
custom 53799267928931408092
Расписание ЭГЭ2Тв-020 на 07.08.2026: №7323 Зеленоград-Крюково — Ипподром (06:22 — 08:31) №7254 Ипподром — Зеленоград-Крюково (08:42 — 10:50) №7379 Зеленоград-Крюково — Ипподром (11:02 — 13:11) №7310 Ипподром — Зеленоград-Крюково (13:22 — 15:30) №7435 Зеленоград-Крюково — Ипподром (15:42 — 17:51) №7366 Ипподром — Зеленоград-Крюково (18:02 — 20:10) №7491 Зеленоград-Крюково — Ипподром (20:22 — 22:31) №7422 Ипподром — Зе…
custom 53799267928931408092
Иволга 20 лет ЦППК отправляется от Яузы в область Акт 16:46
❤9
Сгоревшая голова от ЭП2Д-0014 стоит в парке Перово в ожидании восстановления на МЛРЗ 🛠 Актуально на 16:31
🤯39custom 537992679289314080910🔥3❤1
Иволга 2.0 эг2тв 033 с Площади трёх вокзалов до Нахабино, актуально 15:01
custom 53799381101319650425
Победный Эп2дм 0277 отпр с Савеловской едет в Лесной городок Акт 15:33
custom 53796192259901074778
😕🤩 ЭГЭ2Тв-020 на Красково у направлении Крюково, акула 13:50
custom 53799267928931408095
ЭШ2-002/010 Дегунино на Окружную 14:18
custom 53800227982971055877👍1
090 Иволга остановилась на красном строителе в сторону области. Акт: 14:30
custom 53799381101319650426❤1
ЭД4М - 316 отъехала от Мытищ до Монино спутником Акт 14:35
❤7
Showing the 12 most recent of 22 posts we hold for @where_suburban_train. 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.
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“Где сейчас уникальная электричка Москвы | ГСУЭМ” (@where_suburban_train), 3,241 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/where_suburban_train.
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.