Engagement
3 posts held, back to 18 December 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 8 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.85%
- avg views ÷ 5,109 subscribers
- Avg views / post
- 146
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 3 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
10 Aug 2026, 14:07 UTC35 viewsread 12 August 2026 Forwarded from @chasesz_xlbPhoto
😀 野寻深圳SB撒币互推活动强势来意~ 😀
1⃣️ 报名多奖金多，掏空野寻小金库
报名参与人数越多 → 总奖金池越高
2️⃣0️⃣ 人 → 总奖金 💴5️⃣8️⃣8️⃣
3️⃣5️⃣人 → 总奖金 💴1️⃣8️⃣8️⃣8️⃣
5️⃣0️⃣人 → 总奖金 💴3️⃣8️⃣8️⃣8️⃣
8️⃣0️⃣人 → 总奖金 💴5️⃣8️⃣8️⃣8️⃣
1️⃣0️⃣0️⃣人 → 总奖金 💴6️⃣6️⃣6️⃣6️⃣
2⃣️ 不看邀请人数，符合条件都可以
不看邀请人数，报名参与即可，奖金多少纯看运气
🤔 女生参与条件：
频道/群组人数200+
频道/群组首个有效帖子的时间>30天
通过野寻验证
在个人频道放置活动宣传贴
🥰 男生参与条件：
深圳交流群 积分200分+
在个人频道放置活动宣传贴
在个人主页放置野寻交流群链接
在我的动态发布野寻资讯
3⃣️ 福利全凭运气，拼手气得大红包
😀 活动通知开奖时间发出拼手气红包，按照抢到红包的大小排名
…
22 Jul 2026, 09:11 UTC256 viewsread 12 August 2026 Photo
😀 野寻 · 深圳修车导航 😀
~逐梦鹏城路漫漫，相逢一笑暖心间~
~同行不惧风霜苦，有友相随天地宽~
新手中心: 😀【野寻 · 深圳使用手册】
😀 野寻大讲堂
└ 作业模版
└ 积分商城
└ 会员制度
└ 工兵模版
└ 查找老师
😀 深圳榜单导航
└ 按价格
└ 按地区
└ 按服务
└ 按标签
😀 其它资源
└ 野寻· 深圳外围
└ 野寻· 深圳包养
└ 野寻· 深圳商家
⚡【野寻· 深圳】榜单结构
├ 打卡通告群 @chasesz_tgq
├ 学生交流群 @chasesz_jlq
├ 小喇叭 @chasesz_xlb
├ 榜单导航 @chasesz_bddh
├ 修车档案 @chasesz_lsda
├ 精选档案 @chasesz_lsjx
├ 作业评价 @chasesz_zypj
├ 活动公告 @chasesz_hdgg
…
Channel created
Showing the 3 most recent of 3 posts we hold for @sz_ooxx. 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.
Citation-graph rank
Citation-graph rank — 610,697 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 4 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
野寻 · 深圳活动公告
@chasesz_hdgg · 5,5122 posts野寻 · 深圳学生交流群
@chasesz_jlq · 22,4802 posts"野寻公告"
@ooxxdh · 9,1392 posts野寻 · 深圳榜单导航
@chasesz_bddh · 5,2711 post野寻 · 深圳包养档案
@chasesz_byda · 5,0921 post野寻 · 深圳修车档案
@chasesz_lsda · 5,9131 post野寻 · 深圳精选档案
@chasesz_lsjx · 5,0821 post野寻 · 深圳商家档案
@chasesz_sjda · 5,0811 post野寻 · 深圳打卡通告群
@chasesz_tgq · 21,9391 post野寻 · 深圳外围档案
@chasesz_wwda · 5,1341 post野寻 · 深圳小喇叭
@chasesz_xlb · 5,1841 post野寻 · 深圳作业评价
@chasesz_zypj · 6,3941 post上海【喜茶】广播站
@xichash · 9,1201 post 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 16 August 2026 — this
entry's latest reading, not the date you are reading this.
“野寻 · 深圳官方入口” (@sz_ooxx), 5,109 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/sz_ooxx.
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.
