Telegram RegisterThe public register of Telegram
Telegram profile photo for Hyperliquid Announcements

Channel

Hyperliquid Announcements

@hyperliquid_announcements

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

26,384subscribers

-700 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-1001736253760
TypeChannel
Username@hyperliquid_announcements
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/hyperliquid_announcements

Topic

Crypto & trading — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

26,33827,08726,712.56 August 2026 — 27,084 subscribers6 August 2026 — 27,084 subscribers6 August 2026 — 27,087 subscribers7 August 2026 — 27,085 subscribers8 August 2026 — 26,992 subscribers9 August 2026 — 26,944 subscribers10 August 2026 — 26,910 subscribers11 August 2026 — 26,816 subscribers12 August 2026 — 26,687 subscribers13 August 2026 — 26,604 subscribers14 August 2026 — 26,590 subscribers16 August 2026 — 26,444 subscribers17 August 2026 — 26,416 subscribers18 August 2026 — 26,379 subscribers19 August 2026 — 26,353 subscribers20 August 2026 — 26,338 subscribers21 August 2026 — 26,369 subscribers23 August 2026 — 26,404 subscribers24 August 2026 — 26,450 subscribers25 August 2026 — 26,430 subscribers26 August 2026 — 26,444 subscribers27 August 2026 — 26,462 subscribers28 August 2026 — 26,480 subscribers29 August 2026 — 26,440 subscribers30 August 2026 — 26,387 subscribers31 August 2026 — 26,394 subscribers1 September 2026 — 26,363 subscribers2 September 2026 — 26,360 subscribers4 September 2026 — 26,377 subscribers6 September 2026 — 26,398 subscribers10 September 2026 — 26,385 subscribers12 September 2026 — 26,373 subscribers14 September 2026 — 26,375 subscribers15 September 2026 — 26,366 subscribers17 September 2026 — 26,384 subscribers26,3846 August 202617 September 2026
35 measurements spanning 43 days, net -700. 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 26,226–27,199 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
17 Sept 2026, 23:5826,384+18
15 Sept 2026, 16:5826,366-9
14 Sept 2026, 03:5526,375+2
12 Sept 2026, 08:0026,373-12
10 Sept 2026, 05:1826,385-13
6 Sept 2026, 20:1826,398+21
4 Sept 2026, 04:1526,377+17
2 Sept 2026, 16:4426,360-3
1 Sept 2026, 17:5826,363-31
31 Aug 2026, 19:2526,394+7
30 Aug 2026, 16:2726,387-53
29 Aug 2026, 19:2626,440-40
28 Aug 2026, 21:3426,480+18
27 Aug 2026, 19:3326,462+18
26 Aug 2026, 21:1926,444+14
25 Aug 2026, 22:4426,430-20
24 Aug 2026, 19:3526,450+46
23 Aug 2026, 03:3726,404+35
21 Aug 2026, 13:0626,369+31
20 Aug 2026, 14:1626,338first reading

Engagement

33 posts held, back to 12 June 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
34.6%
avg views ÷ 26,384 subscribers
Avg views / post
9,120
8 posts measured
Reaction rate
1.24%
reactions ÷ views · ER floor
Posts in window
8
of 33 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 September 2026
Posts held33 (12 June 2026 – 23 September 2026)
Views total72,930
Reactions total902
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 09:48 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
287
Videos
4
Links
405

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Video runtime
42s
Average length
14s

Measured directly from 3 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.

Reaction mix

3,891 reactions across 33 posts, in 36 distinct kinds. The most used accounts for 50.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,96850.6%
🔥78820.3%
👍62716.1%
⚡882.26%
🤣872.24%
👏731.88%
❤‍🔥370.951%
🫡270.694%
🙏250.643%
🤡240.617%
🆒180.463%
🕊150.386%
✍130.334%
😁130.334%
☃120.308%
🤬100.257%
🌚70.18%
👀60.154%
🐳50.129%
👎50.129%
16 further kinds431.11%

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

Measured over the 33 most recent posts we hold, published 12 June 2026 to 23 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.

Recent posts

23 Sept 2026, 06:21 UTC≈5,100 views214 reactionsread 27 September 2026
Photo

Open interest reached an all-time high of $18B on Hyperliquid Note: Two-sided OI is calculated as the sum of long and short positions

🔥140❤48👍13⚡7👏2🆒2🌭1😐1

22 Sept 2026, 06:58 UTC≈5,260 views77 reactionsread 27 September 2026

Weekly Update Product & Tech + Trailing stops are now available for perp markets. See the Support Docs for more: https://hyperliquid.gitbook.io/hyperliquid-docs/support/faq/trailing-stops New Teams on HyperEVM & HyperCore (in no particular order) + 1inch deployed on HyperEVM: https://x.com/1inch/status/2098051597364334669 + BitGo's self-custody wallet added support for HyperCore: https://x.com/BitGo/status/20980444…

❤48👍12🔥9🤝3🍌2🌭1🦄1🙏1

21 Sept 2026, 05:43 UTC≈5,990 views176 reactionsread 27 September 2026
Photo

