Telegram RegisterThe public register of Telegram

Channel

CCN-CERT

@CCNCERT

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cross-platform identity · Cite this entry

6,707subscribers

+12 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001385811594
TypeChannel
Username@CCNCERT
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/CCNCERT

Growth

6,6956,7076,7016 August 2026 — 6,695 subscribers6 August 2026 — 6,696 subscribers9 August 2026 — 6,702 subscribers12 August 2026 — 6,707 subscribers6 August 202612 August 2026
4 measurements spanning 7 days, net +12. 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 6,693–6,709 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 18:036,707+5
9 Aug 2026, 16:226,702+6
6 Aug 2026, 08:206,696+1
6 Aug 2026, 03:376,695first reading

Engagement

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

ERR · 30 days
33.8%
avg views ÷ 6,707 subscribers
Avg views / post
2,270
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
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 5 August 2026
Posts held20 (23 June 20265 August 2026)
Views total24,940
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:52 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.

Recent posts

5 Aug 2026, 08:57 UTC≈1,190 viewsread 12 August 2026

📒El Centro Criptológico Nacional incorpora 3 nuevos productos al catálogo #CPSTIC dentro de las categorías de protección de redes y sistemas, protección de perímetro y soporte criptográfico. Mas info👉https://t.co/tRvX0U1fJU https://t.co/auOkvCQwdY — Centro Criptológico Nacional (@CCNCERT) Aug 5, 2026

31 Jul 2026, 07:52 UTC≈2,180 viewsread 12 August 2026

🤝 La Red Nacional de SOC #RNS tiene 7 entidades nuevas: 🏛️ Públicas: Aytos de Buenavista del Norte, Fasnia, San Juan de la Rambla, La Matanza de Acentejo y La Victoria de Acentejo 🏢 Proveedoras: #MultisoftwareDefense y @merabytes Más info 👉https://t.co/23sWdEfHUO https://t.co/1dU4D3BdSL — Centro Criptológico Nacional (@CCNCERT) Jul 31, 2026

30 Jul 2026, 11:17 UTC≈2,110 viewsread 12 August 2026

🚨 @Broadcom publica actualizaciones para 5 vulnerabilidades, 3 de ellas críticas, de productos #VMware 🆙¡Actualiza! Más información 👉https://t.co/xi5G1rChwC https://t.co/MpZ6P5EJHU — Centro Criptológico Nacional (@CCNCERT) Jul 30, 2026

28 Jul 2026, 11:12 UTC≈2,100 viewsread 12 August 2026

🗓️El 4 de septiembre concluye el plazo para presentar propuesta de ponencia y/o taller a las Jornadas #STIC2026 Toda la información 👇 https://t.co/fJZU8M7h65 https://t.co/Ro1e3BiF0t — Centro Criptológico Nacional (@CCNCERT) Jul 28, 2026

27 Jul 2026, 09:22 UTC≈2,320 viewsread 12 August 2026

🆙El CCN actualiza 45 de las 73 familias del #CPSTIC En total 660 productos y servicios: 152 aprobados (información clasificada), 482 cualificados (sistemas bajo el alcance del ENS) y 26 vinculados a conformidad y gobernanza. Más info 👉 https://t.co/ErDgMtMjO9 https://t.co/IXWUZ1DF3h — Centro Criptológico Nacional (@CCNCERT) Jul 27, 2026

23 Jul 2026, 08:57 UTC≈2,810 viewsread 12 August 2026

🙏 El CCN insta a las entidades públicas a completar antes del 15 de septiembre el formulario de autoevaluación sobre #IAofensiva incorporado en INÉS. Es imprescindible conocer el grado de exposición, preparación y respuesta a la IA ofensiva. Más info 👉 https://t.co/djiK6vsPww https://t.co/lCuyvhRwEe — Centro Criptológico Nacional (@CCNCERT) Jul 23, 2026

22 Jul 2026, 12:27 UTC≈2,440 viewsread 12 August 2026

🚨 El CCN-CERT informa de una vulnerabilidad crítica en Microsoft SharePoint Server, identificada como #CVE2026_58644 🆙¡Actualiza! Más info 👉https://t.co/NEjToeIPZU https://t.co/dNh0aOcFex — Centro Criptológico Nacional (@CCNCERT) Jul 22, 2026

22 Jul 2026, 09:47 UTC≈2,230 viewsread 12 August 2026

🚨 El CCN advierte de la amenaza cuántica para la seguridad de la información y llama a prepararse frente a ella. 📄CCN-TEC 009/ BP 37 Recomendaciones para una transición postcuántica segura. #AmenazaCuántica #PQC #QuantumSafe Más info👉https://t.co/YGgGZjIOJh https://t.co/sa8PObcNt1 — Centro Criptológico Nacional (@CCNCERT) Jul 22, 2026

17 Jul 2026, 12:27 UTC≈2,710 viewsread 12 August 2026

🚨 Explotación activa de vulnerabilidades críticas en SonicWall SMA1000, con prueba de concepto pública #PoC El CCN-CERT recomienda aplicar los parches publicados, revisar indicadores de compromiso y extremar medidas de vigilancia. Más info 👉 https://t.co/hPoIK3afhq https://t.co/OH2pCWePKn — Centro Criptológico Nacional (@CCNCERT) Jul 17, 2026

17 Jul 2026, 10:27 UTC≈2,370 viewsread 12 August 2026

🚨Vulnerabilidad de ejecución remota de código en @Microsoft Exchange Server. El CCN-CERT, del Centro Criptológico Nacional, informa de una vulnerabilidad en Microsoft Exchange Server, identificada como #CVE_2026_55005 ¡Actualiza! Más info 👉 https://t.co/X1aFsZllK0 https://t.co/Z2ZBcz1et4 — Centro Criptológico Nacional (@CCNCERT) Jul 17, 2026

14 Jul 2026, 14:07 UTC≈2,480 viewsread 12 August 2026

🚀 Las Jornadas STIC alcanzan su vigésima edición con la mayor convocatoria de su historia. 📣 Abierto el Call for Papers 🗓️ Propuestas hasta el 4 septiembre 📍 Madrid | 24-27 noviembre 2026 #Ciberseguridad #CallForPapers #IA #ComputaciónCuántica Más info👉https://t.co/S7ZeXnPtUO https://t.co/wBdd0mxcMC — Centro Criptológico Nacional (@CCNCERT) Jul 14, 2026

13 Jul 2026, 14:12 UTC≈2,740 viewsread 12 August 2026

🚨 El #CCN incorpora en INES un formulario de autoevaluación para valorar el nivel de preparación de un organismo frente a las amenazas de la #IAofensiva. Más información 👉 https://t.co/XXPEcvuHJz https://t.co/7kU7Eg1wIK — Centro Criptológico Nacional (@CCNCERT) Jul 13, 2026

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

Citation-graph rank — 278,733 of 1,169,250entries 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.

Forward network

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.

Mentions

Named by 2 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Appears in Telegram’s recommendations for other channels

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.

The Hacker News
@thehackernews · 162,047
Telegram ranks this channel #44 of 58 here — alongside 57 others — read 13 August 2026

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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q59771478 on Wikidata, read 9 August 2026
LabelNo label recorded on this Wikidata item
X / Twitter@CcnCert
Official sitehttps://www.ccn-cert.cni.es

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

“CCN-CERT” (@CCNCERT), 6,707 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/CCNCERT.

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.