4 measurements spanning 8 days, net -30. 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 8,525–8,564 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
3 Sept 2026, 18:38
8,529
-20
31 Aug 2026, 04:03
8,549
-7
27 Aug 2026, 22:06
8,556
-3
27 Aug 2026, 00:02
8,559
first reading
Engagement
20 posts held, back to 2 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 2 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
16.3%
avg views ÷ 8,529 subscribers
Avg views / post
1,390
3 posts measured
Reaction rate
1.11%
reactions ÷ views · ER floor
Posts in window
3
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 20 August 2026
Posts held
20 (2 July 2026 – 20 August 2026)
Views total
4,158
Reactions total
46
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
28 Aug 2026, 16:58 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
463 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 64.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
297
64.1%
😁
88
19.0%
🔥
47
10.2%
❤🔥
26
5.62%
⚡
3
0.648%
😭
1
0.216%
🥰
1
0.216%
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 463 reactions 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 2 July 2026 to 20 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.
⏳ باقي أقل من 12 ساعة!
خصم 40% على سعر كورس Application Security Engineering هينتهي خلال أقل من 12 ساعة، وبعدها السعر هيرجع للسعر الأساسي.
لو حابب تشترك في الكورس وتستفيد من الخصم قبل انتهائه، ابعتلنا على واتساب وهتوصلك كل التفاصيل كاملة 👇
📲 لينك الواتساب
ابدأ رحلتك في مجال Application Security الآن.
بفضل الله، تم إطلاق كورس Application Security Engineering رسميًا على سايبر عرب.
الكورس مصمم لتأهيلك للعمل كـ Application Security Engineer، من فهم الـ Architecture والـ Threat Modeling، مرورًا بالـ Secure Code Review والـ Security Assessment، وصولًا إلى الـ DevSecOps والـ Security Monitoring.
الكورس مبني على خبرة عملية وبيحاكي طريقة عمل فرق الـ AppSec داخل الشركات.
خص…
الحجز المسبق لكورس Application Security Engineering مفتوح الآن🔥
سجّل بياناتك في الفورم واحصل على خصم 60%من سعر الكورس، وهنبعتلك تفاصيل الدفع قبل الإعلان الرسمي للكورس، مع أولوية تفعيل الكورس قبل الإطلاق.
بعد إعلان الكورس، هيكون الخصم المتاح 40% لمدة 48 ساعة فقط.
سجّل الآن واستفيد بالخصم.
لينك التسجيل
السلام عليكم ورحمة الله وبركاته ❤️
قريبًا على منصة سايبر عرب، هنعلن عن كورس جديد في مجال الـ Application Security Engineering باللغة العربية. 🔥
لكن قبل الإعلان الرسمي عن الكورس، خلينا نتكلم شوية عن المجال نفسه، لأنه من المجالات المهمة جدًا واللي ناس كتير بتخلط بينه وبين الـ Penetration Testing.
يعني إيه Application Security؟
ببساطة، هو المجال المسؤول عن تأمين التطبيقات خلال دورة حياة تطوير البرمجيات بالكامل Secure…
🚨 قريبًا على منصة سايبر عرب 🚨
لأول مرة في الوطن العربي 🔥
بنقدملكم كورس Application Security Engineering
مع م/ محمد سليم
كورس مختلف هتتعلم فيه إزاي الـ Application Security بيتطبق فعليًا داخل الشركات، بدايةً من تصميم الأنظمة والـ Threat Modeling، مرورًا بالـ Secure Coding وCode Review، وصولًا إلى DevSecOps والـ Security Monitoring.
🎯 لو مهتم بمجال AppSec وعايز تبدأ أو تطور مستواك… استعد.
انتظرونا… اللي جاي مختلف.
🎁 بالمناسبة، لسه عندك فرصة!
متاح خصم 40% على سعر كورس SOC L1 لمدة 24 ساعة فقط للناس اللي ملحقتش العرض السابق. 🔥
📩 للتسجيل والاستفسار، تواصل مع الدعم: واتساب الدعم
⏳ الحق العرض قبل ما ينتهي!
🚨 Announcement | تحديثات مهمة في كورس SOC L1
1. إن شاء Session 14 هتنزل بكرا، ودي آخر Session نظرية. بعدها هنبدأ Labs عملية على سيناريوهات حقيقية زي Phishing وAttacks مختلفة على Splunk, QRadar & Elastic، والـ Practical Section هيتحدث باستمرار بـ Labs جديدة.
2. هيتم حل مشكلة الصوت خلال الأيام الجاية، وتحسين الجودة والمستوى في الفيديوهات القديمة والجديدة.
3. هيتم إضافة أسئلة تساعدك تقيس مدى استيعابك وتعرف إيه اللي م…
نرحب بانضمام مهندس Mohamed Selim إلى فريق Cyber3rb.
محمد يشغل حاليًا منصب Application Security Engineer في Inisev، ولديه خبرة سابقة في Penetration Testing وSoftware Engineering في عدة شركات، بالإضافة إلى سجل مميز في مسابقات CTF وبرامج Bug Bounty، مع acknowledgment من أكثر من 100 منظمة عالمية، من بينها Yandex, Oracle, Godaddy, LinkedIn, IBM, Google, والأمم المتحده
أهلًا بيك في الفريق، ونتمنى لك التوفيق في رحلتنا الق…
25 مشترك وهنقفل عرض 60%
ولكن اللي سجل في الحجز المسبق هيكون قدامه 24 ساعه يشترك فيها ⚠️
🔥7❤1
Showing the 12 most recent of 20 posts we hold for @cyber3rb. 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 3 September 2026 — this
entry's latest reading, not the date you are reading this.
“سايبر عرب | Cyber3rb” (@cyber3rb), 8,529 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/cyber3rb.
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.