Telegram RegisterThe public register of Telegram
Telegram profile photo for Kali Linux

Channel

Kali Linux

@kalilinux

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

18,066subscribers

+31 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001016019829
TypeChannel
Username@kalilinux
CreatedBetween 1 December 2015 and 31 March 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/kalilinux

Growth

18,03518,06718,0515 August 2026 — 18,035 subscribers6 August 2026 — 18,035 subscribers7 August 2026 — 18,044 subscribers8 August 2026 — 18,039 subscribers8 August 2026 — 18,040 subscribers9 August 2026 — 18,049 subscribers10 August 2026 — 18,047 subscribers11 August 2026 — 18,046 subscribers12 August 2026 — 18,053 subscribers14 August 2026 — 18,067 subscribers15 August 2026 — 18,066 subscribers18,0665 August 202615 August 2026
11 measurements spanning 10 days, net +31. 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 18,030–18,072 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 18:5618,066-1
14 Aug 2026, 04:3918,067+14
12 Aug 2026, 23:1218,053+7
11 Aug 2026, 20:1218,046-1
10 Aug 2026, 21:2118,047-2
9 Aug 2026, 20:5218,049+9
8 Aug 2026, 23:3018,040+1
8 Aug 2026, 02:2518,039-5
7 Aug 2026, 00:2518,044+9
6 Aug 2026, 02:1718,035no change
5 Aug 2026, 22:0418,035first reading

Engagement

20 posts held, back to 3 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.9%
avg views ÷ 18,066 subscribers
Avg views / post
3,240
4 posts measured
Reaction rate
0.478%
reactions ÷ views · ER floor
Posts in window
4
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held20 (3 May 20261 August 2026)
Views total12,960
Reactions total62
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 10:05 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.

What this channel posts

Video runtime
11s
Average length
6s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

250 reactions across 19 posts, in 16 distinct kinds. The most used accounts for 29.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7429.6%
👍5321.2%
🤣3614.4%
🤬145.60%
😱114.40%
🔥104.00%
👾93.60%
🤯93.60%
💩83.20%
😁62.40%
❤‍🔥52.00%
🕊52.00%
👨‍💻31.20%
😨31.20%
👀20.8%
👎20.8%

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 19 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 250reactions 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 3 May 2026 to 1 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

1 Aug 2026, 22:23 UTC≈2,290 views31 reactionsread 15 August 2026

Go and donate to dnsmasq to tor to openwrt to wikipedia to vlc.. Some of them you might've already heard of, and some of them you might not even know. But these are the very infrastructure of our world. Have you ever used Wikipedia? probably yes. Have you ever donated them? probably not. If you ever used Youtube, if you ever watched a video on whatever the device you have, you've certainly been involved with ffmpeg

21👍7👎2👾1

28 Jul 2026, 12:30 UTC≈3,060 views8 reactionsread 15 August 2026
Video

No, AI isn’t making you “forget” how to code source @Kalilinux

🤣7👍1

21 Jul 2026, 14:40 UTC≈4,100 views10 reactionsread 15 August 2026

The Insider, together with Der Spiegel, and Le Monde, has obtained a cache of documents containing previously undisclosed details about the growing military cooperation between Russia and China. Secret documents from a series of clandestine Russian-Chinese military forums reveal a joint plan to defeat Elon Musk’s Starlink and a weapons development partnership far deeper than either country will admit. From air- and

7😨3

19 Jul 2026, 21:17 UTC≈3,510 views13 reactionsread 15 August 2026
Forwarded from @thehackernewsPhoto

🛑 WARNING - A new critical NGINX vulnerability that has existed for 15-years lets unauthenticated attackers crash worker processes with crafted HTTP requests. CVE-2026-42533 affects specific regex map configurations. F5 says it may also allow pre-auth RCE if ASLR is disabled or bypassed. Read how the bug works: https://thehackernews.com/2026/07/critical-nginx-vulnerability-can-crash.html

13

17 Jul 2026, 02:27 UTC≈4,010 views15 reactionsread 15 August 2026
Photo

Linus Torvalds told Linux kernel developers this week that Linux is not one of those anti-AI projects and that AI is now a clearly useful tool. He says AI's usefulness was still arguable a year ago but no longer is, and that the doubters simply haven't used the tools. Nobody is forced to use AI, but he will ignore anyone trying to stop others from using it. Anyone who wants an anti-AI project, he says, can fork the

👍8❤‍🔥51💩1

11 Jul 2026, 10:16 UTC≈4,120 views6 reactionsread 15 August 2026

Weeks after the exploit code dropped, Redmond has finally shipped a fix for the Defender zero-day Microsoft has quietly fixed the “RoguePlanet” zero-day in Microsoft Defender, closing the latest hole exposed by security researcher Nightmare Eclipse after months of public sparring over the company's handling of vulnerability reports. According to Nightmare Eclipse, RoguePlanet affects fully patched Windows 10 and Wi

4👾2

9 Jul 2026, 09:14 UTC≈3,990 views17 reactionsread 15 August 2026

AI Hacking and the Critical Shift in Privacy: They now have sophisticated AIs that find bugs in very hardened code bases like the Linux kernel and our other vital infrastructures that are the backbone of our society. They find the bugs in an hour now, they'll soon find them in a minute. And if they couldn't find the 0-day bug, they'll elevate on already known bugs to chain them in a way that was never thought of. Th

👍134

29 Jun 2026, 03:42 UTC≈5,690 views17 reactionsread 15 August 2026

A new Linux kernel exploit (CVE-2026-46331) gets root without modifying a single file on disk. It poisons the cached copy of /bin/su in memory. The binary on disk stays untouched. File-integrity checks come back clean. The root shell is already open! thehackernews.com/2026/06/new-linux-pedit-cow-exploit-enables.html @kalilinux

🔥9🤬5👍2👀1

19 Jun 2026, 00:02 UTC≈6,430 views6 reactionsread 15 August 2026

F5 has released security updates to address not just one, but two critical security flaws in #NGINX Open Source that could be exploited to achieve code execution on affected systems. https://thehackernews.com/2026/06/f5-patches-two-critical-nginx-open.html @kalilinux

6

18 Jun 2026, 23:57 UTC≈6,020 views8 reactionsread 15 August 2026
Video

Here goes nginx-quicburst (CVE-2026-42530), a new RCE in Nginx discovered by Nebula Security's security agent VEGA and demonstrated by them. This is only the third NGINX vulnerability since 2014 to receive NGINX’s “major” severity rating. If you use Nginx 1.31 with QUIC enabled, they recommend upgrading to the latest version. This bug has been patched in the latest Nginx release. They will publish the technical wri

5👍3

17 Jun 2026, 12:05 UTC≈5,320 views37 reactionsread 15 August 2026
Video

AI just took my fucking job source @kalilinux

🤣29😁61😱1

17 Jun 2026, 09:51 UTC≈4,830 views4 reactionsread 15 August 2026

https://socket.dev/blog/152-chrome-live-wallpaper-extensions-hid-ad-tracking @Kalilinux

👍4

Showing the 12 most recent of 20 posts we hold for @kalilinux. 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

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.

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Kali Linux” (@kalilinux), 18,066 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/kalilinux.

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.