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 the other topics.
Growth
62 measurements spanning 96 days, net -107. 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 62
Measured (UTC)
Subscribers
Change
10 Nov 2026, 09:46
26,977
+74
8 Nov 2026, 18:50
26,903
+15
7 Nov 2026, 11:00
26,888
+20
6 Nov 2026, 08:51
26,868
+17
5 Nov 2026, 11:56
26,851
+13
4 Nov 2026, 13:36
26,838
+3
3 Nov 2026, 11:36
26,835
+1
2 Nov 2026, 11:05
26,834
+17
1 Nov 2026, 08:49
26,817
+12
31 Oct 2026, 06:28
26,805
+32
30 Oct 2026, 06:20
26,773
+67
29 Oct 2026, 09:28
26,706
-7
27 Oct 2026, 03:58
26,713
+41
26 Oct 2026, 05:58
26,672
+2
25 Oct 2026, 07:16
26,670
+4
23 Oct 2026, 07:58
26,666
+3
22 Oct 2026, 09:30
26,663
+7
21 Oct 2026, 06:07
26,656
+5
20 Oct 2026, 06:40
26,651
+19
19 Oct 2026, 03:07
26,632
first reading
Engagement
43 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 149 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
34.9%
avg views ÷ 26,977 subscribers
Avg views / post
9,410
7 posts measured
Reaction rate
1.46%
reactions ÷ views · ER floor
Posts in window
7
of 43 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
Window
Rolling 30 days · latest post in window 3 November 2026
Posts held
43 (12 June 2026 – 3 November 2026)
Views total
65,870
Reactions total
960
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Nov 2026, 05:20 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
289
Videos
4
Links
413
Lifetime counters from Telegram’s own channel header, read 12 November 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
5,227 reactions across 43 posts, in 41 distinct kinds. The most used accounts for 51.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
2,667
51.0%
🔥
1,103
21.1%
👍
758
14.5%
⚡
121
2.31%
👏
102
1.95%
🤣
92
1.76%
❤🔥
91
1.74%
🫡
44
0.842%
🙏
37
0.708%
🤡
24
0.459%
🆒
20
0.383%
😁
18
0.344%
🕊
16
0.306%
✍
15
0.287%
☃
14
0.268%
🐳
10
0.191%
🤬
10
0.191%
💯
9
0.172%
🌚
7
0.134%
🦄
7
0.134%
21 further kinds
62
1.19%
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 43 of the 43 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 5,227 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 12 June 2026 to 3 November 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
Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Weekly Update
Trading
+ ICE x trade[xyz] announced their intention to deploy HIP-3* markets: https://x.com/HyperliquidX/status/2115782848192118861
+ Update to TWAPs: TWAP orders with a stop price will be paused instead of canceled when the stop price is breached. This allows TWAP orders to resume if the stop price is no longer breached within the TWAP duration
New Teams on HyperEVM & HyperCore
+ Pumpfun integrated …
Intercontinental Exchange (ICE) and trade[XYZ] have announced their plan to use Hyperliquid as the infrastructure layer to deploy perpetual futures markets for US traders across crypto, equities, commodities, foreign exchange, and other real-world assets, subject to regulatory approvals. ICE operates NYSE and some of the largest exchanges and clearing houses globally.
In this structure:
+ Hyperliquid serves as the u…
Weekly Update
Product & Tech
+ See the API announcements channel for various technical updates re: write priority fees, gossip priority slots, optional sub-builders, etc.
Trading
+ Payward, the parent company of Kraken, announced its intention to be the first CFTC-regulated deployer on HIP-3* markets
+ XTEN hyperp was listed
Community Highlights
+ The India community is organizing an event in Mumbai on November 3:…
By community request, Extended ($XTEN) hyperp has been listed with up to 3x leverage.
As a reminder, hyperps do not rely on any external data for the oracle price. Hyperps trade like perpetual contracts that users are familiar with, but do not require an external spot or index oracle price. Instead, the funding rate is determined relative to a moving average of the hyperp mark price. This makes the hyperp price more…
Payward, the parent company of Kraken, announced its intention to be the first CFTC-regulated deployer on HIP-3* markets. Payward will use Hyperliquid as the infrastructure layer to deploy perpetual futures markets for US clients. Subject to regulatory approval, Bitnomial, Payward’s CFTC-regulated DCM and DCO, would act as the HIP-3* deployer: creating, owning, and administering the markets and clearing and settling …
Weekly Update
Product & Tech
+ See the API announcements channel for updates to write priority fees
New Teams on HyperEVM & HyperCore
+ Ensemble vaults are live on HyperEVM: https://x.com/ensembleio/status/2105313393393737951
Community Highlights
+ Jeff spoke about Hyperliquid on the Bloomberg Odd Lots podcast: https://x.com/TheStalwart/status/2110698207684813053
+ Jeff's fireside at Token2049 was uploaded to YouT…
Weekly Update
New Teams on HyperEVM & HyperCore
+ papertrade is live on HyperEVM:
https://x.com/papertrade_xyz/status/2108852108766437759
+ Xverse integrated Hyperliquid perps via builder codes: https://x.com/xverse/status/2108041688925229554
Community Highlights
+ Thank you to everyone who was part of the HL Community Event! https://x.com/HyperliquidX/status/2109326236145287621
+ Jeff spoke at a fireside moderated…
The Hyperliquid community event will take place on the evening of October 5 in Singapore: luma.com/HL2026Community
This is a chance to spend time with the builders and users who've shaped the ecosystem
The event is oversubscribed; you will only be able to attend if your RSVP was accepted. If your RSVP was accepted but you're no longer able to attend, please cancel your RSVP to make space for others
Weekly Update
Trading
+ Open interest reached an ATH of $18B on Hyperliquid
New Teams on HyperEVM & HyperCore
+ DoubleZero Edge now supports Hyperliquid data feeds:
https://x.com/doublezero/status/2103122298253492244
+ Near Protocol deployed NEAR spot on HyperCore: https://x.com/NEARProtocol/status/2102469065822593316
Community Highlights
+ Jeff is speaking at KBW on Wednesday, Sep 30 from 11-11:20am
There will be…
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…
❤50👍13🔥10🤝3🍌2🦄2🙏2🌭1
Showing the 12 most recent of 43 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
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.
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. The 21 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Hyperliquid Announcements” (@hyperliquid_announcements), 26,977 subscribers as measured 10 November 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.