Channel
@bjbbdq
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
11,061subscribers
+28 since we began measuring on 10 November 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002174078656 |
|---|---|
| Type | Channel |
| Username | @bjbbdq |
| Created | Between 1 June 2024 and 30 September 2024 — 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/bjbbdq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 03:11 | 11,061 | +28 |
| 10 Nov 2026, 21:22 | 11,033 | no change |
| 10 Nov 2026, 20:47 | 11,033 | first reading |
7 posts held, back to 10 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 13 November 2026 |
|---|---|
| Posts held | 7 (10 November 2026 – 13 November 2026) |
| Views total | 1,337 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 10:26 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 5 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.
Telegram’s own ‘edited’ marker: 0 of 7 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).
📍 #朝阳区 立水桥 💚 婉梦 ✈️ @wanmeng9 ⚡️ 💰 1200 (联系请备注:花满楼 ) ✍️ 皮肤白、白虎、御姐 鸳鸯浴、水中箫、指划、漫游、丝袜诱惑、舌吻、口爆、69、胸推、抓龙筋、高跟鞋诱惑、制服诱惑、冰火两重天、吸蛋蛋、深喉、臀推、阴推、性玩具 1️⃣ 白虎没有毛毛 我皮肤非常好，光滑如玉嘿嘿，算是个小白虎，天生体毛稀少，属于冷白皮 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 乔曼 📍 #朝阳区 |亚运村 😈 22岁|身高168|罩杯 D ✈️ @qm0055 ⚡️ @qiaoman_bot 💰 1500 收到 4 个评价 😀 点击我查看评价 标签 白虎、潮喷 服务 可外出、鸳鸯浴、口交、舌吻、舔奶头、调情 1️⃣ 发育好,真实器粉嫩小豆豆,下紧粉嫩,可调教, 听话配合~口活 好,无齿感,潮喷是看家本领，一紧一夹让你特舒服 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 樱桃 📍 #朝阳区 |望京 😈 岁|身高165|罩杯 ✈️ @ying393 ⚡️ @ying393bot 💰 700 标签 御姐 服务 舌吻、口交、深喉、69、胸推、臀推、漫游、按摩、可上门 1️⃣ 刚来北京的湘妹子、莞式服务，包夜不啪啪不限次 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 露莎 📍 #朝阳区 |朝阳北路 😈 20岁|身高170|罩杯 36C ✈️ @lusha8888 ⚡️ @lusha888bot 💰 1000 标签 嫩妹、混血 服务 调情、鸳鸯浴、舌吻、口交、69、吸蛋蛋、丝袜诱惑、可上门 1️⃣ 服务主动、温柔似水、敏感水多、乖巧听话、叫声甜美、服务细致、女友式服务体验 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 沐UU 📍 #朝阳区 |望京 😈 25岁|身高167|罩杯 C ✈️ @muyouyou6 ⚡️ @youyoumu11_bot 💰 1200 标签 御姐 服务 鸳鸯浴、接吻、口交、69、胸推、臀推、情趣诱惑、丝袜诱惑 1️⃣ 来自四川 皮肤白皙 服务超棒 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 刘菲菲 📍 #朝阳区 |亚运村 😈 身高160|罩杯 C ✈️ @feifei0088996 ⚡️ @feifei008899667bot 💰 600 收到 2 个评价 😀 点击我查看评价 标签 御姐 服务 鸳鸯浴、口交、丝袜诱惑、制服诱惑、指划、调情、漫游、刮痧 1️⃣ 南方妹子 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
💚 柯心 📍 #朝阳区 |望京 😈 身高170|罩杯 ✈️ @kexin5188 ⚡️ @kexin5188_bot 💰 799 标签 中小项、大长腿 服务 抓龙筋、角色扮演、丝袜诱惑、制服诱惑、舌滑、足交 1️⃣ 擅长丝足 恋足 大长腿 性感御姐 专业; 足交; 抓龙筋🐉 延时脱敏 三起三落; 前例腺高超; sm调教 角色扮演; 口水; 耳光 羞辱 骑士坐脸 鬼头责 遛狗 钻胯 马眼让你得到全身心的放松解压 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot
Showing the 7 most recent of 7 posts we hold for @bjbbdq. 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.
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.
“北京 北部地区(大屯 亚运村 立水桥)” (@bjbbdq), 11,061 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/bjbbdq.
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.