🔴 ESTAMOS EN DIRECTO!! Estamos en twitch / YouTube para practicar un poco de hacking en entornos Windows!! https://open-in-app.com/o/?u=https%3A%2F%2Fwww.twitch.tv%2Felpinguinodemario
❤9

Channel
@elpinguinohack
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
10,156subscribers
+121 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001748818432 |
|---|---|
| Type | Channel |
| Username | @elpinguinohack |
| Description | Canal de Telegram destinado al pentesting y ciberseguridad. Tenemos grupo de chat donde podemos hablar y consultar dudas entre todos nosotros de una forma muy cómoda!! 👇🏻 CHAT EN TELEGRAM: https://t.me/+4nGEevu6Hus4YWNk |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 58 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/elpinguinohack |
Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 08:21 | 10,156 | -4 |
| 7 Nov 2026, 06:32 | 10,160 | -3 |
| 6 Nov 2026, 06:39 | 10,163 | -4 |
| 5 Nov 2026, 08:49 | 10,167 | +3 |
| 4 Nov 2026, 05:00 | 10,164 | -1 |
| 3 Nov 2026, 03:11 | 10,165 | +1 |
| 1 Nov 2026, 23:59 | 10,164 | +2 |
| 31 Oct 2026, 21:31 | 10,162 | +3 |
| 30 Oct 2026, 20:01 | 10,159 | +1 |
| 29 Oct 2026, 21:38 | 10,158 | -1 |
| 28 Oct 2026, 21:37 | 10,159 | +3 |
| 27 Oct 2026, 21:48 | 10,156 | +10 |
| 26 Oct 2026, 18:49 | 10,146 | +3 |
| 24 Oct 2026, 15:46 | 10,143 | +5 |
| 23 Oct 2026, 16:45 | 10,138 | +8 |
| 22 Oct 2026, 16:05 | 10,130 | +8 |
| 21 Oct 2026, 13:08 | 10,122 | +22 |
| 20 Oct 2026, 10:09 | 10,100 | +10 |
| 19 Oct 2026, 07:18 | 10,090 | +11 |
| 18 Oct 2026, 05:36 | 10,079 | first reading |
38 posts held, back to 29 March 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 48 pages of 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 7 November 2026 |
|---|---|
| Posts held | 38 (29 March 2026 – 7 November 2026) |
| Views total | 17,242 |
| Reactions total | 109 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 10:04 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.
Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
821 reactions across 38 posts, in 14 distinct kinds. The most used accounts for 44.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 368 | 44.8% | |
| 👍 | 250 | 30.5% | |
| 🔥 | 114 | 13.9% | |
| 👏 | 57 | 6.94% | |
| 🎉 | 12 | 1.46% | |
| 🙏 | 4 | 0.487% | |
| ⚡ | 3 | 0.365% | |
| 💯 | 3 | 0.365% | |
| 😁 | 3 | 0.365% | |
| 😱 | 2 | 0.244% | |
| 🤝 | 2 | 0.244% | |
| 🍾 | 1 | 0.122% | |
| 👌 | 1 | 0.122% | |
| 👎 | 1 | 0.122% |
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 38 of the 38 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 821 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 29 March 2026 to 7 November 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.
Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🔴 ESTAMOS EN DIRECTO!! Estamos en twitch / YouTube para practicar un poco de hacking en entornos Windows!! https://open-in-app.com/o/?u=https%3A%2F%2Fwww.twitch.tv%2Felpinguinodemario
❤9
🔥 ESTAMOS EN DIRECTO!! Después de un tiempo volvemos a los directos para practicar un poco de hacking web todos juntos!! Estamos en YouTube y twitch !! https://www.twitch.tv/elpinguinodemario
❤7
🔴 NUEVO VIDEO!! Hoy vamos a aprender a analizar las cabeceras de un email para detectar si es inofensivo o no, para así protegernos de ataques de phishing!! Así Funciona un PHISHING por dentro (y cómo Detectarlo en Segundos) https://youtu.be/kyLkmPsEAbU
👍8❤4🔥2😁2
🔴 YA TENEMOS EL CURSO DE HACKING ÉTICO COMPLETO!! Os dejo por aquí el curso intensivo de hacking ético que impartí junto a Chema Alonso y Gorka en colaboración con Big School, espero que os guste!! 👇🏻 👉 Curso Intensivo de HACKING ÉTICO de 0 a Hackear Aplicaciones 🥷 https://youtu.be/oBYDnLdslJs
👍19❤7🙏4👏3🤝2
Muy buenas chicos!! Hoy estaré en directo a las 19 hora española en youtube haciendo la clase del día 2 del curso de hacking ético, donde vamos a centrarnos en el hacking móvil!! Aquí tenéis el enlace del directo!! https://www.youtube.com/live/WjDVFJobYTY
❤15👎1
🔴 NUEVO VIDEO!! Esta vez tenemos un video nuevo el colaboración con nuestro compañero Gorka y Big School donde vemos las principales vulnerabilidades de un WordPress y cómo parchearlas!! 👇🏻 Hackear tu WEB con IA es MÁS FÁCIL de lo que crees 😳 https://youtu.be/o6uysWUO9Pg
🔥11❤1👍1
🔴 NUEVO VÍDEO!! Seguimos con el curso de bug bounty! Y es momento de aprender cómo analizar una APK para encontrar vulnerabilidades, un vector que poca gente suele analizar y mejores resultados nos da 👇🏻 💻 Curso de Bug Bounty - Aprende a Encontrar Vulnerabilidades en Aplicaciones Android | #7 https://youtu.be/p2t6Nu42t8E
👍11🔥2
🔴 NUEVO VIDEO!! Hoy os traigo un vídeo o curso express de cómo usar wireshark para analizar el tráfico de red, de forma totalmente práctica y muy fácil!! Aprende WIRESHARK en 15 minutos https://youtu.be/tbu4XoYcfrk
👏9❤8👍6🔥6
🔴 ¡NOVEDADES EN LA NEWSLETTER! Muchos ya sabéis que tenemos una newsletter en la que os envío un correo diario sobre ciberseguridad, herramientas, tips y mucho más. Por eso, he mejorado los recursos que recibiréis al suscribiros. Ahora incluye: 👉 Una guía para empezar desde cero 👉 Un roadmap para orientar vuestro aprendizaje 👉 Un curso gratuito de hacking ético que llega directamente a vuestra bandeja de entrad…
❤3👏2
🔥 NUEVO VÍDEO!! Seguimos con el curso de bug bounty! Está vez veremos una de las principales vulnerabilidades client side, el XSS 💻 Curso de Bug Bounty - La Vulnerabilidad que Permite Ejecutar Código en Webs Ajenas | #5 https://youtu.be/ZcIUPVkZX48
🔥8👍6🎉3
🔥 NUEVO VIDEO!! Hoy os traigo una demostración de account takeover 100% práctica, una vulnerabilidad muy crítica en aquellas webs que la tienen 👇🏻 ASÍ LOS HACKERS COMPROMETEN LA SEGURIDAD DE TU WEB https://youtu.be/6YoGigNzTT8
❤9👍8🎉2
🔥 NUEVA CLASE DEL CURSO DE BUG BOUNTY!! Seguimos con la vulnerabilidad IDOR utilizando un ejercicio donde reunimos varios reportes de bug bounty, espero que os guste !! 💻 Curso de Bug Bounty - Cambio un Número en la URL y Accedo a Otra Cuenta | #5 https://youtu.be/ybWWT2L6hIY
👍11❤9🔥4
Showing the 12 most recent of 38 posts we hold for @elpinguinohack. 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.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“El Pingüino de Mario” (@elpinguinohack), 10,156 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/elpinguinohack.
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.