🎯 今日行情预判分析 【0628】 周末市场热度降低了许多,今天的行情以震荡爬升为主 目前 $BTC 的短期支撑位在 $60000 点附近 若向上📈:上方的阻力位依次是 60500 - 60800 - 61200 止损点位在 60000点附近,DYOR(非投资建议)

Channel
XUN Alpha 🐳
@XUNAlpha
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,379subscribers
-71 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002198559401 |
|---|---|
| Type | Channel |
| Username | @XUNAlpha |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/XUNAlpha |
Topic
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 00:22 | 1,379 | -6 |
| 5 Oct 2026, 01:17 | 1,385 | -10 |
| 26 Sept 2026, 11:20 | 1,395 | -9 |
| 17 Sept 2026, 10:18 | 1,404 | -3 |
| 13 Sept 2026, 03:01 | 1,407 | -1 |
| 9 Sept 2026, 03:41 | 1,408 | -7 |
| 3 Sept 2026, 11:40 | 1,415 | -7 |
| 30 Aug 2026, 19:59 | 1,422 | -3 |
| 28 Aug 2026, 06:34 | 1,425 | -4 |
| 24 Aug 2026, 23:23 | 1,429 | -6 |
| 21 Aug 2026, 08:12 | 1,435 | -3 |
| 18 Aug 2026, 08:14 | 1,438 | -4 |
| 14 Aug 2026, 23:15 | 1,442 | -2 |
| 11 Aug 2026, 06:11 | 1,444 | -6 |
| 7 Aug 2026, 22:02 | 1,450 | no change |
| 7 Aug 2026, 14:08 | 1,450 | first reading |
Engagement
19 posts held, back to 24 January 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 28 June 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
9 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 77.8% | |
| 👌 | 1 | 11.1% | |
| 👍 | 1 | 11.1% |
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 10 of the 19 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 24 January 2025 to 28 June 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
建立了一个 X 交易群组(限时)📈 一起交流交易心得 😎 ✅ https://x.com/i/chat/group_join/g1667007835736260608/9k0Zzb0H1G
今日利润来的还挺快的,继续干他! 近期盘面波动大,利润空间和机会也多,得把握住了!
每日大赛 【第十一期】 你发币名,我来分析! 📈 Daily Token Contest [Round 11] Name a token, and I’ll analyze it! ✅ https://x.com/BTCXUN/status/2070318987192537205?s=20
近期会重启这个频道和社区, 覆盖 港股/美股/加密 ,并且会给大家对接各平台福利 主要以分享自己的投资经验和交易心得为主 https://t.me/XUN_Alpha 最后祝大家在2026年都能暴富!
由海外社区主导的CTO $ore 老币新拉非常火热! oreoU2P8bN6jkk3jbaiVxYnG1dCXcYxwhwyK9jSybcp 从 10.16 日就开始拉盘, $10 到目前 $294 接近30x ,大家可以接近下这个 CTO TEAM. ✅ https://x.com/BTCXUN/status/1986690658862833866
Quick Trade Now: 🔥Symbol: ORE 🪙Name: ORE 💦LP: 450.5K 🏦MC:78.4M CA: oreoU2P8bN6jkk3jbaiVxYnG1dCXcYxwhwyK9jSybcp —————————————————————————————
THX $BDXN ✅️ https://x.com/btcxun/status/1986072310277865539
买了点这个 $XNIU,目前市值在 37万 左右 @star_okx 回复 NIU 概念 (牛🐮) X Layer NIU ( $XNIU )| @XLayerOfficial ✅️可以埋伏一下,目前还是低估区,洗盘ing! CA: 0xf6962b6ba932afada38197dc1f0e44f103632f2d https://x.com/BTCXUN/status/1969580873839493573
❤2
🚨 他们在美国内部引发了一场“真正的内战”! 收到了一份来自内部人士的情报,这些信息非常危险。 推文可能会被限制,但我还是决定公布—— 🧵 一切都从 Elon Musk 和特朗普的联盟开始 👇 ✅️ https://x.com/BTCXUN/status/1930820527020740922
❤1
⭐ 我一般很少互关只产出内容,今天也跟个风 如果你也对 Crypto 和交易感兴趣! 留言互关,希望可以向大家多多学习! ✅️ 点击留言互关 🔥
❤2
🚨 这可能是一场堪比 LUNA 崩盘级别的灾难事件🚨 🛫 超过 60亿美元 的资金在短短 30分钟内 从加密市场抽离。 🛫 下面将详细回https://x.com/BTCXUN/status/1911755106749493653/photo/1顾一下 $OM 的这场风暴 🧵 以及投资者们曾忽视的那些危险信号 👇 ✅️ https://x.com/BTCXUN/status/1911755106749493653
Showing the 12 most recent of 19 posts we hold for @XUNAlpha. 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
Names
Channels on the register whose handles appear in this channel's posts.
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
- 3
- 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
- 3
- vacant every time we have ever looked
@XUNAlpha named 3 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.
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 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 October 2026 — this entry's latest reading, not the date you are reading this.
“XUN Alpha 🐳” (@XUNAlpha), 1,379 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/XUNAlpha.
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.