Hacking & security — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
Growth
17 measurements spanning 67 days, net -114. 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 3,997–4,145 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Oct 2026, 14:27
4,014
-6
5 Oct 2026, 22:16
4,020
-13
28 Sept 2026, 18:57
4,033
-18
19 Sept 2026, 01:01
4,051
-5
14 Sept 2026, 06:56
4,056
-7
10 Sept 2026, 07:18
4,063
-13
1 Sept 2026, 13:54
4,076
-8
29 Aug 2026, 15:57
4,084
-4
26 Aug 2026, 17:17
4,088
-9
23 Aug 2026, 18:15
4,097
-8
20 Aug 2026, 04:35
4,105
-8
16 Aug 2026, 18:47
4,113
-6
13 Aug 2026, 08:35
4,119
-4
10 Aug 2026, 17:44
4,123
-1
7 Aug 2026, 15:22
4,124
-4
7 Aug 2026, 02:00
4,128
no change
7 Aug 2026, 01:56
4,128
first reading
Engagement
18 posts held, back to 16 May 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 14 July 2025. An engagement rate over an empty window would be a number about nothing.
{{مهما دعتك قدرتك على ظلم الناس فتذكر قدرة الله عليك}}
حالة ابتزاز تم التعامل معها بكل سهوله تفرمت الجهاز ونحذفت جميع حسابات هذه الشخص
اي حاله ابتزاز نحلها لوجه الله وبدون مقابل فقط الابتزاز
@alsalhi1 {من ستر على مسلم ستره الله في الدنيا والآخرة}
صباح الخير اليوم راح انشر فيديو جدا جدا جدا مهم
برنامج تكدر تحصل بي ارباح يوميه واسبوعيه وبكل بساطه لا تحتاج تدفع ولا تحتاج تكضي وقت طويل بل برنامج فقط ضغطة وحده وتبدي جمع فلوس
الفيديو للفائد اريد لكل تستفاد
راح ينشر داخل قناه تلغرام هنا....
اذا تحبون انزل الكم شرح على قناتي بل يوتيوب حتى الكل تستفاد وتسوي تقديم مسبق
قناتي على يوتيوب
https://youtube.com/@user-alsalhi2000
راح نرجع بل نشر مستمر ونعوض قناة اليوتيوب الي وقفتها الشركة بسبب نشر مواضيع الهكر والاختراق
اشترك بل قناة وفعل جرس تنبيهات
Signed منتظر الصالحي
Showing the 12 most recent of 18 posts we hold for @alsalhi9. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
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 18 most recent posts we hold, published 16 May 2023 to 14 July 2025. 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.
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.
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 12 October 2026 — this
entry's latest reading, not the date you are reading this.
“مقبرة الهكر” (@alsalhi9), 4,014 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/alsalhi9.
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.