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 9 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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
50 measurements spanning 82 days, net -5,997. 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 33,620–41,417 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)
Subscribers
Change
27 Oct 2026, 14:04
34,520
-33
26 Oct 2026, 14:20
34,553
-40
25 Oct 2026, 14:50
34,593
-24
24 Oct 2026, 17:27
34,617
-46
23 Oct 2026, 15:45
34,663
-88
22 Oct 2026, 12:35
34,751
-59
21 Oct 2026, 02:29
34,810
-64
20 Oct 2026, 01:27
34,874
-45
18 Oct 2026, 23:39
34,919
-43
17 Oct 2026, 22:06
34,962
-43
16 Oct 2026, 23:59
35,005
-25
16 Oct 2026, 00:28
35,030
-44
15 Oct 2026, 00:06
35,074
-56
13 Oct 2026, 18:36
35,130
-243
9 Oct 2026, 23:20
35,373
-312
5 Oct 2026, 19:15
35,685
-459
30 Sept 2026, 08:57
36,144
-595
18 Sept 2026, 04:36
36,739
-214
15 Sept 2026, 21:22
36,953
-160
14 Sept 2026, 06:00
37,113
first reading
Engagement
40 posts held, back to 23 June 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 152 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
5.94%
avg views ÷ 34,520 subscribers
Avg views / post
2,050
11 posts measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
11
of 40 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 20 October 2026
Posts held
40 (23 June 2026 – 20 October 2026)
Views total
22,550
Reactions total
249
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
28 Oct 2026, 01:29 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
37
Videos
1
Links
34
Lifetime counters from Telegram’s own channel header, read 28 October 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
40s
Average length
40s
Measured directly from 1 video 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
6,914 reactions across 37 posts, in 31 distinct kinds. The most used accounts for 47.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
3,307
47.8%
👍
1,050
15.2%
🔥
796
11.5%
🤣
279
4.04%
😁
232
3.36%
💩
225
3.25%
🖕
199
2.88%
👎
155
2.24%
💯
133
1.92%
👏
126
1.82%
❤🔥
98
1.42%
⚡
51
0.738%
🐳
44
0.636%
🙏
33
0.477%
🥰
33
0.477%
🆒
25
0.362%
🤡
24
0.347%
🥴
20
0.289%
🤯
16
0.231%
✍
15
0.217%
11 further kinds
53
0.767%
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 37 of the 40 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 6,914 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 23 June 2026 to 20 October 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.
🎥 MINING THE NIGHT — The Night in 40 Seconds | KBW 2026
Missed the night? Or want to relive it? ⛏️⚡️
Take a look back at MINING THE NIGHT, XPHERE’s KBW 2026 side event in Seoul. 🇰🇷
From live mining demos to great conversations with the Web3 community, here are some highlights from the night.
This event was another milestone in XPHERE’s journey. A huge thank you to everyone who joined us and made the night special…
🔥 1M+ XP Burned — And Counting.
Through XP Union Vault’s burn mechanism, XP is permanently removed from circulation.
Over 1,000,000 XP has already been burned, and the total continues to grow. ⛓️
Although the deposit cap has been reached, the burn goes on.
👇 Track the live burn count:
https://stake.x-phere.com/burn.html
https://x.com/Xphere_official/status/2109898384492593376
👀 XPHERE ecosystem just landed on GeckoTerminal.
Explore XPHERE ecosystem tokens and liquidity pools, and track onchain data and real-time market moves — all in one place.📊
Time to dive into the XPHERE ecosystem.⛓️
👇 Explore now
🔗 geckoterminal.com/xphere/pools
DYOR. Stay onchain.
https://x.com/Xphere_official/status/2109470213049889059
🇸🇬 TOKEN2049 Singapore is officially underway!
The XPHERE team has arrived in Singapore, and we’re excited to be here with builders, founders, investors, and the global Web3 community. 🌏
From our dual-chain Layer 1 to the ecosystem we’re building around it, we’re looking forward to sharing more about XPHERE, meeting new faces, and connecting with the people shaping the next chapter of Web3.
If you’re attending TOK…
🇸🇬 TOKEN2049 Singapore is happening this week!
XPHERE is heading to Singapore, and we’ll be there with our own booth. ⚡️
Come meet the XPHERE team, learn more about what we’re building, and pick up a little something we’ve prepared for you. 🎁
Web3 builders, founders, investors, and friends — we’d love to see you at our booth.
See you in Singapore.
#XPHERE #TOKEN2049 #TOKEN2049Singapore #Web3 #Crypto
🎉 Nansen × XPHERE Staking Campaign — Rewards Distributed!
The 247,000 XP reward pool has now been successfully distributed to all eligible participants of the Nansen × XPHERE Staking Campaign. 🎁
Rewards were sent directly to eligible staking wallets, and no manual claim was required.
Thank you to everyone who participated and staked XP through the Nansen Staking Hub.
We’re excited to continue working closely with…
⛏️ MINING THE NIGHT RECAP: — @HackenProof
HackenProof is a leading Web3 security platform, connecting projects with a global community of security researchers through bug bounties, security audits, and continuous security programs.
At MINING THE NIGHT in Seoul, the HackenProof team joined us on stage and shared their insights on Web3 security and building stronger, more secure ecosystems.
As XPHERE continues to gr…
⛏️ MINING THE NIGHT RECAP: — @nansen_ai
Nansen is one of XPHERE’s key ecosystem partners, and we were excited to have the Nansen team join us at MINING THE NIGHT in Seoul.
During the event, Nansen shared insights on how onchain data can help surface real signals beyond the noise, from staking to trading.
It was great to have one of our key partners not only join the event, but also take the stage and share their p…
⛏️ MINING THE NIGHT — Successfully Wrapped at KBW 2026
Real mining. Real builders. Real conversations.
Last night in Seoul, XPHERE brought together builders, miners, investors, and the wider Web3 community for KBW 2026. 🇰🇷
From the live ICERIVER XP0 mining demo to builders and ecosystem partners like XCROLL, Nansen, and HackenProof coming together, the night was filled with ideas, connections, and conversations ab…
Foundation Token Movement Notice
On September 30th (UTC), 14,000 XP will be transferred from the Foundation wallet to support upcoming marketing campaigns and community growth initiatives.
This amount is part of the Foundation’s pre-allocated marketing budget and does not represent additional token issuance or dilution.
All token movements remain fully transparent and verifiable on-chain.
Transaction Hash: To be …
🎙️ XPHERE 2.0: From Fast Finality to Real Usage
📅 Tuesday, September 29
⏰ 08:00 AM UTC
🎙️ Hosts: LBank_Exchange & xmuha0
🎤 Guest: @xkritesh XPHERE Co-Founder
🎁 164,800 $XP will be shared with the community!
Complete these 4 steps to participate:
⭐ Follow @LBank_Exchange & @Xphere_official
⭐ Like, repost & tag 3 friends
⭐ Set a reminder for the Space: https://twitter.com/i/spaces/1oJMvNjqBklxQ
⭐ Submit the form:ht…
Additional 35M XP — FULLY FILLED in record time. 🔥
Vault now at 100% of its 70M XP cap.
From here, 40%+ of daily validator rewards burn forever.
- Real validator revenue, not emissions
- Up to 60% to stakers
🌐 https://stake.x-phere.com/
Thank you! 🚀
https://x.com/Xphere_official/status/2102961642703339855
🔥20❤12👏7😁6🥰1
Showing the 12 most recent of 40 posts we hold for @Xphere_official. 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.
Posts edited after publishing
@Xphere_official edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
14 August 2026
Most recent edit
14 August 2026
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 6 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
6
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
6
vacant every time we have ever looked
@Xphere_official named 6 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.
@nansen_ai named in 7 posts, 6 October 2026 – 27 October 2026
@xcroll_official named in 7 posts, 8 August 2026 – 16 August 2026
@cicada_mm named in 5 posts, 8 August 2026 – 13 August 2026
@pixie_pocket_ named in 4 posts, 8 August 2026 – 15 August 2026
@lbank_exchange named in 1 post, 30 September 2026 – 30 September 2026
@xkritesh named in 1 post, 30 September 2026 – 30 September 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 27 October 2026 — this
entry's latest reading, not the date you are reading this.
“XPHERE” (@Xphere_official), 34,520 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/Xphere_official.
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.