Channel
@olum_pezeshki_qom
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
117subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001002936214 |
|---|---|
| Type | Channel |
| Username | @olum_pezeshki_qom |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 6 times, most recently 18 September 2026 |
| On Telegram | t.me/olum_pezeshki_qom |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 23:32 | 117 | no change |
| 9 Aug 2026, 16:17 | 117 | first reading |
20 posts held, back to 15 December 2017 — 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 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 20 posts for this entry, the most recent from 11 January 2018. An engagement rate over an empty window would be a number about nothing.
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.
بسم الله الرحمن الرحیم پیرو حملات مکرر و تهدید های مکرر مدیران و دانشجویان عضو کانال دانشجویان دانشگاه علوم پزشکی قم از جانب معاونت فرهنگی و دانشجویی دانشگاه علوم پزشکی قم ( مفدا قم ) و با توجه به تصمیم قبلی مدیران و همچنین مشورت های انجام شده با توجه به فیلترینگ تلگرام و همچنین لزوم استفاده از سامانه ملی با در نظر گرفتن اصول پدافند غیر عامل جهت جلوگیری از هر گونه آسیب به دانشجویان عزیز از جانب معاونت مذکور در روز ها…
✅بزرگداشت شهدای هسته ای با حضور ذوالنور، نبویان، عباسی، زاکانی، نوبری، عبدالملکی ✅با موضوع: دستاوردها و بر باد رفته های برجام ✅پنجشنبه 21 دی ساعت 18:30 قم مدرسه دارالشفا @olum_pezeshki_qom
🇮🇷 به مناسب ۱۹ دی...
🔴اطلاعیه مهم ✅بنا بر مصوبه شورای امنیت و شورای تأمین، راهپیمایی چهارشنبه لغو می باشد. ✅زمان برگزاری متعاقبا اعلام می شود. @olum_pezeshki_qom
🔴 حضور دانشجویان بصیر دانشگاه علوم پزشکی قم همراه با اقشار مختلف مردم انقلابی قم در راهپیمایی علیه اغتشاشات اخیر 🔸مکان و زمان تجمع: فردا چهارشنبه ۱۳ دی ماه ساعت ۹:۳۰ ، میدان روح الله، دانشکده بهداشت 🔴🔴راهپیمایی فوق لغو و به زمان دیگری موکول شد @olum_pezeshki_qom
📝مردم قم علیه اغتشاشگران راهپیمایی می کنند ✅چهارشنبه ساعت ۱۰ صبح راهپیمایی بزرگ مردم قم علیه اغتشاشگران از میدان جانبازان به سمت حرم مطهر برگزار میشود. @olum_pezeshki_qom
«پیام رسان سروش» را در بازار اندروید ببین: http://cafebazaar.ir/app/?id=mobi.mmdt.ott&ref=share
با تصمیم سطوح عالی امنیتی فعالیت تلگرام و اینستاگرام به طور موقت محدود می شود. @olum_pezeshki_qom
🔸روحانی: انتقاد و اعتراض حق مردم است ولی شیوه آن باید به حل مشکلات کشور و بهبود زندگی مردم منجر شود. تخریب اموال عمومی و بهم زدن نظم اجتماعی مورد قبول هیچکس نیست. @olum_pezeshki_qom
هم اکنون تجمع دانشجویان مومن و انقلابی دانشگاه تهران در اعتراض به وضع اقتصادی و هتک حرمت مقدسات توسط معاندین @bsouni @olum_pezeshki_qom
🔰ویژه 📹نماهنگ| بصیرت خواص؛ حرکت عوام ⚠️نماهنگی به مناسبت سالگرد حماسهی۹دی درباره نفش #خواص در حوادث فتنهگون با محوریت جناب عمار یاسر ➕تصاویر دیدهنشدهای از بیانات رهبر انقلاب ☑️ @Khamenei_ir
پخش مجدد مستند زخم تازه روایتی متفاوت از ناگفته های فتنه و هتک حرمت عاشورای۸۸ امشب شبکه۳ بعد از خبر ۲۲ @olum_pezeshki_qom
Showing the 12 most recent of 20 posts we hold for @olum_pezeshki_qom. 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.
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.
@olum_pezeshki_qom named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“علوم پزشکی قم” (@olum_pezeshki_qom), 117 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/olum_pezeshki_qom.
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.