Channel
@wuhanbg
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,639subscribers
-34 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001874241615 |
|---|---|
| Type | Channel |
| Username | @wuhanbg |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/wuhanbg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 15:22 | 3,639 | -33 |
| 8 Aug 2026, 04:55 | 3,672 | -1 |
| 7 Aug 2026, 17:17 | 3,673 | no change |
| 7 Aug 2026, 17:03 | 3,673 | first reading |
20 posts held, back to 22 July 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 2 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. It is computed over the 9 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (22 July 2026 – 7 August 2026) |
| Views total | 28,207 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:23 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.
9 reactions across 9 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 9reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：小白G 【验证时间】：8.7 【老师花名】：瑶欣儿 【所在区域】：南湖 【老师电报】：https://t.me/whww5488 【修车水费】：16PP 【人照几成】：9.5 【身高体重】：169 50 【凶器罩杯】：C 【老师类型】： 女友 【服务类型】：(洗吹做 舌吻 69 服务很好） 【服务详情】：看到瑶欣儿老师，对我很有吸引力，果断约上，到地方老师遥控上楼，进门一看基本和照片没啥差距，长相很好看，身材超级好，穿衣显瘦，脱衣有肉，抱起来软软的。洗完就一起进了房间，服务过程能感受到用心，抱着互相抚摸会有很自然的反应，就跟女友一样，笑起来也是如沐春风，前戏后很快都进入了状态，整个过程行云流水，各种姿势都很配合，在一声声中喘息中交出了货。完事后也一点不催，会陪着一起休息聊聊天。总之是值得一去的。 缺点：反差型, 优点: 【推荐程度】：5星 【温馨…
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：亮亮 【验证时间】：8.6 【老师花名】：瑶欣儿 【所在区域】：南湖 【老师电报】：https://t.me/whww5488 【修车水费】：16PP 【人照几成】：9.2 【身高体重】：170 48 【凶器罩杯】：C 【老师类型】： 女友 【服务类型】：(洗吹做 舌吻 69 服务很好） 【服务详情】：二刷瑶欣儿老师，本人很少二刷，老师绝对颜值身材态度服务全面到位，无敌的存在。老师位置好找，好停车，指引上楼很安全。工作室很干净，然后帮洗澡，出来后 小弟我受不了叫帮我口 然后趴在床上 口的我简直升天，无话可说。口了几分钟实在受不了开始了后入，雪白的大屁股真舒服 5分钟后缴枪 和老师聊了一会，开始了第二次 后面不写啦 服务绝了，态度也到位，没有臭脸，只要老师在武汉，一定三刷。如果兄弟们来了，觉得我夸大，群里可以捶我 缺点：反差型,很好,很美 优点:…
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】： 小新 【验证时间】：8月6日 【老师花名】：苏苏 【所在区域】：南湖 【老师电报】：@xss5210 【修车水费】：16PP 【人照几成】：9.6 【身高体重】：169 95 【凶器罩杯】：C 【老师类型】： 女友 年轻妹子 【服务类型】： 口 舌吻 69 鸳鸯浴 调情 【服务详情】：看到老师的照片很心动，遂决定出击。老师住的是个老小区，比较安全，房间也装了隔音棉。开门见到老师就很惊艳，很好看，身材比例很好，在服务过程中也是很配合很用心，是一次不错的出击体验。 优点: 好看 网红 身材好 【推荐程度】：5星 【温馨提醒】：出击报告具有强烈主观性 聊天群组 @wuhannn 上榜联系 @wuhanpbot
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：S S S 【验证时间】：2026年8月1日 【老师花名】：白蝴蝶 【所在区域】：硚口 【老师电报】：@dg1264 【修车水费】：7P 【人照几成】：9 【身高体重】：168cm,51kg 【凶器罩杯】：D 【老师类型】：御姐 【服务类型】：服务系天花板 【服务详情】：刚到武汉觅食，反复刷了群里成堆的好评报告，才在万花丛中精挑细选锁定了白老师。我是个彻彻底底的极致享受主义者，对服务的要求向来苛刻，而白老师的项目几乎全能，刚好正中我的心巴。 说实话，她的热情程度直接拉满，服务技能更是满分级别。衣着性感又恰到好处，完美勾勒出身材曲线，声音轻柔空灵，听着就让人心里发软。全程我就像个被精心服侍的帝王，几乎不用动手，白老师就把我全身和小兵清洗得干干净净，细致又舒服。房间干净整洁，还带着淡淡清香，氛围拉满。 我特意谎称没看过课程表，就是想试探老师会不会偷偷减项，结果…
❤1
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：F 【验证时间】：2026年7月30日 【老师花名】：白蝴蝶 【所在区域】：硚口 【老师电报】：@dg1264 【修车水费】：14PP 【人照几成】：9 【身高体重】：168cm,51kg 【凶器罩杯】：D 【老师类型】：御姐 【服务类型】：服务系天花板 【服务详情】：关注白老师已经有一段时间了，今天终于有幸约上她的课，果断出击，完全不虚此行。不愧是服务界天花板，服务顶级、态度一流，全程温柔体贴，性价比也超高。房间环境优雅温馨，灯光和布置都恰到好处，让人一进去就彻底放松。 “芙蓉不及美人妆，水殿风来珠翠香。”用这句诗来形容白老师的气质和氛围，真是再合适不过。这次体验太满意了，强烈推荐给想找高质量服务的朋友！ 缺点：🈚 优点:全是优点 【推荐程度】：5星 【温馨提醒】：出击报告具有强烈主观性 聊天群组 @wuhannn 上榜联系 …
❤1
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：Tobago 【验证时间】：2026年7月28日 【老师花名】：白蝴蝶 【所在区域】：硚口 【老师电报】：@dg1264 【修车水费】：10PP 【人照几成】：9 【身高体重】：168cm,51kg 【凶器罩杯】：D 【老师类型】：御姐 【服务类型】：服务系天花板 【服务详情】：一进门就被白老师性感的巨乳吸引了目光，服务不仅舒服而且充满了文化气息，灯光调得很柔和，背景音乐也是慢悠悠的节奏，一进门整个人就立刻安静下来，紧绷的神经一点点被卸掉。 尤其是日式凳浴那个环节，氛围感拉满。朦朦胧胧的灯光下，水汽和温度交织，视觉上就特别享受，整个人像被温柔包裹住一样。 最惊喜的是白老师的按摩手法，真的很到位。按完之后浑身都松快了，酸胀和僵硬感被一点点揉开。而且她特别贴心，按的过程中会不时问我力度和感受，怕太重或太轻，细节照顾得非常细腻。 当她那双又软又暖的手按在身上时…
❤1
聊天群@wuhannn 【验证留名】：背带裤 【验证时间】：26.7.28 【老师花名】：虎泉甜甜 【所在区域】： 虎泉 【老师电报】：@qqamn 【修车水费】：500 【人照几成】：9 【身高体重】：156 78斤 【凶器罩杯】：c+ 【老师类型】：嫩妹 【服务类型】：课表服务都有 【服务详情】：看到老师就觉得很嫩很漂亮，身材也很好，爱了，哈哈。 一起共浴后就开始服务；舔的时候胸一直在身上摩擦，心里痒痒的，迫不及待戴上进入； 抱着做很有感觉，胸部一晃一晃的，绝对的纯天然。老师什么姿势都很配合，她比较喜欢在下面，最后紧紧抱着出水，老师同时也高潮了，水很多，特别舒服，最满意的一次体验，念念不忘。嫩妹就是不一样，嫩妹妹更是不一样 【推荐程度】：4.8 【温馨提醒】：出击报告具有强烈主观性聊天群组上榜联系@wuhannn@wuhanpbot
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：FC 【验证时间】：7.26 【老师花名】：#小兰花 【所在区域】：光谷 【老师电报】：@yumi2045 【修车水费】：6p 【人照几成】：人照一致 【身高体重】：身高162 ，体重48kg 【凶器罩杯】：B 【老师类型】：嫩妹，女友 【服务类型】：看课表 【服务详情】：总体评价直接给到棒极了，进门看到老师，人比照片漂亮多了去，讲话非常温柔，身材优美有型，刚进去就忍不住从后面抱住老师，一顿探索，探索过后，才满足一番。热情邀请鸳鸯浴，水中萧伺候，爽的不要不要的。洗完澡后，迫不及待抱着老师就🐍吻和调情，老师的舌头软软的、滑滑的，然后开始69，下面很粉嫩，有一说一，老师的口技很厉害，感觉要受不不了随机叫停。带套开始，先是女上，非常紧，接着换我，把老师抱起来做（真的很轻、可以轻松抱起来），累了换传教士了，随着老师“淫荡”的叫床声二弟撑不住了发射。😌 缺点：无 优点…
❤1
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】： 威哥 【验证时间】：7月27日 【老师花名】：苏苏 【所在区域】：南湖 【老师电报】：@xss5210 【修车水费】：16PP 【人照几成】：9.7 【身高体重】：167 92 【凶器罩杯】：C 【老师类型】： 女友 年轻妹子 【服务类型】： 口 舌吻 69 鸳鸯浴 调情 【服务详情】：今天刚好有空，又约了苏苏。第一次见她的时候，就觉得是自己喜欢的类型，不是那种刻意包装出来的网红感，而是自然、舒服的漂亮。相处几次下来，反而越来越觉得耐看，她的吸引力不仅来自外表，更多是聊天时的温柔、相处时的放松，以及整体带来的女友感。 优点: 二刷 【推荐程度】：5星 【温馨提醒】：出击报告具有强烈主观性 聊天群组 @wuhannn 上榜联系 @wuhanpbot
❤1
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：小青龙 【验证时间】：7.27 【老师花名】：#梅梅 【所在区域】：光谷 【老师电报】：@meimei2006 【修车水费】：600p 【人照几成】：人照九五分 【身高体重】：162/45kg 【凶器罩杯】：B 【老师类型】：嫩妹 女友 【服务类型】：洗吹做 【服务详情】：约好老师，出发因为路上堵车迟到了几分钟，老师提醒注意安全、见面很热情寒暄几句，去洗澡，出来老师示意选择丝袜，我让老师穿了黑丝🤭，听话配合，口技非常好没有齿感。轮到我这老司机开始服务，先是嘴上索要一番满足过后，顺着奶子一路往下，随后到那小穴，再探讨完69这神奇数字后，带上雨伞进入正题，老师很紧。一上一下也是很配合，随后后入时那夹的更紧了，差点给我套套夹掉了。最后正常老汉推车等一系列结束战斗，肤白🐻嫩手感好且听话配合的一位老师，值得二刷。 缺点：无 优点:长相甜美，姿势配合度高，情绪价值拉满 …
❤1
【店 名】：白月光私影 【营业时间】：下午3:00至凌晨3点 【出击人】：RED 【妹妹花名】：心心 【出击时间】：7月25日晚上10点 【位 置】：光谷店 【联系方式】: @byg7708 【所属频道】： https://t.me/bygsy1717 【价 格 】：999套餐，换了个半价券500拿下 【服务类型】：mmk服务 【反馈报告】：之前也在别的地方玩女仆，武汉的私影没玩过几次，今晚刚好看到光谷心心妹妹在，联系了客服，直接换了个5折券。心心不愧是心心，身材真的很好，看着我就很激动。看到心心的大长腿，想着让心心换上白丝筒袜吧，可惜了腿太长了，白丝只能过膝盖。然后我们就开始了，心心舌吻的时候会响应你，胸的触感真好而且很软，两个葡萄也很粉嫩，只有在受到刺激时才会突出出来。和妹妹激战了一个小时，可惜妹妹亲戚还咩走，不然我不敢想战况会多么激烈，这次我们二人先打了个平手吧，下次再战。一小时很…
武汉修车总群报告模版 聊天群 @wuhannn 【验证留名】：不明白 【验证时间】：2026年7月26日 【老师花名】：白蝴蝶 【所在区域】：硚口 【老师电报】：@dg1264 【修车水费】：9 P 【人照几成】：9 【身高体重】：168cm,51kg 【凶器罩杯】：D 【老师类型】：御姐 【服务类型】：服务系天花板 【服务详情】：再次CJ白老师，LY圈里应该都清楚——能反复N次复购、而且每一次都忍不住回来的，含金量到底有多高。 LS真的太优秀了，或者说，“优秀”这两个字根本不够用。白老师身上那种综合实力，已经远远超出了普通评价能覆盖的范围。 先说颜值：冷艳又带着一点温柔的气质，怎么看都耐看，光是坐在那里就已经很有吸引力。 再说服务：从细节到节奏，从氛围到互动，全程都把控得刚刚好，让人完全沉浸其中，一点都不觉得生硬或敷衍。 最难得的是情绪价值：她不只是在提供技术层面的体验，更是在真正懂你、回应你、陪你把整段时间过得又…
❤1
Showing the 12 most recent of 20 posts we hold for @wuhanbg. 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 — 240,334 of 1,340,412entries 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 1 registered channel — 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“武汉修车频道 𖣔” (@wuhanbg), 3,639 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/wuhanbg.
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.