Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 the other topics.
Growth
27 measurements spanning 95 days, net -532. 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,058–8,750 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
10 Nov 2026, 14:40
8,138
-6
7 Nov 2026, 05:36
8,144
-12
4 Nov 2026, 14:14
8,156
-5
1 Nov 2026, 13:28
8,161
-8
29 Oct 2026, 08:35
8,169
-21
26 Oct 2026, 14:48
8,190
-15
23 Oct 2026, 18:18
8,205
-21
20 Oct 2026, 16:46
8,226
-26
17 Oct 2026, 09:05
8,252
-12
14 Oct 2026, 13:11
8,264
-17
10 Oct 2026, 22:57
8,281
-36
4 Oct 2026, 17:41
8,317
-20
25 Sept 2026, 06:41
8,337
-48
16 Sept 2026, 12:57
8,385
-24
12 Sept 2026, 23:20
8,409
-23
8 Sept 2026, 19:16
8,432
-46
3 Sept 2026, 15:38
8,478
-26
31 Aug 2026, 05:35
8,504
-36
27 Aug 2026, 20:34
8,540
-23
25 Aug 2026, 05:27
8,563
first reading
Engagement
40 posts held, back to 22 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 44 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
7.90%
avg views ÷ 8,138 subscribers
Avg views / post
643
7 posts measured
Reaction rate
0.933%
reactions ÷ views · ER floor
Posts in window
7
of 40 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 12 November 2026
Posts held
40 (22 April 2026 – 12 November 2026)
Views total
4,502
Reactions total
42
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Nov 2026, 13:39 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.
What this channel posts
Photos
88
Videos
13
Links
253
Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 17s
Average length
26s
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
403 reactions across 38 posts, in 12 distinct kinds. The most used accounts for 85.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
344
85.4%
🔥
23
5.71%
🆒
10
2.48%
👏
6
1.49%
👍
5
1.24%
😁
5
1.24%
❤🔥
3
0.744%
💯
3
0.744%
🏆
1
0.248%
😈
1
0.248%
🤩
1
0.248%
🤯
1
0.248%
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 38 of the 40 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 403 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 22 April 2026 to 12 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 7 posts held from the last 30 days (14.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
مرحبا بكم جميعا!
لقد تم تحديث البوت وإضافة ميزات جديدة مع تحسينات أخرى:
📚 نظام التعليم:
نظام تعليمي يحتوي على دورات قوية، أصلية ومعتمدة على شكل فيديوهات مرتبة تظهر داخل البوت.
⚔️ الدورات المضافة الآن:
• اختراق المنافذ واستغلالها: بـ50 درس باللغة العربي.
• احتراف أداة Evilginx2: بـ32 درس باللغة الإنجليزية.
⏳ الدورات القادمة تدريجيا:
• تطوير استغلالات الثغرات: اللغة العربية.
• احتراف أداة Wireshark: اللغة الإ…
يمكنكم الآن العودة لاستخدام البوت الخاص بنا والحصول على ادوات مجانية أيضا محدثة والإطلاع على الأدوات الجديدة.
ليعمل معك البوت بشكل جيد احذف سجل المحادثة السابق ثم أرسل /start وسيرد عليك بسرعة.
https://t.me/Cybaron_bot
أعلنت منصة "بينانس" تعرضها لاختراق أمني كبير ربما نتج عن اختراق حاسوب مهندس تطورات، مما أتاح للمهاجم عمليات سحب غير مصرح بها.
وقدرت المنصة التأثير الإجمالي بنحو 6.3 مليارات دولار، مشيرة إلى تجميد قرابة 3 مليارات دولار على الشبكة حتى الآن.
وكإجراء احترازي، علقت المنصة التداول مؤقتاً على بعض المنتجات وخدمات الإيداع والسحب.
وشددت "بينانس" على أن أموال المستخدمين بأمان، وأن الخسائر ستُغطى عبر صندوق تأمين المستخدمين وأم…
ثغرة أمنية تصيب الراوترات وتمكن المهاجم من الوصول إلى كلمة المرور!
تتناول هذه المحاضرة التحقيق في ثغرتين أمنيتين لم تُوثّقا سابقًا في تطبيق Broadcom لبروتوكول 802.11، بدءًا من بوابات الكابلات القديمة القائمة على معالج eCos وصولًا إلى المنصات الأحدث القائمة على نظام Linux. باستخدام مزيج من الهندسة العكسية اليدوية وبحوث الثغرات الأمنية المدعومة ببرامج حاسوبية، تتبعنا مسار التطبيق عبر أجيال البرامج الثابتة، وأعدنا بناء…
php2shell-bypass-aslr-exp
استغلال من نوع php2shell لا يتطلب إجراء أي تعديلات على النسخة الرسمية، كما أنه لا يعتمد على تفعيل خيار display_errors أو تعديل قيود الذاكرة (limit_memory).
php2shell-CVE-2026-109618-CVE-2026-109619-PoC
نموذج إثبات مفهوم (PoC) لاستغلال php2shell، يوضح كيفية تنفيذ تعليمات برمجية عن بُعد (RCE) في بيئات PHP المعرضة للخطر.
PHP2Shell
مجموعة أدوات بحثية تراعي إصدارات PHP، مخصصة للثغرتين CVE-20…
Part of Amazon Users Data:
جزء صغير من تسريبات معلومات مستخدمين لأمازون.
يضم هذا الملف جزء بسيط من معلومات مستخدمين أمازون تم تسريبها، التسريبات تضم الكثير من المعلومات والحسابات تتجاوز 11 مليون مستخدم.
Showing the 12 most recent of 40 posts we hold for @cybro_ac. 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.
Polls
The 3 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 135%, 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.
The shares total 110%, 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.
Shares as published. No per-option vote count is published by Telegram, so none is 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 40 most recent posts we hold, published 22 April 2026 to 12 November 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.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Cybro AC” (@cybro_ac), 8,138 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/cybro_ac.
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.