【妹子花名】:#小嘟 【所属店铺】:#古茗 https://t.me/guming66888 【验证留名】:阿水 【验证时间】:2026-8-8 【大概位置】:婺江路 【服务内容】: ① 舌吻 ✅ ② 摸胸 ✅ ③ 吃胸 ✅ ④情绪价值 ✅ 配合度:10 【颜值打分】:8.5 【身材打分】:8.5 【吻技打分】:8.5 【敏感度分】:9 【推荐程度】:9 【综合评价】:夯到爆炸 流程:进门的时候我们还比较拘谨,但小嘟非常配合,两人调笑间距离感没了,上区衣服也没了。 小嘟身材很好,胸大腰细,修长比例,但我最喜欢的还是她的眼睛,眼睛很有故事感。 每每与之对视我都如触电一般,我的心神也融化了,尽情的投入了激吻。呼吸渐渐粗重,耳畔的娇吟也越来越响,我的双手肆无忌惮的游走着,我的嘴也在贪婪的吮吸着小嘟饱满的酥胸。 在忘情中顺利出水,小嘟非常温柔体贴,经常把我牢牢抱住,女友…

Channel
杭州古茗女仆测评
@gumingcp
On this record: Growth · Engagement · Posts · Citations · Cite this entry
102subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003278925698 |
|---|---|
| Type | Channel |
| Username | @gumingcp |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/gumingcp |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:15 | 102 | -1 |
| 9 Aug 2026, 09:32 | 103 | no change |
| 7 Aug 2026, 20:49 | 103 | first reading |
Engagement
20 posts held, back to 21 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 47.5%
- avg views ÷ 102 subscribers
- Avg views / post
- 48.5
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 20 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 8 August 2026 |
|---|---|
| Posts held | 20 (21 July 2026 – 8 August 2026) |
| Views total | 970 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 09:32 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.
Recent posts
#小嘟 +1
#小嘟 好评+1
#牌局复盘 【麻友】:得了吧 【棋牌室】:#古茗 【麻将搭子】:#小茹 【搭子链接】:https://t.me/guming66888/37002 【台费】:400+200筹码 【胡牌牌型】:#大班 【牌局特点】:#配合 【各项得分】:(0-10,6 为及格,对应大班) 环境:8 人照:8 身材:8 皮肤:8.5 态度:8.5 敏感度:8.6 抽烟:无 纹身:无 各种钉:无 【综合得分】:8.5 【牌局体验】:刷过很多小茹的测评了,这次终于有机会约到她了,人照差不多。小茹很健谈,进了房间后主动拉开话题,很快就破了冰,聊到氛围差不多了,便开始感受小茹的小蟒蛇,虽然亲一段时间要歇一会儿,但是也能一直配合。一边亲吻着,我也一边上下其手,感受着妹妹嫩滑的肌肤。。。后续让妹妹卸甲,很配合,独留0甲。妹妹敏感度很高,光是玩弄葡萄就已经叫声不断,后面浅浅的探索了一下洞穴,已经是水帘洞看,得到妹妹允许,手指…
#空港基地 @6324号飞行员 #世一 #古茗 #上城 #2026.8#2h 店铺:https://t.me/guming66888/37068 颜值8 身材8 皮肤 8 敏感度 7 性格 8 综合体验8 优点:腿型好,配合度高 缺点:情绪一般 过程:听发发说世一已经调好,准备去试试,来到酒店躺下聊了会天破冰,该说不说确实已经调好主动卸甲仅存一甲蜷缩进被子里往我怀里靠,看了一会儿电视,我就操作了起来,A+的熊虽然不大但是很敏感,手掌上去略微抚摸已经是凸起明显了,低头俯身亲下去,妹妹忍不住颤抖,双手往下探去已是微微潮湿,顺利把最后一甲也卸了,些许操作下,妹妹颤抖更明显,按着我的头往胸口凸起出攻击,如此主动邀请,那我自是满足,后续也是在各种操作下顺利出货 总结:发发调教的很不错,配合度很高 妹妹有些许洁癖 兄弟们清爽出击
#空港基地 @666号飞行员 #小嘟 #古茗 #上城 #2026.7#1h 店铺:https://t.me/gumingpb/2088?single 颜值8 身材8 皮肤9 敏感度7 性格8 综合体验8.5 优点:丰满但不胖,皮肤好 缺点:化点妆就更好了 过程: 古茗之前领过优惠券,临时有事鸽了,这次给补上,本来想约小如的,可惜时间不赶趟,就约了小嘟。电梯需要刷卡,发发下来接的。环境不错,设备齐全,床也很软。 小嘟的第一印象是比照片瘦一点,轮廓圆润,笑起来很好看,进门一个大大的拥抱,上手的感觉特别好,2颗大雷非常舒服。破冰很顺畅,亲吻也有激烈的回应,揉揉胸舔一舔就有呻吟声。 下面的毛毛也比较多,隔裤操作能感觉到流水潺潺,进入状态之后就开始独留1甲状态,肚子上是没有赘肉的,摸起来也很舒服。然后柔韧性也没问题,尝试了各种隔裤姿势妹妹也很配合。最后,在妹妹的手法兼喘息声中结束出击之旅。 总结:非bbw,高个丰满可爱型嫩妹,喜…
#空港基地 @57777号飞行员 #小茹#古茗 #上城 #2026.7 #1h 店铺链接:https://t.me/guming66888/36720 颜值8 身材 8 皮肤8.5 敏感度 8.5 性格 8.8 综合体验:8.5 优点:敏感水润 缺点:无明显缺点 内容:连续出击多天,今天本来只想来个中班养生。听说小茹头钟被鸽了,考虑了一下,还是没忍住约上了,好妹妹不能错过。洗完澡驱车来店里,过了一会妹妹进了房间,两人相拥躺下,借着忽闪的灯光,观察妹妹的容颜,还是比较精致的,特别是侧颜更有风味。投影播放的电视剧男女主雪中拥吻,正好借着这个契机吻上了小茹,妹妹先是浅浅回应,随着大手覆上一只胸部,轻轻揉搓,妹妹动情后化身小蟒蛇回击。唇齿交融间,两人已坦诚相见,一对C胸饱满有弹性,含住挺立的小葡萄轻轻吸吮,妹妹的身体止不住扭动。时间成熟,下探幽谷,发现早已水润潮湿,双指轻轻拍打有哗哗水声。最后抬起妹妹双腿开蹭,伴随诱人的呻吟倾泻…
#牌局复盘 【麻友】:zb 【棋牌室】:#古茗 【麻将搭子】:#世一 【搭子链接】:https://t.me/gumingpb/2141 【台费】:600 【胡牌牌型】:#大班 【牌局特点】:#御姐 【各项得分】:(0-10,6 为及格) 环境:8 人照:9 身材:8 皮肤:8 态度:8 敏感度:7 抽烟:无 纹身:无 各种钉:有,唇钉、眉钉 【综合得分】:8 【牌局体验】: 在大鱼就关注过世一,不过因为这牛逼的名字再加上高冷御姐风不敢亵玩只可远观。不过最近朋友说世一是个好妹妹值得一去,跟发发确认之后便立刻行动。妹妹今天淡妆出席,并且其实是个热情活泼大美女,皮肤细嫩光滑有弹性,并且难得的不是很怕痒,于是我使出看家的指滑本领,妹妹舒服的趴在我怀里。感觉形式有点不对怎么变成我给妹妹服务,于是立马换个姿势开始操作起来,妹妹胸是敏感点并且挺注意卫生干净的,建议兄弟们不要浑身大汗淋漓过来,为了有个完美…
#牌局复盘 【麻友】:zb 【棋牌室】:#古茗 【麻将搭子】:#世一 【搭子链接】:https://t.me/gumingpb/2141 【台费】:600 【胡牌牌型】:#大班 【牌局特点】: #御姐 【各项得分】:(0-10,6 为及格) 环境:8 人照:9 身材:8 皮肤:8 态度:8 敏感度:7 抽烟:无 纹身:无 各种钉:有,唇钉、眉钉 【综合得分】:8 【牌局体验】: 在大鱼就关注过世一,不过因为这牛逼的名字再加上高冷御姐风不敢亵玩只可远观。不过最近朋友说世一是个好妹妹值得一去,跟发发确认之后便立刻行动。妹妹今天淡妆出席,并且其实是个热情活泼大美女,皮肤细嫩光滑有弹性,并且难得的不是很怕痒,于是我使出看家的指滑本领,妹妹舒服的趴在我怀里。感觉形式有点不对怎么变成我给妹妹服务,于是立马换个姿势开始操作起来,妹妹胸是敏感点并且挺注意卫生干净的,建议兄弟们不要浑身大汗淋漓过来,为了有个完…
#牌局复盘 【麻友】:外套 【棋牌室】:#古茗 【麻将搭子】:#小茹 【搭子链接】:https://t.me/guming66888/34669 【台费】:400 【胡牌牌型】:#大班 【牌局特点】:#配合 【各项得分】:(0-10,6 为及格,对应大班) 环境:8 人照:8 身材:8 皮肤:8 态度:8.5 敏感度:8.5 抽烟:无烟味 纹身:无 各种钉:无 【综合得分】:8.5 【牌局体验】:手抖拍了个二免一,扫了一圈测评感觉小茹应该不错,便约好时间出击。在房间里等了一段时间终于见到了妹妹,初始印象的话,颜值不算出彩,也可能是由于妆造的问题,也如测评里写的一般,看起来似乎有些冷淡。实际相处过程中,破冰时间确实花的其他妹妹要多了一些,但是场子热好之后,小茹的优势才全部显现出来。不仅人格外热情,也发现妹妹颜值算是耐看型,看的越久越觉得好看,而且真的是特别水润,即便妹妹已经奋战了一天,吻技虽比…
#世一 新评+1
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @gumingcp. 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
Citation-graph rank — 245,660 of 1,345,403entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“杭州古茗女仆测评” (@gumingcp), 102 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/gumingcp.
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.