5 measurements spanning 9 days, net -23. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 6,409–6,438 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Aug 2026, 21:36
6,412
-10
13 Aug 2026, 23:47
6,422
-11
10 Aug 2026, 22:34
6,433
-2
7 Aug 2026, 22:08
6,435
no change
7 Aug 2026, 12:16
6,435
first reading
Engagement
20 posts held, back to 14 April 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 9 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
29.4%
avg views ÷ 6,412 subscribers
Avg views / post
1,890
2 posts measured
Reaction rate
0.637%
reactions ÷ views · ER floor
Posts in window
2
of 20 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 28 July 2026
Posts held
20 (14 April 2026 – 28 July 2026)
Views total
3,770
Reactions total
24
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 03:09 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.
Reaction mix
861 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 55.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
476
55.3%
💔
144
16.7%
🔥
133
15.4%
🥰
43
4.99%
🕊
28
3.25%
💯
21
2.44%
❤🔥
9
1.05%
😍
7
0.813%
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 20 of the 20 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 861reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 April 2026 to 28 July 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.
Telegram Stars
Stars received
6
across the posts below
Posts paid on
5
of 20 we hold a reading for · 25%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Marzban_Nameh. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 14 April 2026 to 28 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
𝗣𝗚𝗖𝗹𝗼𝗰𝗸𝗠𝗚
مهاجرت / ریستور / تغییر دیتابیس
- ریستور بکاپ اتوماتیک
- تبدیل دیتابیس های مختلف به یکدیگر
- مهاجرت آسان از سایر پنل ها به پاسارگارد
- مدیریت ارور ها و رفع اتوماتیک آنها
گیت هاب
⚠️ این نسخه بتا هست ، با وجود تست های مختلف همچنان امکان وجود باگ هست ، حتما از قبل بکاپ داشته باشید
💸 اگر از این پروژه راضی بودید و کمکی به شما کرد ، به پاس قدردانی از تیم پاسارگارد به آنها دونیت کنید
دونیت
⭐️ در صورت امکان ب…
ادونس سرچ پاسارگارد بینظیره!
مثل هلو هر دیتایی که بخواین رو در اختیارتون میزاره، این بخش شبیه همون کوئریهایی هست که توی دیتابیس مرزبان میزدیم منتها با پاسارگارد دیگه به کوئری نیاز نیست.
اگر بزنین روی Protocol Data راحت میتونین UUID یه پروکسی رو توی پنل سرچ کنین و یوزر رو پیدا کنین، کاربرد؟ اگه ببینی یه پروکسی از خودت داره کف تلگرام توی کانالهای مختلف میچرخه راحت میتونی بفهمی کی شیطنت کرده.
یوزر هایی که از یه …
⚡️ « پس از مهاجرت به پاسارگارد »
ممکنه یکی دو روز گیج بزنین ولی در نهایت دستتون میاد که هر بخش مربوط به چی هست و از آزادی عملی که دارین شگفت زده میشین.
☘ « داکیومنت و نکات »
https://docs.pasarguard.org/fa
طبق داکیومنت مهاجرت رو انجام بدین، نکاتی که ذکر شده رو به دقت بخونین چون حائز اهمیت هستند.
☘ « ایمیج MySQL »
به عنوان مثال اگر MySQL هستین و ایمیجتون latest هست اصلا به lts تغییر ندین چون مشکل بوجود میاد و…
چی میشد اگه یک نفر بود که...
🔸 ساعت 4 صبح، بدون یک ثانیه تأخیر، با دقیقترین لحن به مشتریهای کانالت جواب میداد؟ 📞
🔸 فرقی نمیکرد مشتری انگلیسی، عربی یا فارسی چت میکنه؛ به زبان خودش بهش مشاوره میداد و میفروخت؟ 💭
🔸 وقتی مشتری عصبانی میشد، میفهمید و سریع چت رو بهت ارجاع میداد تا مشتری نپره؟ 😡
🔸 هیچوقت خسته نمیشد، مرخصی نمیخواست، حقوق ثابت نمیگرفت و تداخل چت با ادمین انسانی هم نداشت؟ ⚡️
فکر کن چقدر از…
میخوای کاستوم کانفیگ باشی؟
برای این کار دو تا آپشن روی میز هست!
1. کلا سابت رو غیر کلاینتهای کلش و سینگباکس محدود کنی به کاستوم کانفیگ و کلاینتهایی که کاستوم ساپورت میکنن و بای بای با بقیه کلاینتها.
2. صرفاً کلاینتهایی که کاستوم کانفیگ ساپورت میکنن رو کاستوم کنی اما در عین حال اجازه اضافه شدن ساب رو به سایر برنامهها هم بدی.
« آپشن اول »
برای این یکی زحمت شما کمتره، کافیه برای Rule زیر
^.*
از منوی ر…
هرچی از فیچرهای پاسارگارد بگیم کم گفتیم
1. قسمت Settings
2. قسمت Subscription Rule
3. گزینه Add Rule رو بزنید.
به عنوان مثال پترن زیر رو بزارین
^[Vv]2raytun.*
بعد جلوش از منو Block رو انتخاب کنین.
در نهایت گزینه Save انتهای صفحه رو بزنین.
📍اینطوری برنامه v2raytun که گفته میشه back door داره و امن نیست بلاک میشه و دیگه لینک داخلش اضافه نمیشه.
« مهم »
ترتیب این rule ها اهمیت دارد، به عنوان مثال اگر rule ب…
🤖 توی پاسارگارد بخش Settings بات تلگرام رو فعال کنید همچنین تیک For Admins Only رو بردارید.
📊 الان یوزراتون با ارسال کردن لینک سابشون توی بات میتونن مشخصات اشتراک خودشون رو مشاهده کنن.
🌟 بخش جالب اینه که یه فایل txt هم ارسال میشه که تمام پروکسیهای اون یوزر داخلش هست و برای مواقعی که لینک ساب به هر دلیلی کار نمیکنه عالیه.
#TelegramBot
سیر مهاجرت برای بسیاری از ما به این صورت بوده:
1. وبپنل x-ui چینی
2. وبپنل 3x-ui ثنایی (همچنان بهروز)
3. وبپنل مرزبان
4. وبپنل پاسارگارد
مرزبان برای ما صرفاً یک وبپنل نبود؛ یک انقلاب بود. با اومدنش یک کامیونیتی پویا شکل گرفت. از هم یاد گرفتیم، دوستان ارزشمندی پیدا کردیم و کلی تیم مختلف به وجود اومد.
تیم پاسارگارد هم چندین ماه صبر کردند تا تغییرات روی مرزبان اعمال شود، اما در نهایت مسیرشون جدا شد.
به اح…
« در خصوص مهاجرت »
1⃣ اگر از دیتابیس MySQL استفاده میکنین قبل از مهاجرت به پاسارگارد ، هر گونه Trigger یا Event رو دراپ کنید بعد بکاپ رو اکسپورت کنین و طبق داکیومنت پیش برین. اگر دراپ نکنین موقع مهاجرت بکاپ توی پاسارگارد اضافه نمیشه.
2⃣ همچنین تیبلهای node usage همچنین node user usage رو حتماً قبل از اکسپورت کردن بکاپ empty بزنید که پروسه انتقال دیتا به پاسارگارد تسریع بشه.
🌟 واقعاً پاسارگارد شمارو از هر نوع ک…
فیلترنت را وصل کردن اما این اصلا شباهتی به فیلترنت قبل از دیماه ندارد.
فیلترنت قبلا با بسیاری از روشهای مختلف که در همه جای اینترنت خز شده بودن متصل میشد اما الان اکثریت زیر بار فیلترینگ وحشتناک اون کمرشون خم شده.
همه رو عصبی کرده، از کاربر بدبخت که الان قاعدتاً باید هزینه بیشتری متقبل بشه بگیر تا شخصی که تلاش میکنه سرویس ارائه کنه.
دیگه حتی فحشهای مختلفی که نثار وزیر قطع ارتباطات میکنیم هم از شدت عصبانیتمون…
❤47💔7❤🔥4🔥3
Showing the 12 most recent of 20 posts we hold for @Marzban_Nameh. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 14 April 2026 to 28 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 607,883 of 1,480,975entries 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.
Forward network
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.
Mentions
Named by 2 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.
Appears in Telegram’s recommendations for other channels
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.
فیلترشکن پینگچی @chanelletel · 302,487 Telegram ranks this channel #3 of 42 here — alongside 41 others — read 15 August 2026
Hiddify @hiddify · 123,134 Telegram ranks this channel #7 of 65 here — alongside 64 others — read 13 August 2026
Tenzo VPN | تنزو وی پی ان @TenzoVPN · 108,974 Telegram ranks this channel #15 of 46 here — alongside 45 others — read 15 August 2026
Unknown Vpn | فیلترشکن ناشناس @Unknown_Vpn · 90,069 Telegram ranks this channel #16 of 52 here — alongside 51 others — read 17 August 2026
عصر نوین| AminiYT @asrnovin_ir · 150,501 Telegram ranks this channel #17 of 73 here — alongside 72 others — read 12 August 2026
Github_2dust @github_2dust · 90,592 Telegram ranks this channel #18 of 71 here — alongside 70 others — read 17 August 2026
Alaedin VPN 🧞♂ علاءالدین @AlaedinVPN · 171,510 Telegram ranks this channel #22 of 36 here — alongside 35 others — read 15 August 2026
IRCF | اینترنت آزاد برای همه @ircfspace · 96,977 Telegram ranks this channel #30 of 64 here — alongside 63 others — read 16 August 2026
Mahsa Net @mahsa_net · 135,594 Telegram ranks this channel #53 of 66 here — alongside 65 others — read 13 August 2026
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 August 2026 — this
entry's latest reading, not the date you are reading this.
“مرزبان نامه” (@Marzban_Nameh), 6,412 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Marzban_Nameh.
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.