Channel
@bjxbdq
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
10,319subscribers
+44 since we began measuring on 10 November 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002468050832 |
|---|---|
| Type | Channel |
| Username | @bjxbdq |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 November 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/bjxbdq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 17:58 | 10,319 | +44 |
| 10 Nov 2026, 21:22 | 10,275 | no change |
| 10 Nov 2026, 20:47 | 10,275 | first reading |
7 posts held, back to 8 November 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 6 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 12 November 2026 |
|---|---|
| Posts held | 7 (8 November 2026 – 12 November 2026) |
| Views total | 1,693 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 11:06 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.
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
Telegram’s own ‘edited’ marker: 2 of 7 posts held from the last 30 days (28.6%) 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).
💚 水水 📍 #丰台区 |西局 😈 岁|身高|罩杯 F ✈️ @xiaoxiao19197 ⚡️ 💰 600 收到 1 个评价 😀 点击我查看评价 标签 巨乳 服务 毒龙、鸳鸯浴、漫游、莞式、臀推、胸推、阴推、69、口爆 1️⃣ 新人下海,天然F大胸,邻家小妹,情绪 价值拉满,走心水多易高潮可喷,口活细致,宝 贝喜欢的玩法都可以配合、情趣互动、高跟鞋丝 袜诱惑,粘人、性欲强、 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 雅琪 📍 #西城区 |西直门 😈 26岁|身高162|罩杯 C ✈️ @xizhimenyaqi520 ⚡️ @yaqi6688_bot 💰 1200 标签 御姐 服务 臀推、冰火两重天、69、口交 1️⃣ 正规莞式服务 不议价 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 亚 📍 #西城区 |石景山 😈 岁|身高163|罩杯 C ✈️ @anmoshang ⚡️ @yycqcbot_bot 💰 600 标签 御姐、服务系 服务 按摩、指划、胸推、舌滑、冰火两重天、69 1️⃣ 妹妹来自南方、皮肤白、服务态度好、无套路、配合度高 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 小红 📍 #海淀区 |牡丹园 😈 岁|身高170|罩杯 B ✈️ @ggjkm123 ⚡️ @wzf1991bot 💰 600 收到 14 个评价 😀 点击我查看评价 标签 中小项、大长腿 服务 69、冰火两重天、口爆、毒龙、胸推、抓龙筋、spa 1️⃣ 御姐风 全果 口技员 69 阴推 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 悦悦 📍 #海淀区 |西土城 😈 23岁|身高165|罩杯 36E ✈️ @yueyue52069 ⚡️ @yueyue1230629_bot 💰 1200 标签 御姐、巨乳 服务 毒龙、口交、莞式 1️⃣ 悦悦正规莞式服务 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 甜甜 📍 #海淀区 |双榆树东里 😈 26岁|身高162|罩杯 D+ ✈️ @SophiaWhite_s ⚡️ @dfffh_bot 💰 600 收到 7 个评价 😀 点击我查看评价 标签 中小项 服务 鸳鸯浴、按摩、胸推、口交、深喉、69、毒龙 1️⃣ 年纪小、皮肤白，本人比照片耐看。性格温柔、乖巧懂事、不偷懒、不催不急，高端会所里的服务 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 伊雪 📍 #海淀区 |双榆树 😈 24岁|身高1600|罩杯 C+ ✈️ @dffggiu ⚡️ @dffghji_bot 💰 600 收到 8 个评价 😀 点击我查看评价 标签 中小项 服务 鸳鸯浴、水中箫、口痧、胸推、口交、深喉、69、毒龙、丝袜诱惑 1️⃣ 性格开朗，活泼，温柔，大方，身材好，活好，各种花式口，中项无大，女友感觉 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
Showing the 7 most recent of 7 posts we hold for @bjxbdq. 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.
@bjxbdq 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.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“北京 西部地区(西城 海淀 石景山)” (@bjxbdq), 10,319 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/bjxbdq.
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.