Channel
@bj_ooxx
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
6,422subscribers
+1,988 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002429609230 |
|---|---|
| Type | Channel |
| Username | @bj_ooxx |
| Created | 6 October 2024 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/bj_ooxx |
Giveaways & airdrops — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 06:31 | 6,422 | +28 |
| 2 Nov 2026, 12:00 | 6,394 | -88 |
| 30 Oct 2026, 13:34 | 6,482 | -193 |
| 27 Oct 2026, 15:46 | 6,675 | -26 |
| 24 Oct 2026, 16:48 | 6,701 | -54 |
| 22 Oct 2026, 01:59 | 6,755 | -64 |
| 18 Oct 2026, 11:07 | 6,819 | +102 |
| 15 Oct 2026, 01:48 | 6,717 | -8 |
| 12 Oct 2026, 01:19 | 6,725 | +501 |
| 5 Oct 2026, 05:35 | 6,224 | +51 |
| 26 Sept 2026, 18:16 | 6,173 | +301 |
| 17 Sept 2026, 07:58 | 5,872 | -11 |
| 13 Sept 2026, 16:57 | 5,883 | +135 |
| 10 Sept 2026, 08:39 | 5,748 | +222 |
| 4 Sept 2026, 16:57 | 5,526 | +131 |
| 1 Sept 2026, 01:43 | 5,395 | +147 |
| 28 Aug 2026, 19:34 | 5,248 | +15 |
| 25 Aug 2026, 23:04 | 5,233 | -49 |
| 23 Aug 2026, 02:15 | 5,282 | +981 |
| 19 Aug 2026, 11:25 | 4,301 | first reading |
4 posts held, back to 6 October 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 10 pages of 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 20 October 2026 |
|---|---|
| Posts held | 4 (6 October 2024 – 20 October 2026) |
| Views total | 1,737 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 23:57 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.
7 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 100.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 4 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 6 October 2024 to 20 October 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.
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (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 📩 代理合作：野寻·拾光
👑 野寻 HM 星玺厅 👑 🌐 全球华人一站式品质赌场娱乐厅 🎰 热门电子游戏，丰富主题自由选择 🎲 多种经典玩法，加拿大28 ⚽️ 体育赛事同步，热门项目精彩不断 📱 手机电脑均可进入，操作简单、畅快体验 👤 专属客服在线，及时处理相关问题 🔥 好局开场，精彩翻牌 💎 高端场面，每一局都充满期待 👑 牌桌有输赢，野寻有排面 🌹 官方网站：野寻 HM 星玺厅 💬 官方客服：HM国际-泡泡 📢 官方频道：野寻 hm7.cc 📩 代理合作：野寻·拾光
😀 野寻 · 北京修车导航 😀 ~紫禁风轻月色柔，京华邂逅意相投~ ~天涯若得知心友，不负人间一段秋~ 新手中心 : 😀【野寻 · 北京使用手册】 😀 野寻 · 北京 └ 修车档案 └ 精选榜单 └ 榜单导航 └ 商家档案 └ 北京外围 └ 北京包养 ⚡【野寻· 北京】榜单结构 ├ 学生交流群 @chasebj_jlq ├ 打卡通告群 @chasebj_tgq ├ 小喇叭 @chasebj_xlb ├ 作业评价 @chasebj_zypj ├ 活动公告 @chasebj_hdgg ├ 官方入口 @bj_ooxx ├ 更多友群 @ooxxdh ⭐ 一键关注 https://t.me/addlist/np_TNvf_tpVmMzg1 📱 野寻观川 @chase_gc 📱 无法联系 @chase_gc_bot 😀 野寻 · 社区 😀 野寻 · 上海 😀 野寻 · 杭州 😀 野寻 ·…
❤7
Channel created
Showing the 4 most recent of 4 posts we hold for @bj_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.
@bj_ooxx 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.
We recorded 2 posts on @bj_ooxx 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.
Named by 2 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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“野寻·北京官方入口” (@bj_ooxx), 6,422 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/bj_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.