昵称:#卡戴珊 地区:#朝阳 点击下方评论👇,查看老师详细资料

Channel
北京便民
@BJbmxc168
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
45,659subscribers
-2,768 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 | -1001170048784 |
|---|---|
| Type | Channel |
| Username | @BJbmxc168 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/BJbmxc168 |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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 |
|---|---|---|
| 31 Oct 2026, 18:47 | 45,659 | -348 |
| 30 Oct 2026, 20:35 | 46,007 | -399 |
| 29 Oct 2026, 20:37 | 46,406 | -204 |
| 28 Oct 2026, 23:47 | 46,610 | -467 |
| 27 Oct 2026, 21:16 | 47,077 | -213 |
| 26 Oct 2026, 21:47 | 47,290 | -516 |
| 25 Oct 2026, 22:08 | 47,806 | -224 |
| 24 Oct 2026, 20:21 | 48,030 | -542 |
| 23 Oct 2026, 18:27 | 48,572 | -199 |
| 22 Oct 2026, 19:41 | 48,771 | -435 |
| 21 Oct 2026, 17:50 | 49,206 | -430 |
| 20 Oct 2026, 17:28 | 49,636 | -726 |
| 19 Oct 2026, 13:48 | 50,362 | -155 |
| 18 Oct 2026, 16:45 | 50,517 | -155 |
| 17 Oct 2026, 15:47 | 50,672 | -179 |
| 16 Oct 2026, 18:27 | 50,851 | -225 |
| 15 Oct 2026, 19:25 | 51,076 | -153 |
| 14 Oct 2026, 16:45 | 51,229 | -229 |
| 13 Oct 2026, 07:09 | 51,458 | -82 |
| 8 Oct 2026, 23:16 | 51,540 | first reading |
Engagement
80 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 170 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.78%
- avg views ÷ 45,659 subscribers
- Avg views / post
- 813
- 35 posts measured
- Reaction rate
- 0.17%
- reactions ÷ views · ER floor
- Posts in window
- 35
- of 80 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. It is computed over the 26 of 35 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 October 2026 |
|---|---|
| Posts held | 80 (4 August 2026 – 31 October 2026) |
| Views total | 28,465 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Oct 2026, 13:37 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.
What this channel posts
- Video runtime
- 2m 59s
- Average length
- 14s
Measured directly from 13 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
73 reactions across 53 posts, in 2 distinct kinds. The most used accounts for 98.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 72 | 98.6% | |
| 👍 | 1 | 1.37% |
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 59 of the 80 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 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 80 most recent posts we hold, published 4 August 2026 to 31 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.
Recent posts
🍾北京商k最好玩的KTV,情趣游戏场,项目好玩刺激 📱兄弟们,别再玩普通的局了,来点真刺激的!全程情趣游戏的商K,尺度直接拉满,爽到停不下来! • 💝👍开场即开始:佳丽进包厢立刻换上战袍,料子薄到透光,走两步就让人血脉喷张。 • 🤮全程可撕:战袍就是为撕而生,手起布落,撕到只剩小内内,玩得够狠才算合格。 • ❌熄灯环节:全场一黑,暧昧声此起彼伏,光靠想象就能冲击极限。 • 📱📱📱200➕在岗:175+模特、学生兼职、制服御姐,每天都有不同面孔给你惊喜 • 💋游戏不断:吹瓶、换妻 互撕、换装、PK,边喝边撕边笑,📱氛围直接封神。 ------------------------------- 联系客服:@BST899 双向机器人: @BST899_bot 客服电话:16218003333 微信: jj16561 #北京商k #北京KTV #北京游戏场 #北京摸摸唱 #北京商务KTV
昵称:#欲梦 地区:#西大望路 点击下方评论👇,查看老师详细资料
昵称:#娜漫 地区:#朝阳 点击下方评论👇,查看老师详细资料
❤1
昵称:#婉清 地区:#天通苑 点击下方评论👇,查看老师详细资料
❤1
昵称:#小桃气 地区:#丰台 点击下方评论👇,查看老师详细资料
❤1
#频道互推 #相似推荐 ------------------------------ 📢 惠州太子宫 📢 昆明·凯迪拉克【验证公开榜】 📢 苏州•苏妃阁 📢 武汉 红牌 📢 厦门佳人 📢 北京首府 📢 重庆资源 📢 杭州风情 📢 广州-向日葵 📢 南京美女屋 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
昵称:#榴莲 地区:#丰台 点击下方评论👇,查看老师详细资料
❤1
昵称:#舒瑶 地区:#丰台 点击下方评论👇,查看老师详细资料
❤1
昵称:#倩儿 地区:#朝阳 点击下方评论👇,查看老师详细资料
❤2
昵称:#宁可欣 地区:#朝阳 点击下方评论👇,查看老师详细资料
❤2
昵称:#锁锁 地区:#朝阳 点击下方评论👇,查看老师详细资料
❤1
Showing the 12 most recent of 80 posts we hold for @BJbmxc168. 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
@BJbmxc168 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
- 18 October 2026
- Most recent edit
- 19 October 2026
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@BJbmxc168 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 4 posts, 9 September 2026 – 18 September 2026 · confirmed gone 27 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“北京便民” (@BJbmxc168), 45,659 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/BJbmxc168.
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.