Telegram RegisterThe public register of Telegram
Telegram profile photo for PlanX DEX-Announcement

Channel

PlanX DEX-Announcement

@PlanX_info

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

56,396subscribers

-2,813 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002186392459
TypeChannel
Username@PlanX_info
DescriptionEmpowering the next era of decentralized trading, where AI trades with precision, and humans own the outcome. PlanX unites AI-driven strategies, non-custodial vaults and on-chain execution—building the autonomous trading layer for the entire DeFi economy.
Created16 July 2024 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live29 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 29 September 2026
On Telegramt.me/PlanX_info

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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

56,39659,20957,802.57 August 2026 — 59,209 subscribers7 August 2026 — 59,209 subscribers8 August 2026 — 59,147 subscribers10 August 2026 — 59,089 subscribers11 August 2026 — 59,024 subscribers12 August 2026 — 58,986 subscribers13 August 2026 — 58,958 subscribers14 August 2026 — 58,921 subscribers15 August 2026 — 58,886 subscribers17 August 2026 — 58,794 subscribers18 August 2026 — 58,744 subscribers19 August 2026 — 58,696 subscribers20 August 2026 — 58,671 subscribers21 August 2026 — 58,665 subscribers23 August 2026 — 58,582 subscribers24 August 2026 — 58,498 subscribers25 August 2026 — 58,456 subscribers26 August 2026 — 58,418 subscribers28 August 2026 — 58,380 subscribers28 August 2026 — 58,343 subscribers29 August 2026 — 58,288 subscribers31 August 2026 — 58,248 subscribers1 September 2026 — 58,215 subscribers2 September 2026 — 58,149 subscribers3 September 2026 — 58,100 subscribers4 September 2026 — 58,025 subscribers7 September 2026 — 57,888 subscribers10 September 2026 — 57,772 subscribers12 September 2026 — 57,716 subscribers14 September 2026 — 57,646 subscribers16 September 2026 — 57,456 subscribers18 September 2026 — 57,281 subscribers29 September 2026 — 56,396 subscribers7 August 202629 September 2026
33 measurements spanning 53 days, net -2,813. 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 55,974–59,631 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
29 Sept 2026, 17:0056,396-885
18 Sept 2026, 03:5857,281-175
16 Sept 2026, 00:1757,456-190
14 Sept 2026, 06:1757,646-70
12 Sept 2026, 11:4257,716-56
10 Sept 2026, 09:5857,772-116
7 Sept 2026, 06:5457,888-137
4 Sept 2026, 16:3758,025-75
3 Sept 2026, 01:5458,100-49
2 Sept 2026, 03:1558,149-66
1 Sept 2026, 03:1858,215-33
31 Aug 2026, 01:5558,248-40
29 Aug 2026, 22:2558,288-55
28 Aug 2026, 22:3458,343-37
28 Aug 2026, 00:0358,380-38
26 Aug 2026, 21:1858,418-38
25 Aug 2026, 22:5958,456-42
24 Aug 2026, 20:2958,498-84
23 Aug 2026, 03:1458,582-83
21 Aug 2026, 14:1758,665first reading

Engagement

106 posts held, back to 16 July 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 117 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.101%
avg views ÷ 56,396 subscribers
Avg views / post
56.8
88 posts measured
Reaction rate
1.21%
reactions ÷ views · ER floor
Posts in window
88
of 106 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. It is computed over the 6 of 88 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 October 2026
Posts held106 (16 July 2024 – 3 October 2026)
Views total4,996
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Oct 2026, 17:25 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
7
Videos
2
Links
90

Lifetime counters from Telegram’s own channel header, read 3 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
2m 02s
Average length
1m 01s

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

28 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1450.0%
❤‍🔥414.3%
🔥414.3%
👏27.14%
😁27.14%
👍13.57%
👎13.57%

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 106 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 106 most recent posts we hold, published 16 July 2024 to 3 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.

Recent posts

3 Oct 2026, 16:07 UTC10 viewsread 3 October 2026

