12 Aug 2026, 09:12 UTC89 viewsread 12 August 2026
新版本暂停打包，订阅加密那里有问题，待我彻底修复。
Channel
Apex顶点客户端频道
@jichangbiji
On this record: Growth · Engagement · Posts · Citations · Cite this entry
521subscribers
-20 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001355271820 |
|---|---|
| Type | Channel |
| Username | @jichangbiji |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/jichangbiji |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 15:18 | 521 | -2 |
| 9 Sept 2026, 22:36 | 523 | -1 |
| 1 Sept 2026, 06:46 | 524 | -10 |
| 26 Aug 2026, 03:28 | 534 | -3 |
| 20 Aug 2026, 03:41 | 537 | -3 |
| 13 Aug 2026, 15:47 | 540 | -1 |
| 12 Aug 2026, 23:00 | 541 | no change |
| 12 Aug 2026, 22:46 | 541 | first reading |
Engagement
20 posts held, back to 3 June 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 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 20 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
11 Aug 2026, 15:49 UTC293 viewsread 12 August 2026
v4.0.0重构版本震撼发布，打包机器人打包体验极致的内核性能 @Apex_build_bot
11 Aug 2026, 14:53 UTC158 viewsread 12 August 2026
打包机器人0点准时上架新版客户端，mihomo内核全新构建脱离flclash，吊打同行的客户端。没有人比我更懂客户端！
10 Aug 2026, 02:20 UTC235 viewsread 12 August 2026
Photo
客户端已彻底脱离flclash独立构建，新UI即将完成，随后会下发打包机器人。
9 Aug 2026, 06:15 UTC293 viewsread 12 August 2026
6端客户端源码出售，适合自己二开封端。
9 Aug 2026, 01:31 UTC299 viewsread 12 August 2026
客户端源码已经重构完毕，基于最新mihomo内核脱离flclash
5 Aug 2026, 14:02 UTC492 views0 reactionsread 12 August 2026
Apex客户端源码冗余，将进行彻底脱离flclash完全重构，购买过源码的老板我会在重构完发放。
4 Aug 2026, 08:22 UTC526 viewsread 12 August 2026
客户端3.7.9版本发布，修复软路由BUG
15 Jul 2026, 06:27 UTC≈1,260 viewsread 12 August 2026
AWS独享转发带面板，被墙自动换ip，一个月200U，无流量限制！
13 Jul 2026, 15:25 UTC≈1,220 viewsread 12 August 2026
apex 3.7.7版本发布，修复用户反馈上来的bug，设置导出日志新增更广泛的收集bug信息。
24 Jun 2026, 14:05 UTC≈1,650 viewsread 12 August 2026
v3.7.1 — bugfix 修复有未支付订单后再次下单偶发 "XBoardSDK is not initialized" 报错
19 Jun 2026, 14:10 UTC≈1,700 viewsread 12 August 2026
File
不是必须，按需使用。clash默认下发模板，每个套餐必须包含🇭🇰 香港, 🇯🇵 日本, 🇸🇬 新加坡, 🇨🇳 台湾, 🇺🇸 美国节点，否则订阅会出错，节点名称包含上述国家就行，国旗不是必须！
Showing the 12 most recent of 20 posts we hold for @jichangbiji. 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 1 registered channel — 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.
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.
“Apex顶点客户端频道” (@jichangbiji), 521 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/jichangbiji.
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.