4 measurements spanning 7 days, net +94. 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 5,148–5,333 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Sept 2026, 19:00
5,312
+143
3 Sept 2026, 06:26
5,169
-49
2 Sept 2026, 03:00
5,218
no change
2 Sept 2026, 02:45
5,218
first reading
Engagement
5 posts held, back to 21 February 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.
ERR · 30 days
28.8%
avg views ÷ 5,312 subscribers
Avg views / post
1,530
1 post measured
Reaction rate
0.588%
reactions ÷ views · ER floor
Posts in window
1
of 5 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 1 September 2026
Posts held
5 (21 February 2026 – 1 September 2026)
Views total
1,530
Reactions total
9
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
2 Sept 2026, 03:00 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
62 reactions across 3 posts, in 9 distinct kinds. The most used accounts for 51.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
32
51.6%
🤣
11
17.7%
❤🔥
8
12.9%
🔥
5
8.06%
👍
2
3.23%
🌭
1
1.61%
👏
1
1.61%
💋
1
1.61%
🥰
1
1.61%
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 3 of the 5 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 62 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 21 February 2026 to 1 September 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.
یه زیرنویس خوب فقط ترجمه خوب نمیخواد؛ یه ادیتور خوب هم میخواد.
سابیار هر دو رو کنار هم آورده:
ترجمه هوشمند و محاورهای
با درک کانتکست، اسلنگ و لحن شخصیتها.
استودیوی کامل زیرنویس داخل مرورگر
پخش ویدیو، تایمینگ دقیق، Split و Merge، جستجو و جایگزینی، استایلینگ ASS و پیشنمایش زنده.
و مهمتر از همه؛ از پایه برای فارسی و RTL ساخته شده؛ بدون جابهجا شدن علائم، بههمریختن فارسی و انگلیسی یا جدا شدن حروف.
بدون نصب نرما…
ترجمه حرفهای زیرنویس انیمه فقط انتقال معنی جملهها نیست.
ممکن است دو شخصیت یک حرف را بزنند، اما یکی رسمی و مؤدب باشد و دیگری خودمانی، گستاخ یا شوخطبع. اگر ترجمه فقط لغوی باشد، لحن شخصیتها، فاصله اجتماعی و حس واقعی صحنه از بین میرود.
سابیار تلاش میکند قبل از ترجمه، خود اثر را بهتر بشناسد.
قسمتهای مختلف یک انیمه به یک پروفایل لحن متصل میشوند تا در قسمت بعد، تنظیمات و سبک ترجمه قبلی دوباره قابل استفاده باشد؛ …
سابیار برای زمانی ساخته شده که ترجمهی زیرنویس فقط «ترجمهی چند خط متن» نیست.
در زیرنویس، فقط معنی جملهها مهم نیست؛ زمانبندی باید حفظ شود، فرمت فایل نباید بههم بریزد، متن فارسی باید درست نمایش داده شود، اسمها و اصطلاحات باید یکدست بمانند و خروجی نهایی باید قابل بررسی، ویرایش و استفاده باشد.
سابیار این مسیر را دقیقتر، منظمتر و قابلکنترلتر میکند.
📝 ترجمه در سابیار
بخش ترجمه، هستهی اصلی سابیار است.
کاربر …
Showing the 5 most recent of 5 posts we hold for @SubYarcom. 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.
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.
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 8 September 2026 — this
entry's latest reading, not the date you are reading this.
“SubYar | سابیار” (@SubYarcom), 5,312 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/SubYarcom.
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.