🐋 链上巨鲸活动|HYPE 交易时间:2026年10月3日21:04:52(北京时间) 链上记录 HyperEVM浏览器确认,未知地址0xea4e…4709a通过Kinetiq完成一笔大额质押赎回:约377,484.29枚kHYPE销毁,对应收到387,005.74976枚HYPE。交易成功,调用为batchConfirmWithdrawals。Whale Alert在监测时估值约3,415万美元;TechFlow摘要美元金额存在约十倍偏差,本条采用原始监测口径。 市场背景 这不是Kinetiq团队向外转移自有资金的证据,而是用户赎回质押资产。接收者身份未知,也未确认其将资产转入交易所或卖出。估值不是成交收入。 PlanX 判断 这笔操作将质押凭证转换为可用HYPE,增加该钱包直接可支配的代币,但不代表全市场供应新增。后续可能重新质押、持有或交易,当前不能认定为抛售。 ──────── ENGLISH ──────── …

3 Oct 2026, 08:07 UTC29 viewsread 3 October 2026

🐋 链上巨鲸活动|BTC 披露时间:2026年10月3日11:19(北京时间) 统计截至:2026年10月2日 链上记录 Bitdeer官方周度更新披露:挖矿产出292.3 BTC,出售292.3 BTC,净新增0 BTC;自有BTC持仓为0,不包含客户存款。本条依据矿企官方经营披露,而非逐笔链上交易核验;未披露成交价格、交易哈希或买方。 市场背景 这是一周矿产与出售的汇总,不是单笔卖单,也不是将此前储备一次性清仓。零持仓口径只指自有BTC,不能延伸为客户资产为零。 PlanX 判断 本期出售量与挖矿产出相等,表明该期新增矿产未留存在自有BTC储备中。但缺少具体执行时间与市场承接数据,不能据此认定其导致币价下跌,亦不能推断未来出售政策。 ──────── ENGLISH ──────── 🐋 Onchain Whale Activity | BTC Disclosure: October 2, 2026, 23:19 E…

3 Oct 2026, 07:08 UTC22 viewsread 3 October 2026

🐋 链上巨鲸活动|ENA 交易时间:2026年10月3日03:42–04:09(北京时间) 链上记录 地址0xa554…E4D1在超过12个月未见ENA转账后,先测试转出0.303枚,再转出约29,999,999.70枚ENA,合计约3,000万枚。Lookonchain报道估值约698万美元;以太坊浏览器确认转出数量与时间,前次ENA收币记录为2025年9月10日。 市场背景 Lookonchain将路径描述为经BitGo充值Binance;本次未独立确认中转及最终交易所归属。地址所有者未知,符合的是休眠地址重新活动门槛,而非已确认机构身份。美元金额为监测时估值,不是卖出成交额。 PlanX 判断 长期静置代币重新流转值得关注,但转账不等于卖出。即使交易所标签准确,也可能用于托管或其他安排;不能仅凭充值推断抛售及价格影响。 ──────── ENGLISH ──────── 🐋 Onchain Whale Activi…

3 Oct 2026, 02:10 UTC24 viewsread 3 October 2026

🐋 链上巨鲸活动|ZRO 交易时间:2026年10月3日01:40–01:42(北京时间) 链上记录 两个以太坊地址分别转出5,000,001枚和2,999,999枚ZRO至同一接收地址,合计800万枚。据余烬监测,报道时估值约1,498万美元。浏览器记录显示,两地址此前曾从同一个多签地址收币,支持将这两笔转账作为关联事件观察,但不能据此确认最终所有者。 市场背景 余烬将历史来源描述为LayerZero战略合作伙伴多签,并将本次去向标为Coinbase Prime。这两项身份标签本次未独立确认;已核对的是ZRO合约、转账数量、方向及时间。美元金额是监测时估值,不是成交额。 PlanX 判断 若交易所归属准确,资金进入机构交易或托管渠道值得关注,但充值不等于卖出,也不能据此认定合作伙伴正在减仓。没有成交证据,不推断价格影响。 ──────── ENGLISH ──────── 🐋 Onchain Whale Activit…

3 Oct 2026, 02:03 UTC19 viewsread 3 October 2026

