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 11 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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
63 measurements spanning 96 days, net -965. 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 10,877–12,132 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)
Subscribers
Change
11 Nov 2026, 00:05
11,022
-8
9 Nov 2026, 11:18
11,030
-13
8 Nov 2026, 00:46
11,043
-7
6 Nov 2026, 19:47
11,050
-6
5 Nov 2026, 18:49
11,056
-11
4 Nov 2026, 15:16
11,067
-4
3 Nov 2026, 16:26
11,071
-10
2 Nov 2026, 13:59
11,081
-8
1 Nov 2026, 11:37
11,089
-9
31 Oct 2026, 08:28
11,098
-6
30 Oct 2026, 05:36
11,104
-6
29 Oct 2026, 09:01
11,110
-10
28 Oct 2026, 07:09
11,120
-14
27 Oct 2026, 04:16
11,134
-6
26 Oct 2026, 02:57
11,140
-4
25 Oct 2026, 01:21
11,144
-6
24 Oct 2026, 02:50
11,150
-7
23 Oct 2026, 06:07
11,157
-16
22 Oct 2026, 03:41
11,173
-12
21 Oct 2026, 00:28
11,185
first reading
Engagement
63 posts held, back to 1 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 65 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.05%
avg views ÷ 11,022 subscribers
Avg views / post
226
18 posts measured
Reaction rate
1.40%
reactions ÷ views · ER floor
Posts in window
21
of 63 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 9 November 2026
Posts held
63 (1 July 2026 – 9 November 2026)
Views total
4,067
Reactions total
57
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 21:46 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
≈956
Videos
≈221
Links
≈1,440
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Video runtime
6m 00s
Average length
36s
Measured directly from 10 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
295 reactions across 57 posts, in 8 distinct kinds. The most used accounts for 65.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
192
65.1%
🔥
32
10.8%
⚡
26
8.81%
❤🔥
20
6.78%
👍
18
6.10%
☃
3
1.02%
✍
3
1.02%
🤣
1
0.339%
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 57 of the 63 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 295 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 63 most recent posts we hold, published 1 July 2026 to 9 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: 2 of 21 posts held from the last 30 days (9.52%) 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).
Thank you to everyone who sent in a sticker for the Humanode Sticker Contest! Humanode team is reviewing every entry, and it’s been fun to see how each of you put your own spin on Humanode.
We’ll announce the winners in two days, on November 11. Keep an eye on Humanode's official announcement channels for the winners list.
Until then, a big thank you to everyone who took the time to draw, design, and share a sticke…
## HumanodeCon V is coming 🌐
Hey Human Nodes!
We’re back for round five and you’re invited.
This December, HumanodeCon returns online, bringing familiar faces and new humans together from across the globe.
Been with us for years? Come catch up. Following from the sidelines? Come meet the community. You’re part of this, too.
Let’s celebrate one human = one node = one vote and the people bringing it to life.
📅 De…
🚨 Last Call! Humanode Sticker Contest Ends Today!
We're loving the submissions so far, but there's still room for more! If you've been thinking about making a sticker, now's the time.
You've got until 24:00 UTC tonight to get yours in!
A quick reminder:
▸ 10 stickers. 10 winners.
▸ $200 in HMND prizes.
▸ Original Humanode-themed designs.
How to enter:
▸ Create your sticker.
▸ Post it on X with # Humanode # Humano…
Humanode Announcements pinned «Victor is live in ~10 mins at Devcon India.Talk: DAO Governance failures and ways of mitigation Victor dropping the real empirical record on why most DAOs get captured, drained, or just slowly die… and the three classes of mitigations that actually hold up…»
Victor is live in ~10 mins at Devcon India.Talk: DAO Governance failures and ways of mitigation
Victor dropping the real empirical record on why most DAOs get captured, drained, or just slowly die… and the three classes of mitigations that actually hold up (including identity-weighted systems).
If you’ve ever watched a treasury get voted away or sat through another “governance is hard” cope, this one’s for you.
Wa…
We've spent a lot of time talking about trust in technology. Maybe we should spend more time talking about how to verify it.
Humanode CVM explores how data processing can be made independently verifiable, giving users a way to check what's happening behind the scenes instead of relying on promises.
Don't trust. Verify.
More on how it works:
https://blog.humanode.io/humanode-cvm-for-verifiable-data-processing/
Humanode Sticker Contest: The Creativity Is Rolling In! 👨🎨
We've been checking out your submissions, and we're happy with what we're seeing so far. Some great ideas are already coming through, and we're looking forward to seeing what else the community comes up with!
There's still time to join Humanode Sticker Pack 2 and get your designs into the mix.
A quick reminder:
▸10 stickers. 10 winners.
▸$200 in HMND priz…
Dear Human nodes and friends,
The DEX and Bridges have been restored, and are operational again. The next step is the reimbursement of the wallets on the EVM.
More about the exploit, the fix, and the steps we have, and will be taking on the community call from 14:00 UTC.
Sincerely,
Humanode Core
Humanode incident update: security fixes and recovery
The incident has been contained, and all identified security issues have been fixed, including the EVM vulnerability and the unauthorized approval affecting the ChainPort vault. The full investigation continues.
We deployed the EVM fix on mainnet at 15:40:48 UTC on 28 October 2026. Verification confirmed that the exploited call paths are blocked.
We are sorry f…
Humanode Newsletter Vol. 124 is live!
This cycle, Vortex started showing what real governance looks like in practice:
🌀 Three projects in Formation, milestone votes, funding releases, and rejected proposals
🗳 Dev Log #21: a fairer way to calculate Active Governor status
🎮 A refreshed Vortex UI built to feel more like a grand-strategy console
💸 A new transaction-fee model
🎙 OpenServ on agent reliability and SERV…
❤3⚡1
Showing the 12 most recent of 63 posts we hold for @humanode. 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 2 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.
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.
Self Chain @selfchainxyz · 99,660 Telegram ranks this channel #53 of 91 here — alongside 90 others — read 14 August 2026
HAQQ Ecosystem @islamic_coin · 168,363 Telegram ranks this channel #58 of 79 here — alongside 78 others — read 8 September 2026
ZNS Connect Name Service @znsconnect · 43,140 Telegram ranks this channel #81 of 95 here — alongside 94 others — read 27 August 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.
“Humanode Announcements” (@humanode), 11,022 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/humanode.
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.