号池补了 早上经常崩溃没自动补上 十分抱歉
❤2
Channel
@api86channel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,468subscribers
-12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003564807659 |
|---|---|
| Type | Channel |
| Username | @api86channel |
| Created | 28 April 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 29 October 2026 |
| On Telegram | t.me/api86channel |
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Oct 2026, 20:56 | 3,468 | -1 |
| 26 Oct 2026, 14:48 | 3,469 | +6 |
| 23 Oct 2026, 08:07 | 3,463 | +3 |
| 20 Oct 2026, 09:09 | 3,460 | -1 |
| 17 Oct 2026, 16:27 | 3,461 | +2 |
| 14 Oct 2026, 08:16 | 3,459 | -5 |
| 10 Oct 2026, 09:19 | 3,464 | -13 |
| 4 Oct 2026, 15:41 | 3,477 | +6 |
| 24 Sept 2026, 21:21 | 3,471 | -15 |
| 16 Sept 2026, 15:58 | 3,486 | -7 |
| 13 Sept 2026, 04:19 | 3,493 | -1 |
| 9 Sept 2026, 06:37 | 3,494 | +7 |
| 4 Sept 2026, 01:22 | 3,487 | +2 |
| 31 Aug 2026, 06:04 | 3,485 | -2 |
| 28 Aug 2026, 06:43 | 3,487 | +2 |
| 25 Aug 2026, 04:26 | 3,485 | -4 |
| 21 Aug 2026, 13:55 | 3,489 | +5 |
| 18 Aug 2026, 06:52 | 3,484 | -4 |
| 14 Aug 2026, 23:35 | 3,488 | +2 |
| 11 Aug 2026, 12:03 | 3,486 | first reading |
11 posts held, back to 28 April 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 11 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
219 reactions across 9 posts, in 13 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 67 | 30.6% | |
| ❤ | 42 | 19.2% | |
| 😢 | 25 | 11.4% | |
| 💯 | 24 | 11.0% | |
| 🤯 | 17 | 7.76% | |
| 🤬 | 13 | 5.94% | |
| 🙏 | 6 | 2.74% | |
| 👀 | 5 | 2.28% | |
| 💊 | 5 | 2.28% | |
| 🔥 | 5 | 2.28% | |
| 🤔 | 4 | 1.83% | |
| 👨💻 | 3 | 1.37% | |
| 🕊 | 3 | 1.37% |
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 11 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 219 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 28 April 2026 to 7 August 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.
号池补了 早上经常崩溃没自动补上 十分抱歉
❤2
codex官方炸了
🙏6😢4
Claude Max纯血号池分组暂时维护 恢复会说 可以切逆向分组用着
增加Claude Max纯血号池分组 支持Fable5 限时0.6倍率测试 可外接 不限制客户端 有需要可以接入测试
💯12❤1
codex分组现已支持GPT-5.6模型
💯12❤1
因政策与合规要求,即日起我们将不再向中国大陆 IP 及其他不符合条件地区IP提供 AI 中转服务,以遵守当地法律法规。受影响地区访问将看到提示页面,支持地区用户不受影响。给您带来不便,敬请谅解,感谢理解 Due to policy and compliance requirements, effective immediately, we will no longer provide AI services to IP addresses from mainland China or other ineligible regions, in order to comply with applicable local laws and regulations. Affected visitors will see a notice page displaying their IP address. Users in suppor…
🤡67🤬13❤6💊5🤔4
今天大部分codex号池又炸了 给plus分组接了几个pro号用着 pro分组正常运行
🤯13❤5
5.2及5.3模型中午被官方关掉了 还在用该系列模型的客户可以切换其他可用模型 如5.4 5.5试试 claude系列死号维护 外面市场应该都差不多
🔥5🤯4❤2
今天大部分日抛PLUS号池都死了 刚新接了一批PLUS号池暂时用着 可能会不太稳定
😢21👀5👨💻3🕊3❤1
API 网站:https://api.86gamestore.com 教程地址:https://www.yuque.com/u41886052/aw9ona 中转站余额充值下单地址:https://faka.redeemgpt.com 登录后如果显示账号余额为0\账号禁用 清空浏览器缓存后使用ctrl+f5刷新页面 或者 换个浏览器重新登录就正常了
❤24
Channel created
Showing the 11 most recent of 11 posts we hold for @api86channel. 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.
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“86中转站API通知频道” (@api86channel), 3,468 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/api86channel.
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.