3 measurements spanning 2 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 495–496 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Sept 2026, 11:17
496
+1
5 Sept 2026, 12:23
495
no change
5 Sept 2026, 11:47
495
first reading
Engagement
20 posts held, back to 18 August 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.
ERR · 30 days
41.0%
avg views ÷ 496 subscribers
Avg views / post
203
20 posts measured
Reaction rate
2.13%
reactions ÷ views · ER floor
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. It is computed over the 14 of 20 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 2 September 2026
Posts held
20 (18 August 2026 – 2 September 2026)
Views total
4,065
Reactions total
60
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
5 Sept 2026, 12:23 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.
Reaction mix
60 reactions across 14 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
60
100.0%
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 14 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 60 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 18 August 2026 to 2 September 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.
N’asturianu.
AICIÓN D’ASTURIES INSUMISA EN CANDÁS: ¡PISOS PA VIVIR, NON PAL TURISMU!
Faise necesario tornar el turismu nun aliáu pal desarrollu y non nuna amenaza de graves consecuencies pal nuesu propiu futuru.
______
En castellano.
ACCIÓN DE ASTURIES INSUMISA EN CANDÁS: ¡PISOS PARA VIVIR, NO PARA EL TURISMO!
Se hace necesario convertir el turismo en un aliado para el desarrollo y no en una amenaza de graves co…
N’asturianu.
AICIÓN D’ASTURIES INSUMISA EN XIXÓN: ¡PISOS PA VIVIR, TURISTES PAL HOTEL!
Trátase d’algamar un modelu de turismu razonable y respetuosu, que se convierta nuna actividá económica beneficiosa pal conxuntu la sociedá asturiana, ensin les pergafes consecuencies del turismu masificáu.
_______
En castellano.
ACCIÓN DE ASTURIES INSUMISA EN XIXÓN: ¡PISOS PARA VIVIR, TURISTAS PARA EL HOTEL!
Se trata de alcan…
N’asturianu.
VERMÚ SOLIDARIU EN BENEFICIU DE FAMILIES PALESTINES REFUXAES N’ASTURIES
DOMINGU 6 DE SETIEMBRE. 13:00 h. XAGÓ SURF COMPANY. XAGÓ. GOZÓN. ASTURIES.
_______
En castellano.
VERMÚ SOLIDARIO EN BENEFICIO DE FAMILIAS PALESTINAS REFUGIADAS EN ASTURIES
DOMINGO 6 DE SEPTIEMBRE. 13:00 h. XAGÓ SURF COMPANY. XAGÓ. GOZÓN. ASTURIES.
N’asturianu.
MANIFESTACIÓN EN SOLIDARIDÁ COL PUEBLU SAHARAUI
DOMINGU 30 D’AGOSTU. 12:30 h. PONTE’L PILES-XARDINES DEL NÁUTICU. XIXÓN ASTURIES.
_______
En castellano.
MANIFESTACIÓN EN SOLIDARIDAD CON EL PUEBLO SAHARAUI
DOMINGO 30 DE AGOSTO. 12:30 h. PUENTE DEL PILES-JARDINES DEL NÁUTICO. XIXÓN ASTURIES.
Showing the 12 most recent of 20 posts we hold for @Asturies_Insumisa. 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.
Appears in Telegram’s recommendations for other channels
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.
vpn turbo | V2rayNG | فیلترشکن @vpnturbo_proxy · 32,193 Telegram ranks this channel #14 of 52 here — alongside 51 others — read 5 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 7 September 2026 — this
entry's latest reading, not the date you are reading this.
“Asturies Insumisa” (@Asturies_Insumisa), 496 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/Asturies_Insumisa.
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.