Telegram RegisterThe public register of Telegram
Telegram profile photo for Kali Linux en Español

Supergroup

Kali Linux en Español

@kalilinux_es

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

3,454members

+5 since we began measuring on 6 August 2026

79 online right now

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

Register entry

Telegram ID-1001183939535
TypeSupergroup
Username@kalilinux_es
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live7 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/kalilinux_es

Topic

Technology — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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

3,4353,4603,447.56 August 2026 — 3,449 members10 August 2026 — 3,445 members14 August 2026 — 3,450 members17 August 2026 — 3,445 members20 August 2026 — 3,438 members24 August 2026 — 3,442 members27 August 2026 — 3,436 members29 August 2026 — 3,439 members1 September 2026 — 3,437 members5 September 2026 — 3,440 members8 September 2026 — 3,440 members11 September 2026 — 3,438 members14 September 2026 — 3,437 members19 September 2026 — 3,442 members28 September 2026 — 3,435 members5 October 2026 — 3,436 members12 October 2026 — 3,447 members15 October 2026 — 3,459 members18 October 2026 — 3,456 members21 October 2026 — 3,460 members26 October 2026 — 3,458 members30 October 2026 — 3,451 members2 November 2026 — 3,450 members4 November 2026 — 3,452 members7 November 2026 — 3,454 members3,4546 August 20267 November 2026
25 measurements spanning 93 days, net +5. 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 3,431–3,464 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
7 Nov 2026, 04:013,454+2
4 Nov 2026, 14:243,452+2
2 Nov 2026, 00:363,450-1
30 Oct 2026, 00:073,451-7
26 Oct 2026, 14:163,458-2
21 Oct 2026, 02:403,460+4
18 Oct 2026, 10:093,456-3
15 Oct 2026, 20:073,459+12
12 Oct 2026, 14:093,447+11
5 Oct 2026, 17:203,436+1
28 Sept 2026, 14:383,435-7
19 Sept 2026, 05:363,442+5
14 Sept 2026, 15:203,437-1
11 Sept 2026, 00:563,438-2
8 Sept 2026, 20:093,440no change
5 Sept 2026, 19:383,440+3
1 Sept 2026, 17:363,437-2
29 Aug 2026, 21:533,439+3
27 Aug 2026, 05:473,436-6
24 Aug 2026, 03:283,442first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“Kali Linux en Español” (@kalilinux_es), 3,454 members as measured 7 November 2026. Telegram Register, tgregister.com/channel/kalilinux_es.

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.