小苍井 身高 165 体重 96 🐻36D 小蛮腰 大桃子 可御 可萝莉 地址: 化工路 联系TG: @qdd628 双向机器人: @xiaocjbot 个人频道: https://t.me/xiaocangjing629

Channel
北京娱乐修车资源库
@fgdbhrthr
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
32,984subscribers
+4,405 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002116856671 |
|---|---|
| Type | Channel |
| Username | @fgdbhrthr |
| Description | 北京聊天交友平台,为群友老师提供公平聊天环境。谨防被骗 北京娱乐修车大队 https://t.me/nanjinghongjiu |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/fgdbhrthr |
Topic
Adult — 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 98% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:17 | 32,984 | +366 |
| 15 Sept 2026, 05:55 | 32,618 | +282 |
| 13 Sept 2026, 12:20 | 32,336 | -31 |
| 11 Sept 2026, 19:36 | 32,367 | +296 |
| 9 Sept 2026, 08:57 | 32,071 | +509 |
| 6 Sept 2026, 03:57 | 31,562 | +426 |
| 3 Sept 2026, 22:39 | 31,136 | +93 |
| 2 Sept 2026, 14:09 | 31,043 | +216 |
| 1 Sept 2026, 16:46 | 30,827 | +169 |
| 31 Aug 2026, 14:48 | 30,658 | +134 |
| 30 Aug 2026, 14:58 | 30,524 | +102 |
| 29 Aug 2026, 16:54 | 30,422 | +141 |
| 28 Aug 2026, 19:24 | 30,281 | +148 |
| 27 Aug 2026, 19:17 | 30,133 | +172 |
| 26 Aug 2026, 19:27 | 29,961 | +168 |
| 25 Aug 2026, 17:07 | 29,793 | +55 |
| 24 Aug 2026, 16:02 | 29,738 | +180 |
| 22 Aug 2026, 23:17 | 29,558 | +90 |
| 21 Aug 2026, 16:22 | 29,468 | +52 |
| 20 Aug 2026, 15:24 | 29,416 | first reading |
Engagement
11 posts held, back to 8 June 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 49 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.47%
- avg views ÷ 32,984 subscribers
- Avg views / post
- 1,140
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 11 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.
| Window | Rolling 30 days · latest post in window 16 September 2026 |
|---|---|
| Posts held | 11 (8 June 2026 – 16 September 2026) |
| Views total | 3,434 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Sept 2026, 17:33 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
- ≈1,930
- Videos
- ≈262
- Links
- ≈133
Lifetime counters from Telegram’s own channel header, read 21 September 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
- 1m 38s
- Average length
- 10s
Measured directly from 10 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
【精品推荐】 北京商K、北京KTV 及北京游戏场所。 签到人数逾80人,服务态度热情周到,提供帝王级尊享体验。 注重情绪价值的提供,倒酒、剥瓜子及贴身热舞等服务项目。 价格透明,酒水消费合理,主打经济实惠,确保顾客娱乐体验愉快。 北京极具娱乐性的KTV及情趣游戏场所,游戏内容精彩且具刺激性。 北京商k最好玩的KTV,情趣游戏场,项目好玩刺激 ------------------------------- 联系客服:@BST899 双向机器人: @BST899_bot 客服电话(同微):13127723272 (支持U支付) #北京商K #北京KTV
😂北京摸摸唱KTV-死摸死亲❗️ 如果你觉得摸摸唱只是喝酒😏🍻+摸一摸❓ 那你就真的只体验到了冰山一角🥳 摸🥵只是最基础的互动👅 👅氛围到位,🍓互动才是重点🥵 🍓各种互动游戏🍓欢乐不断🍓 包厢里想怎么玩就怎么玩🍓气氛直接拉满😀 😀😀😀😀🌼💛😀😀😀😀😀 💕兄弟聚会🤩生日小酌🤩下班放松🤩 🔥来这里图的就是一个开心💞尽兴、放松🥂 来一次🤩你就知道为什么这么多兄弟反复来玩✨ 🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣 😱提前订房🏗少排队,🏗早点来选择更多! 🧴🛎🧺🧺🧺🧺🧺 ✈️:@sk15010512321 频道:https://t.me/beijingSk888888 双向:@Beijing9998_bot 📞:15028718237同🌍 #北京摸摸唱 #北京ktv #北京商k预定
倩倩 年龄:25岁 身高:168 熊:36c 皮肤白皙光滑细腻 1000P 60分钟 1500PP 90分钟 地址: 朝阳区 国家体育场附近 联系TG:@chenchen1789 机器人:@Bbchene_bot 个人频道: https://t.me/bjinchenchen
娇娇 和表妹 特色双飞:1200两次90分钟 身高:167cm 年龄:29 南方人 🐻 :D【纯天然】 👙体重:49kg 坐标:朝阳 草房 ⏰:600 P (50min) ⏰:1000 PP(90min) ✈️: @biaimei222 双向机器人: @fyiyfdbot QQ:310786184
😂北京摸摸唱KTV-死摸死亲❗️ 如果你觉得摸摸唱只是喝酒😏🍻+摸一摸❓ 那你就真的只体验到了冰山一角🥳 摸🥵只是最基础的互动👅 👅氛围到位,🍓互动才是重点🥵 🍓各种互动游戏🍓欢乐不断🍓 包厢里想怎么玩就怎么玩🍓气氛直接拉满😀 😀😀😀😀🌼💛😀😀😀😀😀 💕兄弟聚会🤩生日小酌🤩下班放松🤩 🔥来这里图的就是一个开心💞尽兴、放松🥂 来一次🤩你就知道为什么这么多兄弟反复来玩✨ 🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣 😱提前订房🏗少排队,🏗早点来选择更多! 🧴🛎🧺🧺🧺🧺🧺 ✈️:@sk15010512321 频道:https://t.me/beijingSk888888 双向:@Beijing9998_bot 📞:15028718237同🌍 #北京摸摸唱 #北京ktv #北京商k预定
倩倩 年龄:25岁 身高:168 熊:36c 皮肤白皙光滑细腻 1000P 60分钟 1500PP 90分钟 地址: 朝阳区 联系TG:@chenchen1789 机器人:@Bbchene_bot 个人频道: https://t.me/bjinchenchen
艺名:兔兔H 课费:1500p 3000pp 位置:北京朝阳 电报: @wsdbaby_bot 频道:https://t.me/aimi1314009 频道:https://t.me/Babyxxbb8866
北京商k北京KTV北京情趣游戏场 签到80+,亲摸不躲,热情似火 帝王级享受 📱📱📱📱 📱 📱 📱 📱 📱 情绪价值拉满,从倒酒剥瓜子到贴身热舞 沙发秀,高山流水,冰火,九宫格,舌尖缠编全程零冷场,玩到你腿软关键不乱加价,做的口碑服务一流 价格透明 酒水不贵 主要经济实惠玩的开心 北京最好玩的KTV,情趣游戏场,游戏精彩刺激 ------------------------------- 联系客服:@BST899 微信客服:jj16561 双向机器人: @BST899_bot 频道展示 @BST88999 客服电话:13127723272 (支持U支付) #北京商K #北京KTV #北京商务KTV #北京游戏场
➡️😆北京摸摸唱 😄👈 ☺️单刷 兄弟局 商务接待兼职 00后 大学 妹子多 🥛挺 屁股翘 妹子,年纪小,活泼,开放。 🥰🥰🥰🥰🥰🥰🥰🥰🥰 ☺️ 乃头都是粉色的,情趣游戏,贴身服务,能亲 能摸,包你玩得开心。全场妹子随便摸亲,解衣,亲乃子,舌吻,各种特色玩法游戏。 主打00后 每天到场美女100+海选 🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰 🔴订房联系 @ktv666889 🟢微信SKI92566 🔴双向机器 @beijingSK_bot 🟢 频道链接 https://t.me/SKI92588 #北京真空游戏场 #北京ktv #荤场KTV #北京游戏场 #北京商k
晓晓 蒙古妹子 身高 166cm 体重108 微微胖 皮肤白皙 FW 好 特色: 月工 交 3通 SM 地址: 朝阳区 联系TG: @kpl97643 机器人: @kpl97643_bot 个人频道: https://t.me/kplxx0097
Showing the 11 most recent of 11 posts we hold for @fgdbhrthr. 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
@fgdbhrthr 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
- 15 August 2026
- Most recent edit
- 15 August 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“北京娱乐修车资源库” (@fgdbhrthr), 32,984 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/fgdbhrthr.
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.