联系方式:@buding88666 #布丁 价格:8p 年龄:19 基本信息:165cm 90斤 腿型好看 a胸 无符文 人照完全一致,身材高瘦苗条,腿型又长又匀称好看,小蟒蛇,嫩妹三件套,女上桩基感觉在操我,下体毛毛原生较多,下面特别紧,拔出来的时候感觉有负压在吸我,客人多所以敏感度一般,做爱反馈合格水平,会叫爸爸。 紧b 嫩妹 颜值可爱 腿长 8p好菜 ⭐️⭐️⭐️⭐️✨(特别吃做爱反馈减✨)
❤2

Channel
@Duanping_hz
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
865subscribers
+384 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003952709938 |
|---|---|
| Type | Channel |
| Username | @Duanping_hz |
| Created | Between 1 April 2026 and 22 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/Duanping_hz |
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 19 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 08:18 | 865 | +307 |
| 4 Sept 2026, 23:15 | 558 | +36 |
| 29 Aug 2026, 07:43 | 522 | +37 |
| 22 Aug 2026, 11:08 | 485 | +4 |
| 21 Aug 2026, 11:15 | 481 | first reading |
19 posts held, back to 22 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 11 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.
35 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 71.4% | |
| 💋 | 4 | 11.4% | |
| 🍌 | 3 | 8.57% | |
| 🥰 | 2 | 5.71% | |
| 🤯 | 1 | 2.86% |
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 14 of the 19 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 22 June 2026 to 20 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.
联系方式:@buding88666 #布丁 价格:8p 年龄:19 基本信息:165cm 90斤 腿型好看 a胸 无符文 人照完全一致,身材高瘦苗条,腿型又长又匀称好看,小蟒蛇,嫩妹三件套,女上桩基感觉在操我,下体毛毛原生较多,下面特别紧,拔出来的时候感觉有负压在吸我,客人多所以敏感度一般,做爱反馈合格水平,会叫爸爸。 紧b 嫩妹 颜值可爱 腿长 8p好菜 ⭐️⭐️⭐️⭐️✨(特别吃做爱反馈减✨)
❤2
联系方式:@xiyanhenmei #知知 价格:8p 年龄:20 基本信息:165cm 95斤 B罩杯 脂肪胸 无符文 人照8.5分基本一致,身材梨形微胖有点肉,小蟒蛇,舔胸吸胸很猛,口的吸力压力超强,下体敏感,舔b的时候会跳虾,做爱反馈真实,比较耐桩,做爱时候叫声很大能激发ly的兽欲。 东北姑娘很直爽好聊天。 ⭐️⭐️⭐️✨
❤1
7刷薯片 @shup1233,每次都有新感觉,这次进化出了女上桩基技能,学坏了会秒人了😭 打分在这:https://t.me/Duanping_hz/22
❤5
联系方式:@jiuer061599 #九儿 价格:9p 年龄:20 基本信息:160cm 40kg 胸部a+ 无符文 身材苗条匀称,皮肤紧实,毫无赘肉,颜值高,全妆的话非常漂亮,小蟒🐍,口的时候会看向你 很懂,屁股撅起来能看到臀部曲线很漂亮,胸部和下体敏感,我反向服务的时候反应很好,插入后做爱反馈真实并且非常敏感能感受到老师的抖动,能给去的ly很不错的成就感。老师比较有自己的小性子,小野猫的类型。 一口一个老公,明明年纪很小但是很媚,好老师,值得一去 ⭐️⭐️⭐️⭐️✨
💋4❤3
联系方式:@Lluo123love #洛洛 价格:8p 年龄:18 基本信息:165 罩杯a+ 大片纹身 四肢非常瘦 人照 8 人工白虎有点扎,黄皮,三件套,馒头b,几乎是一线天,b真紧,一加速活塞我就感觉要射,左胸敏感,下体对蛇痒➕敏感会夹头,她服务不叫停会一直舔胸,给我舔的有点爽我都要躲了,口的常规水平,女上趴菜不太会,大蟒蛇很爽啊,做爱反馈嫩妹里优秀,有叫声也会主动腿勾上来,加速凿她的反馈会突然增加,高速ly去反馈会很好。人偏i但不严重,交流顺畅,大方回应我的话题。 吃嫩吃颜的ly可以去看看 ⭐️⭐️⭐️⭐️✨
🍌3❤1
联系方式:@meolululu 价格:13p 基本信息:172 c+大胸 颜值网红脸 有情趣内衣可以选,房间浴室很小站不下两个人,只能他服务我洗所以水中萧起不来,ab面服务 指滑 胸滑 胸推 舔耳很好,口活很顶有深喉,过程和反馈相对流程化 ,舌吻没有主动,需要ly正戏开始自己索吻, 一开始没伸舌头询问后才伸出来,吊感不错很会秒人,5分钟就出了。 ⭐️⭐️⭐️✨
❤1
6刷薯片了,1p结束被勾引的又加了一p,真的燃尽了 @shup1233 打分在这:https://t.me/Duanping_hz/22
❤2
联系方式:@xiaohuya789hz #小虎牙 价格:12p 年龄:18岁嫩妹 基础信息:身高160 体重80斤 人照8,身材我给满分,很瘦但是有c胸,细枝结硕果!传教士看着胸晃动视觉效果是一绝!乳头还是粉色 ,大蟒🐍,人很可爱,有点脱线天然呆。科室有镜子,对着镜子看她一对双峰真是绝了,视觉盛宴。 ⭐️⭐️⭐️⭐️✨(缺点做爱反馈,介意扣✨)
联系方式:@xileqiao2003 #汐乐荞 价格:6p 女菩萨 年龄:18 基础信息:157身高 罩杯c 没蛇 瘦瘦的,腿型好看,颜值高,本人和视频无差,现实更好看点,脸和妆容像网红椰子,胸部稍瘪 可能刚减肥身上肉稍松,口技很好很不错,服务还有水中萧 和事后萧 ,做爱反馈不错不假,态度也很好。 6p要什么自行车 ⭐️⭐️⭐️⭐️(不介意无🐍加✨)
❤2
联系方式:@Ruanruan108 #软软 价格:8p 年龄:20 瘦瘦的 a+胸软软, 人照8.5去掉磨皮基本无差,不喜舔b就没做,女上弱鸡也没做,蟒蛇但是🐍完中途会擦口水,传教士敏感流白浆,后入水会变少,洞口紧 ,叫声大,小脆皮不耐日不到10分钟就不行了,e人挺能聊 下体特别会夹 ⭐️⭐️⭐️✨
💣💥 踩雷了 @Youmi5210 10p 工兵去的 0反馈 啥也不会 死鱼 除了态度可以 没有可取之处 别踩雷了😭!
联系方式:@zrsa12 #晚梦 价格:700p 基础信息:163 bbw 嫩妹 好评 人照和视频里比7.9 就是瘦脸比较多 其他一致 bbw 服务好 有阴推太狠了 整得我猝不及防 体力很好 很好交流 会叫爸爸 床上挺骚的 很会夹 这个价位搭配上服务 喜欢bbw的话可以无脑吃 bbw 700服务系嫩妹 ⭐️⭐️⭐️⭐️✨(不喜bbw减✨)
🤯1
Showing the 12 most recent of 19 posts we hold for @Duanping_hz. 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“人海晤面” (@Duanping_hz), 865 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/Duanping_hz.
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.