HECO Announcement pinned «Retiring HECO Network & Disposing Some HRC20 Assets The HECO Network will retire on Jan 15, 2025 (UTC), coupled with the removal of some HRC20 assets (i.e. HRC20ETH, HRC20TUSD, HRC20LINK, HRC20USDC, HRC20UNI, HRC20SHIB, HRC20HBTC, and HRC20USDT). Holders…»

Channel
HECO Announcement
@HECOAnnouncement
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
11,232subscribers
-40 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001485102730 |
|---|---|
| Type | Channel |
| Username | @HECOAnnouncement |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/HECOAnnouncement |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:05 | 11,232 | -7 |
| 13 Aug 2026, 01:08 | 11,239 | -3 |
| 12 Aug 2026, 02:13 | 11,242 | -14 |
| 11 Aug 2026, 00:14 | 11,256 | -4 |
| 9 Aug 2026, 23:33 | 11,260 | -7 |
| 8 Aug 2026, 19:27 | 11,267 | -5 |
| 7 Aug 2026, 00:00 | 11,272 | no change |
| 6 Aug 2026, 23:58 | 11,272 | first reading |
Engagement
20 posts held, back to 19 February 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof 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 18 November 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 174
- Videos
- 1
- Links
- 239
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Retiring HECO Network & Disposing Some HRC20 Assets The HECO Network will retire on Jan 15, 2025 (UTC), coupled with the removal of some HRC20 assets (i.e. HRC20ETH, HRC20TUSD, HRC20LINK, HRC20USDC, HRC20UNI, HRC20SHIB, HRC20HBTC, and HRC20USDT). Holders of these HRC20 assets can visit HecoDAO's official website (https://heco123.com) and deposit their assets to the designated address before Jan 10, 2025. The deposi…
🎁HECO X Plato Farm Winner List - Each Will Be Rewarded 20$ in $PLATO Julissa Robless (user id 2122043182) Chua te rung sanh (user id 5081539743) Milagros canfield (user id 5016953221) Nam boss (user id 2136123166) Nancey crabtree (user id 2138591404) Congratulations to the winners! Please share your HECO address to @Rased91 to claim your rewards before 1th April, 2022 6AM UTC+0!
🎉$5,000 #Airdrop for supporting https://www.iswap.com 💰 🎊0 fee trading & suprise reward here for you! 👐Invite your friends and grab incredible prizes!💸 👉Join for more details: https://t.me/iSwapCom #crosschian #HECO #BSC #ETH #TRON https://iswapcom.medium.com/iswap-15-chains-event-with-5-000-airdrop-23c01c7263f8
We are pleased to announce HECO 54th AMA at 5:00 PM, 30th March 2022 SGT: HECO x Plato Farm ⚠️Total Reward pool: $500 We will have the following structure: Section:1 Part 1️⃣: Speaker Introduction Part 2️⃣: Q&A - We will ask 6-10 questions to speaker about Plato Farm so we would know more about them. Part 3️⃣: Live Question - $100/10 Winners – Open chat for 120 seconds. You can post Max 3 questions.Plato Farm Te…
🎉More tokens supported! USDT, USDC, #ETH& #DAI, 0 fee for large order!👀 🤩1:1 bridge! Large order on #Heco & #OEC supported!🪙 🥳Trade on https://www.iswap.com DAI, #UNI& #LINK for 0 slippage!😆 👉Join in for more information: https://t.me/iSwapCom
🎁HECO X Trust Swap Winner List - Each Will Be Rewarded 10$ in $SWAP @jean_2001a @Britanydiehl62 @clorinda_PO @Prestonoet @Griffin1993a @niohowell @Spencer_1995 @Doimatns @kerrie_jose_62 Lenora Shin (user I'd 2107615113) Congratulations to the winners! Please share your HECO address to @Rased91 to claim your rewards before 18th March, 2022 6AM UTC+0!
🧐Wanna know more about @TrustSwap ? Do not miss the #HECO #AMA Series with #TrustSwap! ⏰1pm SGT, 16th Mar 2022 📍https://t.me/Huobiecochainofficial
😍Tell me about Hanazawa Kana and win 50 R NFT 👉About R NFT Name: Hanazawa Kana Classic Edition R NFT Issue Amount: 900 Steps: 1️⃣ Follow @TheHuobiNFT& @NEXTYPE1 2️⃣ Rt @ 3 3️⃣ Fill the form:https://forms.gle/6vQNfr4LeVji7J1q8 🏆50 Lucky winners will win R NFT for free @hanazawa_staff
🚀Join Golden mining day on HECO earn APY up to 54.49 % Date: Mar.10-11 #btcmt #eth #hbtc @BTCMTOfficial @ChannelsEN @MdexEN
🎁HECO X CroxSWAP Winner List - Each Will Be Rewarded $10 of tokens @MilagroCowles Annabelle Miranda (User I'd 2037617091) Michelle (User I'd 2095398200) @Garrett_Hallman Alexander weaver (user I'd 2001463610) Uyen Holder (user I'd 2133547929) Diep bich III Monster (user I'd 2060440837) Tran yen (user I'd 2144164977) Marilu Hoang (user I'd 2043237902) Khanh Linh (user I'd 2070671920) Congratulations to the winners! …
🚀Join Golden mining day on HECO earn APY up to 33.87 % Date: Mar.3-4 (SGT) #HUSD #USDT #HBTC @FilDAFinance @LendHubDefi @ChannelsFinance
Showing the 12 most recent of 20 posts we hold for @HECOAnnouncement. 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
Citation-graph rank — 1,181,512 of 1,480,688entries 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.
Mentions
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 16
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 16
- vacant every time we have ever looked
@HECOAnnouncement named 16 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 6 posts, 8 August 2026 – 13 August 2026
named in 6 posts, 8 August 2026 – 13 August 2026
named in 6 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 13 August 2026
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“HECO Announcement” (@HECOAnnouncement), 11,232 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/HECOAnnouncement.
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.