Channel
@Parsashonam
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
131,063subscribers
+191 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001414830801 |
|---|---|
| Type | Channel |
| Username | @Parsashonam |
| Description | دریافت کانفیگ شخصی رایگان: @Parsashonam_Bot خرید کانفیگ: @ParsashonamRobot تبلیغات: @ParsashonamBots |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Parsashonam |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 62% 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 |
|---|---|---|
| 12 Aug 2026, 10:54 | 131,063 | +22 |
| 11 Aug 2026, 11:42 | 131,041 | +119 |
| 10 Aug 2026, 09:50 | 130,922 | +72 |
| 9 Aug 2026, 07:54 | 130,850 | +16 |
| 8 Aug 2026, 06:31 | 130,834 | -13 |
| 7 Aug 2026, 08:37 | 130,847 | -25 |
| 6 Aug 2026, 17:33 | 130,872 | first reading |
21 posts held, back to 14 June 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 17 pagesof 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 6 August 2026 |
|---|---|
| Posts held | 21 (14 June 2026 – 6 August 2026) |
| Views total | 438,600 |
| Reactions total | 3,640 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 18:17 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
9,657 reactions across 21 posts, in 3 distinct kinds. The most used accounts for 62.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6,020 | 62.3% | |
| 💔 | 2,539 | 26.3% | |
| 🤣 | 1,098 | 11.4% |
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 9,657reactions 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 14 June 2026 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.
دو آپدیت اعمال شد. 1️⃣ مشکل کانفیگ مختص همراهاول در ساب رایگان حل شد، لطفا سابتون رو آپدیت کنید. 2️⃣ مشکلی در خصوص اجرای ویدیوهای دانلود شده با دانلودر روی iOS وجود داشت که اون هم رفع شد. دریافت کانفیگ رایگان شخصی: @Parsashonam_Bot 🤖 اگر نیاز به خرید هم داشتید، با گیگی دو تومن میتونید مولتی لوکیشن خرید کنید: @ParsashonamRobot ✅
❤79💔1
Signed Parsa
علاوهبر دانلودر، از این به بعد نرخ ارز هم دیگه میتونید با ربات بگیرید، مثلا بنویسید تتر نرخ لحظهایش رو میگه، یا میتونید از تبدیل ارزی به ارز دیگهای استفاده کنید. برای تبدیل اینطوری میتونید استفاده کنید: مثلا برای تبدیل سه میلیون تومان به تتر: ۳ میل تومن تتر یا ۳۰۰۰۰۰۰ تومن تتر برای سایر ارزها به هم همینطور میتونید پیش برید. درضمن مثل دانلودر این بخش هم در گروهها قابل استفاده هست. هدف صرفا اینه که هرچیزی که …
❤148
Signed Parsa
Parsashonam everything🎀
❤274💔2
Signed Yasi🐾
سلام، به ربات رایگان یه قابلیت دانلودر پست هم اضافه شده. برای دانلود فقط کافیه لینک پست رو بفرستید دانلود میکنه براتون، توی گروه هم قابل اد هست و کار میکنه. درحال حاضر برنامههای زیر رو برای دانلود ساپورت میکنه: اینستاگرام (بهجز استوری) تیکتاک توییتر ساندکلاد پینترست یوتوب اسپاتیفای هدفم این بود که نیاز نباشه برای هرچیزی از یک ربات جدا استفاده کنید، مشکلی که خودم با این رباتا داشتم. پس از این به بعد دریافت کان…
❤375💔1
Signed Parsa
مشکل جمنای روی کانفیگای رایگان حل شد. دریافت کانفیگ رایگان شخصی: @Parsashonam_Bot🤖 اگر نیاز به خرید هم داشتید، با گیگی دو تومن میتونید مولتی لوکیشن خرید کنید: @ParsashonamRobot✅
❤94💔8
Signed Parsa
فینال واقعا شروع شد. ایران - آمریکا
🤣552💔116❤23
Signed Parsa
درود بچهها🥹 شبتون بخیر🤩 این مدت ما خیلی اوقات باهم صحبت کردیم و من واقعا از این همصحبتی با شما خوشحالم. اما نمیخوام فعالیت و روتین چنل پارسای عزیزم بخاطر این موضوع تغییر بکنه؛ به همین خاطر، تصمیم گرفتیم که برای این صحبتها یک چنل جداگانه داشته باشیم. اگر دوست داشتین همراه صحبتهای ما باشید، اونجا میبینمتون🤩 https://t.me/Yasishonamtalk
❤143💔2
Signed Yasi🐾
آیا کشور فقط تهرانه؟
💔1,700❤30
Signed Parsa
دوستانی که از ربات رایگان ساب گرفته بودید، لطفا آپدیت کنید، کانفیگ ipv6 اضافه شد. دریافت کانفیگ رایگان شخصی: @Parsashonam_Bot 🤖 کانفیگهای ربات رایگان هم مجدد شارژ شد. با زدن دکمه "دریافت/تمدید کانفیگ رایگان" میتونید کانفیگ شخصیتون رو دریافت کنید.
❤92
Signed Parsa
چه عجب، ipv6 داره برمیگرده!
❤250💔22
Signed Parsa
سلام، یکسری اختلالات عجیب روی شبکه هست مثل قطع و وصلی یا حتی پریدن آنتن، حقیقتا نمیدونم دارن چکار میکنن یا چه اتفاقی قراره بیوفته ولی خب تا وقتی که دسترسی به اینترنت بینالملل قطع نشده باشه کانفیگهای ربات رایگان هم وصلن. @Parsashonam_Bot 🤖 اخبار هم از این خبر میده که باز جنگی در راهه در نتیجه مراقبت کنید، شبتون خوش.💙
❤142💔20
Signed Parsa
جهت یادآوری کانفیگای ربات رایگان فعاله، میتونید کانفیگ شخصی رایگان خودتون رو از ربات بگیرید. @Parsashonam_Bot 🤖 اگر نیاز به خرید هم داشتید، با گیگی دو تومن میتونید مولتی لوکیشن خرید کنید: (حتما قبلش تست بگیرید) @ParsashonamRobot ✅
❤84💔5
Signed Parsa
Showing the 12 most recent of 21 posts we hold for @Parsashonam. 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.
Citation-graph rank — 84,350 of 1,151,006entries 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.
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 11 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Parsashonam | V2Ray | VPN” (@Parsashonam), 131,063 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Parsashonam.
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.