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 11 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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
25 measurements spanning 102 days, net +142. 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,825–9,024 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)
Subscribers
Change
16 Nov 2026, 07:57
8,990
-11
6 Nov 2026, 20:25
9,001
+12
3 Nov 2026, 17:49
8,989
+1
31 Oct 2026, 17:21
8,988
+1
28 Oct 2026, 23:06
8,987
+5
26 Oct 2026, 03:05
8,982
+4
23 Oct 2026, 10:56
8,978
+6
20 Oct 2026, 09:00
8,972
-1
11 Oct 2026, 04:38
8,973
+1
4 Oct 2026, 17:41
8,972
+10
25 Sept 2026, 00:55
8,962
+6
15 Sept 2026, 15:01
8,956
+16
11 Sept 2026, 22:19
8,940
+3
2 Sept 2026, 17:25
8,937
+9
30 Aug 2026, 21:48
8,928
+5
27 Aug 2026, 19:24
8,923
+12
24 Aug 2026, 20:46
8,911
+14
21 Aug 2026, 08:06
8,897
+10
18 Aug 2026, 11:17
8,887
+12
15 Aug 2026, 15:23
8,875
first reading
Engagement
20 posts held, back to 17 March 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 59 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 20 posts for this entry, the most recent from 19 January 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
≈35
Videos
≈1
Links
≈1,980
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
426 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 29.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
124
29.1%
🔥
117
27.5%
❤
93
21.8%
👏
13
3.05%
🤔
11
2.58%
⚡
10
2.35%
🥰
10
2.35%
🤣
9
2.11%
👎
8
1.88%
😁
8
1.88%
😴
8
1.88%
😐
6
1.41%
🤯
4
0.939%
😍
2
0.469%
🥱
2
0.469%
🤝
1
0.235%
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 426 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 17 March 2024 to 19 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
New blog on using CLR customizations to improve the OPSEC of your .NET execution harness. This includes a novel AMSI bypass that identified by author in 2023. By taking control of CLR assembly loads, we can load assemblies from memory with no AMSI scan.
https://securityintelligence.com/x-force/being-a-good-clr-host-modernizing-offensive-net-tradecraft/
Proof-of-concept for the AMSI bypass and an implementation of a…
Happy New Year! May every binary reveal its secrets, every challenge find its solution, and the Year of the Snake bring you stability, inspiration, and success!
Attacking UNIX Systems via CUPS, Part I
CVE-2024-47176, CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177 have been assigned around these CUPS issues.
CVSS 9.9
This remote code execution issue can be exploited across the public Internet via a UDP packet to port 631 without needing any authentication, assuming the CUPS port is open through your router/firewall. LAN attacks are also possible via spoofing zeroconf /…
SGN is a polymorphic binary encoder for offensive security purposes such as generating statically undetecable binary payloads. It uses a additive feedback loop to encode given binary instructions similar to LSFR. This project is the reimplementation of the original Shikata ga nai in golang with many improvements.
https://github.com/EgeBalci/sgn
#redteam #golang
🔥3👍2🤔2
Showing the 12 most recent of 20 posts we hold for @R0_Crew. 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.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Dr.FarFar @Dr_FarFar_Channel · 43,189 Telegram ranks this channel #15 of 17 here — alongside 16 others — read 29 August 2026
vx-underground @vxunderground · 52,910 Telegram ranks this channel #17 of 41 here — alongside 40 others — read 24 August 2026
The Bug Bounty Hunter @thebugbountyhunter · 52,284 Telegram ranks this channel #21 of 60 here — alongside 59 others — read 25 August 2026
Offensive Xwitter @OffensiveTwitter · 21,343 Telegram ranks this channel #26 of 53 here — alongside 52 others — read 25 September 2026
🔗 Join in RedBlueTM 🎩 @RedBlueTM · 21,504 Telegram ranks this channel #35 of 36 here — alongside 35 others — read 23 September 2026
Hide01 @Hide01 · 36,009 Telegram ranks this channel #38 of 41 here — alongside 40 others — read 2 September 2026
The Hacker News @thehackernews · 165,822 Telegram ranks this channel #49 of 58 here — alongside 57 others — read 13 August 2026
S.E.Reborn @S_E_Reborn · 22,441 Telegram ranks this channel #66 of 66 here — alongside 65 others — read 20 September 2026
پاف @pafiha · 34,656 Telegram ranks this channel #71 of 71 here — alongside 70 others — read 13 September 2026
Investigation & Forensic TOOLS @forensictools · 22,620 Telegram ranks this channel #74 of 74 here — alongside 73 others — read 20 September 2026
Codeby @codeby_sec · 37,076 Telegram ranks this channel #75 of 76 here — alongside 75 others — read 1 September 2026
SecAtor @true_secator · 42,222 Telegram ranks this channel #78 of 78 here — alongside 77 others — read 29 August 2026
Информация опасносте @alexmakus · 18,744 Telegram ranks this channel #83 of 85 here — alongside 84 others — read 5 October 2026
Хакер — Xakep.RU @xakep_ru · 40,322 Telegram ranks this channel #83 of 83 here — alongside 82 others — read 30 August 2026
This channel appears in 14 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“r0 Crew (Channel)” (@R0_Crew), 8,990 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/R0_Crew.
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.