17 Jun 2022, 04:38 UTC≈2,390 viewsread 15 August 2026
Photo
【寻欢地点】：郑州惠济区观臻苑 【信息来源】：朋友推荐的 【服务项目】：共浴，KB，dh，指滑 【妹妹数量】：1 【环境设备】：一般般 【营业时间】：自己联系妹子 【价格一览】：600 【安全评估】：评分，满分100。 【服务星级】：★★★★ 【重点推荐】：最值得推荐的地方以供参考
Channel
郑州品茶资源群🍵
@zhengzhou321
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
84subscribers
-8 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001550416295 |
|---|---|
| Type | Channel |
| Username | @zhengzhou321 |
| Created | Between 1 August 2021 and 13 May 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/zhengzhou321 |
Topic
Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 17:39 | 84 | -2 |
| 30 Sept 2026, 10:36 | 86 | -4 |
| 8 Sept 2026, 23:55 | 90 | -1 |
| 23 Aug 2026, 22:55 | 91 | -1 |
| 15 Aug 2026, 00:15 | 92 | no change |
| 15 Aug 2026, 00:02 | 92 | first reading |
Engagement
7 posts held, back to 13 May 2022 — 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 7 posts for this entry, the most recent from 17 June 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
17 Jun 2022, 04:37 UTC≈2,250 viewsread 15 August 2026
Photo
【寻欢地点】：郑州管城万通街 【信息来源】：朋友推荐 【服务项目】：鸳鸯浴，kb，dh，制服诱惑 【妹妹数量】：1 【环境设备】：小区 【营业时间】：自己问妹子 【价格一览】：700 【安全评估】：评分，满分100。 【服务星级】：★★★★ 【重点推荐】：最值得推荐的地方以供参考
17 Jun 2022, 04:37 UTC≈1,970 viewsread 15 August 2026
Photo
【寻欢地点】：河南省郑州市经开区航海路七里河 【信息来源】：其他女孩介绍，亲身体验 【服务项目】：抚摸，亲亲，口活，爱爱（不能亲吻） 【妹妹数量】：1 【环境设备】：酒店式公寓 【营业时间】：晚6点到12点 【价格一览】：1200/次，略贵。 【安全评估】：95分。 【服务星级】：服务看个人，只要不是太过分的要求，应该都可以 【重点推荐】：网红脸，照片和真人差距不大，我这人就是喜欢看脸
17 Jun 2022, 04:36 UTC≈1,820 viewsread 15 August 2026
Photo
【寻欢地点】：郑州21世纪大厦附近 【信息来源】：朋友推荐 【服务项目】：进门拥抱换鞋，暖和会儿洗澡，吹拉弹唱不变态都行 【妹妹数量】：2 【环境设备】：自租房，比较干净 【营业时间】：自己谈 【价格一览】：300p，600pp，叶1000 【安全评估】：10 【服务星级】：★★★★★ 【重点推荐】：态度好
17 Jun 2022, 04:36 UTC≈1,640 viewsread 15 August 2026
Photo
【寻欢地点】：郑州金水区东三街北段8号院1楼（大概位置） 【信息来源】：狼友推荐、论坛、亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱、SM（可选，勿必填写真实服务项目） 【妹妹数量】：1 【环境设备】：民宅 【营业时间】： 【价格一览】：200/次或600/天等 【安全评估】：评分，满分100。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】：最值得推荐的地方以供参考
17 Jun 2022, 04:35 UTC≈1,570 viewsread 15 August 2026
Photo
【寻欢地点】：二七区三峡路和爱心路交叉口附近 【信息来源】：亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69，水晶之恋，冰火两重天 【妹妹数量】：一人 【环境设备】：租房 【营业时间】：中午12点左右开 【价格一览】：400p 【安全评估】：100 【服务星级】：★★★★★ 【重点推荐】：比少妇还骚
13 May 2022, 14:07 UTC≈1,670 viewsread 15 August 2026
Photo
【寻欢地点】：郑州市金水区弘康路与香山路 海亮时代 【信息来源】：狼友推荐、论坛、亲身体验 【服务项目】：漫游，胸推，口 调情 爱爱 制服诱惑 【妹妹数量】：个人 【环境设备】：自己租的房子 【营业时间】：早上10点到下午6点 提前联系约好时间就行 【价格一览】：500/次 【安全评估】：评分，满分100。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】： 颜值高 水多 逼紧 皮肤水嫩 现在郑州这个价位找到这样人照一致的很少了。 【寻欢细节】：下午单位没事翻出微信 约了下妹子 驱车赶到妹子发的位置，按照妹子的指引来到楼上，一看到妹子比照片要好看 就迫不及待的进屋，进屋后洗澡，洗完澡看到穿了一条蕾丝情趣内衣我一下就窜到床上，妹子 23岁 160 90斤 皮肤水嫩 开始给我服务，服务完切入正题，我操 那个小水逼真紧 没几下就能听到抽插的水声 兼职欲仙欲死。 干了十几分钟就缴枪了。太爽了。 没…
Showing the 7 most recent of 7 posts we hold for @zhengzhou321. 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.
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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“郑州品茶资源群🍵” (@zhengzhou321), 84 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/zhengzhou321.
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.