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 91% 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
34 measurements spanning 41 days, net -754. 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,444–19,424 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)
Subscribers
Change
17 Sept 2026, 10:18
18,557
-26
15 Sept 2026, 07:18
18,583
-19
13 Sept 2026, 14:42
18,602
-27
11 Sept 2026, 21:38
18,629
-32
9 Sept 2026, 08:37
18,661
-58
5 Sept 2026, 22:18
18,719
-44
3 Sept 2026, 17:40
18,763
-13
2 Sept 2026, 10:38
18,776
-25
1 Sept 2026, 08:52
18,801
-15
31 Aug 2026, 10:38
18,816
-25
30 Aug 2026, 09:03
18,841
-10
29 Aug 2026, 10:18
18,851
-20
28 Aug 2026, 09:26
18,871
-17
27 Aug 2026, 08:47
18,888
-15
26 Aug 2026, 06:22
18,903
-8
25 Aug 2026, 09:02
18,911
-15
24 Aug 2026, 10:16
18,926
-27
22 Aug 2026, 20:18
18,953
-21
21 Aug 2026, 13:28
18,974
-29
20 Aug 2026, 12:36
19,003
first reading
Engagement
26 posts held, back to 14 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 55 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
2.39%
avg views ÷ 18,557 subscribers
Avg views / post
443
1 post measured
Reaction rate
2.71%
reactions ÷ views · ER floor
Posts in window
1
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 25 August 2026
Posts held
26 (14 August 2025 – 25 August 2026)
Views total
443
Reactions total
12
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 02:11 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
Video runtime
1m 59s
Average length
1m 00s
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
592 reactions across 22 posts, in 12 distinct kinds. The most used accounts for 38.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
230
38.9%
❤
222
37.5%
🤯
33
5.57%
👀
24
4.05%
👏
24
4.05%
🎉
20
3.38%
🥰
15
2.53%
👍
11
1.86%
💯
7
1.18%
👌
4
0.676%
😍
1
0.169%
🙏
1
0.169%
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 22 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 592 reactions 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 14 August 2025 to 25 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.
WE’RE LIVE!
The Encrypted Markets Roadmap AMA is happening right now
You’ve seen the vision ~ now come hear what’s next for Nillion, encrypted markets, and the roadmap ahead
Join the livestream:
https://x.com/nillion/status/2092245209736188267?s=20
Come hang out, listen in, and bring your questions!
Nillion Official Announcements pinned «$NIL spot trading is now live on UpBit! 업비트에서 $NIL 현물 거래가 시작되었습니다. https://x.com/nillion/status/2090710572207833326»
Nillion Official Announcements pinned «Nillion is building Encrypted Markets. Covenants are the primitive that makes them possible. They let users seal an instruction to a condition, post it onchain encrypted and have it unlock only when the condition is met. Today, we’re releasing the roadmap.…»
Nillion is building Encrypted Markets.
Covenants are the primitive that makes them possible.
They let users seal an instruction to a condition, post it onchain encrypted and have it unlock only when the condition is met.
Today, we’re releasing the roadmap.
https://x.com/nillion/status/2087569973837533597
THE FLOOR IS RISING
The latest numbers are in, and they tell a very clear story:
• +78% growth in the holder base
• 5,653 wallets now in the ecosystem
• 62% retention from the Q2 cohort
• 6.2x increase in daily transfer activity in just 3 months
More wallets joining.
More activity happening.
It’s more people choosing to STAY.
While much of the market has been focused on short-term narratives, the Nillion ecosyste…
Today the Nillion association will begin its structured buyback progfram with our market making partners at flowdesk.
The program is structured for long term recovery of the Nillion ecosystem and NIL token market liquidity.
Full disclosure on program here: https://x.com/nillion/status/2002022134147694677
The Nillion Twitter account has put out a statement about the incident that occured last week. You can find the full update here
Link: https://x.com/nillion/status/1994473962168819719
If you were surprised by yesterday's price action, you’re not alone.
Our entire team was confused until we realized what happened: a market maker sold NIL tokens without legal authorization from the Nillion Association. Then refusing to respond to any team communications during the flash sell and hours following.
This type of behavior unfortunately happens in crypto.
We are not going to just say “nice words of hop…
Regarding the $NIL price:
No team or treasury tokens have moved. To confirm this yourself, you can check on-chain:
https://
mintscan.io/nillion/address
We want to assure our users, community, and partners that all Nillion wallets remain fully secure. The network remains fully operational and will continue as usual without disruption.
We are investigating this external variable and will report findings shortly.
T…
$NIL now on Uniswap! 🦄
https://x.com/nillion/status/1990805297519300789
🔥20❤5👀2🥰2
Showing the 12 most recent of 26 posts we hold for @nillionofficialannouncements. 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.
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.
peaq @peaqnetwork · 42,721 Telegram ranks this channel #4 of 94 here — alongside 93 others — read 28 August 2026
Rivalz Network Announcement @RivalzAI_Ann · 48,895 Telegram ranks this channel #6 of 89 here — alongside 88 others — read 25 August 2026
VERONA Announcements @verona_announcements · 116,283 Telegram ranks this channel #6 of 92 here — alongside 91 others — read 14 August 2026
Allora Network Announcements @alloranetworkannouncements · 54,245 Telegram ranks this channel #9 of 93 here — alongside 92 others — read 23 August 2026
Quai Network Announcements @QuaiNetwork_Announcements · 22,154 Telegram ranks this channel #13 of 84 here — alongside 83 others — read 21 September 2026
Cookie DAO Announcements @cookiedaoannouncements · 59,712 Telegram ranks this channel #16 of 94 here — alongside 93 others — read 22 August 2026
Aethir Announcements @Aethir_Official · 132,461 Telegram ranks this channel #16 of 92 here — alongside 91 others — read 13 August 2026
Dill Announcement @dill_announcement · 57,900 Telegram ranks this channel #18 of 86 here — alongside 85 others — read 22 August 2026
Cultured @cultured_rwa · 67,044 Telegram ranks this channel #22 of 91 here — alongside 90 others — read 20 August 2026
The Data Foundation @datafdn · 57,613 Telegram ranks this channel #28 of 90 here — alongside 89 others — read 22 August 2026
StableJack Announcement @stablejack · 42,512 Telegram ranks this channel #29 of 87 here — alongside 86 others — read 28 August 2026
Galxe @galxe · 165,065 Telegram ranks this channel #31 of 95 here — alongside 94 others — read 14 August 2026
Hybrid | Announcements @HybridAnnouncements · 54,095 Telegram ranks this channel #32 of 88 here — alongside 87 others — read 23 August 2026
Prom @prom_ann · 22,342 Telegram ranks this channel #33 of 86 here — alongside 85 others — read 21 September 2026
Kontos Announcements by Zecrey Labs @ZecreyAnnouncement · 23,185 Telegram ranks this channel #33 of 86 here — alongside 85 others — read 19 September 2026
Slinky Announcements @slinkylayer_ann · 40,830 Telegram ranks this channel #34 of 86 here — alongside 85 others — read 29 August 2026
Allo VIP @allo_xyz · 77,560 Telegram ranks this channel #37 of 86 here — alongside 85 others — read 18 August 2026
Glacier News @glacier_news · 72,190 Telegram ranks this channel #40 of 92 here — alongside 91 others — read 19 August 2026
Monad Announcements @monad_xyz · 38,443 Telegram ranks this channel #41 of 89 here — alongside 88 others — read 31 August 2026
Artfi Official Announcements @artfi_announcement · 28,510 Telegram ranks this channel #42 of 82 here — alongside 81 others — read 9 September 2026
Assisterr @assisterr · 90,990 Telegram ranks this channel #46 of 89 here — alongside 88 others — read 16 August 2026
Blazpay Announcement @BlazpayAnnouncement · 28,432 Telegram ranks this channel #47 of 85 here — alongside 84 others — read 9 September 2026
Nubit Announcement | Bitcoin Thunderbolt @nubit_announcement · 45,691 Telegram ranks this channel #50 of 87 here — alongside 86 others — read 26 August 2026
Caldera 🌋 @calderaofficial · 68,731 Telegram ranks this channel #50 of 90 here — alongside 89 others — read 20 August 2026
This channel appears in 32 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Nillion Official Announcements” (@nillionofficialannouncements), 18,557 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/nillionofficialannouncements.
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.