🐋 链上巨鲸活动|ETH 交易时间:2026年10月3日05:06:23(北京时间) 链上记录 以太坊地址0x102B…2e383向0x8853…9eE8b转出6,595.2 ETH,交易成功。据Ai姨监测,接收方为Coinbase充值地址,报道估值约1,757万美元。浏览器证实转账数量与时间,但本次未独立确认接收方的Coinbase归属;美元金额为监测时估值,并非成交额。 市场背景 未知地址的该笔转账超过1,000万美元门槛。交易所充值标签来自监测方,链上转账本身不能证明卖出或亏损已经实现。 PlanX 判断 若充值归属准确,这笔资金可能增加交易所可用ETH,但也可能用于托管、抵押或其他用途。没有成交证据,不能将其认定为抛售,更不能归因为价格下跌原因。 ──────── ENGLISH ──────── 🐋 Onchain Whale Activity | ETH Transaction: October 2, 202…

3 Oct 2026, 02:03 UTC19 viewsread 3 October 2026

🐋 链上巨鲸活动|NEAR Intents 资金追回更新 披露时间:2026年10月2日23:52(北京时间) 链上记录 NEAR Intents 总经理 Alex Shevchenko 披露,此前被盗的约380万美元已全额退还,团队停止调查。本次为项目负责人披露;尚未独立逐笔核验退款交易、币种和接收地址,不将其写成已完成链上审计。 市场背景 这是此前已发安全事件的实质更新:资金状态由被盗转为据官方披露已追回,不是新的380万美元损失,也不是NEAR代币买入。 PlanX 判断 资金追回降低了该事件的直接资金缺口,但不等于漏洞风险已全面消除或用户补偿已结清;仍需关注后续技术复盘与结算披露。不能据此推断代币价格方向。 ──────── ENGLISH ──────── 🐋 Onchain Whale Activity | NEAR Intents recovery update Disclosure: October 2,…

2 Oct 2026, 11:08 UTC42 views1 reactionsread 3 October 2026

🐋 链上巨鲸活动|SOL 披露跟踪:2026年10月2日(北京时间) 链上记录 据Forward Industries官方投资者页面,截至9月30日,其SOL财库持有8,501,298枚SOL及等价资产,披露增加948,601枚。按公司披露的期末SOL价格118.06美元计算,增量对应约1.12亿美元;这是期末估值换算,不是买入花费。数据为初步、未经审计。 市场背景 这是季度财库变化披露,不是今天的一笔链上买入;SOL等价资产不应全部视为可立即流通的现货。本文未独立核验逐笔成交和钱包交易。 PlanX判断 机构财库规模扩大值得关注,但不能把整个季度的增量当作当前新增买盘,也不能据此判断短期价格方向。 ──────── ENGLISH ──────── 🐋 Whale & Onchain Activity|SOL Disclosure watch: October 2, 2026 (EDT) Onchain record…

👍1

2 Oct 2026, 02:31 UTC53 viewsread 3 October 2026

🐋 链上巨鲸活动|NEAR 核验时间:2026年10月2日 10:31(北京时间) 链上记录 据 Bitwise CEO Hunter Horsley 官方披露,Bitwise NEAR ETF(NRR)上市第三日录得约900万美元资金流入。这里记录的是基金层面的资金流数据,并非一笔已核验的链上 NEAR 买入;原帖未提供钱包、交易哈希或对应代币数量。 市场背景 这笔资金流与此前 NEAR Intents 安全事件属于不同事件,不能用 ETF 流入证明安全事件已解决,也不能将其直接等同于即时现货买盘。 PlanX 判断 新基金仍有资金进入,值得跟踪后续连续性。但单日流入不足以确认趋势,实际 NEAR 持仓变化及申赎结算仍需进一步披露。 ──────── ENGLISH ──────── 🐋 Whale & Onchain Activity|NEAR Verified: October 1, 2026, 10:31 PM …

1 Oct 2026, 14:07 UTC61 viewsread 3 October 2026

