😍😂🤣😍😂😍😎😂 🔥 50个代理席位,正在逐个减少 全新代理❤️福利多多 每日返佣❤️月入百万 席位数量固定,招满后申请通道立即关闭。 ❌ 不追加 ❌ 不扩编 ❌ 不临时开放 我们宁缺毋滥,不是谁来都收,只寻找真正同频、有行动力的长期伙伴。 机会不会停下来等你,席位只留给先行动的人。 📩 立即私信,申请锁定资格。 🎉🐶🐶🔥🤡 野寻·拾光

Channel
"野寻公告"
@ooxxdh
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
6,122subscribers
-3,099 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002427885983 |
|---|---|
| Type | Channel |
| Username | @ooxxdh |
| Created | 16 September 2024 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/ooxxdh |
Topic
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 05:49 | 6,122 | -62 |
| 2 Nov 2026, 00:08 | 6,184 | -342 |
| 29 Oct 2026, 19:30 | 6,526 | -312 |
| 27 Oct 2026, 00:27 | 6,838 | -288 |
| 24 Oct 2026, 00:46 | 7,126 | -394 |
| 21 Oct 2026, 01:40 | 7,520 | -273 |
| 18 Oct 2026, 08:05 | 7,793 | -274 |
| 15 Oct 2026, 09:48 | 8,067 | -258 |
| 12 Oct 2026, 16:21 | 8,325 | -440 |
| 6 Oct 2026, 11:19 | 8,765 | -289 |
| 29 Sept 2026, 01:58 | 9,054 | +2 |
| 18 Sept 2026, 21:36 | 9,052 | -14 |
| 14 Sept 2026, 16:38 | 9,066 | -23 |
| 11 Sept 2026, 08:39 | 9,089 | -5 |
| 1 Sept 2026, 15:03 | 9,094 | -6 |
| 29 Aug 2026, 20:15 | 9,100 | -14 |
| 27 Aug 2026, 04:42 | 9,114 | -4 |
| 23 Aug 2026, 23:58 | 9,118 | -8 |
| 20 Aug 2026, 04:25 | 9,126 | -13 |
| 16 Aug 2026, 20:45 | 9,139 | first reading |
Engagement
7 posts held, back to 16 September 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 35 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.17%
- avg views ÷ 6,122 subscribers
- Avg views / post
- 133
- 5 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 7 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.
| Window | Rolling 30 days · latest post in window 2 November 2026 |
|---|---|
| Posts held | 7 (16 September 2024 – 2 November 2026) |
| Views total | 665 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 02:01 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.
Reaction mix
16 reactions across 1 post, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 75.0% | |
| 💩 | 4 | 25.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 1 of the 7 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 16 September 2024 to 2 November 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
Telegram’s own ‘edited’ marker: 1 of 5 posts held from the last 30 days (20.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
👑 野寻 HM 富贵厅 👑 🌐 全球华人一站式品质赌场娱乐厅 🎰 热门电子游戏,丰富主题自由选择 🎲 多种经典玩法,加拿大28 ⚽️ 体育赛事同步,热门项目精彩不断 📱 手机电脑均可进入,操作简单、畅快体验 👤 专属客服在线,及时处理相关问题 🔥 好局开场,精彩翻牌 💎 高端场面,每一局都充满期待 👑 牌桌有输赢,野寻有排面 🌹 官方网站:野寻 HM 富贵厅 💬 官方客服:HM国际-泡泡 📢 官方频道:野寻 hm7.cc 📩 代理合作:野寻·拾光
🔥 【福利二 · 排名福利】 🔥 🧧 抢红包争排名,会员、代理专享排名奖励! 🏆 排名奖励 🥇 第一名:9️⃣9️⃣9️⃣元 🥈 第二名:8️⃣8️⃣8️⃣元 🥉 第三名:7️⃣7️⃣7️⃣元 🏅 第四名:6️⃣6️⃣6️⃣元 🏅 第五名:5️⃣5️⃣5️⃣元 🏅 第六名:4️⃣4️⃣4️⃣元 🏅 第七名:3️⃣3️⃣3️⃣元 🏅 第八名:2️⃣2️⃣2️⃣元 🏅 第九名:1️⃣1️⃣1️⃣元 🏅 第十名:9️⃣9️⃣元 🎁 领取提醒 以上奖励面向 野寻HM会员/代理,以彩金形式发放,达到规定流水要求后可提现,提现金额设有上限。 💰 达标可直接领现金 野寻HM会员/代理 满足相应条件,可直接领取现金奖励,具体指标及领取方式请咨询活动管理员。 💗 社区专属奖励 面向 社区老师/学生 🧧 抢最佳:2️⃣2️⃣2️⃣元现金 🐆 抢豹子:2️⃣2️⃣2️⃣元现金 🥳🔥🔥🔥🤡 野寻 HM 富贵厅 🐶🔥🔥💪🐶 野寻 hm7.cc
🐆 野寻 · 金豹送喜 🐆 🧧 抢到豹子有惊喜,月内累计再升级! 活动期间,领取活动红包抽中“豹子号”,即可获得: 1⃣️ 当月首次抢到豹子 💰 普通用户:2️⃣2️⃣2️⃣元 💗 代理专属:1️⃣3️⃣1️⃣4️⃣元 2⃣️ 当月第二次抢到豹子 💰普通用户:2️⃣2️⃣2️⃣元 💗 代理专属:2️⃣8️⃣8️⃣8️⃣元 3⃣️ 当月第三次抢到豹子 💰 普通用户:2️⃣2️⃣2️⃣元 💗 代理专属:8️⃣8️⃣8️⃣8️⃣元 ✨ 您的身份升级,您的待遇也在升级! 💌 申请成为 野寻 HM 富贵厅 代理 ➡️ 代理招商:野寻·拾光 ❓ 什么是豹子号? 红包金额去掉小数点后,三个数字完全相同。 ✅ 例如:¥5.55、¥6.66、¥7.77 ⏰ 每日红包时间:22:00 中奖结果以 @okpay 后台记录及野寻官方审核为准。 🥳🔥🔥🔥🤡 野寻 HM 富贵厅 🐶🔥🔥💪🐶 野寻 hm7.cc 🎉🐶🐶🔥🤡 野寻·拾光 😍😍😍
🌿 野寻指南 · 入野有径 初来乍到,从这里出发; 久别重逢,从这里找到新鲜事。 😵💫 野寻路标 😀 社区导航 🎲 博弈小筑 😂🤣😍😎🤯😱🤯 🥳🔥🔥🔥🤡 野寻 HM 富贵厅 😂🤣🥳😴🙄🐶👀👀 🐶🔥🔥💪🐶 野寻 hm7.cc 🎁 拾野有礼 🐆 福利一 · 豹子福利 📊 福利二 · 排名福利
😀 野寻 · 社区 😀 万流汇野寻,一站链全域 万般所需,皆有归处 🔥 野寻计划 📱 社长 @chase_psz ✏️ 一键关注野寻计划 🙂 野寻贴吧 📱 无名 @chase_wm ✏️ 一键关注野寻贴吧 ☀️ 野寻社群 🌈 野寻真新镇 📱 皮仔 @Pokemonpizai ✏️ 一键关注真新镇 🌈 野寻北京 📱 观川 @chase_gc ✏️ 一键关注野寻北京 🌈 野寻上海 📱 星野 @chase_yx ✏️ 一键关注野寻上海 🌈 野寻深圳 📱 南汐 @chase_nx ✏️ 一键关注野寻深圳 🌈 野寻杭州 📱 临洲 @chase_lz ✏️ 一键关注野寻杭州 🌈 野寻广州 📱 清河 @chase_qh ✏️ 一键关注野寻广州 🌈 野寻南京 📱 芷宁 @chase_zn ✏️ 一键关注野寻南京 🌈 野寻长沙 📱 橘子 @chase_jz ✏️ 一键关注野寻长沙 🌈 野寻成都 📱 …
❤12💩4
Channel created
Showing the 7 most recent of 7 posts we hold for @ooxxdh. 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
@ooxxdh 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
- 26 August 2026
- Most recent edit
- 4 November 2026
Posts recorded as deleted after publishing
We recorded 1 post on @ooxxdh as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 4 November 2026
- Most recent seen missing
- 4 November 2026
- Median time before seen missing
- 4 months
- Seen missing in the last 30 days
- 1
Mentions
Named by 36 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@chasebj_sjda · 4,5638 posts野寻·北京活动公告
@chasebj_hdgg · 11,4867 posts野寻·北京小喇叭
@chasebj_xlb · 5,4377 posts野寻·上海小喇叭
@chasesh_xlb · 5,1407 posts野寻 · 深圳活动公告
@chasesz_hdgg · 12,1166 posts野寻 · 深圳小喇叭
@chasesz_xlb · 1,2016 posts野寻·北京榜单导航
@chasebj_bddh · 5,5024 posts野寻·杭州小喇叭
@chasehz_xlb · 1,1664 posts野寻.武汉小喇叭
@chasewh_xlb · 3,3264 posts野寻 · 深圳官方入口
@sz_ooxx · 1,3084 posts野寻·北京官方入口
@bj_ooxx · 6,4223 posts野寻·长沙小喇叭
@chasecs_xlb · 3,9083 posts野寻·上海榜单导航
@chasesh_bddh · 5,4593 posts野寻 · 深圳商家档案
@chasesz_sjda · 2,1753 posts皮仔の小喇叭
@Pokemonpz_xlb · 2,3973 posts野寻·上海官方入口
@sh_ooxx · 4,7503 posts野寻.武汉官方入口
@wh_xxoo · 2,8803 posts野寻·北京作业评价
@chasebj_zypj · 12,2252 posts野寻·广州活动公告
@chasegz_hdgg · 6,1622 posts野寻·杭州活动公告
@chasehz_hdgg · 13,0942 posts野寻 · 深圳精选档案
@chasesz_lsjx · 10,5532 posts野寻·杭州商家档案
@chasehz_sjda · 9701 post野寻·南京包养档案
@chasenj_byda · 9871 post野寻·南京商家档案
@chasenj_sjda · 1,0581 post
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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“"野寻公告"” (@ooxxdh), 6,122 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ooxxdh.
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.