Telegram RegisterThe public register of Telegram

Channel

Railwex

@rsuperstructure

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

778subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001095562658
TypeChannel
Username@rsuperstructure
CreatedBetween 1 September 2016 and 31 October 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/rsuperstructure

Growth

778779778.56 Aug 2026, 14:49 — 779 subscribers6 Aug 2026, 15:36 — 779 subscribers7 Aug 2026, 00:28 — 778 subscribers6 Aug 2026, 14:497 Aug 2026, 00:28
3 measurements taken within a single day, net -1. 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 778–779 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 00:28778-1
6 Aug 2026, 15:36779no change
6 Aug 2026, 14:49779first reading

Engagement

15 posts held, back to 1 May 2022the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 13 August 2022. An engagement rate over an empty window would be a number about nothing.

Reaction mix

9 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
666.7%
👎333.3%

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 6 of the 15 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 9reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 1 May 2022 to 13 August 2022, 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

13 Aug 2022, 09:30 UTC≈1,440 views1 reactionsread 6 August 2026
Forwarded from @iciirFile

کتاب راهنمای کاربردی توليد صنعتی بتن خودتراکم. دبير کميته مهندس جواد چگينی

1

8 Aug 2022, 19:59 UTC≈1,620 views2 reactionsread 6 August 2026
Forwarded from @GEatysazFile

🔵 مجموعه اصطلاحات پر کاربرد و رایج در عملیات ساختمان بخش اول : عمران و معماری بخش دوم : #نقشه_برداری 🦅 تخصصی civil eng 🆔 @geatysaz

2

6 Aug 2022, 21:30 UTC≈1,500 viewsread 6 August 2026
Video

52ec2e350255bf4e2753224e4f3b9ff036445914-360p.mp4

5 Aug 2022, 11:01 UTC≈1,310 viewsread 6 August 2026

روش کار دستگاه TBM https://www.instagram.com/tv/CflravjloD6/?igshid=MDJmNzVkMjY=

1 Jul 2022, 22:47 UTC≈1,630 viewsread 6 August 2026
File

Share 'گزارش سانحه قطار مسافری مشهد یزد.pdf'

27 Jun 2022, 10:51 UTC≈1,400 views3 reactionsread 6 August 2026
Forwarded from @EslahatnewsPhoto

📢 لکوموتیوران، مقصر حادثه قطار مشهد-یزد شد ◀️ کمیسیون عالی سوانح طی اطلاعیه‌ای ۵ عامل بروز حادثه مرگبار قطار مشهد-یزد را اعلام کرد که در آن سرعت غیرمجاز و لکوموتیوران مقصر معرفی شده‌اند. _ اصلاحات نیوز ✅ @Eslahatnews

👎3

13 Jun 2022, 17:07 UTC≈1,290 views1 reactionsread 6 August 2026
Forwarded from @railir

🔺 اطلاعیه شماره 1 کمیسیون عالی سوانح راه‌آهن درباره سانحه قطار مسافری مشهد-یزد بسمه تعالی کمیسیون عالی سوانح راه‌آهن ضمن عرض تسلیت به خانواده های داغدیده و ابراز همدردی با آنان و آرزوی سلامتی برای مصدومین سانحه قطار مسافری مشهد- یزد مورخ 18/3/1401، اعلام می‌دارد این کمیسیون از لحظه وقوع سانحه تاکنون، ضمن حضور در محل سانحه ، نسبت به بررسی شواهد و قرائن میدانی و مستندات مربوطه از جمله مکالمات ضبط شده مامورین، وقایع ث

1

8 Jun 2022, 16:39 UTC≈1,050 viewsread 6 August 2026
Forwarded from @cimorgh30Photo

🔸خروج قطار مسافربری مشهد به یزد از ریل خالدی، سخنگوی اورژانس کشور: 🔹ساعت ۵ و ۳۰ دقیقه صبح امروز قطار مسافربری مشهد به یزد در محور طبس از خط خارج شد. 🔹در حال حاضر تیم‌هایی از اورژانس کشور و همچنین هلال احمر به منطقه اعزام شدند. 🔹از ۷ واگن ۳ واگن از ریل خارج شد که متأسفانه در این حادثه 20 نفر فوت کردند و حال ۱۵ نفر نیز وخیم است و حدود ۵۰ نفر نیز زخمی شدند.

8 Jun 2022, 16:37 UTC921 viewsread 6 August 2026

توضیحات وزیر راه و شهرسازی بابت علت حادثه 👆👆👆👆

8 Jun 2022, 16:36 UTC987 viewsread 6 August 2026

تسلیت عرض می کنم بابت سانحه پیش آمده برای قطار مسافری یزد مشهد

17 May 2022, 23:48 UTC≈2,310 views1 reactionsread 6 August 2026

سختی خط ترانزیشن زون یا ناحیه انتقال سختی خط در راه آهن به نقاطی گفته می شود که بستر خط از بالاستـي یه بتنی تغییر می یابد. در این قسمت، با توجه به اختلاف فاحش سختی، خط دائما دچار تغییرات در کیفیت می شود و خسارت های زیادی به خط وارد می شود. روشهای متعددی برای جبران این اختلاف سختی در فاصله متناسبی پیش از ورود به بستر بتنی وجود دارد. استفاده از ریل مضاعف، تقویت بستر با سیمان و آهک، استفاده از ستون های سنگی و بتنی زیر خ

1

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

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

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.

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

“Railwex” (@rsuperstructure), 778 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/rsuperstructure.

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.