Channel
@yakhchaldarantehran
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7,808subscribers
+9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001083373941 |
|---|---|
| Type | Channel |
| Username | @yakhchaldarantehran |
| Description | تلفن تماس:۰۹۱۲۴۷۹۴۰۸۷ ۰۹۱۲۰۷۹۴۰۸۷ ۰۹۳۷۱۷۹۴۰۸۷ هادی |
| Created | Between 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/yakhchaldarantehran |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 11:28 | 7,808 | +2 |
| 24 Aug 2026, 20:49 | 7,806 | -11 |
| 21 Aug 2026, 10:45 | 7,817 | +6 |
| 18 Aug 2026, 18:57 | 7,811 | +6 |
| 16 Aug 2026, 05:28 | 7,805 | -4 |
| 12 Aug 2026, 16:46 | 7,809 | +7 |
| 10 Aug 2026, 02:51 | 7,802 | +3 |
| 6 Aug 2026, 21:30 | 7,799 | no change |
| 6 Aug 2026, 03:51 | 7,799 | first reading |
211 posts held, back to 3 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 19 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 211 (3 August 2026 – 28 August 2026) |
| Views total | 72,312 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:26 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.
Lifetime counters from Telegram’s own channel header, read 28 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
🔵در صنعت حملونقل جادهای، خرابی ناگهانی کامیون میتواند علاوه بر تحمیل هزینههای سنگین تعمیرات، باعث تأخیر در تحویل بار، از دست رفتن فرصتهای کاری و حتی بروز حوادث جادهای شود. 🔹بسیاری از این خرابیها بهصورت ناگهانی اتفاق نمیافتند، بلکه از مدتها قبل با نشانهها و علائم هشداردهنده خود را نشان میدهند. 🔹رانندگان حرفهای و مدیران ناوگان میدانند که سرویس دورهای کامیون یکی از مهمترین اقدامات برای حفظ عملکرد خودرو…
Signed Zamani sardpema
بارگیری تریلی یخچال 🥬🧅🥦🍊🍎 کرج 🥬 🥦 🥦 آستارا ارتفاع بلند ازنا 👈👈👈 بستان مشکین شهر 🍎🍋 شیراز تخلیه میدان بار کرمانشاه 🧅 🧅 🧅 ریمدان 👈 یکشنبه 👇👇👇 09106520456
Signed ..
تریلی یخچالدار ازنا به مریوان فردا بارگیری 🔺️09160200962 پاپی زاده 🔺
Signed Alireza_papi zadeh. .
بارگیری تریلی یخچال ازنا 👈👈👈 بستان مشکین شهر 🍎🍋 شیراز تخلیه میدان بار کرمانشاه 🧅 🧅 🧅 ریمدان 👈 یکشنبه 👇👇👇 09106520456
Signed ..
بارگیری تریلی یخچال ازنا 👈👈👈 بستان مشکین شهر 🍎🍋 شیراز تخلیه میدان بار 👇👇👇 09106520456
Signed ..
جفت یخچالدار تهران به شیراز فردا بارگیری رمضانی ۰۹۹۱۶۰۲۵۶۳۲
Signed شهریخچالداران 🚛09126136344🚛
بار خاور یخچالدار تهران به شیراز 09122158230
Signed Mehran Sakhaei
سلام ده چرخ یخچال دار اصفهان به کرمان تک یخچال دار اصفهان به یاسوج ده چرخ یخچال دار شهری اصفهان 09136573590 ابوالفضل نایینی
Signed .ابولفضل نایینی
جفت یخچالدار تهران به شیراز فردا بارگیری رمضانی ۰۹۹۱۶۰۲۵۶۳۲
Signed شهریخچالداران 🚛09126136344🚛
تک یخچالدار تهران به اهواز تهران به الیگودرز فردا بارگیری رمضانی ۰۹۹۱۶۰۲۵۶۳۲
Signed شهریخچالداران 🚛09126136344🚛
سلام ده چرخ یخچال دار اصفهان به کرمانشاه 09136573590 ابوالفضل نایینی
Signed .ابولفضل نایینی
تریلی یخچالدار ازنا به خسروی فردا بارگیری 🔺️09160200962 پاپی زاده 🔺
Signed Alireza_papi zadeh. .
Showing the 12 most recent of 211 posts we hold for @yakhchaldarantehran. 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.
Citation-graph rank — 56,467 of 1,625,954entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“حمل و نقل یخچالداران تهران” (@yakhchaldarantehran), 7,808 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/yakhchaldarantehran.
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.