Channel
@RNetsec
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
7,756subscribers
+21 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001107873651 |
|---|---|
| Type | Channel |
| Username | @RNetsec |
| Description | This channel posts the feed from r/netsec. For any suggestions dm @streaak Donate to keep the bot running https://www.paypal.me/akhilgv |
| Created | 16 July 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/RNetsec |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 17:21 | 7,756 | +7 |
| 16 Aug 2026, 15:05 | 7,749 | +5 |
| 13 Aug 2026, 06:04 | 7,744 | +2 |
| 9 Aug 2026, 20:31 | 7,742 | +3 |
| 6 Aug 2026, 23:13 | 7,739 | +4 |
| 6 Aug 2026, 03:05 | 7,735 | no change |
| 6 Aug 2026, 01:55 | 7,735 | first reading |
80 posts held, back to 31 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 15 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 20 August 2026 |
|---|---|
| Posts held | 80 (31 July 2026 – 20 August 2026) |
| Views total | 30,313 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 20:43 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.
Lifetime counters from Telegram’s own channel header, read 22 August 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.
GLM-5.3's emergent security capabilities: 1,097 critical/high severity bugs discovered across kernels, browsers, and infrastructure, oldest flaw from 1981 https://ift.tt/63cwNvB Submitted 2026-08-20T12:48:26Z by Sinver_Nightingale27 via reddit https://ift.tt/DI4chNz
Graphing AWS Attack Paths in Bloodhound https://ift.tt/xPshKkw Submitted 2026-08-19T20:26:22Z by n0pe_sled via reddit https://ift.tt/yMnjul1
Hacking SAML with Claude Code https://ift.tt/xbauAhj Submitted 2026-08-19T18:40:47Z by ericchiang via reddit https://ift.tt/h3pLY9b
Iran's Mabna Institute ran a 3-phase spearphishing campaign against university professors for a decade. The 50-page superseding indictment has more methodological detail than the press coverage suggests. https://ift.tt/GaNSEQl Submitted 2026-08-19T16:34:25Z by Robert-Nogacki via reddit https://ift.tt/nL9bR7p
I escaped the WebAssembly's sandbox and got arbitrary shell execution on the host. https://ift.tt/UChpW3K Submitted 2026-08-19T15:54:04Z by trustsigRobert via reddit https://ift.tt/v7xb8Eh
ValleyRAT campaign uses fake GSTR-3B overdue notice targeting Indian taxpayers https://ift.tt/nGIDjOB Submitted 2026-08-19T13:18:26Z by unknownhad via reddit https://ift.tt/MYJLkPK
CRLF-Powered Desync Attacks: Beheading HTTP Streams https://ift.tt/PeLy6BI Submitted 2026-08-19T12:58:25Z by t0xodile via reddit https://ift.tt/fsgyJkn
How to break secure boot without touching any cryptography https://ift.tt/KOpdh8m Submitted 2026-08-19T12:01:19Z by 0x00rick via reddit https://ift.tt/WyQkioq
The Curious Incidents with DNS in the Sandbox at Escape-Time https://ift.tt/BM5tkEP Submitted 2026-08-19T03:58:53Z by lowlevelprog via reddit https://ift.tt/1odOKbL
When Burp Suite Isn't Enough: Intercepting Thick Client Traffic https://ift.tt/SPIyJq2 Submitted 2026-08-19T03:45:57Z by Ano_F via reddit https://ift.tt/QdDapuG
Kimi Desktop Ships With an Updater That Can Install Unverified Code https://ift.tt/2oJWuCq Submitted 2026-08-18T23:27:51Z by ryanmerket via reddit https://ift.tt/ikcsqCH
How a popular Android library silently exposed thousands of apps to Arbitrary File Overwrite (AFO). https://itis911.github.io/writeups/cropper-vulnerability.html https://itis911.github.io/writeups/cropper-vulnerability.html Submitted 2026-08-18T16:24:33Z by Fit_Veterinarian4403 via reddit https://ift.tt/cHeKYrL
Showing the 12 most recent of 80 posts we hold for @RNetsec. 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.
Citation-graph rank — 270,009 of 1,584,420entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 1 registered channel — 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“Netsec” (@RNetsec), 7,756 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/RNetsec.
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.