Telegram RegisterThe public register of Telegram
Telegram profile photo for 全网资源导航分类·橙子社区

Channel

全网资源导航分类·橙子社区

@czNav

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

50,756subscribers

+1,173 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002745985909
TypeChannel
Username@czNav
Description橙子大群 @c65588 橙子供需 @c69911 橙子曝光 @c69922 橙子公告 @c69933 全网需求 @c69966 橙子公群 @czNav 工具导航 t.me/c69933/38 ——————————————————- 橙子-官方客服 客服: @c65588bot 担保: @c68800 广告: @c68822 会员: @c68833 仲裁: @c68844 公群: @c68855 资源项目|担保服务|信息支持
Created23 June 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/czNav

Topic

Marketing & affiliate — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Growth

49,58350,76050,171.57 August 2026 — 49,583 subscribers8 August 2026 — 49,633 subscribers9 August 2026 — 49,630 subscribers10 August 2026 — 49,718 subscribers11 August 2026 — 49,687 subscribers12 August 2026 — 49,735 subscribers13 August 2026 — 49,825 subscribers14 August 2026 — 49,900 subscribers16 August 2026 — 49,925 subscribers17 August 2026 — 49,883 subscribers18 August 2026 — 49,864 subscribers19 August 2026 — 49,933 subscribers20 August 2026 — 49,983 subscribers21 August 2026 — 50,067 subscribers22 August 2026 — 50,139 subscribers24 August 2026 — 50,234 subscribers25 August 2026 — 50,257 subscribers26 August 2026 — 50,252 subscribers27 August 2026 — 50,260 subscribers28 August 2026 — 50,429 subscribers29 August 2026 — 50,455 subscribers30 August 2026 — 50,600 subscribers31 August 2026 — 50,679 subscribers1 September 2026 — 50,760 subscribers2 September 2026 — 50,708 subscribers3 September 2026 — 50,688 subscribers5 September 2026 — 50,609 subscribers9 September 2026 — 50,570 subscribers11 September 2026 — 50,418 subscribers13 September 2026 — 50,363 subscribers15 September 2026 — 50,439 subscribers17 September 2026 — 50,553 subscribers19 September 2026 — 50,751 subscribers26 September 2026 — 50,756 subscribers50,7567 August 202626 September 2026
34 measurements spanning 50 days, net +1,173. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 49,406–50,937 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 16:3850,756+5
19 Sept 2026, 15:5750,751+198
17 Sept 2026, 05:0150,553+114
15 Sept 2026, 03:3950,439+76
13 Sept 2026, 12:1750,363-55
11 Sept 2026, 17:0150,418-152
9 Sept 2026, 02:1750,570-39
5 Sept 2026, 19:1950,609-79
3 Sept 2026, 20:3950,688-20
2 Sept 2026, 10:1350,708-52
1 Sept 2026, 09:3550,760+81
31 Aug 2026, 08:1350,679+79
30 Aug 2026, 07:2750,600+145
29 Aug 2026, 08:0550,455+26
28 Aug 2026, 09:1750,429+169
27 Aug 2026, 06:5850,260+8
26 Aug 2026, 07:0850,252-5
25 Aug 2026, 05:2750,257+23
24 Aug 2026, 03:4350,234+95
22 Aug 2026, 09:0750,139first reading

Engagement

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 103 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 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.

What this channel posts

Links
3

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

21 Apr 2026, 11:52 UTC≈13,700 viewsread 27 September 2026

🚀 引流与获客 (Traffic & Marketing) 全网精准流量,真粉、数据、投放全覆盖 0000 0000 供押10000U TK/FB/GG 老户现户源头户商-海拓 🌟 1188 供押10000U 蝴蝶代投 打粉&代投TK / FB 纯广告粉 🌟 0033 供押6000U 全球数据股民快杀刷单精聊电销 0011 供押5000U 海外一手BC充值数据数据 2211 供押5000U 专注于WS群发业务图文超链公群 0022 供押3500U海外数据源头高质量高转化公群 1199 供押3000U 电销线路/AI群呼打粉全球可打 2200 供押3000U 海外渗透一手源头数据公群 0055 供押3000U TG/WS拉群源头全球可拉机房公群

21 Apr 2026, 11:52 UTC≈11,700 viewsread 27 September 2026

🛩 账号与服务 (Accounts & Service) 全球社交号商源头,接码验证与各类安全辅助服务 2288 供押5000U/FB劫持大小黑源头 稳定供应 1133 供押3000U Ws普混普印/五段混合老号公群 1177 供押2000U Ws/tg 老号 协议 劫持 直登 接粉号 暂停作业 🌟 0099 供押1000u INS/FB/领英/GV/脸书/ins/Twitter号商

21 Apr 2026, 11:52 UTC≈9,870 viewsread 27 September 2026

🌐 搭建与开发 (Tech & Dev) 黑科技软件、盘口搭建、APP上架与前端美工服务 3300 供押5000U(beta搭建)记账/各种机器人

21 Apr 2026, 11:51 UTC≈9,130 viewsread 27 September 2026

🐶 游戏与竞技 (Gaming & Gambling) 骰子扫雷、加拿大28、红包等真人游戏群组 橙子只担保游戏公群供押额度 正常上下分,不担保群老板个人信誉,不担保代理、拉手、代收付等和群老板的其他交易或合作。

23 Jun 2025, 10:14 UTC≈22,500 viewsread 27 September 2026

🌟🌟🌟🌟 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 👥 橙子总群 @c65588 【 群组】 👥 全网需求 @c69966 【 群组】 📢 橙子供需 @c69911 【 频道】 📢 橙子曝光 @c69922 【 频道】 📢 橙子公群 @czNav 【 频道】 官方客服 ✅ 担 保 @c68800 ❗️ 橙信 广 告 @c68822 🛜 橙翼 会 员 @c68833 👑 橙享 仲 裁 @c68844 🔨 橙诉 公 群 @c68855 👥 橙务 🤖 橙子机器人 🎛 橙子群管 @czManageBot 🎭 橙子表情 @czEmojiBot 🕸 骗子查询 @pianziAdminbot 💰 查U 监控 @czUSDTbot 🖌 橙子记账 @czJiZhangBot 🔎 资源引擎 @czDemandBot 🔨 公群报备 @CzBaoBeiBot 💎 橙子游戏 @cz_play_bot 🪟 橙子钱包 @cz_pay_bot

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.

Posts edited after publishing

@czNav edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
3 September 2026
Most recent edit
3 September 2026

Mentions

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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“全网资源导航分类·橙子社区” (@czNav), 50,756 subscribers as measured 26 September 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.