Channel
@RNetsec
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
7,744subscribers
+9 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 |
| Created | 16 July 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/RNetsec |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 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 |
44 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 11 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 12 August 2026 |
|---|---|
| Posts held | 44 (31 July 2026 – 12 August 2026) |
| Views total | 17,208 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 17:10 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.
ERPNext's Document Follow feature exposed unauthorized data https://robinroy.xyz/blog/frappe-document-follow-vulnerability/ Submitted August 12, 2026 at 02:53PM by TeraTrox_ via reddit https://ift.tt/hATJG3f
GhostSplice: Malicious MCP Servers Split Instructions to Make AI Coding Agents Exfiltrate Secrets (ASSET Research Group) https://asset-group.github.io/disclosures/ghostsplice/ Submitted August 12, 2026 at 05:44AM by Altruistic_Hope_2559 via reddit https://ift.tt/kvFYnf2
Expired DMARC reporting endpoint exposed a NYSE Fortune 1000's infrastructure for $10 https://ift.tt/orqVKdh Submitted August 12, 2026 at 01:53AM by PlasmaJam via reddit https://ift.tt/1JLC8s7
CopyEscape: Container-to-host arbitrary file write via docker cp (CVE-2026-17106) https://ift.tt/TJsZL5B Submitted August 11, 2026 at 09:03PM by ronmasas via reddit https://ift.tt/W45vYeh
ETW for Security Research: Providers, Sessions, and Detection Engineering https://idov31.github.io/posts/inside-etw-with-etwsuite Submitted August 11, 2026 at 07:52PM by Idov31 via reddit https://ift.tt/hqyV62S
SMAP is Pre-Disarmed: How a Stack Pivot That Shouldn't Work Revealed a Kernel-Wide Design Compromise https://ift.tt/9wJAD7H Submitted August 11, 2026 at 04:16PM by Important_Map6928 via reddit https://ift.tt/Aeb75tP
Mandatory User Profile for Persistence & EDR Evasion https://ipurple.team/2026/08/11/mandatory-user-profile/ Submitted August 11, 2026 at 01:50PM by netbiosX via reddit https://ift.tt/PHek4A0
Inside a Russian-speaking operator's toolkit for compromising Ukrainian IP cameras https://ift.tt/tfeoPMd Submitted August 11, 2026 at 12:11AM by Straight-Practice-99 via reddit https://ift.tt/0rjL39p
Beyond Prompt Injection: Hacking Apple's Private Cloud Compute https://ift.tt/3wZvSnp Submitted August 10, 2026 at 03:03AM by smaury via reddit https://ift.tt/KI3d7vL
HTTP/3 Trailer HEADERS Frame Triggers Unhandled Exception in Google ESF: 60s Hang & QUIC INTERNAL_ERROR 0x0001 | Protocol RE | Netacoding https://ift.tt/iuB1nW0 Submitted August 10, 2026 at 01:18AM by Pale_Surround_3924 via reddit https://ift.tt/hy14mVo
When terrible disclosure from the vendor results in zero days plus a fun dive in to bypassing full disk encryption https://ift.tt/aPD95lo Submitted August 10, 2026 at 12:14AM by kev-thehermit via reddit https://ift.tt/ub4kno8
Finally, something useful from Google regarding search hijacking https://ift.tt/HoXVNc9 Submitted August 9, 2026 at 11:50AM by Huge-Skirt-6990 via reddit https://ift.tt/a1ZRyfe
Showing the 12 most recent of 44 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 — 256,758 of 1,340,412entries 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Netsec” (@RNetsec), 7,744 subscribers as measured 13 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.