Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 34 comparable posts for this entry, running 7 July 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @hashkeyhsk — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
66 measurements spanning 98 days, net -26,707. 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 67,242–101,961 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)
Subscribers
Change
11 Nov 2026, 15:48
71,248
-136
9 Nov 2026, 23:01
71,384
-161
8 Nov 2026, 17:41
71,545
-132
7 Nov 2026, 08:55
71,677
-109
6 Nov 2026, 06:07
71,786
-55
5 Nov 2026, 08:01
71,841
-3,164
4 Nov 2026, 05:11
75,005
-11,750
3 Nov 2026, 05:40
86,755
-71
2 Nov 2026, 06:07
86,826
-87
1 Nov 2026, 03:30
86,913
-115
31 Oct 2026, 03:26
87,028
-136
30 Oct 2026, 03:56
87,164
-53
29 Oct 2026, 06:56
87,217
-168
28 Oct 2026, 01:50
87,385
-78
27 Oct 2026, 03:16
87,463
-287
26 Oct 2026, 01:40
87,750
-259
24 Oct 2026, 22:20
88,009
-651
24 Oct 2026, 00:48
88,660
-100
22 Oct 2026, 21:41
88,760
-1,838
21 Oct 2026, 15:16
90,598
first reading
Engagement
36 posts held, back to 7 July 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 198 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.272%
avg views ÷ 71,248 subscribers
Avg views / post
194
11 posts measured
Reaction rate
0.656%
reactions ÷ views · ER floor
Posts in window
12
of 36 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 4 of 11 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 11 November 2026
Posts held
36 (7 July 2026 – 11 November 2026)
Views total
2,130
Reactions total
6
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Nov 2026, 06:52 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
183
Videos
12
Links
270
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
14s
Average length
7s
Measured directly from 2 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
28 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 39.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
11
39.3%
💩
7
25.0%
👍
6
21.4%
🔥
3
10.7%
🌚
1
3.57%
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 15 of the 36 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 7 July 2026 to 11 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 12 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).
🇸🇬 Singapore FinTech Festival 2026 is Almost Here! 🚀
The HashKey On-Chain team is heading to Singapore FinTech Festival 2026! Join us to explore the future of institutional on-chain finance and blockchain infrastructure.
💡 Key discussion topics:
▫️ Institutional on-chain infrastructure
▫️ Stablecoin settlement solutions
▫️ Moving blockchain projects from pilot to production
📅 Date: November 18–20, 2026
📍 Venue: S…
🎬 Horizon Hackathon India | Event Recap 🇮🇳
A look back at Horizon Hackathon India, where builders gathered in Mumbai to turn fresh ideas into real projects on HSK Chain! 🚀
💡 Participants explored new possibilities across two key tracks:
▫️ AI Agent Trading
▫️ Agent Payments & A2A Settlement
👏 Thank you to all the teams who participated, shared their ideas, and showcased what they built.
🎥 Watch the Horizon Hacka…
📢 HSK Staking Phase 1 | Important Update
✅ HSK Staking Phase 1 has officially matured, and users can now unstake as normal.
⚠️ A technical issue in the yield calculation formula may have caused some users to receive less than expected, including a principal shortfall and missing yield.
💰 Compensation Details:
▫️ Compensation will be calculated using a 5.5% annualized yield, prorated based on the lock-up period.
▫️…
🚀 HSK Chain Horizon Hackathon · India | 21 Projects Selected! 🇮🇳
🎉 Congratulations to the 21 projects advancing to Demo Day on November 4 in Mumbai! Teams will showcase their Web3 innovations, with exclusive hackathon merchandise available for onsite participants. 🎁
📅 November 4 | 13:00 SGT / 10:30 IST
📍 Mumbai, India
⚠️ Selected teams must attend Demo Day to remain in the program.
🔗 View the selected projects an…
📸 HKFTW2026 Day 1 Is Underway! 🚀
Hong Kong FinTech Week 2026 has officially kicked off, and HSK Chain is on the ground in Hong Kong! 🇭🇰
🌐 Come meet the HSK Chain team, explore the ecosystem, and get a chance to win exclusive prizes! 🎁
📍 Venue: Hong Kong Convention and Exhibition Centre (HKCEC)
🏢 Hall 5 | Booth 5FG-DA01
🤝 If you're attending, make sure to stop by and say hello!
🔗 Check out the Day 1 highlights an…
🌏 HashKey On-Chain Heads to Singapore FinTech Festival 2026! 🚀
HashKey On-Chain is joining Singapore FinTech Festival 2026, bringing together industry leaders, innovators, and financial institutions to explore the future of finance and blockchain technology.
🤝 Visit the HashKey team to connect, exchange insights, and discover what's next for on-chain finance!
📍 Booth: 4H03
🏢 Venue: Singapore EXPO
📅 Date: November …
📢 Beyond the Hype: What Makes a Web3 Demo Worth Backing? 🚀
What makes a Web3 project worth supporting? 💡
Join the Horizon Hackathon AMA with industry builders and experts to explore what makes a Web3 demo stand out and gain backing.
🎤 Moderator:
▫️ Piyush Maheshwari | Head of Ecosystem, MOI Technology
👥 Speakers:
▫️ Alex D (Ding) | Core Builder, HSK Chain
▫️ 10K Rotator | Co-founder, Stablecorp
▫️ Prince Gupta | …
🎃 Hashoo’s Spooky Mine Is LIVE! 👻
Halloween has arrived on HSK Chain! Help Hashoo collect candy, earn tickets, and compete for a share of the 200 USDT prize pool! 🍬⛏️
🎮 How to Participate:
1️⃣ Follow HSK Chain on X.
2️⃣ Like and repost the official event post.
3️⃣ Tag 2 friends in the event post.
4️⃣ Play the game and share your results on X.
5️⃣ Submit a screenshot of your tickets and your EVM wallet address in th…
🚀 HSK Chain Horizon Series Hackathon Is Coming to Mumbai! 🇮🇳
The HSK Chain Horizon Series Hackathon · India is officially underway, hosted by HSK Chain and organized by 021Lab!
Developers and builders are invited to explore AI-powered trading and payment solutions, compete for rewards, and showcase their projects in Mumbai. 💻
📅 Hackathon: October 23 – November 4, 2026
📍 Demo Day: November 4 | Mumbai, India
🛠 Two …
👍3
Showing the 12 most recent of 36 posts we hold for @hashkeyhsk. 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.
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.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 28 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
QK哈希实时观战频道 @lookqk · 49,402 Telegram ranks this channel #29 of 62 here — alongside 61 others — read 28 August 2026
HashKey Global Announcements @hashkeyglobal_announcement · 155,195 Telegram ranks this channel #68 of 87 here — alongside 86 others — read 28 August 2026
Bot Gameyard @BotGameyard · 28,287 Telegram ranks this channel #72 of 75 here — alongside 74 others — read 6 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists 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 11 November 2026 — this
entry's latest reading, not the date you are reading this.
“HSK Chain News” (@hashkeyhsk), 71,248 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/hashkeyhsk.
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.