Channel
@bjmengbb
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
9,015subscribers
+56 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002258465500 |
|---|---|
| Type | Channel |
| Username | @bjmengbb |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/bjmengbb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:05 | 9,015 | +27 |
| 11 Aug 2026, 14:08 | 8,988 | +31 |
| 8 Aug 2026, 14:24 | 8,957 | -2 |
| 7 Aug 2026, 16:01 | 8,959 | no change |
| 7 Aug 2026, 15:53 | 8,959 | first reading |
18 posts held, back to 7 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 13 pagesof 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 August 2026 |
|---|---|
| Posts held | 18 (7 August 2026 – 12 August 2026) |
| Views total | 11,317 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 15:44 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.
Measured directly from 6 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.
🚘修车铺8.7特惠款🚘 #朝阳 #百子湾 #亲民大众系 04年的青春大白软，身高174🐻天然D，体重125+，标准BBW。长相甜美，气质温柔。🉑🐍🉑品🉑亲咪咪，性价比超级绝。现承诺给修车铺司机们独家尝鲜特惠三天，全场减100；优惠后7️⃣张次。截止日期8月15号。 橘子 TG：@juzi90 个人简介：https://t.me/bjmengbb/7703 【验证必须备注：69号修车铺，方可享独家优惠】
8.12更新 橘子 【独家首发】【个人 #00后 】【174D白软嫩妹】【青春BBW】 #朝阳 #百子湾 #亲民大众系 04年的青春大白软，身高174🐻天然D，体重125+，标准BBW。长相甜美，气质温柔。 全场温柔如女友，全程听从指挥。🉑🐍🉑品🉑亲咪咪，不做作不矫情。各种姿势超耐干，性价比超级绝；8️⃣张次 TG：@juzi90 【备注：69号修车铺】
8.11更新 小乖 【独家播报】【个人 #05后 】【学妹白🐯】【🉑轻度SM】 #朝阳 #东二环 #中档精英系 06年的天津乖乖妹，新鲜下海。清纯可爱，天然C杯蜜桃臀。正宗白🐯，全身无整。 有M倾向的小女友，乖巧听话，任由摆布。🉑🐍💋🉑六九，🉑3P🉑轻度SM🉑拍视频。全场尽兴，惊喜不断；1️⃣5️⃣张次 TG：@xggsss 【备注：69号修车铺】
8.11更新 菜菜 【独家播报】【 个人#05后 丝足】【大学刚毕业】【玲珑小脚】 #朝阳 #大悦城 #中小 05年南方小妞，大学刚毕业。身材玲珑小巧，体重未达90，脚36码。主打丝足恋足，情趣式小项。三起三落，足胶腿胶，女王调教样样皆🉑；8️⃣张起 TG：@caicai399 【备注：69号修车铺】
8.11更新 艾草 【独家播报】【 个人 #95后 按摩騷女】【酥爽小项】【抓🐉筋】 #昌平 #抓龙筋 #中小 风情小騷姐，专业按摩女。妩媚温柔，超懂男人。主打居家小项保健，专业手法经络调理。擅长抓🐉筋，三起三落，全身酥爽；6️⃣张70分钟 TG：@aicao99 【备注：69号修车铺】
8.10更新 豆豆同学 【独家首发】【个人 #05后 】【168C粉嫩】【🉑🐍🉑品】 #丰台 #宋家庄 #中档精英系 19岁清纯小妞崽，满满少女感。身高168+饱满C杯，皮肤白嫩，毛少馒头穴，三点粉嫩水滋滋。 乖巧听话不事比，活泼开朗小女友。🉑🐍💋🉑六九，亲亲互舔不停歇。情绪价值到位，全程不机车，超有征服感；1️⃣3️⃣张次 TG：@doud688 【备注：69号修车铺】
8.10更新 玥玥 【独家播报】【个人 #95后 】【D杯小騷姐】【居家中项】 #朝阳 #潘家园 #中小 妙龄小騷姐，新鲜下海。天然D罩杯，气质妩媚，风情迷人。主打居家中项，🉑按摩🉑独🐉，🉑包时🉑包夜。项目全面灵活，情绪价值到位；中项5️⃣张60分钟 TG：@dyujgffg 【备注：69号修车铺】
8.10更新 琪琪 【独家播报】【个人 #95后 】【170长腿騷妞】【居家中尺】 #朝阳 #潘家园 #中小系 邻家小騷，身高一米七。颜值温柔，气质甜美，身材白皙无纹身。主打居家中尺，🉑独🐉🉑👅蛋，🉑包时🉑包夜，酥麻入骨超实惠；中项5️⃣张60分钟 TG：@AndrejKlimov_HS 【备注：69号修车铺】
6⃣修车铺新品系列展9⃣ 🚗特色主题每日甄选🚗 漂亮可人颜值高系列： 1️⃣劲松 24岁青春颜系小御姐身高170+天然E罩杯温柔女友 2️⃣三元桥 极品美御姐尤物🐄168G杯三十如狼战斗力爆表 3️⃣大郊亭 成都美御姐诱惑S款手法专业技法一流抓🐉筋 4️⃣成寿寺 21岁娇俏嫩货青春可爱🉑🐍🉑品敏感易高潮 5️⃣南磨房 19岁青春小靓妹169天然柔体🉑🐍🉑品尝鲜特惠中 🚘更多香车请看👉8️⃣月开课🏮香车榜①🚘 🚘更多香车请看👉8️⃣月开课🏮香车榜②🚘 🚘更多香车请看👉8️⃣月开课🏮香车榜③🚘 🚘更多香车请看👉8️⃣月开课🏮香车榜④🚘 🚘特惠香车请看👉福利不断😍特惠💰香车榜🚘 🚘中小香车请看👉8️⃣月中小🈚️大香车榜①🚘 🚘中小香车请看👉8️⃣月中小🈚️大香车榜②🚘 🚘名牌香车请看👉8️⃣月开课🏮名车榜🚘 🚘本周好评请看👉名车五星榜 👉新品五星榜🚘 👉修车铺小二💡为你指路
8.9更新 Jackie_进口酒业 【独家播报】【🇲🇳留子洋酒】【活力四射】【青春无敌】 #东四环 #中档精英系 蒙古国舞蹈生，在京留学，年芳十九。苗条S款，电臀达人，BB紧致。会说中文英语，交流没问题。性格开朗，热情大方。🉑kiss🉑六九，青春无敌爽。 现承诺给修车铺司机们独家尝鲜特惠，P15-1；优惠后1️⃣4️⃣张次 客服TG：@xxx_jackie 【备注：69号修车铺】
6⃣修车铺新品好评展9⃣ 🚗人气款每周五星榜🚗 ⭐️⭐️⭐️⭐️⭐️ 8月第2周： 1️⃣草房 23岁兼职模特身高175大长腿超紧B性价比高 2️⃣大悦城 云南青春软妞夜场小太妹D杯🉑艳舞🉑陪酒🉑3通 3️⃣双井 03年的纯欲小女神白皙嫩妹纯欲天花板🉑🐍🉑品 4️⃣亚运村 32岁温柔小少妇热情大方料足水多泻火好去处 5️⃣蒲黄榆 04年的南方姑娘萝莉音又纯又嗲主打情趣小项 6️⃣苏州街 邻家美騷姐五官端正身材有料口💥中尺大湿 7️⃣育新站 火辣小御姐身高168+天然C杯花式中小挑逗 8️⃣回龙观 热情辣妹身高170长腿御姐S款情趣小项 9️⃣西土城 妙龄御姐苗条辣妹舌漫金三角中尺专项 🌸香车已全部进驻本铺 🚘总部 @bjmengnb ⭐️新款分铺 @bjmengbb 🚗总群 @bjmeng 👍名车分群 @bjmingc 💰特惠分群 @bjtehui 👠中小分群 @bjsmall 🛞备用分群 @bjmengg ⚠️防骗分铺 @…
8.8更新 雨婷 【独家首发】【个人 #00后 】【F杯青春甜妹】【情趣制服多样】 #朝阳 #广渠门 #中档精英系 01年的青春小甜妹，身高167，天然F杯。细腻冷白皮，纯欲兼得，不吸烟无纹身。 温柔服务控，🉑🐍💋🉑六九，🉑深🐵🉑口💥。深度调情，轻度SM，自蔚潮吹样样行。人照致，真实刺激；1️⃣2️⃣张起 TG：@yutinga 【备注：69号修车铺】
Showing the 12 most recent of 18 posts we hold for @bjmengbb. 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.
Citation-graph rank — 160,695 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 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.
@bjmengbb 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.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“北京69号修车铺【新款分铺】” (@bjmengbb), 9,015 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/bjmengbb.
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.