🚀 نسخهٔ ۰.۹.۱۹ 📅 آخرین نسخه — شهریور ۱۴۰۵ ✨ امکانات جدید 🔗 دریافت همزمان چند لینک با راستکلیک روی صفحه یا متن انتخابشده، میتوانید فهرست لینکهای موجود را مشاهده کرده و چند لینک را بهصورت همزمان برای دانلود انتخاب کنید. برای استفاده از این قابلیت، نصب آخرین نسخهٔ افزونهٔ مرورگر ضروری است. 💡 ارسال پیشنهاد و گزارش مشکل اکنون میتوانید ایدهها، پیشنهادها و گزارش مشکلات خود را مستقیماً از طریق منوی «راهنما» ا…

Channel
PersianDownloadManager
@persiandownloadmanager
On this record: Topic · Growth · Engagement · Posts · Cite this entry
8subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003964986692 |
|---|---|
| Type | Channel |
| Username | @persiandownloadmanager |
| Created | Between 1 April 2026 and 27 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/persiandownloadmanager |
Topic
Technology — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 12:36 | 8 | +3 |
| 13 Sept 2026, 07:58 | 5 | +1 |
| 4 Sept 2026, 20:16 | 4 | +3 |
| 28 Aug 2026, 21:45 | 1 | no change |
| 7 Aug 2026, 22:57 | 1 | first reading |
Engagement
2 posts held, back to 27 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 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 2 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
🚀 نسخهٔ ۰.۹.۱۸ 📅 شهریور ۱۴۰۵ ✨ امکانات جدید 🔤 تنظیم اندازهٔ قلم از این پس میتوانید اندازهٔ قلم برنامه را از طریق منوی «نمایش»، روی یکی از حالتهای «کوچک»، «معمولی» یا «بزرگ» تنظیم کنید. اندازهٔ انتخابشده بهصورت خودکار ذخیره خواهد شد. 🗑 حذف گروهی فایلها در هنگام حذف گروهی دانلودها، اکنون میتوانید فایلهای مرتبط را نیز از روی دیسک حذف کنید. امکان انتقال فایلها به «سطل بازیافت» یا حذف دائمی آنها وجود دارد. …
Showing the 2 most recent of 2 posts we hold for @persiandownloadmanager. 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.
Cite this entry
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“PersianDownloadManager” (@persiandownloadmanager), 8 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/persiandownloadmanager.
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.