Telegram RegisterThe public register of Telegram
Telegram profile photo for SASEPA Noticias

Channel

SASEPA Noticias

@sasepaweb

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

77subscribers

+1 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003537287265
TypeChannel
Username@sasepaweb
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live13 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/sasepaweb

Topic

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Growth

767977.515 August 2026 — 76 subscribers17 August 2026 — 76 subscribers31 August 2026 — 77 subscribers10 September 2026 — 78 subscribers2 October 2026 — 79 subscribers13 October 2026 — 77 subscribers7715 August 202613 October 2026
6 measurements spanning 58 days, net +1. 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 76–79 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 01:4177-2
2 Oct 2026, 13:1779+1
10 Sept 2026, 03:5678+1
31 Aug 2026, 11:4677+1
17 Aug 2026, 09:3676no change
15 Aug 2026, 20:3176first reading

Engagement

20 posts held, back to 21 July 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 20 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

16 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍425.0%
❤318.8%
👏318.8%
🤨318.8%
🎉212.5%
😐16.25%

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 7 of the 20 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 21 July 2026 to 14 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.

Recent posts

14 Aug 2026, 04:42 UTC18 views3 reactionsread 15 August 2026
Forwarded from @SASEPAMxPhoto

¡Llegó la hora! 👊🏻🔥 Hemos modificado el Monitor SASEPA, ahora podrás encontrar nueva cobertura en la zona de Jalisco, y las ciudades de difusión gracias a RBS 🙌🏻 Ahora la zona de Guadalajara y Tuxtla Gutiérrez entran en nuestra zona de recepción de alertas. 👏🏻 👉🏻 Recuerda que Chiapas empezará a operar en los próximos meses. 🔗 Monitor SASEPA (monitor.sasepa.net) ¡Gracias por hacer posible esto, sin ustedes, SASEP…

❤3

Signed Emix

14 Aug 2026, 03:39 UTC36 views4 reactionsread 15 August 2026
Photo

Ya casi…. 👀⏳💣 13/Agosto/2026 22:00hrs (CDMX) Tic tac… 🗣️

🤨3😐1

Signed Emix

14 Aug 2026, 03:29 UTC35 viewsread 15 August 2026

13/Agosto/2026 22:00 hrs (tiempo del centro de México)… 🇲🇽 👀💣⏳

Signed Emix

14 Aug 2026, 03:27 UTC35 views2 reactionsread 15 August 2026

Gran sorpresa… 💣⏳ Tictac… ¿están listos? 👀

🎉2

Signed Emix

13 Aug 2026, 01:02 UTC219 viewsread 15 August 2026
Photo

refresca el monitor SASEPA, y explora la nueva función que agregamos en el conteo del 2do Simulacro Nacional 2026! 👉🏻 Únicamente en sasepa.net

12 Aug 2026, 02:36 UTC40 viewsread 15 August 2026

Viene nueva actualización del monitor en los próximos días. Únicamente tendrán adelantos los que están en este canal. 👀

Signed Emix

8 Aug 2026, 05:44 UTC70 viewsread 15 August 2026

📣 Aviso Vuelve a sus funciones el mapa de SASEPA. Gracias por su paciencia.

Signed Emix

8 Aug 2026, 02:41 UTC30 views2 reactionsread 15 August 2026
Photo

📣 Aviso de Prueba - SASEPA El Sábado 8 de Agosto de 2026 a las 13:00 hrs, realizaremos una simulación de evento menor entre los límites de Puebla, Guerrero y Oaxaca, como parte de los preparativos para el Segundo Simulacro Nacional 2026. Esto es solo una prueba del sistema, no es real. 👉🏻 IMPORTANTE: Solo sonará el Monitor de SASEPA como un sismo menor en la localización antes mencionada. No habrá notificación en T…

👍2

Signed Emix

8 Aug 2026, 02:29 UTC57 viewsread 15 August 2026

Tenemos problemas con el servidor interno. Ahorita el mapa de SASEPA no está funcionando.

Signed Emix

5 Aug 2026, 01:01 UTC83 viewsread 15 August 2026
Photo

👀 Usuario de SASEPA: Después de varios reportes que nos llegaron sobre el Monitor, que les aparecía que era virus, hemos tomado una decisión drástica. 👨🏻‍💻 ¡YA ESTÁ DISPONIBLE! Monitor SASEPA nuevamente vía web (sasepa.net) 🏃‍♂️ ¡GRACIAS por tu apoyo en Telegram! 👊💙 #LaPrevenciónEsNuestraFuerza

Signed Emix

3 Aug 2026, 00:43 UTC397 views1 reactionsread 15 August 2026
Photo

📣 Aviso de Prueba - SASEPA El Sábado 8 de Agosto de 2026 a las 13:00 hrs, realizaremos una simulación de evento menor entre los límites de Puebla, Guerrero y Oaxaca, como parte de los preparativos para el Segundo Simulacro Nacional 2026. Esto es solo una prueba del sistema, no es real. 👉🏻 IMPORTANTE: Solo sonará el Monitor de SASEPA como un sismo menor en la localización antes mencionada. No habrá notificación en T…

👏1

Signed Emix

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“SASEPA Noticias” (@sasepaweb), 77 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/sasepaweb.

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.