Channel
@emcomEA
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
844subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001128840392 |
|---|---|
| Type | Channel |
| Username | @emcomEA |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/emcomEA |
Other / unclassifiable — 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 58% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 05:21 | 844 | -1 |
| 13 Sept 2026, 07:36 | 845 | -1 |
| 6 Sept 2026, 07:15 | 846 | -1 |
| 29 Aug 2026, 04:25 | 847 | +5 |
| 22 Aug 2026, 22:06 | 842 | +2 |
| 14 Aug 2026, 21:58 | 840 | +1 |
| 8 Aug 2026, 01:20 | 839 | no change |
| 7 Aug 2026, 21:02 | 839 | first reading |
20 posts held, back to 26 September 2025 — 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 27 June 2026. An engagement rate over an empty window would be a number about nothing.
Os trasladamos el mensaje de apoyo enviado al Radio Club Venezolano por parte de RE: Estimados compañeros de la Red Nacional de Emergencias del Radio Club Venezolano: Desde la Unión de Radioaficionados Españoles, a través de su Vocalía de Emergencias, queremos trasladarles nuestro apoyo y solidaridad ante el terremoto ocurrido en Venezuela. Asimismo, nos ponemos a su disposición para colaborar, dentro de nuestras p…
📢 Aviso a la comunidad de radioaficionados EA Tras el fuerte terremoto registrado en Venezuela (magnitud 7,0), la Red Nacional de Emergencia del Radio Club Venezolano ha activado sus comunicaciones de emergencia debido a cortes eléctricos y problemas en las telecomunicaciones. Se solicita la colaboración de los radioaficionados para mantener libre de uso la frecuencia 7135 kHz (40 metros), utilizada para la coordin…
Photo, posted without a caption
File, posted without a caption
🔋📡 ¿Te perdiste la charla de EA3ANC, Peter, sobre la autosuficiencia energética aplicada a la radioafición? Ya está disponible en el canal de YouTube de EMCOM ESPAÑA el vídeo completo de esta interesante charla, donde se presentan soluciones prácticas para mantener nuestras estaciones operativas en situaciones de emergencia, actividades en portable y entornos sin acceso a la red eléctrica. Durante la presentación s…
📢 Compañeros de la radio y la CB: Necesitamos vuestro apoyo para evitar el traslado del Museo CB de San Roque, un referente internacional para radioaficionados y cebeístas y parte de la historia de nuestras comunicaciones. Solo te pedimos un minuto para firmar y compartir. ✍️ Firma aquí: https://c.org/pQgPprBJxS Ayúdanos a proteger este patrimonio de todos. ¡73!
🔋📡 ¿Te interesa la autosuficiencia energética aplicada a la radioafición? La Vocalía de Emergencias de URE (EMCOM España) organiza la formación "Autosuficiencia Energética para Radioaficionados", una oportunidad para adquirir conocimientos prácticos sobre sistemas de alimentación autónoma, gestión energética y preparación de estaciones de radio para situaciones de emergencia. ⚡️ Aprende a mejorar la autonomía de tu…
File, posted without a caption
Photo, posted without a caption
⚠️Cerramos las inscripciones para la formación de "Winlink - Vara"⚠️
https://www.ure.es/ure-y-proteccion-civil-abordan-la-colaboracion-en-comunicaciones-de-emergencia/
https://www.rtve.es/play/audios/memoria-de-delfin/memoria-delfin-radioaficionados-32000-espana-casi-4-millones-todo-mundo/17003361/
Showing the 12 most recent of 20 posts we hold for @emcomEA. 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.
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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“EMCOM Noticias” (@emcomEA), 844 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/emcomEA.
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.