Telegram RegisterThe public register of Telegram
Telegram profile photo for 北京 东部地区(朝阳 通州)

Channel

北京 东部地区(朝阳 通州)

@bjdbdq

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

11,485subscribers

+48 since we began measuring on 10 November 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002307606998
TypeChannel
Username@bjdbdq
Description花满楼管理员 @bopnp_bot 【花满楼 主群】 @huamanlou_beijing 【花满楼 男群】 @bopnp 【花满楼优惠榜】 @hhmly 【老师频道】 @acosb 【好评频道】 @huamanlou_beijing_post 【中小项】 @bjzxx 【一键关注 花满楼所有群组】 t.me/addlist/rR1FOnT1wY1mYzFk
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 November 2026
Last confirmed live12 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/bjdbdq

Topic

Adult — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 13 November 2026 and assigned it the closest of 31 fixed categories, at 50% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hmlbi/1520111 Nov 2026, 07:04 UTC@bjdbdq/13410 · this entry11 Nov 2026, 07:10 UTC1.006 minutes
@hmlbi/1521011 Nov 2026, 15:45 UTC@bjdbdq/13428 · this entry11 Nov 2026, 15:46 UTC1.0072 seconds
@hmlbi/1521911 Nov 2026, 15:47 UTC@bjdbdq/13437 · this entry11 Nov 2026, 15:52 UTC1.005 minutes
@hmlbi/1522511 Nov 2026, 16:01 UTC@bjdbdq/13443 · this entry11 Nov 2026, 16:03 UTC1.002 minutes
@hmlbi/1524812 Nov 2026, 07:48 UTC@bjdbdq/13486 · this entry12 Nov 2026, 07:51 UTC1.003 minutes
@hmlbi/1527712 Nov 2026, 14:28 UTC@bjdbdq/13524 · this entry12 Nov 2026, 14:32 UTC1.004 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@hmlbi7 (7/7 hand-verifiable sample passed)1.003 minutes@hmlbi (7–0)
@acosb7 (7/7 hand-verifiable sample passed)1.00under a minute@acosb (5–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 12 of the 12 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 10 November 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @hmlbi. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

11,43711,48511,46110 November 2026 — 11,437 subscribers10 November 2026 — 11,437 subscribers12 November 2026 — 11,485 subscribers10 November 202612 November 2026
3 measurements spanning 2 days, net +48. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11,430–11,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 20:3811,485+48
10 Nov 2026, 21:2211,437no change
10 Nov 2026, 20:4711,437first reading

Engagement

17 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 · 30 days
0.428%
avg views ÷ 11,485 subscribers
Avg views / post
49.1
17 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
17
of 17 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 November 2026
Posts held17 (10 November 2026 – 13 November 2026)
Views total835
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 10:04 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

Photos
≈2,450
Videos
≈325
Links
≈398

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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 07s
Average length
11s

Measured directly from 12 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 17 posts held from the last 30 days (11.8%) 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).

13 Nov 2026, 08:39 UTC19 viewsread 13 November 2026
Photo

💚 露露 📍 #朝阳区 |呼家楼 😈 岁|身高|罩杯 ✈️ @alen_wangy ⚡️ @LL1357924680_bot 💰 400 收到 4 个评价 😀 点击我查看评价 标签 中小项 服务 抓龙筋、足交 1️⃣ ⚠️ 中小项 无大 中式按摩与泰式抓龙筋的结合,手法专业且力度到位。在进入闺房环节后,通过魔指仙境与丰臀碾压提供极强的身体包裹感,水漫程度高且生理反馈真实。尤其是丝袜足交与手交的衔接,吞吐技巧纯熟,能给到非常直接的紧致吸附力。 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

13 Nov 2026, 07:02 UTC36 viewsread 13 November 2026
Photo

💚 安然 📍 #朝阳区 |京铁瑞园 😈 26岁|身高165|罩杯 D ✈️ @Lst6555 ⚡️ 💰 800 标签 御姐 服务 鸳鸯浴、胸推、按摩、69、舌吻、毒龙 1️⃣ 皮肤光滑 腰细屁股 热情体贴 配合度高 服务天花板 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

13 Nov 2026, 04:40 UTC44 viewsread 13 November 2026
Photo

💚 奶茶 📍 #朝阳区 |呼家楼 😈 岁|身高165|罩杯 C ✈️ @q3625667694 ⚡️ @Naicha55bot 💰 600 标签 御姐、中小项 服务 胸推、臀推、阴推、足交、毒龙 1️⃣ 身高165休重94 C杯敏感休质 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

