Channel
@majidascary
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
120subscribers
+0 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001037999202 |
|---|---|
| Type | Channel |
| Username | @majidascary |
| Description | دوستم سلام تلاش کردم تا سیر دوران زندگیم، از جوانی تا دوران کهنسالی، در دفتری مجازی جمع گردد. با آرزوی توفیق کسب خدمت و نهایت شهادت. پل ارتباطی از طریق آی دی @khademoreza8 تعجیل در فرج مهدی زهرا، صلوات مومنانه شاد باشی، همسفرتابهشت مجید طهوریان عسکری |
| Created | 1 March 2016 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/majidascary |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 04:15 | 120 | no change |
| 5 Aug 2026, 18:40 | 120 | first reading |
14 posts held, back to 13 June 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 1 pageof 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 1 August 2026 |
|---|---|
| Posts held | 14 (13 June 2026 – 1 August 2026) |
| Views total | 37 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 04:15 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 9 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 3 videos 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 جهاد
🟡نشست مردمی خدمت 🟢شنبه 27 تیرماه - ساعت 22 🟢میدان شریعتی (تقیآباد) #مشهد_الرضا_علیه_السلام #جهانشهر_برکت_و_کرامت 🖥️SHORA.MASHHAD.IR 🔗 ble.ir/shoramashhad_ir 🌐 @SHORAMASHHAD_IR 📲instagram.com/shoramashhad_ir
Signed جهاد
🎥 مصاحبه #مجید_طهوریانعسکری، عضو شورای اسلامی شهر مشهدمقدس: نقش آفرینی هر شهروند برای میزبانی از زائران و عزاداران امام شهید #مشهد_الرضا_علیه_السلام #جهانشهر_برکت_و_کرامت 🖥SHORA.MASHHAD.IR 🔗 ble.ir/shoramashhad_ir 🌐 @SHORAMASHHAD_IR 📲 instagram.com/shoramashhad_ir
Signed جهاد
♦️ مروری بر توصیه رهبر شهید انقلاب به جوانان: اگر این چیزها را رعایت کنید از فرشته بالاتر خواهید شد #بدرقه_یار 🇮🇷 ✊ @AkhbareFori | Link
Signed جهاد
🟡 هر شهروند برای میزبانی از زائران و عزاداران امام شهید نقشآفرینی کند #مجید_طهوریانعسکری، عضو شورای اسلامی شهر مشهد مقدس گفت: گزارشهای ارائهشده از سوی شهرداری نشاندهنده چابکی و آمادگی کامل مدیریت شهری برای برگزاری آیین تشییع پیکر مطهر امام شهید انقلاب است، اما تحقق میزبانی شایسته نیازمند مشارکت گسترده مردم در کنار دستگاههای اجرایی خواهد بود. https://shora.mashhad.ir/s/mfaVCSN #مشهد_الرضا_علیه_السلام #جهانشه…
Signed جهاد
آقای مظلوم
Signed جهاد
🔵 استوری #مجید_طهوریانعسکری #مشهد_الرضا_علیه_السلام #جهانشهر_برکت_و_کرامت 🖥 SHORA.MASHHAD.IR 🔗 ble.ir/shoramashhad_ir 🌐 @SHORAMASHHAD_IR 📲 instagram.com/shoramashhad_ir
Signed جهاد
به تلاش جمعی یک #استان و مدیران خدوم صدر تا ذیل آن، تلاش های شهرداری مشهد، اداره کل راه و شهرسازی، میراث فرهنگی و گردشگری و البته #پیگیری های کمیسیون توسعه و بهسازی #توس در شورای شهر ، #طرح_تفصیلی بلوار #شاهنامه تصویب شد. #آقای_شهیدمان، این هم انجام شد. شما از ما راضی باشید... سرباز کوچک انقلاب #مجید_طهوریان_عسکری
Signed جهاد
🔵 دیدار #مجید_طهوریانعسکری، عضو شورای اسلامی شهر مشهدمقدس با فعالین اجتماعی محله وحید منطقه ۴ #مشهد_الرضا_علیه_السلام #جهانشهر_برکت_و_کرامت 🖥 SHORA.MASHHAD.IR 🔗 ble.ir/shoramashhad_ir 🌐 @SHORAMASHHAD_IR 📲 instagram.com/shoramashhad_ir
Signed جهاد
https://x.com/i/status/2071327931754836059
Signed جهاد
حسین
Signed جهاد
بازگشایی گره ترافیکی ورودی پل فجر گره ای دیگر، که آن هم باز شد... سالها پیگیری مردم برای جا به جایی ایستگاه بی آر تی در انتهای خیابان طبرسی جنوبی و ورودی به پل فجر برای بازتر شدن مسیر عبور خودرو انجام شده بود تا بالاخره مسئولیت کمیته نظارتی شهرداری منطقه۴ را بر عهده گرفتم. به قول امام شهیدمان، پیگیری و پیگیری و پیگیری و حالا به همت معاونت عمران و حمل و نقل شهرداری مشهد این گره نیز در حال باز شدن است. راستی قرار شد تا…
Signed جهاد
Showing the 12 most recent of 14 posts we hold for @majidascary. 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 — 427,590 of 1,478,351entries 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“همسفرتابهشت” (@majidascary), 120 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/majidascary.
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.