Channel
@sh_ooxx
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6,286subscribers
+1,911 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1004424002438 |
|---|---|
| Type | Channel |
| Username | @sh_ooxx |
| Created | 19 June 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/sh_ooxx |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:23 | 6,286 | +1,973 |
| 10 Aug 2026, 03:11 | 4,313 | -57 |
| 7 Aug 2026, 06:10 | 4,370 | -5 |
| 6 Aug 2026, 20:18 | 4,375 | first reading |
6 posts held, back to 19 June 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 6 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 August 2026 |
|---|---|
| Posts held | 6 (19 June 2026 – 2 August 2026) |
| Views total | 1,535 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18:18 UTC |
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.
⚠️ 野寻·上海｜官方安全提醒 ⚠️ 近期发现有人冒充官方群主、管理员或客服私聊拉群、收取费用，请大家提高警惕，谨防诈骗 ✔️ 官方群主： @chase_yx 🤖 官方机器人： @chase_yx_bot 🚫 请注意 ❌ 不向未经官方认证的人员支付任何定金或费用。 ❌ 不轻信陌生人主动私聊、拉群或发送链接。 ❌ 涉及资金交易，请先联系官方群主确认身份。 😀 温馨提醒： 野寻·上海致力于为大家提供安全、真实、放心的交流环境。如发现冒充官方、诈骗或其他异常行为，请第一时间联系官方群主或官方机器人举报。 请认准官方账号，保护好自己的资金安全，共同维护良好的群内环境。
😀 野寻上海互推抽奖活动第三期已圆满结束 😀 😀 恭喜所有获奖的小伙伴，奖金已全部发放，获奖名单和领奖截图都已公开，感谢大家的支持！❤️ 😀 第四期8月7日晚22：00开奖 快快参与起来吧！ 😀 报名人数越多，奖金池越高！ 😀 不看邀请人数 😀 报名即可参与抽奖 😀 最高可得 2️⃣3️⃣3️⃣3️⃣元现金红包！ 活动方案 : https://t.me/chasesh_xlb/988 上海交流 : https://t.me/chasesh_jlq 上海报名 : 野寻·星野 @chase_yx 双向联系 @chase_yx_bot
😀 野寻上海互推抽奖活动第二期已圆满结束 😀 😀 恭喜所有获奖的小伙伴，奖金已全部发放，获奖名单和领奖截图都已公开，感谢大家的支持！❤️ 😀 第三期7.31晚22：00开奖 快快参与起来吧！ 😀 报名人数越多，奖金池越高！ 😀 不看邀请人数 😀 报名即可参与抽奖 😀 最高可得 2️⃣3️⃣3️⃣3️⃣元现金红包！ 活动方案 : https://t.me/chasesh_xlb/988 上海交流 : https://t.me/chasesh_jlq 上海报名 : 野寻·星野 @chase_yx 双向联系 @chase_yx_bot
😀 野寻上海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⃣️ 福利全凭运气，拼手气得大红包 😀 活动通知开奖时间发出拼手气红包，按照抢到红包的大小排名 拼手气第1️⃣名领取总奖…
😀 野寻 · 上海修车导航 😀 ~十里霓虹映夜长，相逢沪上话沧桑~ ~红尘有幸成知己，不负流年共举觞~ 新手中心: 😀【野寻 · 上海使用手册】 😀 野寻 · 北京 └ 修车档案 └ 精选榜单 └ 外围档案 └ 榜单导航 └ 包养档案 └ 商家档案 ⚡【野寻· 上海】榜单结构 ├ 打卡通告群 @chasesh_tgq ├ 学生交流群 @chasesh_jlq ├ 小喇叭 @chasesh_xlb ├ 榜单导航 @chasesh_bddh ├ 修车档案 @chasesh_lsda ├ 作业评价 @chasesh_zypj ├ 活动公告 @chasesh_hdgg ├ 官方入口 @sh_ooxx ├ 更多友群 @ooxxdh ⭐ 一键关注 https://t.me/addlist/jit97g7hXW0yN2Y0 📱 野寻星野 @chase_yx 📱 无法联系 @chase_yx_
Channel created
Showing the 6 most recent of 6 posts we hold for @sh_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 — 571,922 of 1,480,688entries 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.
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.
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.
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.
“野寻·上海官方入口” (@sh_ooxx), 6,286 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/sh_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.