更新订阅可以试试三网优化中转

Channel
鲜橙汁二周目
@czcz1145
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
147subscribers
+40 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002479455518 |
|---|---|
| Type | Channel |
| Username | @czcz1145 |
| Created | 27 January 2025 — measured — dated from the channel’s first post |
| First recorded | 22 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/czcz1145 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 04:57 | 147 | +7 |
| 8 Sept 2026, 19:15 | 140 | +11 |
| 30 Aug 2026, 17:55 | 129 | +9 |
| 23 Aug 2026, 05:18 | 120 | +13 |
| 22 Aug 2026, 01:31 | 107 | first reading |
Engagement
12 posts held, back to 27 January 2025 — 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 12 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 4 of the 12 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 27 January 2025 to 4 June 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
目前新套餐包括老套餐的流量已翻倍,因为当前环境中转机难以获得,中转倍率要提高,直连倍率不变甚至更低,直连节点倍率0.3倍到1倍,中转1.5倍到2.5倍以内,没有标倍率默认一倍
中转-恢复-更新订阅即可用 但封锁还未结束,可能后续会被通报,且用且珍惜
送点礼品卡(20次使用,每个账号限一次) 使用教程:从官网登录-个人中心-礼品卡输入卡券 流量+100G的礼品卡券:100++ 余额+5的卡劵(可免费购买月付)卡券:+5CNY 已兑换完
❤1
收到部分地区速度慢的反馈,新加的入口,目前节点香港03,日本01,新加坡01,台湾01,美国01,韩国01为新的入口,速度可观(除了香港03要更新订阅以外,其他节点不用更新订阅)
我们已完成全部节点更换至高速稳定的Vless协议,并依旧是中转节点,该协议可以有效的抗封锁抗省墙。 SS节点将于2025.9.12日删除!!!! SS节点将于2025.9.12日删除!!!! SS节点将于2025.9.12日删除!!!! 若您更新订阅后没有出现Vless,说明您的客户端不支持Vless协议(如:原版Clash、Clash for Windows 老版本V2raynG Quantumult X Surge) 需更换至以下支持Vless的客户端 PC/Mac软件推荐: FlClash 点我去下载 Clash Verge 点我去下载 Clash Party 点我去下载 V2rayN 点我去下载 安卓端软件推荐: FlClash 点我去下载 NekoBox 点我去下载 IOS端软件推荐: 小火箭 Loon (圈x、surge不支持) 软路由: openclash 请更换至meta内核 推荐您使用nikki
协议更换vless ss的这几天不受影响 过几天就要麻烦更新一下订阅
优惠劵: 节日快乐 (8折,不限) 五一快乐 (5.1折,月付到季付,只有5个劵) 有效时间:4月30到5月2号
优惠劵: 2015年5折 2015年8折 季付8折有效,5折只能月付 2月6日失效,或者使用88次失效 (年份不建议,主要怕你们担心我坚持不下去) 注意事项:1.有套餐的重新创号买 2.支付金额不能低于3元(支付那边没办法解)
Channel name was changed to «鲜橙汁二周目»
Channel photo updated
Channel created
Showing the 12 most recent of 12 posts we hold for @czcz1145. 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
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.
“鲜橙汁二周目” (@czcz1145), 147 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/czcz1145.
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.