5 measurements spanning 7 days, net +9. 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 1,064–1,079 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Aug 2026, 01:39
1,075
-2
11 Aug 2026, 10:16
1,077
+9
8 Aug 2026, 08:02
1,068
+2
8 Aug 2026, 00:17
1,066
no change
7 Aug 2026, 17:30
1,066
first reading
Engagement
20 posts held, back to 26 July 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
26.0%
avg views ÷ 1,075 subscribers
Avg views / post
279
20 posts measured
Reaction rate
1.39%
reactions ÷ views · ER floor
Posts in window
20
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. It is computed over the 15 of 20 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
20 (26 July 2026 – 7 August 2026)
Views total
5,580
Reactions total
57
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 00: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.
Reaction mix
57 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 68.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
39
68.4%
👏
4
7.02%
🎃
2
3.51%
👍
2
3.51%
🥰
2
3.51%
☃
1
1.75%
🎄
1
1.75%
💅
1
1.75%
💋
1
1.75%
🔥
1
1.75%
😍
1
1.75%
😭
1
1.75%
🙉
1
1.75%
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 15 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 57reactions 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 26 July 2026 to 7 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.
🎮 تیم ARMSX2 حالا برای PS3 هم شبیهساز توسعه میده! نیمنگاهی به ARMSX3 هم داشته باشید!
نمیدونم تیم ARMSX2 چی میزنن که اینقدر انرژی دارن ولی خب سراغ شبیهساز PS3 هم رفتن و الان دارن روی فورک RPCS3 هم کار میکنن!
کمی بگذره ببینیم از RPCSX بهتر میشه یا نه.
و البته امیدوارم که این کارها باعث نشه تمرکزشون از روی ARMSX2 برداشته بشه.
‼️ این شبیهساز تازه شروع شده پس اگه حوصلهی باگ ندارید سمتش نرید.
⌨ پیوند به گیتها…
▶️ برنامهنویسهای شبیهساز RPCS3 اصلا دارن چکار میکنن؟
هرگاه سخن از شبیهسازی PS3 با RPCS3 میشه، خیلیا میگن خوب نیست و باگ داره و گیر داره و ...
این در صورتیه که تیم RPCS3 با اختلاف بیشتر از هر تیم دیگری داره روی شبیهساز کار میکنه، اون چیزی که سخته و اذیت میکنه معماری PS3ئه که استاندارد نیست!
این یعنی در آینده احتمالا شبیهساز PS4 و PS5 سبکتر از RPCS3 باشن!
برای اونهایی که تئوری توطئه و توهم دارند که مثلا…
🎮 تیم ARMSX2 حالا برای PS1 هم شبیهساز توسعه میده! نیمنگاهی به ARMSX1 هم داشته باشید!
همونطور که میدونید برنامهنویس DuckStation خیلی وقته که به روز رسانی برای اندروید نداده و نگارش اندروید اون اوپنسورس هم نیست.
تیم ARMSX2 حالا اومده و با فورک کردن PSXE میخواد این مشکل را هم حل کنه و قراره یک شبیهساز اوپنسورس و به روز برای PS1 هم داشته باشیم.
‼️ این شبیهساز تازه شروع شده پس اگه حوصلهی باگ ندارید سمتش نرید…
📌 بهروزرسانی برای پک شبیهساز Obtainium
این پک مناسب دستگاههاییست که دو اسکرین دارند
AYN Thor, RG Dual, ...
Obtainium Emulation Pack • v7.14.0
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Android-dual:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 آموزش استفاده از این برنامه
🐙 GitHub
#ObtainiumEmulationPack
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
به روزترین…
📌 بهروزرسانی برای پک شبیهساز Obtainium
پک مناسب تمامی دستگاههای اندرویدی
Obtainium Emulation Pack • v7.14.0
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Android:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 آموزش استفاده از این برنامه
🐙 GitHub
#ObtainiumEmulationPack
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
به روزترین کانال اخبار و برنامههای شبیهسازی:
🎮 …
📌 به روز رسانی برای شبیهساز پیاس ۳
مناسب مکبوکهای جدید که پردازنده Apple Silicon سری M دارند.
RPCS3 • build-5295f3ac18667050f59b0faa34f4d319f3c86413
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Macos arm:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 پیوند به آموزشها، هرچی نیاز داشته باشید اینجا هست
🌐 لیست سازگاری
🐙 GitHub
#ps3 #RPCS3 #sony
ـــــــــــــــــــــــــــ…
📌 به روز رسانی برای شبیهساز پیاس ۳
مناسب مکبوکهای قدیمی که که پردازنده اینتل x86_64 دارن.
RPCS3 • build-5295f3ac18667050f59b0faa34f4d319f3c86413
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Macos:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 پیوند به آموزشها، هرچی نیاز داشته باشید اینجا هست
🌐 لیست سازگاری
🐙 GitHub
#ps3 #RPCS3 #sony
ــــــــــــــــــــــــــــــــــ…
📌 به روز رسانی برای شبیهساز پیاس ۳
‼️ توجه: این نگارش مخصوص معماری ARM است و روی کامپیوترهای معمولی کار نخواهد کرد، اگر پردازنده اینتل یا AMD دارید باید نگارش x86_64 را نصب کنید.
RPCS3 • build-5295f3ac18667050f59b0faa34f4d319f3c86413
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Linux arm:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 پیوند به آموزشها، هرچی نیاز داشته باشی…
📌 به روز رسانی برای شبیهساز پیاس ۳
مناسب برای بیشتر کامپیوترها که پردازنده x86_64 دارن.
RPCS3 • build-5295f3ac18667050f59b0faa34f4d319f3c86413
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Linux:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 پیوند به آموزشها، هرچی نیاز داشته باشید اینجا هست
🌐 لیست سازگاری
🐙 GitHub
#ps3 #RPCS3 #sony
ـــــــــــــــــــــــــــــــــــــــ…
📌 به روز رسانی برای شبیهساز پیاس ۳
‼️ توجه: این نگارش مخصوص معماری ARM است و روی کامپیوترهای معمولی ویندوز کار نخواهد کرد، اگر پردازنده اینتل یا AMD دارید باید نگارش x86_64 را نصب کنید.
RPCS3 • build-5295f3ac18667050f59b0faa34f4d319f3c86413
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Windows arm:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 پیوند به آموزشها، هرچی نیاز د…
📌 به روز رسانی برای شبیهساز پیاس ۳
مناسب برای بیشتر کامپیوترهای ویندوزی، که پردازنده x86_64 دارن.
RPCS3 • build-5295f3ac18667050f59b0faa34f4d319f3c86413
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
Windows:
📥 پیوند برای دانلود
ـــــــــــــــــــــــــــــــــــــــــــــــــــــ
🌐 پیوند به آموزشها، هرچی نیاز داشته باشید اینجا هست
🌐 لیست سازگاری
🐙 GitHub
#ps3 #RPCS3 #sony
ـــــــــــــــــــــــــــ…
Showing the 12 most recent of 20 posts we hold for @gooyban_emulation. 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.
Mentions
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.
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 15 August 2026 — this
entry's latest reading, not the date you are reading this.
“Gooyban Emulation” (@gooyban_emulation), 1,075 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/gooyban_emulation.
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.