Local community — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 the other topics.
Growth
25 measurements spanning 90 days, net +128. 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 7,249–7,415 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)
Subscribers
Change
6 Nov 2026, 08:27
7,396
+6
3 Nov 2026, 00:07
7,390
+3
31 Oct 2026, 06:20
7,387
+2
28 Oct 2026, 05:41
7,385
+5
25 Oct 2026, 11:15
7,380
+27
22 Oct 2026, 03:21
7,353
-8
18 Oct 2026, 21:56
7,361
+5
15 Oct 2026, 20:58
7,356
+3
12 Oct 2026, 22:16
7,353
-8
6 Oct 2026, 02:55
7,361
-7
28 Sept 2026, 21:38
7,368
+22
18 Sept 2026, 23:00
7,346
+36
14 Sept 2026, 09:58
7,310
+20
10 Sept 2026, 23:38
7,290
+10
5 Sept 2026, 23:57
7,280
-5
2 Sept 2026, 05:45
7,285
+3
30 Aug 2026, 06:17
7,282
+2
27 Aug 2026, 01:36
7,280
+5
23 Aug 2026, 23:17
7,275
-1
20 Aug 2026, 11:28
7,276
first reading
Engagement
60 posts held, back to 21 July 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 17 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
18.6%
avg views ÷ 7,396 subscribers
Avg views / post
1,380
18 posts measured
Reaction rate
0.296%
reactions ÷ views · ER floor
Posts in window
20
of 60 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. It is computed over the 15 of 18 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 29 October 2026
Posts held
60 (21 July 2026 – 29 October 2026)
Views total
24,750
Reactions total
62
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 00:38 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.
What this channel posts
Video runtime
39s
Average length
39s
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.
Reaction mix
120 reactions across 43 posts, in 9 distinct kinds. The most used accounts for 35.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
43
35.8%
👍
43
35.8%
👎
15
12.5%
😢
7
5.83%
🤬
6
5.00%
👏
2
1.67%
🔥
2
1.67%
😐
1
0.833%
🥰
1
0.833%
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 46 of the 60 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 120 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 60 most recent posts we hold, published 21 July 2026 to 29 October 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
Telegram’s own ‘edited’ marker: 1 of 20 posts held from the last 30 days (5.00%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🚨 خبر برخورد دو قطار سریع السیر در اسپانیا به روز شد
▫️جزئیات جدیدی درباره دقایق منتهی به برخورد قطارهای Renfe و Iryo منتشر شده است.
▫️از اختلال سیستم ایمنی LZB و دستور مرکز کنترل برای ازسرگیری حرکت قطارها تا مکالمات میان مرکز کنترل و رانندگان و روند تحقیقات درباره علت حادثه.
👈 آخرین آمار و جزئیات فنی جدید حادثه را در گزارش به روزشده پورتال حمل و نقل ریلی بخوانید.
🔗 مطالعه گزارش به روزشده در سایت
#راه_آهن #حواد…
🔴 برخورد دو قطار سریع السیر در اسپانیا
▫️یک قطار سریع السیر Renfe در خط مادرید ـ اندلس با یک قطار Iryo که متوقف بود برخورد کرد؛ حادثه ای که به خروج چند واگن از ریل و تلفات گسترده منجر شد.
▫️جزئیات حادثه، وضعیت خط سریع السیر، واکنش نخست وزیر اسپانیا و آخرین اطلاعات درباره علت وقوع این سانحه را در پورتال حمل و نقل ریلی بخوانید.
🔗 مطالعه گزارش کامل در سایت
#راه_آهن #حوادث #بین_الملل
🚆جامع ترین پورتال حمل و نقل ریل…
🚇 سه شنبه ها در تبریز، حمل و نقل عمومی رایگان شد
▫️بر اساس مصوبه شورای شهر تبریز، استفاده از مترو و خطوط BRT در روزهای سه شنبه تا پایان سال ۱۴۰۵ رایگان خواهد بود.
🔗 مشاهده جزئیات
#مترو #تبریز
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
✅ ژاپن سفر ریلی را لوکستر میکند/راه اندازی کابین خصوصی شینکانسن و قطار شبانه
▫️کابین های خصوصی جدید به شینکانسن اضافه شده اند و در کنار آن، یک قطار شبانه جدید نیز برای مسیرهای طولانی در ژاپن در راه است.
▫️اما این کابین ها چه امکاناتی دارند و قطار شبانه Luna Azul قرار است در چه مسیری حرکت کند؟
👈جزئیات این دو پروژه جدید ریلی ژاپن را در پورتال حمل و نقل ریلی بخوانید.
🔗 مشاهده جزئیات
#راه_آهن #بین_الملل
🚆جامع تری…
✅ قابل توجه مسافرین محترم قطارهای حومه ای؛
📌به اطلاع می رساند:
▫️قطار مسیر تبریز - جلفا به شماره (944) در مورخه 1405/08/07 در مسیر رفت و برگشت از برنامه حرکت قطارهای مسافری حذف گردید.
🔗 مشاهده برنامه حومه ای منطقه آذربایجان
#قطارهای_حومه_ای
#آذربایجان
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
🟩 بهای بلیت قطارهای حومه ای
▫️جدیدترین بهای بلیت قطارهای حومه ای منتشر شده به همراه روش های تهیه بلیت این قطارها ارائه شده است.
🔸آخرین نرخ اعلام شده ی بلیت قطارهای حومه ای، مربوط به آبان ماه 1405 در لینک زیر قابل مشاهده می باشد.
🔗 جدول بهای بلیت قطارهای حومه ای
🚉انتقادات و پیشنهادات : 5149-021 سامانه صدای مسافر راه آهن 🚊
#قطارهای_حومه_ای
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
✅ قابل توجه مسافرین محترم قطارهای حومه ای؛
📌به اطلاع می رساند:
▫️قطار مسیر اندیمشک - دورود به شماره (941) از مورخه 1405/08/04 لغایت 1405/12/24 بجای ساعت 13:00 در ساعت 13:20 از ایستگاه اندیمشک اعزام می گردد.
🔗 مشاهده برنامه حومه ای منطقه جنوب
#قطارهای_حومه_ای
#جنوب
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
✅ قابل توجه مسافرین محترم قطارهای حومه ای؛
📌به اطلاع می رساند:
▫️برنامه جدید مسیر زیر در تاریخ 4 آبان ماه با تغییرات جزئی بروزرسانی شده است.
🔸اندیمشک-دورود
🟢 [بروز رسانی: 4 آبان - 15:30]
🔗 مشاهده برنامه حومه ای منطقه جنوب
#قطارهای_حومه_ای
#جنوب
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
✅ قابل توجه مسافرین محترم قطارهای حومه ای؛
📌به اطلاع می رساند:
▫️قطار مسیر تبریز - جلفا به شماره (944) در مورخه های 5 و 1405/08/06 در مسیر رفت و برگشت از برنامه حرکت قطارهای مسافری حذف گردید.
🔗 مشاهده برنامه حومه ای منطقه آذربایجان
#قطارهای_حومه_ای
#آذربایجان
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
✅ حمل خودرو با قطار
▫️در این مقاله میتوانید تمام ضوابط و قوانین مرتبط با حمل خودرو با قطار را به همراه جدول قیمت به روز حمل خودرو مطالعه نمایید.
⭐️ زمان پیش فروش قطار حمل خودرو - آبان
👈 بروزرسانی قیمت ها ؛ آبان ماه ۱۴۰۵
🔗 قوانین+جدول قیمت
🚆جامع ترین پورتال حمل و نقل ریلی
🆔 @rahahan_ir
Showing the 12 most recent of 60 posts we hold for @rahahan_ir. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is 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 60 most recent posts we hold, published 21 July 2026 to 29 October 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.
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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“حمل و نقل ریلی | Rah-ahan.ir” (@rahahan_ir), 7,396 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/rahahan_ir.
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.