Channel
@sysadm_in_channel
On this record: Growth · Engagement · Posts · Citations · Cite this entry
12,935subscribers
+23 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001142915694 |
|---|---|
| Type | Channel |
| Username | @sysadm_in_channel |
| Created | 1 July 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/sysadm_in_channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 08:36 | 12,935 | +6 |
| 14 Aug 2026, 21:24 | 12,929 | +3 |
| 13 Aug 2026, 10:37 | 12,926 | +2 |
| 12 Aug 2026, 09:04 | 12,924 | +7 |
| 11 Aug 2026, 12:16 | 12,917 | +2 |
| 10 Aug 2026, 14:12 | 12,915 | -3 |
| 9 Aug 2026, 17:41 | 12,918 | +3 |
| 8 Aug 2026, 14:55 | 12,915 | -1 |
| 7 Aug 2026, 16:52 | 12,916 | +4 |
| 6 Aug 2026, 14:21 | 12,912 | no change |
| 6 Aug 2026, 04:21 | 12,912 | first reading |
22 posts held, back to 11 May 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 19 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 13 August 2026 |
|---|---|
| Posts held | 22 (11 May 2026 – 13 August 2026) |
| Views total | 10,585 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 12:12 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.
3 BILLION DNS queries. Almost +1 billion in one week. OpenBLD started in 2019 as a homegrown project handling around 35K DNS queries a day. Today: → ~15M queries/hour → 4K+ queries/second → servers distributed around the world → billions of DNS queries processed And it still runs mostly on regular VPS infrastructure - with plenty of performance headroom left. Getting here required years of optimizing the entire…
Claude in Chrome: From alert(1) to Full Account Takeover https://labs.zenity.io/post/claude-in-chrome-from-alert-to-full-account-takeover
7-Zip Leaves Extracted Malware Without Mark-of-the-Web, Bypassing Windows SmartScreen evil 7-zip) https://cyberpress.org/7-zip-bypasses-smartscreen-protections/
Threat Actors Abuse Trusted Software Lures and Cloudflare Tunnels to Deploy ScreenConnect RMM Agents Across Windows and macOSScreenConnect RMM Agents Across Windows and macOS Analyzing SMOKE#SCREEN: https://www.securonix.com/blog/smoke-screen-screenconnect-rmm-abuse-cloudflare-tunnels/
Welcome to Danglegeddon Silent Push Simulation Demonstrates Why Dangling Dns Domains Continue To Pose Global Threats..: https://www.silentpush.com/blog/danglegeddon/
ClickLock Stealer: Paste Once, Lose Everything Upon execution of the ClickFix command, the malicious script shows a terminal-based loading animation mimicking Cloudflare progress bar with browser verification flow..: https://www.group-ib.com/blog/clicklock-stealer-macos-malware/
Coordinated AsyncAPI Supply Chain Attack: Miasma RAT Delivered via Compromised CI/CD Pipelines in Two Repositories https://www.stepsecurity.io/blog/compromised-next-branch-pushes-malicious-asyncapi-generator-generator-helpers-and-generator-components-to-npm
Cursor 0day: When Full Disclosure Becomes the Only Protection Left https://mindgard.ai/blog/cursor-0day-when-full-disclosure-becomes-the-only-protection-left
Inside Forg365: A Telegram-Distributed Sneaky 2FA-Style PhaaS Targeting https://zerobec.com/blog/inside-forg365-telegram-distributed-sneaky2fa-style-phaas
Vishing actors target Entra passkey enrollment (mimics the Microsoft passkey enrollment) The threat actor registers domains that incorporate the word passkey as part of a voice-enabled phishing (“vishing”) scheme. The threat actor then calls targeted users on the phone in an attempt to persuade them that they need to register a new passkey.: https://www.okta.com/en-au/blog/threat-intelligence/vishing-actors-target-…
DuneSlide: Two Critical RCE vulnerabilities via Zero-Click Prompt Injection in Cursor IDE https://www.catonetworks.com/blog/duneslide-two-critical-rce-vulnerabilities/
FortiBleed - Breach How 80,000+ Corporate= Firewalls Were Quietly Compromised If your organization uses a Fortinet firewall or VPN product and appears in this dataset, treat your network perimeter as already compromised and act immediately. SOCRadar rates this campaign Critical..: https://socradar.io/blog/fortibleed-fortinet-firewalls-compromised/
Showing the 12 most recent of 22 posts we hold for @sysadm_in_channel. 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 — 291,247 of 1,481,346entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Sys-Admin InfoSec” (@sysadm_in_channel), 12,935 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/sysadm_in_channel.
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.