Channel
@packycoder
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,641subscribers
+20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002813886339 |
|---|---|
| Type | Channel |
| Username | @packycoder |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/packycoder |
Giveaways & airdrops — 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 77% 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 |
|---|---|---|
| 13 Oct 2026, 15:39 | 1,641 | +2 |
| 7 Oct 2026, 22:37 | 1,639 | -4 |
| 1 Oct 2026, 04:54 | 1,643 | +18 |
| 16 Sept 2026, 03:17 | 1,625 | +1 |
| 12 Sept 2026, 17:01 | 1,624 | +7 |
| 8 Sept 2026, 20:18 | 1,617 | +1 |
| 3 Sept 2026, 09:54 | 1,616 | +4 |
| 31 Aug 2026, 03:46 | 1,612 | -5 |
| 27 Aug 2026, 23:46 | 1,617 | +1 |
| 24 Aug 2026, 16:35 | 1,616 | +1 |
| 21 Aug 2026, 06:23 | 1,615 | +3 |
| 17 Aug 2026, 20:34 | 1,612 | +3 |
| 14 Aug 2026, 19:33 | 1,609 | -5 |
| 11 Aug 2026, 07:27 | 1,614 | -5 |
| 8 Aug 2026, 05:07 | 1,619 | -2 |
| 7 Aug 2026, 21:16 | 1,621 | no change |
| 7 Aug 2026, 17:54 | 1,621 | first reading |
20 posts held, back to 3 February 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 20 July 2026. An engagement rate over an empty window would be a number about nothing.
【键盘福利抽奖来袭！！！】 为了感谢大家一直以来对 PackyCode 的支持，这次直接送出 9 把机械键盘： 一等奖：ROG 魔导士 × 1 人 二等奖：ATK RS6 Air × 3 人 三等奖：艾石头 MG68 × 5 人 关注、点赞、评论 、转发即可参与抽奖，开奖后会核查参与记录，请勿取消互动～ 参与链接：https://x.com/cccchuizi/status/2079115252705407383
codex-sale现已重新推送上线，并已开放使用。 本次上线后： codex-sale 按 0.3 倍倍率 计费 感谢大家的支持与等待。
Claude-Sale 分组限时降价！ claude-sale 分组 倍率已调整至 0.8x（约官方 1.12 折），限时一周！ 支持模型：Claude Opus 4.8 / 4.7 / 4.6、Sonnet 4.6 / 4.5、Haiku 4.5 等全系列 该分组底层与 cc 分组完全一致。 使用方法： 在 PackyCode 平台创建令牌或修改令牌时 选择 分组 → claude-sale 模型名称直接填写对应模型即可（如 claude-opus-4-8、claude-sonnet-4-6 等） 注意事项： 该分组为限时优惠，一周后将恢复原价 目前稳定性良好，适合追求性价比的用户 如需极致纯净度，可继续使用 claude-officially 分组 欢迎大家体验～
推送 claude-sale 分组底层和 cc 分组一致，限定时段优惠分组，下架日期待定，分组倍率为 1.0
【重要公告】CC 分组倍率下调通知 近期随着相关成本压力阶段性缓解，为了给大家提供更友好的使用价格，我们决定对 CC 分组倍率 进行下调。 自 2026 年 5 月 12 日 12:00 起，CC 分组倍率由 2.5 下调至 2。 后续我们将继续根据上游政策、额度和服务情况动态调整，若条件进一步改善，也会争取继续下调。 codex、cc-sale 可正常选择，其他分组不受影响。 Packy Team 2026 年 5 月 12 日
Packycode pinned «【公告】新增异常缓存补偿机制 为了进一步提升服务稳定性和用户体验，我们上线了异常缓存补偿机制。 补偿规则： 当系统检测到连续创建异常缓存时，将对该部分异常缓存产生的费用只收取原费用 20% 的扣费。 当前生效范围： 目前仅在 Claude 渠道 开启 Beta 测试。 后续计划： 该机制将逐步覆盖 PackyAPI 全部渠道。 此机制主要用于减少高峰期因异常缓存导致的不必要扣费情况，保护用户利益。 感谢各位用户一直以来的支持与反馈。如在使用过程中遇到任何问题，欢迎随时联系我们。 PackyAPI…»
【公告】新增异常缓存补偿机制 为了进一步提升服务稳定性和用户体验，我们上线了异常缓存补偿机制。 补偿规则： 当系统检测到连续创建异常缓存时，将对该部分异常缓存产生的费用只收取原费用 20% 的扣费。 当前生效范围： 目前仅在 Claude 渠道 开启 Beta 测试。 后续计划： 该机制将逐步覆盖 PackyAPI 全部渠道。 此机制主要用于减少高峰期因异常缓存导致的不必要扣费情况，保护用户利益。 感谢各位用户一直以来的支持与反馈。如在使用过程中遇到任何问题，欢迎随时联系我们。 PackyAPI 团队 2026 年 5 月
Packycode pinned «codex分组同步官方下掉部分模型，下方模型不再支持 • gpt-5.2-codex • gpt-5.1-codex-mini • gpt-5.1-codex-max • gpt-5.1-codex • gpt-5.1 • gpt-5»
codex分组同步官方下掉部分模型，下方模型不再支持 • gpt-5.2-codex • gpt-5.1-codex-mini • gpt-5.1-codex-max • gpt-5.1-codex • gpt-5.1 • gpt-5
推送 cc-claw 分组，原生 claude api，倍率 2x，养殖户专用～
codex 包月套餐无限期停售
Packycode pinned Deleted message
Showing the 12 most recent of 20 posts we hold for @packycoder. 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.
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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“Packycode” (@packycoder), 1,641 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/packycoder.
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.