https://linktr.ee/hackenverse
Stay in the loop with everything on Hackenverse! Get the latest from Hacken, stay tuned for upcoming events, meet our esteemed clients & partners, and keep up with the latest $HAI updates – all right here in one spot!
Created
Between 1 January 2017 and 31 January 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated.
9 measurements spanning 6 days, net -99. 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 18,955–19,084 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 06:13
18,970
-21
11 Aug 2026, 07:45
18,991
-18
10 Aug 2026, 04:11
19,009
-11
9 Aug 2026, 04:11
19,020
-6
8 Aug 2026, 05:49
19,026
-24
7 Aug 2026, 04:37
19,050
-14
6 Aug 2026, 05:10
19,064
-5
6 Aug 2026, 02:15
19,069
no change
5 Aug 2026, 22:00
19,069
first reading
Engagement
26 posts held, back to 20 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 17 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
3.08%
avg views ÷ 18,970 subscribers
Avg views / post
584
26 posts measured
Reaction rate
1.35%
reactions ÷ views · ER floor
Posts in window
26
of 26 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 12 August 2026
Posts held
26 (20 July 2026 – 12 August 2026)
Views total
15,196
Reactions total
205
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 23:59 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
≈1,190
Videos
≈44
Links
≈1,800
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
196 reactions across 25 posts, in 4 distinct kinds. The most used accounts for 47.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
93
47.4%
🔥
84
42.9%
👍
17
8.67%
👏
2
1.02%
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 26 of the 26 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 205reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 20 July 2026 to 12 August 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.
The 7-day HODL is done. Lucky HAI starts tomorrow🍀
Keep at least 10,000 qualifying $HAI on MEXC for 14 more days to enter the draw.
20 winners get 10,000 $HAI each. Every eligible holder gets one equal draw entry.
Starting Aug 13 until Aug 27.
Register by August 13: https://forms.gle/ZUi5G6Z1FBq5NsR27
Not financial advice ⚠️
6 days just flew by, with just 24 hours left.
HAI Power-Up is entering the final HOLD stretch.
Keep your qualifying $HAI balance in your MEXC Spot Wallet until the end. A reduced balance could affect eligibility.
Click a 🔥 emoji if you are still holding.
JUST IN🚨: HAI holders are getting access to TastyCo at early-backer conditions.
See the banner for full allocation details.
The participation window is 14 days and may be extended if needed.
Review the full terms before joining
https://tastyco.io/en/token
Not financial advice⚠️
Before the HAI × TastyCo Round opens, do the part hype usually skips: DYOR.
Our DYOR Community broke down TastyCo, $TASTY, tokenomics, vesting, the team, operating model, dependencies, and risks.
Read the sources and make your own call.
DYOR REPORT➡️https://assets.hacken.io/assets/dyor-report-tastyco.pdf
What food brands do you know that aren’t public yet and have a ticker, market cap, or a liquid market?
TastyCo wants to change that.
They are building an on-chain exchange for tokenized food brands, connecting real sales and operating businesses with public markets.
Existing brands can tokenize, while new concepts can launch via an operator network that covers kitchens, menus, delivery, and more.
For founders, Ta…
HAI × TastyCo Round
A limited opportunity is taking shape for the HAI community.
For the first time, HAI will be the entry asset in a Hacken Round, opening access to TastyCo.
The exact access stage and Round terms are now being finalized.
Follow HackenAI and TastyCo
Full details are coming next.
At the AMA, we made HAI’s direction clear: ownership.
Yesterday, we said ownership and utility do not have to be a forced choice.
And you can participate in both of them
The next HAI Round will open access to TastyCo, and this time, HAI will be the entry asset.
HAI Rounds x TastyCo Round details coming soon
⚡️ HAI POWER-UP: Deposit Closed
The deposit and registration window is officially closed.
Together, the community reached the 20M HAI Power Level, unlocking a final reward pool of 2M HAI.
Reward pool allocation:
⚡️ Deposit and Hold Pool — 1,500,000 HAI
⚡️ Existing Holder Loyalty Pool — 200,000 HAI
⚡️ Lucky HAI Pool — 200,000 HAI
⚡️ Social Mining — 100,000 HAI
The mandatory 7-day HODL period now begins.
Keep your qu…
Final 24 Hours⚡️
The HAI Power-Up deposit and registration window closes on 5 August.
The community has already reached 15M HAI deposited, unlocking a 1.5M HAI reward pool. One final day remains to move toward the 20M HAI Maximum Power Level and unlock up to 2M HAI in rewards.
Important campaign update:
The previously announced 35-day HODL period has been replaced by one final seven-day HODL period.
Keep your qual…
Ownership or utility?
For a moment, it looks like a difficult choice, but it isn’t.
Follow both paths or wait until you see all the details.
Your HAI. Your decision.
Today’s AMA was held in text format and is now available in the chat, so you can return to every answer at any time.
Beginning of the AMA: https://t.me/hackenclub/535648
If you remember only three things, make them these:
- HAI’s long-term direction is ownership.
- Utility still has a future, but it belongs inside the product that uses it.
- This week, HAI holders will see how HAI can open the door to a separate opp…
Hacken turns 9 today 🎂
From a cybersecurity startup in 2017 to a company building trust infrastructure for Web3.
Join our anniversary AMA with Hacken CEO Dyma Budorin today at 17:00 UTC. We’ll look back, talk $HAI, and open the floor to the community.
🗓 Monday, 17:00 UTC, 3 Aug
📍Telegram chat: https://t.me/hackenclub
❓Submit your question: https://forms.gle/9hDYddBGaFQsRYCM9
❤6👍1
Showing the 12 most recent of 26 posts we hold for @hackenai. 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 — 189,071 of 1,160,990entries 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.
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 9 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.
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.
Handles this channel named that no longer answer
Dead references
2
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
2
vacant every time we have ever looked
@hackenai named 2 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.
@godoyltk named in 3 posts, 8 August 2026 – 12 August 2026
@softdynamism named in 3 posts, 8 August 2026 – 12 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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“Hacken Club (HAI) Official Announcements Channel” (@hackenai), 18,970 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/hackenai.
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.