12 Nov 2026, 15:38 UTC42 viewsread 12 November 2026
Photo

💚 白昕昕 📍 #朝阳区 |朝阳北1号花园 😈 岁|身高175|罩杯 D ✈️ @baizinxin ⚡️ 💰 2600 标签 嫩妹、大长腿 服务 舌吻、可车震、69 1️⃣ 知名高校 在校子生 英语无障碍沟通 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

12 Nov 2026, 14:32 UTC44 viewsread 12 November 2026
Photo

💚 糯米 📍 #朝阳区 |大郊亭 😈 18岁|身高160|罩杯 D+ ✈️ @nuomi1314521 ⚡️ 💰 1300 标签 御姐 服务 舌吻、69、鸳鸯浴、上门 1️⃣ 天然大胸 真人真照 情商高 自带性感 性格超好清纯可爱 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

12 Nov 2026, 10:10 UTC72 viewsread 12 November 2026
Photo

💚 止止 📍 #朝阳区 |百子湾 😈 19岁|身高160|罩杯 36B ✈️ @zhimei1102 ⚡️ @zhimei1102BOT 💰 1300 🏡 :报花满楼 优惠 200 需要写作业反馈 备注:花满楼 收到 2 个评价 😀 点击我查看评价 标签 可爱、三点粉 服务 鸳鸯浴、制服诱惑、胸推、臀推、深喉、水中箫、69 1️⃣ 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

12 Nov 2026, 08:27 UTC17 viewsread 12 November 2026
Photo

💚 奶猫 📍 #朝阳区 |双井 😈 25岁|身高165|罩杯 E ✈️ @naimao69 ⚡️ 💰 1500 标签 御姐、巨乳 服务 口交、69、舌吻、上门 1️⃣ 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

12 Nov 2026, 07:51 UTC24 viewsread 12 November 2026
Photo

💚 美羊羊 📍 #通州区 |万达 😈 25岁|身高160|罩杯 B+ ✈️ @meiyangyang297 ⚡️ 💰 800 标签 御姐 服务 鸳鸯浴、指划、胸推、69、口交 1️⃣ 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

12 Nov 2026, 07:16 UTC24 viewsread 12 November 2026
Photo

💚 知念 📍 #朝阳区 |芍药居 😈 29岁|身高168|罩杯 C+ ✈️ @zhinian221 ⚡️ @zn221bot 💰 600 收到 7 个评价 😀 点击我查看评价 标签 御姐 服务 臀推、足交、乳交、漫游、花式吹箫、深喉、69 1️⃣ 芍药居地铁站A口附近步行3.4分钟 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

11 Nov 2026, 16:03 UTC31 viewsread 11 November 2026
Photo

💚 韩小衣 📍 #朝阳区 |九龙山 😈 岁|身高170|罩杯 C ✈️ @hanxiaoyi11 ⚡️ @Hanyi12bot 💰 1200 收到 1 个评价 😀 点击我查看评价 标签 御姐 服务 毒龙、胸推、深喉、69、角色扮演、艳舞 1️⃣ 长相甜美 皮肤光滑 大长腿 听话 热情主动 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

11 Nov 2026, 15:52 UTC32 viewsread 11 November 2026
Photo

💚 艾雪 📍 #朝阳区 |金台路 😈 岁|身高165|罩杯 C+ ✈️ @aixue226666 ⚡️ @aixueai_bot 💰 1300 标签 御姐 服务 鸳鸯浴、调情、舌吻、69、冰火两重天、口爆、艳舞、角色扮演 1️⃣ 个人自聊、人照一致、可甜可御、可车、可空降、可伴游、情绪体感拉满 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

11 Nov 2026, 15:46 UTC34 viewsread 11 November 2026
Photo

💚 王茜 📍 #朝阳区 |大望路 😈 24岁|身高171|罩杯 F ✈️ @Waqq6869 ⚡️ @Waqq6869_bot 💰 3000 收到 12 个评价 😀 点击我查看评价 标签 御姐、大长腿 服务 胸推、乳交、舌吻、深喉 1️⃣ 极品大蜜健身达人 F杯浑圆坚挺 全身皮肤白皙光滑 精致御姐脸 漫画身材 S曲线丰乳肥臀 🎀关注花满楼所有群组 @acohx 🎀老师上榜 投稿报告找 @bopnp_bot

Showing the 12 most recent of 17 posts we hold for @bjdbdq. 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.

Mentions

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.

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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“北京 东部地区(朝阳 通州)” (@bjdbdq), 11,485 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/bjdbdq.

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.