Channel
@czNav
On this record: Growth · Engagement · Posts · Citations · Cite this entry
49,825subscribers
+242 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002745985909 |
|---|---|
| Type | Channel |
| Username | @czNav |
| Created | 23 June 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/czNav |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 03:45 | 49,825 | +90 |
| 12 Aug 2026, 06:24 | 49,735 | +48 |
| 11 Aug 2026, 07:32 | 49,687 | -31 |
| 10 Aug 2026, 07:52 | 49,718 | +88 |
| 9 Aug 2026, 05:55 | 49,630 | -3 |
| 8 Aug 2026, 05:12 | 49,633 | +50 |
| 7 Aug 2026, 18:45 | 49,583 | first reading |
6 posts held, back to 23 June 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 15 pagesof 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 6 posts for this entry, the most recent from 21 April 2026. An engagement rate over an empty window would be a number about nothing.
🚀 引流与获客 (Traffic & Marketing) 全网精准流量，真粉、数据、投放全覆盖 0000 供押10000U 谷歌账单老户海外户商源头 🌟 0033 供押6000U 全球数据股民快杀刷单精聊电销 0011 供押5000U 海外一手BC充值数据数据 2211 供押5000U 专注于WS群发业务图文超链公群 0022 供押3500U海外数据源头高质量高转化公群 1199 供押3000U 电销线路/AI群呼打粉全球可打 2200 供押3000U 海外渗透一手源头数据公群 1188 供押1500U筛料数据币粉股票兼职交友精准数据公群 0055 供押3000U TG/WS拉群源头全球可拉机房公群
🛩 账号与服务 (Accounts & Service) 全球社交号商源头，接码验证与各类安全辅助服务 2288 供押5000U/FB劫持大小黑源头 稳定供应 1133 供押3000U Ws普混普印/五段混合老号公群 1177 供押2000U Ws/tg 老号 协议 劫持 直登 接粉号 暂停作业 🌟 0099 供押1000u INS/FB/领英/GV/脸书/ins/Twitter号商
🌐 搭建与开发 (Tech & Dev) 黑科技软件、盘口搭建、APP上架与前端美工服务 3300 供押5000U(beta搭建)记账/各种机器人
🐶 游戏与竞技 (Gaming & Gambling) 骰子扫雷、加拿大28、红包等真人游戏群组 橙子只担保游戏公群供押额度 正常上下分，不担保群老板个人信誉，不担保代理、拉手、代收付等和群老板的其他交易或合作。
🌟🌟🌟🌟 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 👥 橙子总群 @c65588 【 群组】 👥 全网需求 @c69966 【 群组】 📢 橙子供需 @c69911 【 频道】 📢 橙子曝光 @c69922 【 频道】 📢 橙子公群 @czNav 【 频道】 官方客服 ✅ 担 保 @c68800 ❗️ 橙信 广 告 @c68822 🛜 橙翼 会 员 @c68833 👑 橙享 仲 裁 @c68844 🔨 橙诉 公 群 @c68855 👥 橙务 🤖 橙子机器人 🎛 橙子群管 @czManageBot 🎭 橙子表情 @czEmojiBot 🕸 骗子查询 @pianziAdminbot 💰 查U 监控 @czUSDTbot 🖌 橙子记账 @czJiZhangBot 🔎 资源引擎 @czDemandBot 🔨 公群报备 @CzBaoBeiBot 💎 橙子游戏 @cz_play_bot 🪟 橙子钱包 @cz_pay_bot
Channel created
Showing the 6 most recent of 6 posts we hold for @czNav. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“全网资源导航分类·橙子社区” (@czNav), 49,825 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/czNav.
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.