🐋 链上巨鲸活动|NEAR Intents 安全事件 核验时间:2026年10月1日 22:07(北京时间) 链上记录 NEAR Intents 官方确认发生安全事件,初步估计损失约380万美元,原因涉及 Omni 充提基础设施与智能合约交互缺陷。此为协议披露的损失估计,不代表380万美元的 NEAR 代币被出售。 据 ZachXBT 追踪,BSC 热钱包出现异常流出,相关资金转入 KuCoin 并桥接至比特币网络;其公布涉案地址为 0x09fd1f5d9f185067a92493e43aa259ea4ab3ad37。该路径为调查员归因,本次未独立逐笔核验,不作已确认完整资金路线表述。 市场背景 官方称合约侧漏洞已修复,承诺全额补偿;核心服务预计一小时内恢复,BSC、Polygon、TON等链充提预计额外暂停约12小时。这些是公告中的预计时程及承诺,不等于已经恢复或完成赔付。 PlanX 判断 当前可确认的是协议承认损失…

1 Oct 2026, 06:07 UTC53 viewsread 3 October 2026

🐋 链上巨鲸活动|ETH 记录时间:2026年10月1日 11:30–11:33(北京时间) 链上记录 地址 0xE1Ad…c1691 从 Etherscan 标记为 Binance 14 的地址收到4,999.99992 ETH,约三分钟后向 Aave V3 存入5,000 ETH,并收到对应 aWETH 凭证。两笔均已成功。按 TechFlow 引述 Ai 姨的估值,规模约1,343万美元;这是代币估值,不是已核实的买入成本。 市场背景 报道将此描述为再次建仓;链上能直接确认的是交易所转出及随后进入借贷协议,无法单独证明交易所内的买入价格或成交时间。地址实际所有者尚未确认。 PlanX 判断 这批 ETH 从交易所地址转向 DeFi 存款,值得跟踪后续是否借款或再转移。Aave 存款不等于以太坊验证者质押,也不能据此断言长期看多。两笔是同一批资产的连续动作,不应相加成1万 ETH 的新增资金流。 来源 https:/…

1 Oct 2026, 01:51 UTC44 viewsread 3 October 2026

🐋 链上巨鲸活动|HYPE 核验时间:2026年10月1日 09:55(北京时间) 链上记录 Hyperliquid 官方接口确认:地址 0x43e9…8a251 于9月30日23:38:57(北京时间)发起375万枚 HYPE 质押赎回,状态为 initiated,并非已到账。余烬将该地址标记为 HyperLabs,按其报道估值约3.375亿美元;身份标签及美元估值来自监测方,不是成交金额。 市场背景 此前 TechFlow 报道团队计划解除相同数量的质押。本次可核验记录补上了执行申请证据,但不代表代币已转入交易平台,也不代表场外出售已结算。 PlanX 判断 重点是大额质押资产进入提取流程,而非即时卖压。余烬预计七天后提取,并根据历史路径推测后续或流向 Flowdesk;这仍是预期,不能视为本次已发生的去向或卖出。 来源 https://www.techflowpost.com/newsletter/138484 h…

30 Sept 2026, 13:08 UTC48 viewsread 3 October 2026

🐋 链上巨鲸活动|BTC 快讯时间:2026 年 9 月 30 日 21:06(北京时间) 链上记录 / 机构披露 PowerCompute 今日公告:Arch 于 9 月 24 日约定重置日,出售其抵押 BTC 中约 267.3 枚,用于结清约 2,245 万美元本金、利息及费用;约 39.6 BTC 返还公司。公司明确表示并非追加保证金或强制平仓,现已无 BTC 被抵押。 本条依据公司官方披露,未获得交易哈希及精确成交时间;属于今日披露的历史结算,不是今日新卖出。 市场背景 公司表示不再追求杠杆 BTC 财库策略,未来将 BTC 用作设备采购和运营资金,而非通过借贷持续囤币。 PlanX 判断 这反映单家矿企从抵押融资转向偿债与经营投入,不能外推为整个机构群体转空。相关卖出已在此前完成,不应当作今天新增的抛压;未来用途是公司计划,不是已经发生的资金流。 来源 公司公告:https://www.power-comput…

Showing the 12 most recent of 106 posts we hold for @PlanX_info. 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.

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 29 September 2026 — this entry's latest reading, not the date you are reading this.

“PlanX DEX-Announcement” (@PlanX_info), 56,396 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/PlanX_info.

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.