Channel
@QuanX_API
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
28,565subscribers
-55 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001172046742 |
|---|---|
| Type | Channel |
| Username | @QuanX_API |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/QuanX_API |
Technology — 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 97% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 17:21 | 28,565 | -3 |
| 6 Sept 2026, 09:14 | 28,568 | -4 |
| 4 Sept 2026, 00:16 | 28,572 | -2 |
| 2 Sept 2026, 16:39 | 28,574 | -7 |
| 1 Sept 2026, 12:34 | 28,581 | +42 |
| 31 Aug 2026, 12:46 | 28,539 | -3 |
| 30 Aug 2026, 11:22 | 28,542 | +1 |
| 29 Aug 2026, 13:54 | 28,541 | -5 |
| 28 Aug 2026, 12:34 | 28,546 | +3 |
| 27 Aug 2026, 11:46 | 28,543 | -3 |
| 26 Aug 2026, 13:56 | 28,546 | -4 |
| 25 Aug 2026, 14:27 | 28,550 | -4 |
| 24 Aug 2026, 14:24 | 28,554 | -10 |
| 22 Aug 2026, 22:28 | 28,564 | -4 |
| 21 Aug 2026, 15:28 | 28,568 | -4 |
| 19 Aug 2026, 15:17 | 28,572 | -9 |
| 18 Aug 2026, 15:02 | 28,581 | -3 |
| 17 Aug 2026, 11:58 | 28,584 | -10 |
| 16 Aug 2026, 03:53 | 28,594 | -5 |
| 14 Aug 2026, 16:36 | 28,599 | first reading |
20 posts held, back to 6 July 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 59 pages 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 17 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
#解析器 2025-05-17 • 新增参数 UA=1（供Quantumult X, TF 版本 921+有效） 添加此参数，将会尝试使用 Shadowrocket 的User-Agent重新获取一次订阅内容，以解决部份机场面板下发节点内容不同的问题。 ———————————— 如有 解析失败 /错误或其它问题，请找bot“有效反馈” @ShawnKOP_Parser_Bot
#解析器 2026-04-28 • 解析器参数可视化编辑、添加（Quantumult X, TF 版本 918+） ———————————— 如有 解析失败 /错误或其它问题，请找bot“有效反馈” @ShawnKOP_Parser_Bot
#解析器 2026-04-15 - 支持anytls 部分格式的解析 - 需要 Quantumult X 1.5.6 （914） TF 测试版本 ps. 如果你已经是TF版本且确定机场提供了vless或者anytls节点 但添加后无vless或者anytls节点， 大概率说明，机场面板识别客户端UA，没有给quanx下发对应节点， 请自行在订阅链接后添加 “&flag=shadowrocket” 或 “?flag=shadowrocket” ———————————— 如有 解析失败 /错误或其它问题，请找bot“有效反馈” @ShawnKOP_Parser_Bot
#解析器 2026-1-12 添加节点订阅并开启解析器时，如遇下列问题，请自行解决，无需反馈 1、Qauntumult X提示 403错误 - 与资源解析器无关，自行找机场解决 2、解析器提示「引用返回内容为空」，点击通知跳转到浏览器打开链接 - 如果里面为空，找机场解决 - 如果里面存在有效内容，说明链接识别客户端UA，订阅链接后添加 “&flag=shadowrocket” 或 “?flag=shadowrocket”后再添加 另外，本资源解析器对yaml格式的解析能力有限，请尽量使用其它格式。 如有 解析失败 /错误或其它问题，请找bot“有效反馈” @ShawnKOP_Parser_Bot
#解析器 2025-12-30 - 支持vless reality 部分URI格式的解析 如有 解析失败 /错误或其它问题，请找bot“有效反馈” @ShawnKOP_Parser_Bot
#解析器 2025-05-15 - 支持重写引用内的 rewrite&filter 混搭解析输出 【版本1.5.2 844+】 - 支持 ss2022 解析 【版本1.5.1+】 如有 解析失败 /错误或其它问题，请找bot“有效反馈” @Shawn_Parser_Bot
#解析器 2024-01-18 初步支持 vless. URI格式 解析 样本较少 ，如有 解析失败 /错误，请找bot“有效反馈” @Shawn_Parser_Bot ⚠️ Quantumult. X版本 1.5.0（821+） ONLY！！！
该机场✈️用户大爷们，如果你们实在不愿意按照图片提示，提供“订阅链接”，请不要1⃣️个接着1⃣️个接着1⃣️个接着1⃣️个接着1⃣️个接着1⃣️个接着1⃣️个来【反馈】了。 我真的没法根据图片算出问题的答案
这位，请记住，这才叫 “挂到频道” 刚刚那个不是
当你看到这种提示，请动动 🧠，不要来反馈好吗
“用不了”
这本身就很让人着迷，不是吗 🎉🇦🇷
Showing the 12 most recent of 20 posts we hold for @QuanX_API. 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.
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.
Named by 5 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“QuantumultX 教程&API&解析器 通知频道” (@QuanX_API), 28,565 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/QuanX_API.
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.