Telegram RegisterThe public register of Telegram
Telegram profile photo for ℝ𝕒𝕚𝕝ℂ𝕠𝕣𝕖

Channel

ℝ𝕒𝕚𝕝ℂ𝕠𝕣𝕖

@railcore_MZD

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

133subscribers

+7 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002855898041
TypeChannel
Username@railcore_MZD
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/railcore_MZD

Growth

124133128.59 August 2026 — 126 subscribers9 August 2026 — 126 subscribers31 August 2026 — 124 subscribers9 September 2026 — 128 subscribers16 September 2026 — 133 subscribers9 August 202616 September 2026
5 measurements spanning 39 days, net +7. 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 123–134 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 21:38133+5
9 Sept 2026, 23:36128+4
31 Aug 2026, 13:03124-2
9 Aug 2026, 02:17126no change
9 Aug 2026, 00:00126first reading

Engagement

18 posts held, back to 28 July 2026the 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 18 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

54 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52381202614080053651425.9%
custom 52062733022464723431324.1%
custom 5305634763594281691713.0%
👍611.1%
custom 519991825818190640659.26%
custom 537543370305071656247.41%
❤‍🔥35.56%
custom 523822468494787428611.85%
custom 537521674707272770011.85%

Custom emoji. 7 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 15 of the 18 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 18 most recent posts we hold, published 28 July 2026 to 8 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.

Recent posts

8 Aug 2026, 03:57 UTC24 viewsread 9 August 2026
Photo

Пока главадмин пашет на работе, 2 админ свалил в Беларусь 🇧🇾 Railcore🟥 (ВЖД❤️‍🔥)

7 Aug 2026, 19:12 UTC74 views1 reactionsread 9 August 2026

Граждане, хайп момент. Я решил не мелочиться с обычным розыгрышем, а сделать лютую акцию. Если Ковальский напишет жалобу на Рейлкор, то проведем розыгрыш на 600 звезд 😍 Делайте как хотите, главное что бы он отчитался о своей работе в своём тгк. Хайп момент стартует!🇮🇱 RailCore🛤

custom 53752167470727277001

6 Aug 2026, 12:23 UTC37 views6 reactionsread 9 August 2026
Photo

Редчайший момент. Главадмин делится своими художествами. #щитпост

custom 52381202614080053656

5 Aug 2026, 09:19 UTC50 views3 reactionsread 9 August 2026
Photo

Заебало всё #щитпост

custom 53056347635942816913

5 Aug 2026, 06:52 UTC49 views4 reactionsread 9 August 2026

Ловить чеха с двухэтажкой из админов никто не выйдет. Один на работе, другой пропал безвести. Первого жалко😱 #щитпост

custom 52062733022464723434

3 Aug 2026, 11:43 UTC61 views1 reactionsread 9 August 2026
Photo

Сплотка электровозов ожидающих отправку на РППЖТ ЭП10-009; ЭП10-006; ЭП10-002; ЭП10-005; ЭП10-003; ЧС7-054; ЧС7-069; ЧС7-051 Так же недалеко стоящий электропоезд поездом №6992 «Москва-Рязань-1» ЭД4М-0293 Станция: Рязань-1 Архив: 18 ноября 2023 Railcore🟥 (ВЖД❤️‍🔥)

custom 51999182581819064061

3 Aug 2026, 11:40 UTC55 viewsread 9 August 2026
Photo

ЭД4М-0212 сообщением «Пермь-2 — Левшино» Станция: Пермь-2 Архив: 2 ноября 2025 Railcore🟥 (ВЖД❤️‍🔥)

3 Aug 2026, 11:34 UTC55 views4 reactionsread 9 August 2026
Photo

Обрубок Памятник на территории ТЧПРИГ-31 Домодедово ЭР2Т-7109 Railcore🟥 (ВЖД❤️‍🔥)

custom 53056347635942816914

3 Aug 2026, 06:21 UTC58 views2 reactionsread 9 August 2026
Photo

#щитпост

custom 52381202614080053652

3 Aug 2026, 04:49 UTC53 views3 reactionsread 9 August 2026

Граждане, не знал что такое скажу, но... У нас контентный дефолт😐 Главадмин в данный момент на повышении квалификации каждый рабочий день, хоть и второй админ где нибудь да шароебится. Если хотите, можете присылать какой нибудь контент в сообщения каналу, а мы будем его публиковать от вашего имени. 🫥

custom 52062733022464723432custom 53754337030507165621

31 Jul 2026, 21:05 UTC237 views7 reactionsread 9 August 2026

1 августа. Для многих эта дата это просто напоминание об единственном оставшемся месяце лета. Но для этого канала эта дата - по сути... День рождения!🎉 1 августа 2025 года был создан этот канал. Это не было переработкой старых каналов главадмина, а полностью с нуля созданный канал. А вот уже 15 августа был сделан первый пост - приветствие, структура которого не менялась с даты создания. Как раз на день рождения п

custom 51999182581819064064❤‍🔥3

31 Jul 2026, 08:39 UTC75 views2 reactionsread 9 August 2026
Photo

Электровоз прибывший на восстановление из Южно-Уральской жд в депо ТЧЭ-33 Ожерелье. По итогу стоит в депо без дела и без проведения какого-либо ремонта ВЛ60К-2556 Railcore🟥 (ВЖД❤️‍🔥)

👍2

Showing the 12 most recent of 18 posts we hold for @railcore_MZD. 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.

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.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“ℝ𝕒𝕚𝕝ℂ𝕠𝕣𝕖” (@railcore_MZD), 133 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/railcore_MZD.

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.