#牌局复盘 【麻友】:乌萨奇大哥哥 【棋牌室】:#鹿鼎记 【麻将搭子】:#晶晶 【搭子链接】:https://t.me/aiyedejingdi/192373 【台费】:600 【胡牌牌型】:#大班 【牌局特点】:#中大蟒蛇 【各项得分】:(0-10,6 为及格) 环境:6 人照:7 身材:7 皮肤:7 态度:10 敏感度:9 抽烟:无 纹身:无 各种钉:无 【综合得分】:8 【牌局体验】: 好哥哥推荐,观察已久,正好今日得空随即出发,停车方便出入方便,就是房间略显老旧,并且略有些许霉味,杭州这个天气也是无奈。 进门后晶晶占用洗手间化妆,稍等了片刻,一支烟没抽完,便拉着我进房了,等我用过漱口水后,便关上了灯,躺下后,晶晶便开始跟遥控器搏斗,看得出来配合的不是很好,几分钟后总算是调试完毕。钻进了我怀里,破冰一分钟直接就亲上了,青春的肉体突出一个嫩字,卸甲非常顺利,全身上下都是敏感点,小C胸很挺…

Channel
杭州鹿鼎记测评与反馈集
@LudingjiCP
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003957535408 |
|---|---|
| Type | Channel |
| Username | @LudingjiCP |
| Description | 欢迎来到 杭州鹿鼎记女仆馆!✨ TG客服: @ludingjikf 每日排班: @LudingjiPB 玩家交流: @LudingjiChat 测评反馈: @LudingjiCP |
| Created | Between 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/LudingjiCP |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 04:33 | 4 | no change |
| 8 Aug 2026, 11:34 | 4 | first reading |
Engagement
19 posts held, back to 2 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3434.2%
- avg views ÷ 4 subscribers
- Avg views / post
- 137
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 19
- of 19 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 12 August 2026 |
|---|---|
| Posts held | 19 (2 August 2026 – 12 August 2026) |
| Views total | 2,610 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 04: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
- 21
- Links
- 22
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
小怡反馈+1
#牌局复盘 【麻友】:现在 现在(戒了) 【棋牌室】:#鹿鼎记 【麻将搭子】:#晶晶 【搭子链接】:https://t.me/LudingjiChat/6406 【台费】:600 【胡牌牌型】:#大班 【牌局特点】:#中蟒蛇 #素人感 【各项得分】:8 环境:7 人照:8 身材:8.6 皮肤:8.8 态度:9 敏感度:8 抽烟:无 纹身:无 各种钉:无 【综合得分】:8.5 【牌局体验】:憋了一天,忍不住想要找个地方释放。找来找去还是选择去了鹿鼎记。每次去鹿鼎记都是充满期待的心情。第一眼看到晶晶,感觉就是懵懂无知的少女一样。充满青春气息。很白嫩,真的是白!嫩!胸又大又挺。身材确实不错。刚开始感觉长得一般。后面房间细看,又感觉还是不错的。身材也是很顶。我的观点是,人白,怎么样都好看。怎么样都上头。上来聊几句便一卸到底😏*.。(๑・∀・๑)*.。稍微摸了下,就开始小水潺潺。便开始了标志性动作,云…
#空港基地 @3154号飞行员 #小怡 #鹿鼎记 #拱墅 #2026.8#1h 店铺:https://t.me/LudingjiChat/6255 颜值8 身材8 皮肤8 敏感度8 性格9 综合体验8.2 优点:配合度拉满的小萌妹,颜值身材也都不错 缺点:客人自己把握上钟流程体验会更好 过程:看到小怡本人,和照片大概7-8分像,整体比较小只,偏瘦弱,黄头发,气质是小萌妹类型的。 妹妹带领进屋,楼梯旁的那种夹层房间,室内较简陋但配套还行,有一次性床单和投影。小怡递上了漱口水,钻到我怀里,然后一直哥哥哥哥的喊个不停,聊天的时候还会自己咯咯的笑,比较蠢萌。舌吻配合,卸甲顺畅。小怡皮肤整体还凑合,胸相对体型就是正常大小,不算大也不平。身上敏感度尚可但反馈不太强,水量一般。 小怡做女仆时间还不久,之前赚的钱出去玩花完了,这次回来对工作便又认真了起来。妹妹可能不太会一些主动服务,但操作妹妹的时候都很配合。结束正题后妹妹也没马上懈怠,…
#鹿鼎记 #晶晶 店铺:https://t.me/LudingjiChat 出击人:吹雪 @chuixuejiang 类型:#巨乳 #萌妹 出击时间:2026.08 环境:标准大床房,有一次性床单,投影正常 人照相似度:8.5(脸很像) 本人颜值:6.7 身材:身高158 体重110,胸围C 抽烟:无 纹身:无 唇钉舌钉:无 吻技:大蟒蛇 班型:超大 妹妹优点:听话懂事配合度高,巨乳大屁股,能接受轻微m,声音好听。 妹妹缺点:标准圆脸小胖妹,下体有味(湿巾擦之后无味),反馈单一(只会轻哼),主动性欠佳。 (优缺点以吹雪个人审美为标准,有些在我这里是缺点可能在其他玩家眼里是优点,请勿纠结) 妹妹服务(尺度):超大+,十分卸甲,可蹭 吹雪评价:带任务出击的,小怡在上钟,选了晶晶,见面第一感觉是个标准的学生时代小胖妹,穿的是带裙撑的女仆装还挺可爱的,进房间和妹妹坐在床上待了一会,妹妹有主动找我说话,可能因为年龄问题,话题还是…
小怡好评+1
#目录 #模板 模板A 返回频道导航 #No 店铺:#鹿鼎记 女仆:#晶晶 类型:#邻家妹妹(例,可以写御姐,bbw,萝莉,S/M等,可以有复合类型,比如萝莉M等) 出击人:#泽熙 出击时间:2026.08 环境: A,小区房 人照相似度:人照8 罩杯:胸C 身材:屁股大胸大 身高:160 体重:100 皮肤:较白较滑 态度:A,配合度较高 聊天交流:拘谨 敏感处: 胸,豆豆敏感 抽烟:无 纹身:无 唇钉舌钉:无 吻技:吻技一般 过程:人照8分,可爱的小妹妹,有肉感,微胖,说话小声比较腼腆,破冰后非常配合,因为衣服多,卸全甲花了好几分钟,之后舌了一会往下一模湿透了,那我必须要用上加藤鹰之手了,很紧很滑,不愧是年轻的身体,之后就开始隔裤蹭起来,湿湿的很舒服,蹭了一段时间后在妹妹的小手的帮助下,边吃奶边发射了,很乖的妹妹,弟兄们下手轻点 以下为六维评分,分项目评分(严格按照评分标准打分,不要带有太多感情色彩,不要遗漏六维评…
晶晶 +1
布丁好评+1
晶晶好评+1
#空港基地 @837号飞行员 #晶晶 #鹿鼎记 #拱墅 #2026.8#1h 店铺:https://t.me/LudingjiPB/107 颜值7.5 身材7.5 皮肤8 敏感度9 性格9 综合体验8.5 优点:很棒的素人感,敏感度、配合度均在线 缺点:略微有些小肉肉 过程: 1.一进房间,就让妹妹幼态的气质、无辜的眼神吓了一跳,还正津津有味的看着熊大熊二。。不会是wcn吧,顿时有点方。。邻家小萝莉的既视感,牙齿矫正下会更加甜美,微微有些肉肉,时常会憨憨的笑,有点可爱。。 2.妹妹可能是在偏压抑的环境中长大,认知上对外部世界并没有怯魅,缺乏一些底气和自信,于是呈现出一种生命力十足却小心翼翼的状态,不禁会让人有些心疼。。 3.破冰拉扯了下聊了会天,妹妹慢慢开始放松下来,甚至放声大笑开始放飞。。这节奏不对啊,于是郑重其事的告诉妹妹,爸爸不是搞笑来的,是ghs来的,我们赶紧开始吧。。 4.中蟒蛇起手,闭上眼很投入,皮肤丝滑而有…
#No1659 店铺:#鹿鼎记 女仆:#晶晶 💯评分标准 店铺链接: t.me/LudingjiPB 类型:#邻家妹妹 价格:600/h 出击人:#danzhi 出击时间:2026.7 环境: A,小区房 人照相似度:人照8 罩杯:C 身材:胸大屁股大 身高:160 体重:95 皮肤:皮肤较滑 态度:A,配合度较高 聊天交流:不拘谨 敏感处: 三点敏感 抽烟:无 纹身:无 唇钉舌钉:无 吻技:中蟒蛇 🌱初见 进门第一感觉,就是还没长开的小妹妹,稍微肉感,眼睛布灵布灵的,挺可爱的。 🔥过程 真人跟模卡数据没差,是个带着点微肉感的青春小嫩妹,绝不是坦克!妹子特别懂事又有讨好感,一进屋就主动牵手、热情反向破冰。最离谱的是她体质巨敏感,还没怎么预热呢下面就直接泛滥了,指尖试探又紧又湿,水声听得人火气大涨。不管是隔裤互动还是骑马配合都相当有一套,拉扯感直接拉满。结束之后抱着聊天也特别接地气,古灵精怪的完全不冷场。一句…
Showing the 12 most recent of 19 posts we hold for @LudingjiCP. 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 — 141,192 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“杭州鹿鼎记测评与反馈集” (@LudingjiCP), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/LudingjiCP.
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.