https://youtu.be/hZyNHmAPg_g?is=hQdQi5pmo42fNWTV

Channel
AMSAVIVERE
@amsavivere
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
24subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001346861165 |
|---|---|
| Type | Channel |
| Username | @amsavivere |
| Description | Amor Salud Vida Verdad & Realidad |
| Created | 26 April 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/amsavivere |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 11:04 | 24 | no change |
| 7 Aug 2026, 19:46 | 24 | first reading |
Engagement
20 posts held, back to 30 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 27.3%
- avg views ÷ 24 subscribers
- Avg views / post
- 6.5
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- 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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 20 (30 July 2026 – 11 August 2026) |
| Views total | 131 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 11: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.
What this channel posts
- Photos
- ≈1,340
- Videos
- ≈2,070
- Links
- ≈2,860
Lifetime counters from Telegram’s own channel header, read 11 August 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.
- Video runtime
- 28m 41s
- Average length
- 2m 52s
Measured directly from 10 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.
Recent posts
Gracias a los agentes de autoridad y alcaldes que han decidido desobedecer a sus partidos y jefes para aceptar la ayuda de Alvise Pérez. Priorizar a los españoles SIEMPRE es una buena decisión.
https://youtu.be/SUy_Krjwuok?is=XtaXv7PXXx6CIinw
Nos acaban de informar de que hemos sido denunciados por supuestamente violar los confinamientos durante los incendios de este mes. Tenemos pruebas de cómo se dejaba pasar a cualquier voluntario o vecino, pero a nosotros que portábamos material retardantes, agua, uniformes, ignífugos, más de 65.000 € en materiales contra incendios y 11.000 litros de Ecofire, nos detenían. Esto es Venezuela. Pero no nos vamos a acha…
Intentan acabar con todo aquél que enfrente al sistema. No lo van a conseguir. SE ACABÓ LA FIESTA.
URGENTE: TODO FUE PLANIFICADO El escritor y conferencista Damián Galerón expone una surrealista conversación que tuvo hace 20 años, con un catedrático de la Sorbona de París. Hace 20 años, el catedrático le dijo que España sufriría invasiones masivas, que Marruecos estaría detrás de atentados, que Europa sería islamizada progresivamente y que los militares serían obligados a quedarse en sus cuarteles y no interveni…
https://www.youtube.com/watch?v=BCocLSd0MfY
Movilización contra la Embajada y el Consulado General de Marruecos tras querellarnos contra altos cargos marroquíes y el Rey Mohamed VI ante la Audiencia Nacional, que acaba de aceptarnos la denuncia y ordenado diligencias. Quien no condene a Mohamed VI, ese es el traidor. SE ACABÓ LA FIESTA.
Influencers marroquíes organizan masivamente otro gran salto para volver a entrar en Ceuta el 15/08/26.
"Los primeros análisis sobre la avalancha de Ceuta apuntan a Rabat": la dirección del diario El Mundo ha mostrado una sagacidad digna de Sherlock Holmes. ¡Quién hubiera pensado que fue el gobierno de Marruecos quien dirigió la invasión de Ceuta! 😜😝😝
🔴 ÚLTIMA HORA: ALVISE DENUNCIA EN LA AUDIENCIA NACIONAL AL REY DE MARRUECOS POR DELITOS DE LESA HUMANIDAD
ASÍ EMPEZÓ EL SAQUEO AL MERCADONA DE CEUTA: La población civil está encerrada. Suspendidas fiestas y eventos. Cierre masivo de tiendas. Huída de miles de ceutíes. Marruecos guarda silencio de por qué transporta decenas de miles hacia la frontera. Miembros del Ejército denuncian 'bloqueo no motivado' del Gobierno de España.
Showing the 12 most recent of 20 posts we hold for @amsavivere. 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
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“AMSAVIVERE” (@amsavivere), 24 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/amsavivere.
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.