👩🦰【艺名】:#糖小雅 📍【位置】:#拱墅区 💴【价格】:1500P 2500PP ☎️【联系】:@tangyaya789 ⚠️【提示】:#嫩妹 #高颜值 #陪浴 #Kiss 📋【报告】: 报告一 报告二 报告三 📌【返回拱墅嫩妹系榜单】
❤1

Channel
@hzdx6
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
48,737subscribers
+2,244 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002273517117 |
|---|---|
| Type | Channel |
| Username | @hzdx6 |
| Description | 励志成为您最好的出击搭子 群聊吹水专区:https://t.me/hz_dx 新人老师榜单:https://t.me/Hzdxgbrz 杭大报告频道:https://t.me/HzdxBGp 黑车信息披露:https://t.me/Hzdxgbrz01 半套认证榜单:https://t.me/HzdFLS 半套交流专区:https://t.me/HzdxBT 上榜认证、合作商家、工兵等事宜联系 @HzdxhqGLbot 群内经常性开展各类福利活动,欢迎加入 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/hzdx6 |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 9 Sept 2026, 14:19 | 48,737 | -262 |
| 6 Sept 2026, 06:40 | 48,999 | +179 |
| 4 Sept 2026, 03:17 | 48,820 | +111 |
| 2 Sept 2026, 15:47 | 48,709 | +65 |
| 1 Sept 2026, 18:05 | 48,644 | +2,067 |
| 31 Aug 2026, 17:39 | 46,577 | -1,515 |
| 30 Aug 2026, 21:13 | 48,092 | +146 |
| 29 Aug 2026, 20:17 | 47,946 | +35 |
| 28 Aug 2026, 19:33 | 47,911 | +104 |
| 27 Aug 2026, 20:34 | 47,807 | +88 |
| 26 Aug 2026, 17:56 | 47,719 | +56 |
| 25 Aug 2026, 19:47 | 47,663 | +45 |
| 24 Aug 2026, 19:04 | 47,618 | +116 |
| 23 Aug 2026, 04:14 | 47,502 | +24 |
| 21 Aug 2026, 16:45 | 47,478 | +67 |
| 20 Aug 2026, 15:11 | 47,411 | +111 |
| 19 Aug 2026, 14:16 | 47,300 | +57 |
| 18 Aug 2026, 17:52 | 47,243 | +67 |
| 17 Aug 2026, 16:27 | 47,176 | +111 |
| 16 Aug 2026, 08:55 | 47,065 | first reading |
189 posts held, back to 7 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 70 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 115 of 176 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 189 (7 August 2026 – 9 September 2026) |
| Views total | 333,662 |
| Reactions total | 68 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 22:23 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.
Lifetime counters from Telegram’s own channel header, read 9 September 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.
Measured directly from 162 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.
79 reactions across 59 posts, in 4 distinct kinds. The most used accounts for 87.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 69 | 87.3% | |
| 👍 | 6 | 7.59% | |
| 💘 | 3 | 3.80% | |
| 🥰 | 1 | 1.27% |
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 125 of the 189 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 79 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 189 most recent posts we hold, published 7 August 2026 to 9 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hzdx6. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 189 most recent posts we hold for this entry, published 7 August 2026 to 9 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
👩🦰【艺名】:#糖小雅 📍【位置】:#拱墅区 💴【价格】:1500P 2500PP ☎️【联系】:@tangyaya789 ⚠️【提示】:#嫩妹 #高颜值 #陪浴 #Kiss 📋【报告】: 报告一 报告二 报告三 📌【返回拱墅嫩妹系榜单】
❤1
👩🦰【艺名】:#团子 📍【位置】:#萧山区 💴【价格】:1100P 2000PP ☎️【联系】:@NN5562 ⚠️【提示】:#嫩妹 #萝莉 #陪浴 #舌吻 #69互舔 📋【报告】: 报告一 报告二 📌【返回萧山嫩妹系榜单】
❤1
👩🦰【艺名】:#杭州嘉兴真空KTV 📍【位置】:#商家 💴【价格】:详情咨询客服 ☎️【联系】:@KTVddofkfk ⚠️【简介】: 真空游戏场,今晚最值得来的夜晚。 消费透明.好玩不贵.骨折优惠进行中,200+ 00后极品嫩妹现场海选,年轻漂亮,身材匀称,活力满满,随你挑选。 今晚主打玩法 激情互动,真空贴身,嘴对嘴喂酒,魅惑热舞,情趣小游戏几十个,洗面奶找老婆,冰火两重天枪王打通关 旋转地球中原一点红等等关灯沙发秀,轻度触感互动,关灯环节氛围直接拉满,沙发秀 + 大尺度互动游戏,让你彻底放松。 从唱歌聊天到贴身游戏,每一步都玩得舒服,玩得开心,尺度适中,氛围热烈不会尴尬,也不会过火。 本人亲自接待,消费全程透明,先谈好价格,后消费,根据你的预算灵活安排,绝不乱加费用想商务应酬后放松,想和朋友聚会尽兴,想找个舒服的地方好好玩一晚,今晚就来杭州真空战保证让你玩得尽兴又 🧾电 报🔍 @ktvddofkfk 双向机器人: @…
👩🦰【艺名】:#婷姐 📍【位置】:#拱墅区 💴【价格】:498起 ☎️【联系】:@dft18888 ⚠️【提示】:#半套 #抓龙筋 #柔式丝足 #三起三落 #前列腺高潮 📌【返回个人半套类榜单】
👩🦰【艺名】:#哆哆 📍【位置】:#萧山区 💴【价格】:800P 1500PP ☎️【联系】:@duoduo9889 ⚠️【提示】:#嫩妹 #陪浴 #舌吻 #水中萧 #69互舔 📋【报告】: 报告一 报告二 📌【返回萧山嫩妹系榜单】
👩🦰【艺名】:#知音 📍【位置】:#上城区 💴【价格】:700H ☎️【联系】:@zhiyin89 ⚠️【提示】:#服务系 #性价比 #陪浴 #舌吻 #毒龙 #AB面 #69互舔 📌【返回上城区服务系榜单】
❤1
👩🦰【艺名】:#小朋友 📍【位置】:#西湖区 💴【价格】:1300P 2200PP ☎️【联系】:@xiaopayou1 ⚠️【提示】:#御姐系 #高颜值 #陪浴 #Kiss #69互舔 📋【报告】: 报告一 报告二 报告三 报告四 报告五 报告六 报告七 📌【返回西湖区御姐榜单】
👩🦰【艺名】:#小希 📍【位置】:#上城区 💴【价格】:800P 1500PP ☎️【联系】:@dior1847 ⚠️【提示】:#嫩妹 #陪浴 #舌吻 #69互舔 📋【报告】: 报告一 报告二 📌【返回上城区嫩妹榜单】
👑【独家冠名商家】👑 -悦龙轩·杭城首创抓龙筋- 🎖️【专业包养】 江浙沪专业包养 良品铺子江浙沪包养 🎖️【甄选半套】 拱墅92会所 月月SPA会所 杭州白金翰全裸SPA 杭州老四SPA会所 泰愈持续无限控射 杭州老六SPA会所 樱花谷5T会所 擒龙阁男士帝王喷 花公子全裸5T会所 西湖全裸5T會所 西湖区小悦SPA会所 小青海选四推 缦纱风情SPA泡泡浴 小乖抓龙筋工作室 亨泰莱养生会所 临平高颜值四推会所 🎖️【精选全套】 沐云天堂SPA会所 🎖️【娱乐生活】 杭州真空情趣KTV 杭州嘉兴真空KTV 杭州游戏场KtV 杭州真空摸摸唱 印度大药房
❤1
👩🦰【艺名】:#安若冰 📍【位置】:#上城区 💴【价格】:800P 1500PP ☎️【联系】:@kka6619 ⚠️【提示】:#嫩妹 #无纹身 #陪浴 #舌吻 #深喉 #69互舔 📋【报告】: 报告一 报告二 📌【返回上城区嫩妹榜单】
👩🦰【艺名】:#梨花诗 📍【位置】:#上城区 💴【价格】:1000P 1800PP ☎️【联系】:@tianlin2005 ⚠️【提示】:#嫩妹 #陪浴 #舌吻 #水中萧 #事后萧 #69互舔 📌【返回上城区嫩妹榜单】
👩🦰【艺名】:#馨儿 📍【位置】:#上城区 💴【价格】:800P 1500PP ☎️【联系】:@xiner9002 ⚠️【提示】:#服务系 #陪浴 #舌吻 #毒龙 #水中萧 #AB面 #69互舔 📋【报告】: 报告一 报告二 📌【返回上城区服务系榜单】
Showing the 12 most recent of 189 posts we hold for @hzdx6. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@hzdx6 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@hzdx6 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“【杭州大学】认证教师榜” (@hzdx6), 48,737 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/hzdx6.
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.