Telegram RegisterThe public register of Telegram
Telegram profile photo for LinuxSec

Channel

LinuxSec

@linuxsec

On this record: Topic · Growth · Engagement · Posts · Cite this entry

847subscribers

-23 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001029926795
TypeChannel
Username@linuxsec
CreatedBetween 1 January 2016 and 30 April 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live3 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/linuxsec

Topic

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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

847870858.56 August 2026 — 870 subscribers7 August 2026 — 870 subscribers14 August 2026 — 866 subscribers21 August 2026 — 863 subscribers28 August 2026 — 859 subscribers4 September 2026 — 858 subscribers12 September 2026 — 856 subscribers25 September 2026 — 852 subscribers7 October 2026 — 849 subscribers20 October 2026 — 850 subscribers27 October 2026 — 848 subscribers3 November 2026 — 847 subscribers6 August 20263 November 2026
12 measurements spanning 89 days, net -23. 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 844–873 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 22:57847-1
27 Oct 2026, 12:08848-2
20 Oct 2026, 22:06850+1
7 Oct 2026, 00:20849-3
25 Sept 2026, 16:22852-4
12 Sept 2026, 07:01856-2
4 Sept 2026, 06:38858-1
28 Aug 2026, 20:33859-4
21 Aug 2026, 03:29863-3
14 Aug 2026, 01:28866-4
7 Aug 2026, 08:57870no change
6 Aug 2026, 23:03870first reading

Engagement

20 posts held, back to 19 December 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 24 March 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Feb 2024, 00:20 UTC705 viewsread 6 August 2026

https://www.linuxsec.org/2024/02/atomic-red-team.html Adversary Emulation Menggunakan Atomic Red Team

1 Feb 2024, 23:09 UTC608 viewsread 6 August 2026

https://www.darkreading.com/perimeter/microsoft-teams-exploit-toll-autodeliver-malware

28 Jan 2024, 19:51 UTC525 viewsread 6 August 2026

https://assume-breach.medium.com/im-not-a-pentester-and-you-might-not-want-to-be-one-either-8b5701808dfc

1 Jan 2024, 04:47 UTC623 viewsread 6 August 2026

Bypass SSL Pinning Android dengan Frida https://www.linuxsec.org/2023/12/bypass-ssl-pinning-android-dengan-frida.html

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

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

“LinuxSec” (@linuxsec), 847 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/linuxsec.

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.