Channel
@MexicanMilitaryArchives
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,729subscribers
+277 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003724865301 |
|---|---|
| Type | Channel |
| Username | @MexicanMilitaryArchives |
| Created | Between 1 February 2026 and 2 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/MexicanMilitaryArchives |
National news — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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 |
|---|---|---|
| 16 Sept 2026, 02:59 | 1,729 | +70 |
| 12 Sept 2026, 05:59 | 1,659 | +48 |
| 8 Sept 2026, 09:58 | 1,611 | +118 |
| 2 Sept 2026, 20:28 | 1,493 | +15 |
| 30 Aug 2026, 21:45 | 1,478 | +2 |
| 27 Aug 2026, 20:14 | 1,476 | -1 |
| 25 Aug 2026, 05:53 | 1,477 | +3 |
| 22 Aug 2026, 13:57 | 1,474 | +3 |
| 18 Aug 2026, 19:22 | 1,471 | +4 |
| 15 Aug 2026, 09:24 | 1,467 | +12 |
| 12 Aug 2026, 03:32 | 1,455 | +3 |
| 11 Aug 2026, 20:45 | 1,452 | first reading |
12 posts held, back to 2 June 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 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 12 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
392 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 64.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 254 | 64.8% | |
| ❤ | 78 | 19.9% | |
| 👍 | 48 | 12.2% | |
| 🫡 | 7 | 1.79% | |
| 🤣 | 4 | 1.02% | |
| 🥱 | 1 | 0.255% |
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 12 of the 12 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 392 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 2 June 2026 to 10 August 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.
A pesar de no tener mucho adiestramiento, los Caballeros Templarios eran letales debido a su ideologia y culto religioso que los volvia casi suicidas en el combate. Cualquier grupo irregular con una ideologia solida, no importa que tan ridicula sea, es bastante peligroso. Igual que Los Zetas, el grupo perdio su letalidad y eficacia cuando sus lideres comenzaron a ser abatidos y detenidos, los miembros poco a poco d…
👍18🤣2🫡2🔥1
24 de julio de 2013 Pichilinguillo, Michoacan Policias Federales son emboscados por sicarios de los Caballeros Templarios. Supuestamente, 6 elementos fueron heridos, se desconoce el saldo de los sicarios.
🔥15🫡2
Recopilacion de actividades de adiestramiento del Cuerpo de Fuerzas Especiales. Un rumor es que el CFE acostumbraba grabar los adiestramientos de cada generacion y al finalizar el curso, se le entregaban a los graduantes un disco CD conteniendo las actividades grabadas. Hay una posibilidad de que algunas partes de este video sea de algun CD de esos.
❤31🔥7
Fecha desconocida, alrededor del 2010. Ciudad Juarez, Chihuahua Policias federales se enfrentan contra 3 sicarios refugiados en un edificio abandonado. Se puede hacer notar el uso de escudos tacticos por los policias. El saldo fue el siguiente: 2 sicarios abatidos. Un civil herido. El ultimo sicario logro huir.
🔥25❤1
Lugar y fecha desconocida. Sicarios se graban siendo perseguidos y rodeados por un helicoptero UH-60, el helicoptero da disparos de advertencia con su minigun enfrente del vehiculo de los sicarios, se desconoce el paradero final de los sicarios, pero se escucha al final del video como se estan preparando para abandonar el vehiculo.
🔥32❤1
Subido a Youtube el 25 de marzo de 2010. Una recopilacion de actividades de las fuerzas armadas, un "edit" clasico vaya.
👍23🔥8❤4🫡1
Marinos revientan casa de seguridad de Los Zetas Son recibidos con fuego, asi que simplemente responden con una minigun empotrada en su suburban
🔥50❤5🫡2
El Estado de Coahuila califico el ataque a Villa Union como un atentado terrorista.
❤27🔥7👍6
Al final, el saldo fue: 19 sicarios abatidos (aprox.). Mas de 30+ detenidos, incluyendo a 21 halcones que ayudaron a planear el ataque, detenidos el mes siguiente. (Ahora sirviendo sentencias de mas de 100 años por terrorismo, Coahuila es el unico estado del pais en dar sentencias de terrorismo a sicarios de cualquier grupo del CO). 18 vehiculos asegurados y destruidos. Equipo, armas y mucho mas asegurado. En est…
🔥37❤7👍1
Las antenas fueron retiradas y destruidas. Aqui el reportaje sobre ello: https://www.youtube.com/watch?v=jDKhuCYmOYA
🔥13
A unas solas horas del ataque, el gobernador del estado en ese entonces, Miguel Riquelme, pidio ir a la zona a inspeccionar y coordinar la busqueda de los sicarios del CDN. Tambien regaño la policia municipal quejandose porque no les llamaron antes, pero tras investigaciones, descubrieron que el CDN tenia antenas interceptoras de radio, razon por la cual tardo la respuesta.
🔥25
30 de noviembre de 2019 Villa Union, Coahuila Sicario del CDN graba con una camara de accion en su casco, el momento que inicia el famoso ataque al municipio de Villa Union, los sicarios incendiaron varios vehiculos y abrieron fuego en contra del ayuntamiento. El sicario grabando fue despues abatido por la policia estatal y su video fue publicado por la Policia Estatal de Coahuila. Al intentar salir del municipio,…
🔥34❤2🤣2🥱1
Showing the 12 most recent of 12 posts we hold for @MexicanMilitaryArchives. 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.
Named by 1 registered channel — 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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Mexican Military Archives” (@MexicanMilitaryArchives), 1,729 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/MexicanMilitaryArchives.
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.