Channel
@shafiei_kadkani
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
44,378subscribers
-137 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001067067296 |
|---|---|
| Type | Channel |
| Username | @shafiei_kadkani |
| Created | 14 September 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/shafiei_kadkani |
Literature — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 12:01 | 44,378 | -7 |
| 8 Nov 2026, 05:18 | 44,385 | -5 |
| 5 Nov 2026, 23:01 | 44,390 | -1 |
| 4 Nov 2026, 20:57 | 44,391 | -7 |
| 3 Nov 2026, 21:15 | 44,398 | -3 |
| 2 Nov 2026, 20:51 | 44,401 | -10 |
| 1 Nov 2026, 18:08 | 44,411 | -7 |
| 31 Oct 2026, 17:15 | 44,418 | -2 |
| 30 Oct 2026, 15:45 | 44,420 | +9 |
| 29 Oct 2026, 17:41 | 44,411 | +10 |
| 28 Oct 2026, 18:19 | 44,401 | -1 |
| 27 Oct 2026, 20:40 | 44,402 | +1 |
| 26 Oct 2026, 23:04 | 44,401 | -16 |
| 25 Oct 2026, 20:30 | 44,417 | +4 |
| 24 Oct 2026, 17:01 | 44,413 | -15 |
| 23 Oct 2026, 18:10 | 44,428 | -4 |
| 22 Oct 2026, 19:21 | 44,432 | -3 |
| 21 Oct 2026, 15:01 | 44,435 | +10 |
| 20 Oct 2026, 12:05 | 44,425 | -1 |
| 19 Oct 2026, 13:15 | 44,426 | first reading |
31 posts held, back to 11 December 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 185 pages of 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 24 October 2026 |
|---|---|
| Posts held | 31 (11 December 2025 – 24 October 2026) |
| Views total | 93,100 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 05:30 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.
Measured directly from 12 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.
Telegram’s own ‘edited’ marker: 1 of 5 posts held from the last 30 days (20.0%) 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).
@shafiei_kadkani ـــــــــــــــــــــــ بیهقی توانست. [به بهانهٔ اول آبان و بزرگداشت ابوالفضل بیهقی. بزرگا مردا که این بوالفضل بود!] ◽️فصلی خوانم از دنیای فریبندهٔ به یک دست شکر پاشنده و به دیگر دست زهر کشنده، گروهی را به محنت آزموده کرده و گروهی را پیراهنِ نعمت پوشانیده، تا خردمندان را مقرّر گردد که دل نهادن بر نعمتِ دنیا مُحال است، و متنبّی گوید، *و مَن صَحِبَ الدّنیا طَویلاً تقلّبَتْ عَلی عَینهِ حَتّی یَری …
بزرگا! جاود‌انْ‌مرد‌ا! هُشیواری و د‌انایی نه د‌یروزی که امروزی، نه امروزی که فرد‌ایی همه د‌یروزِ ما از تو، همه امروزِ ما با تو همه فرد‌ایِ ما در تو، که بالایی و والایی [در ستایش فردوسی، محمدرضا شفیعی کدکنی] ویدیو: استاد دکتر میرجلال‌الدین کزازی بر مزار فردوسی #ایران #شاهنامه #فردوسی
می‌تونی یک مصرع حافظ رو یک عمر زندگی کنی. محمدرضا شفیعی کدکنی #یکشنبه_ها_و_حافظ درسگفتارهایی دربارهٔ حافظ محمدرضا شفیعی کدکنی لمس کنید.
دانشگاه شیراز در روز تولد ۱۹ مهرماه ۱۴۰۵ ویدیو: محمد محمدی رابع
و مرا گفت: میانِ خاموشی و سخن گفتن مغاکی است که در آن گور خرد است و گورستان چیزها. و قال لی: بین النُطقِ و الصُمتِ برزخٌ فیه قبرُ العقلِ و فیه قُبورُ الأشیاء نفری [از مقدمهٔ دفتر شعر «مثل درخت در شب باران»] *مَغاک: گودالی ژرف و عمیق محمدرضا شفیعی کدکنی هشتاد و هفت ساله شد. #شفیعی_کدکنی عکس: سارا بقایی، دانشکدهٔ ادبیات دانشگاه تهران
به بهانهٔ هشتم مهرماه روز بزرگداشت جلال الدین محمد بلخی «مثنوی معنوی حضرت مولانا بزرگ‌ترین حماسهٔ روحانی بشریّت است که خداوند برای جاودانه کردنِ فرهنگ ایرانی آن را به زبان پارسی هدیه کرده است.» محمدرضا شفیعی کدکنی این هشتگ را در این کانال پی بگیرید: #بزرگداشت_خداوندگار
زن باش! ۲۶ فروردین ۱۳۷۴ سفرنامهٔ باران[ نقد و تحلیل و گزیدهٔ اشعار شفیعی کدکنی]، به اهتمام دکتر حبیب‌الله عباسی، انتشارات سخن، صفحهٔ ۴۰۱ پی‌نوشت: این قطعه دو بیت بیشتر ندارد. در فضای مجازی ابیات دیگری در ادامهٔ این چهار بیت منسوب به ایشان منتشر شده است که جعلی‌ست.
نقشهٔ آزادی #مهسا_امینی
چو ازین کویر وحشت به سلامتی گذشتی به شکوفه‌ها به باران، برسان سلام ما را! شبِ استاد مجید درخشانی به همت مجلهٔ بخارا. اجرای قطعهٔ «به کجا چنین شتابان» با شعری از دکتر محمدرضا شفیعی کدکنی، با آهنگسازی استاد مجید درخشانی و آواز وحید تاج جمعه، ۲۰ شهریور ۱۴۰۵ فرهنگسرای نیاوران
@shafiei_kadkani ـــــــــــــــــــــــ نظام اطلاع‌رسانیِ شعرِ حافظ #یکشنبه_ها_و_حافظ ▪️در کوچک‌ترین واحد زبانِ حافظ تا متوسطش، و تا عالی‌ترین واژه‌اش خاصیت پیام‌رسانی وجود دارد. هنرمند باید تجربه کند و بکوشد تا تجارب تازه‌ای را که دیگران نکرده‌اند به انجام برساند. تجربهٔ روحی هر انسانی با تجربهٔ روحی دیگران کاملاً فرق دارد. تجربهٔ حافظ را در مورد حلاج ببینیم که چگونه است: گفت آن یار کزو گشت سرِ دار بلند جرمش ای…
هنرمند باید تجربه کند و بکوشد تا تجارب تازه‌ای را که دیگران نکرده‌اند به انجام برساند. تجربهٔ روحی هر انسانی با تجربهٔ روحی دیگران کاملاً فرق دارد. تجربهٔ حافظ را در مورد حلاج ببینیم که چگونه است: گفت آن یار کزو گشت سرِ دار بلند جرمش این بود که اسرار هویدا می‌کرد اما این دیدِ جدید که سربلند شدنِ دار است عظمت مقام حلاج را به دیگران می‌رساند. می‌گوید او آنچنان باعظمت و بزرگ بود که دار از او سربلندی و افتخار یافت. در …
@shafiei_kadkani ـــــــــــــــــــــــ نقشهٔ آزادی ▪️با نقطه، نقطه، نقطهٔ خون، خونِ رهروان خونِ هزار مهسا خونِ بسی جوان این نقشه بر سراسر میهن در حال شکل‌گیری و در گسترانگی می‌گسترد به هرسو در بیکرانگی. این نقشه را، شبانه، به یکبار نتوان کشید و دید در طول سالیانش، با خون توان کشید با خون نسل‌ها پررنگ و آشکار شود، در برابرت تا ناکجایِ هرگزیِ حیرت…
Showing the 12 most recent of 31 posts we hold for @shafiei_kadkani. 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.
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 17 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 28 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 20 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“شفیعی کدکنی” (@shafiei_kadkani), 44,378 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/shafiei_kadkani.
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.