17 Jun 2022, 04:48 UTC961 viewsread 15 August 2026
Photo
【寻欢地点】：贵州贵阳.观山湖区.美的林城 【信息来源】：亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱 【妹妹数量】：一个 【环境设备】：干净温馨 【营业时间】：全天 【价格一览】：600/次或1000/两次，2000包夜 【安全评估】：评分，满分100。 【服务星级】：★★★★★ 【重点推荐】：胸大皮肤白粉嫩紧
Channel
贵阳品茶资源群🍵
@gzhou123
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
41subscribers
+0 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 | -1001785585992 |
|---|---|
| Type | Channel |
| Username | @gzhou123 |
| Created | Between 1 December 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 | 11 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/gzhou123 |
Topic
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 30 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 |
|---|---|---|
| 11 Oct 2026, 16:39 | 41 | -1 |
| 2 Oct 2026, 04:59 | 42 | +2 |
| 16 Sept 2026, 16:17 | 40 | -1 |
| 15 Aug 2026, 00:15 | 41 | no change |
| 15 Aug 2026, 00:02 | 41 | 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:47 UTC899 viewsread 15 August 2026
Photo
【寻欢地点】：贵阳市区 【信息来源】：亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱、SM（可选，勿必填写真实服务项目） 【妹妹数量】：1 【环境设备】：公寓 【营业时间】：提前问 【价格一览】：一次600 【安全评估】：评分，满分100。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】：服务态度好
17 Jun 2022, 04:47 UTC793 viewsread 15 August 2026
Photo
【寻欢地点】：贵州省贵阳市 【信息来源】：狼友推荐、论坛、亲身体验 【服务项目】：舌吻、鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱、三通 【妹妹数量】：1 【环境设备】：自己的房子，安全 【营业时间】：电话自己联系 【价格一览】：700次或2200天，新增三通1500 【安全评估】：评分，满分99。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】：服务控
13 May 2022, 14:27 UTC837 viewsread 15 August 2026
Photo
【寻欢地点】：贵阳会展城美的林城 【信息来源】：亲身体验 【服务项目】：制服，丝袜情趣内衣，口爆，鸳鸯浴，舍漫 水漫 环游刮痧 胸推 臀推 波推 可69 【妹妹数量】：1个 【环境设备】：干净，卫生 【营业时间】：全天,最好电话联系 【价格一览】：700/次，900/两次 【安全评估】：评分，98 【服务星级】：★★★★★ 【重点推荐】：人很漂亮，有气质
13 May 2022, 14:26 UTC765 viewsread 15 August 2026
Photo
【寻欢地点】：花果园（大概位置） 【信息来源】：狼友推荐、论坛、亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱、SM（可选，勿必填写真实服务项目） 【妹妹数量】1： 【环境设备】：好 【营业时间】：10.00 22.00 【价格一览】：600/次或800/pp 【安全评估】：评分，满分100。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】：温柔漂亮
13 May 2022, 14:26 UTC705 viewsread 15 August 2026
Photo
【寻欢地点】：贵阳飞山街 【信息来源】：狼友推荐、论坛、亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱、乳交 【妹妹数量】：1 【环境设备】：80 【营业时间】：约上 【价格一览】：600/次或800两次等 【安全评估】：评分90，满分100。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】：最值得推荐的地方以供参考 【寻欢细节】：本人极少数想约第二次的妹子，之前约过几次都因为时间不合适作罢，当天晚上约的最后一场，虽然等了一会但还是很值得的，妹妹态度很好很会营造气氛。 照片相似度80%一对巨乳非常吸引人 菜单有的都做了 乳交非常的爽。还会一直叫爸爸。我做的两次 中间休息的时候一直在聊天 没有冷场过 非常推荐两次。这个 价格非常值得。绝对真实有效。
13 May 2022, 14:25 UTC610 viewsread 15 August 2026
Photo
【寻欢地点】：贵阳市区 【信息来源】：亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱、SM（可选，勿必填写真实服务项目） 【妹妹数量】：1 【环境设备】：公寓 【营业时间】：提前问 【价格一览】：一次600 【安全评估】：评分，满分100。 【服务星级】：★★★★★（最高5星）应适当评价质量 【重点推荐】：服务态度好 【寻欢细节】：加了有一段时间，今天问好直接就去了，到了后妹子在楼下买东西，第一眼看到，长的不错，身材也可以，穿着比较清新，然后帮她提着些零食一起上楼，到了房间后，妹子显得有点害羞，然后随便聊了一会，就先洗澡，洗完后妹子换上丝袜，就开始调情，再口活，口活不错，口了一会然后就带上TT开做，细节就不一一描述了，总体还不错，妹子给我最深的映像没什么风尘气息，气质挺好。
Showing the 7 most recent of 7 posts we hold for @gzhou123. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“贵阳品茶资源群🍵” (@gzhou123), 41 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/gzhou123.
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.