Trailing stops are now available for perp markets. A trailing stop's trigger price follows the mark price as it moves in favor of the position. When the mark price retraces from its best level by the selected distance or percentage, it triggers a market order for the selected size. For long positions, the trigger price follows the highest mark price reached since activation; for short positions, it follows the lowes…

❤113👍21⚡12❤‍🔥10🔥10🌚3👏3🙏2

18 Sept 2026, 06:46 UTC≈7,940 views155 reactionsread 27 September 2026
Photo

Manual borrows are live on Hyperliquid Portfolio margin and manual borrows use the same underlying HyperCore infrastructure, with $269M in assets borrowed today. Users can supply HYPE and BTC as collateral to borrow quote assets (USDC and USDT). Borrowed quote assets pay interest, and supplied quote assets earn interest, with rates set by utilization. See the Support Docs for more: https://hyperliquid.gitbook.io/h…

❤100🔥30👍16⚡5👏3🙏1

8 Sept 2026, 16:06 UTC≈11,200 views69 reactionsread 27 September 2026
Photo

By community request, $USELESS perps have been listed with up to 3x leverage. Listing is not an endorsement of the project. Past performance does not guarantee future results. Do not trade assets you are unfamiliar with and do not understand the risks for. Exercise control. NFA. https://app.hyperliquid.xyz/trade/USELESS

👍39❤17🔥6⚡5👎2

8 Sept 2026, 02:47 UTC≈9,440 views68 reactionsread 27 September 2026

Weekly Update Product & Tech + Manual borrowing on HyperCore is live on mainnet. As a reminder, HyperEVM smart contracts can access HyperCore borrow/lend functionality from CoreWriter and read precompiles + HIP-3* spec was shared New Teams on HyperEVM & HyperCore + Chainalysis added support for HyperEVM: https://x.com/chainalysis/status/2095568202663092401 Community Highlights + New Hypurr stickers were added to T…

👍31❤26💊4🕊4⚡3

31 Aug 2026, 10:42 UTC≈12,200 views75 reactionsread 27 September 2026

Weekly Update Product & Tech + HIP-4 permissionless deployments were enabled on mainnet Trading + PONS perps were listed; VINE perps were delisted + HyENA's HIP-3 dex is sunsetting. See information on market wind-down here: https://docs.hyena.trade/ New Teams on HyperEVM & HyperCore + Pumpfun added support for HyperEVM: https://x.com/Pumpfun/status/2092613331299291421 Community Highlights + Bloomberg wrote about …

❤46🔥16👍7🤣3⚡1🏆1🙏1

31 Aug 2026, 03:53 UTC≈15,800 views68 reactionsread 27 September 2026
Video

By community request, $PONS perps have been listed with up to 3x leverage. Listing is not an endorsement of the project. Past performance does not guarantee future results. Do not trade assets you are unfamiliar with and do not understand the risks for. Exercise control. NFA. https://app.hyperliquid.xyz/trade/PONS

🔥39🤣22👍5❤1💯1

27 Aug 2026, 06:01 UTC≈12,600 views191 reactionsread 27 September 2026
Photo

The Hyperliquid community event will take place on the evening of October 5, 2026 in Singapore: https://luma.com/HL2026Community This is a chance to spend time with the builders and users who've shaped the ecosystem over the past years. If you're with a project or institution, please share your team and role as well as social media handles when you register. The event will be extremely oversubscribed, so this will m…

❤130🔥25👍17❤‍🔥9👏9🙏1

24 Aug 2026, 10:04 UTC≈11,100 views108 reactionsread 27 September 2026

Weekly Update Product & Tech + HIP-1 spot annotations and deployer labels are now supported. For details, see the API announcements channel + HIP-4 templates on testnet are pending builder feedback; see the API announcements channel + See Docs re: infra providers' peering services that builders can connect to: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/nodes/foundation-non-validating-node-for-inf…

🔥63❤33👍8⚡2🌭1🙏1

17 Aug 2026, 05:48 UTC≈11,800 views89 reactionsread 27 September 2026

Product & Tech + Based on feedback, the HIP-1 spec will be extended. Existing deployers and teams interested in HIP-1 deployment are encouraged to share further feedback. For details, see the API announcements channel + Based on feedback, additional features for HIP-4 have been implemented. For details, see the message above + Hyper Foundation's non-validating node is open to high-quality infrastructure providers as …

👍54❤20👏7❤‍🔥3🤣3🙏2

14 Aug 2026, 09:37 UTC≈11,600 views138 reactionsread 27 September 2026

Additional features for HIP-4 have been implemented: 1. Deployer actions now support registerAndAssociateNamedOutcomeFromTemplate which allows deployers to add additional named outcomes to a question after creation. The initial balances of the new named outcome match the outstanding fallback balances. See hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/hip-4-deployer-actions for details. 2. Template instan…

🔥77❤43👍11👏3🤣2🙏2

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

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.

Mentions

Named by 22 registered channels — 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.

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.

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

“Hyperliquid Announcements” (@hyperliquid_announcements), 26,384 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hyperliquid_announcements.

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.