Channel
@helium_es
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
52subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001672401369 |
|---|---|
| Type | Channel |
| Username | @helium_es |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/helium_es |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 13:38 | 52 | -1 |
| 10 Aug 2026, 09:16 | 53 | no change |
| 6 Aug 2026, 05:05 | 53 | first reading |
20 posts held, back to 17 October 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 pageof 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 5 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 1reactions 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 17 October 2025 to 28 July 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.
Active upstream carrier 2 offload outage https://status.helium.com/incidents/xtryf43453qz Jul 27, 23:43 UTC Identified - Carrier 2 general outage. Awaiting resolution. Jul 27, 23:17 UTC Investigating - Investigating connectivity issue affecting upstream carrier traffic with carrier 2.
Decrease in Hotspot Heartbeats https://status.helium.com/incidents/94477dlychr1 Jul 12, 16:53 UTC Investigating - We’re observing an increase in hotspot heartbeat issues and are currently investigating. We will continue to keep the community updated.
Helium packet Router - Maintenance https://status.helium.com/incidents/r9hprbtqgrlb THIS IS A SCHEDULED EVENT Jun 25, 18:00 - 19:00 UTC Jun 24, 20:22 UTC Scheduled - We will be performing a scheduled update to the Helium Packet Router (v1.7.0). No downtime is expected.
Helium Mobile Hotspot Connection Issue https://status.helium.com/incidents/999g1m2vgfvb Apr 15, 01:00 UTC Resolved - Some Helium Mobile Hotspots had an issue where devices could connect to WiFi but couldn’t actually use the internet, due to a problem on those specific units, while the overall network was working normally. A fix is being worked on for affected hotspots - if you experience this behaviour, restarting …
IoT Network Improvements https://status.helium.com/incidents/5vqs6pt9m9jg Apr 2, 20:17 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr 2, 20:16 UTC Scheduled - We are currently updating our IoT infrastructure to enable support for custom multibuy services. This rollout is designed to expand our service capabilities without impact to system availability. Th…
Helium Packet Router Maintenance https://status.helium.com/incidents/97jqnpyw36t0 THIS IS A SCHEDULED EVENT Mar 26, 18:30 - 20:30 UTCMar 26, 17:24 UTC Scheduled - Performance improvements and better handling of routing updates.
Helium Packet Router Upgrade https://status.helium.com/incidents/gjk2tg4rhny1 THIS IS A SCHEDULED EVENT Mar 16, 18:00 - 20:00 UTCMar 13, 17:24 UTC Scheduled - The core team will be deploying updates to Helium Packet Router. This maintenance includes performance improvements.
IoT Packet Router Diminished Performance https://status.helium.com/incidents/bzpy4mvk6xl3 Mar 11, 02:44 UTC Monitoring - A fix has been implemented and we are monitoring the results.Mar 11, 02:04 UTC Identified - A performance issue is affecting Helium Packet Router performance in the Frankfurt region. This may affect IoT device message delivery in Europe. The team has identified the issue and is scaling resources …
Helium Packet Router Maintenance https://status.helium.com/incidents/bhyy7402n85g Mar 9, 22:00 UTC Completed - The scheduled maintenance has been completed.Mar 9, 19:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar 9, 17:49 UTC Scheduled - The core team will be deploying an infrastructure update to Helium Packet Router. We'll update this page when the d…
IMS-Prod Upgrade Service Interruption https://status.helium.com/incidents/ltlhql83kwl2 Feb 12, 16:24 UTC Resolved - During the IMS-Prod upgrade, services experienced a brief outage of roughly 15–20 minutes due to a load balancer and DNS issue introduced during the update. This impacted the Hotspot dashboard and related IMS services. The issue was identified and resolved, and all systems are now fully operational.
❤1
IoT Oracle Infrastructure Update https://status.helium.com/incidents/rc0rrzmm6d8w THIS IS A SCHEDULED EVENT Feb 2, 15:00 - 16:00 UTCJan 29, 22:47 UTC Scheduled - The core team will be deploying an infrastructure update to IoT Oracles. While the update is in progress, some route configurations for OUI operators may fail to be accepted by the config service. IoT data transfer for existing routes will continue during t…
World Explorer Degraded Service https://status.helium.com/incidents/kmx0spybkgy4 Jan 27, 19:54 UTC Resolved - This incident has been resolved.Jan 27, 17:57 UTC Identified - An upstream service is causing some Hotspots to fail to load. The team is investigating the issue and will deploy a fix shortly.
Showing the 12 most recent of 20 posts we hold for @helium_es. 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.
Citation-graph rank — 423,319 of 1,620,105entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Helium HNT Canal” (@helium_es), 52 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/helium_es.
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.