Channel
@oragheparishan
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,449subscribers
+58 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001095797316 |
|---|---|
| Type | Channel |
| Username | @oragheparishan |
| Created | 12 December 2016 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/oragheparishan |
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 19:22 | 3,449 | +9 |
| 13 Sept 2026, 13:38 | 3,440 | +6 |
| 9 Sept 2026, 08:37 | 3,434 | +15 |
| 4 Sept 2026, 01:19 | 3,419 | -2 |
| 31 Aug 2026, 06:04 | 3,421 | +5 |
| 27 Aug 2026, 23:12 | 3,416 | +12 |
| 24 Aug 2026, 19:14 | 3,404 | +2 |
| 21 Aug 2026, 06:36 | 3,402 | +4 |
| 18 Aug 2026, 07:04 | 3,398 | +3 |
| 12 Aug 2026, 00:42 | 3,395 | +1 |
| 9 Aug 2026, 01:13 | 3,394 | +3 |
| 6 Aug 2026, 04:46 | 3,391 | no change |
| 6 Aug 2026, 00:58 | 3,391 | first reading |
21 posts held, back to 21 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages 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 21 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
2,239 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 685 | 30.6% | |
| ❤ | 640 | 28.6% | |
| 👏 | 299 | 13.4% | |
| 👎 | 166 | 7.41% | |
| 👌 | 163 | 7.28% | |
| 🤣 | 149 | 6.65% | |
| 😢 | 97 | 4.33% | |
| 💯 | 21 | 0.938% | |
| 🙏 | 10 | 0.447% | |
| 😱 | 4 | 0.179% | |
| 🤯 | 3 | 0.134% | |
| 🤬 | 2 | 0.089% |
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 21 of the 21 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 2,294 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 21 August 2025 to 6 August 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.
«میانجیگری»، یعنی بین طرفین دعوا، میانجی شدن. متأسفانه بعضی فکر میکنند، قضیه به «جگر/ جیگر» ربط دارد و برای اینکه لفظ قلم حرف بزنند، «میان جگری» میگویند که غلط است. https://t.me/oragheparishan
🤣37👍8😱4🤯2❤1
«مردی احنف قیس را دشنام میداد و از پسِ وی میدوید. احنف چون با قبیلهی خویش رسید بایستاد و گفت: اگر چیزی دیگر اندر دلت مانده است بگو آنجا تا کسی ازین بیخردان از قبیلهی ما نشنود که ترا جواب دهد.» (رسالهٔ قشیریه، به تصحیح بدیعالزمان فروزانفر، ص ۳۹۴) این حکایت کوتاه، نقد حال روزگار ما است. وضعیتی را توصیف کرده که بعد از گذشت هزار سال، بخشی از چهره جمعی امروز ما در آن پیداست. شبکههای اجتماعی قرار بود میدان گسترش گف…
❤50👍16👏6💯4
دیروز آذر عظیما در ۹۳ سالگی در اصفهان درگذشت. او همسر مرتضی حنانه بود. یکی از شاهکارهای موسیقی ایران این آهنگ محلی شیرازی است که این دو بازآفرینی کردند. در این سالها مانند بسیاری دیگر از زنان خواننده صدایش قربانی جهل و تعصب شد و کمتر کسی سراغی از او گرفت و این گنج بزرگ از نظرها پنهان ماند. پینوشت: ۱. متأسفانه درگذشت عظیما در ۲۰ اردیبهشت بوده و این سوگ با تأخیر رسانهای شده. ۲. گویا سن دقیقتر عظیما ۹۳ سال است و…
❤74👍6😢6👎4
همی تا برآید به تدبیر کار، مدارایِ دشمن به از کارزار اگر پیلزوری و گر شیرچنگ به نزدیکِ من صلح بهتر که جنگ بوستان سعدی
👏44❤29👎18👍10
درد بومی در دلِ نازکِ جهانوطنت اندکی جا اگر به جا ماندهست از غمی خانگی پریشان باش روز و شب در عزای بیگانه مویه کردی و جامه چاک زدی ساعتی سوگوار ایران باش ◽️ وحید عیدگاه طرقبهای @vahididgah
❤81👏14👎9👍4👌3😢2
چرا پزشکیان سؤالاتی را که باید از مسؤلین بپرسد، از مردم میپرسد؟!
🤣86👍28👏6❤5
عجیب واقعهای و غریب حادثهای؛ أنا اصطبرتُ قتیلاً و قاتلی شاکی* حافظ *من بر کشته شدن صبورم و قاتلم شاکیست!
👏70😢25❤16👌9👍6👎4
ز هزار خونِ سعدی بحلند بندگانت؛ تو بگوی تا «بریزند» و بگو که: «من نگفتم»! بِحِل: معاف
👌62❤29👏13👍11👎2💯1😢1
بدیهی است که اکثریت قاطع مردم مخالف خسارت به اموال عمومیاند. قطعی اینترنت باعث روزانه هزاران میلیارد ضرر است؛ آیا خسارت به اموال عمومی فقط شامل سطل آشغال و نرده و... است و این مورد جزو خسارت به اموال مردم شمرده نمیشود؟
👍150👏22👎9❤8💯1🙏1
کنند تهنیت یکدگر همی به حیات بقیّتی که ز انسان بمانْد و از حیَوان کمال اسماعیل این شعر را پس از کشتار مغول در وصف آن فجایع سروده و در ادامه گفته: به دستِ تیغ، گریبانِ زندگی شده چاک به پای عمر در افتاده دامنِ خِذلان کمال امیدوار بوده که سلطان جلال الدین خوارزمشاه بتواند در برابر مغولان ایستادگی کند. امیدی که پایانش را میدانید. خذلان: درماندگی، ضعف، سستی، بییار ماندن. https://t.me/oragheparishan
😢45❤15👏3👍2
ای درختانِ عقیمِ ریشهتان در خاكهایِ هرزگی مستور یك جوانهی ارجمند از هیچ جاتان رُست نتواند ای گروهی برگِ چركین تار چركین پود یادگارِ خشكسالیهای گردآلود هیچ بارانی شما را شست نتواند (مهدی اخوان ثالث)
❤86👍20👏7👎6👌5💯3😢3🙏2
نفرین بر شما که ایران را از بزرگانش محروم کردید و مشتی رجاله را بر صدر نشاندید که مجیزگویتان باشند. بیضاییها را راندید که به سلحشورها میدان بدهید. تاریخ بر تباهی شما گواه است.
👍142❤31👏15👎12👌5💯1🤣1😢1
Showing the 12 most recent of 21 posts we hold for @oragheparishan. 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.
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 5 registered channels — 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“اوراق پریشان-رضا ضیاء” (@oragheparishan), 3,449 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/oragheparishan.
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.