Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州烟雨城上榜频道

Channel

杭州烟雨城上榜频道

@HZH68866

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

24,721subscribers

-6,103 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001865012384
TypeChannel
Username@HZH68866
Description上榜管理: @vdgrf3 轮播群:https://t.me/HZh6886
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/HZH68866

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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

24,65230,99627,8247 August 2026 — 30,824 subscribers7 August 2026 — 30,824 subscribers8 August 2026 — 30,379 subscribers9 August 2026 — 30,209 subscribers10 August 2026 — 29,881 subscribers11 August 2026 — 29,320 subscribers12 August 2026 — 28,931 subscribers14 August 2026 — 28,257 subscribers15 August 2026 — 27,989 subscribers16 August 2026 — 27,168 subscribers17 August 2026 — 26,819 subscribers18 August 2026 — 26,438 subscribers19 August 2026 — 30,996 subscribers20 August 2026 — 30,466 subscribers22 August 2026 — 29,798 subscribers23 August 2026 — 28,719 subscribers25 August 2026 — 27,846 subscribers26 August 2026 — 27,357 subscribers27 August 2026 — 26,974 subscribers28 August 2026 — 26,706 subscribers29 August 2026 — 26,214 subscribers30 August 2026 — 25,784 subscribers31 August 2026 — 25,548 subscribers1 September 2026 — 25,391 subscribers2 September 2026 — 25,116 subscribers3 September 2026 — 24,652 subscribers5 September 2026 — 29,261 subscribers8 September 2026 — 28,764 subscribers11 September 2026 — 28,022 subscribers13 September 2026 — 27,209 subscribers14 September 2026 — 26,985 subscribers16 September 2026 — 26,467 subscribers19 September 2026 — 26,126 subscribers25 September 2026 — 24,721 subscribers24,7217 August 202625 September 2026
34 measurements spanning 49 days, net -6,103. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 23,700–31,948 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
25 Sept 2026, 21:3724,721-1,405
19 Sept 2026, 03:4026,126-341
16 Sept 2026, 17:1726,467-518
14 Sept 2026, 21:0126,985-224
13 Sept 2026, 10:0127,209-813
11 Sept 2026, 12:0228,022-742
8 Sept 2026, 19:5628,764-497
5 Sept 2026, 12:5829,261+4,609
3 Sept 2026, 13:5724,652-464
2 Sept 2026, 09:1925,116-275
1 Sept 2026, 06:3625,391-157
31 Aug 2026, 09:1325,548-236
30 Aug 2026, 06:4725,784-430
29 Aug 2026, 04:4726,214-492
28 Aug 2026, 02:0826,706-268
27 Aug 2026, 04:3626,974-383
26 Aug 2026, 01:3727,357-489
25 Aug 2026, 01:1727,846-873
23 Aug 2026, 15:4728,719-1,079
22 Aug 2026, 03:0329,798first reading

Engagement

24 posts held, back to 22 July 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 66 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.54%
avg views ÷ 24,721 subscribers
Avg views / post
1,120
9 posts measured
Reaction rate
0.244%
reactions ÷ views · ER floor
Posts in window
9
of 24 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. It is computed over the 2 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 September 2026
Posts held24 (22 July 2026 – 27 September 2026)
Views total10,109
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 05:57 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
≈1,420
Videos
≈286
Links
≈369

Lifetime counters from Telegram’s own channel header, read 30 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 07s
Average length
12s

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.

Reaction mix

7 reactions across 7 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7100.0%

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 10 of the 24 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 22 July 2026 to 27 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.

Recent posts

27 Sept 2026, 14:22 UTC146 viewsread 30 September 2026
Photo

🥐艺名: 娜娜 🤗尺年: 172 体重:52 熊:D 📍位置: #上城区 💸价格: 1400p 2500pp 🎮标签: 舌吻💋丝袜🦵69 💦水多紧致 前凸后翘玩👙纯天然无科技😘🉑甜🉑盐🉑邻家女孩🉑御姐🉑女王 情绪☺️价值提供满满🤗各种姿势均可配合 🥂联系老师: @daxnana 双向机器人: @nanagenbanbot 💓老师频道:https://t.me/nanabb172

24 Sept 2026, 06:07 UTC258 viewsread 30 September 2026
Photo

艺名:鑫鑫 坐标:地址杭州滨江区聚才路地铁站, 课费:6米P-7米PP,一小时不限次8米,三通一次加2米 标签: 熟女 课表:三通,口爆,毒龙,🐻推,足交,深喉,69,🐍吻,鸳鸯浴,倒挂金钩,颜射(颜射一次加2米,包夜15米不限次,三通一次二米) qq3929266538 微信:kb1998s 与你1996fc 电报: @feng0215 频道: https://t.me/hzxinxin 注意:现金,不是必须

22 Sept 2026, 12:43 UTC264 views1 reactionsread 30 September 2026
Photo

🟡昵称:(王牌中介) 🕐地区:杭州(各区🉑安排) 🚀电报 ☎️双向 : 🔔频道:点击预览详细 🔴水费: #800P 📤 #1500PP 🔴开工区域位置如⬇️ #拱墅 临平 萧山 余杭 西湖 #临安 上城 钱塘 富阳 滨江 🔴标签 #可放心出击 #已验证

❤1

22 Sept 2026, 08:51 UTC172 viewsread 27 September 2026
Video

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩亿级域名|78.COM 🤩官方飞投|充提自由 🤩NO钱包担保3亿U|可查验! 😀 东南亚大事件联合担保🤩🤩🤩🤩🤩(电子) 📱官方频道:@DF78 ➡️关注领VIP 🔝大品牌,实力派:78.COM 本身就是最好的辨识度。 ✅️香港六合彩 · 独家盈利无上限! 🤩所有的特码🤩🤩倍,封顶赔率! 🤩连码三中三🤩🤩🤩倍 🤩连码四中四🤩🤩🤩🤩🤩倍 🤩百家乐全网最高返水🤩% 🤩电子|棋牌|捕鱼返水🤩.🤩% 🤩十三水|德州自主组队,无抽佣; 🏆百家乐真人视讯台红🤩🤩万U; 💥新人超会赢,精彩时刻分享: 🥇六合彩 玩家用7个号码组合下注连码三全中(35注)➕四全中(35注),每注100U,结果开出4个号码。命中4注878倍及一注10000倍大奖,稳稳落袋135万U; 🥈PG电子 2.6万U本金,爆出268万U大奖!玩家一局逆袭,豪取268万U! 🥉DB真人 玩百家乐的老板,第一天存款50万U,连续7天每日…

22 Sept 2026, 05:52 UTC≈1,840 viewsread 27 September 2026
Photo

艺名:久久,年龄22,高160,体重100.B 项目:洗澡调情69互舔无套口爱爱黑丝乖巧听话 各种姿势配合第一次做时间超20用手打出 禁:无套,吸毒,吃药,口嗨低素质桩机 课费:700lp40。1300/pp90.3000/夜,现金最好一妹妹平时正经工作,兼职接单提前预约 上 pp起外加一张车费 频道:jj 私信:@zxcvbnmfei

20 Sept 2026, 11:09 UTC≈3,650 viewsread 23 September 2026
Photo

艺名:馨馨,年龄20,高165,体重85.B 项目:洗澡调情69互舔无套口爱爱黑丝乖巧听话 各种姿势配合第一次做时间超20用手打出 禁:无套,吸毒,吃药,口嗨低素质桩机 课费:700lp40。1300/pp90.3000/夜,现金最好一妹妹平时正经工作,兼职接单提前预约 上 pp起外加一张车费 频道: https://t.me/zxxx9898 双向: @baoinsbot 私信: @RMB098

20 Sept 2026, 11:06 UTC≈3,500 viewsread 23 September 2026

https://t.me/HZh6886 【验证留名】:546 【验证时间】:919 【妹子花名】:鑫鑫 【联系方式】: @feng0215 【所在位置】:滨江 【修车水费】:700 【照片相似】:一样 【颜值身材】:高 【凶器罩杯】:c 【服务项目】:课表一样 【服务详情】:pp 【优点缺点】:老师气质型少妇,服务和实力在线,有一次性毛巾和拖鞋,服务口活无齿感进,床上服务热情主动,骚穴淫水多,干了几分钟,老师本人也很健谈不敷衍,不催促,不冷场。其他活也非常顶级,服务非常的到位,穿着丝袜很有感觉,是值得二刷的老师。放心冲

4 Sept 2026, 11:59 UTC146 views0 reactionsread 7 September 2026
Photo

甜甜的私密空间互动室 (个人自聊) 年龄03 身高165 体重103- B+ 天然無整容, 🖐🏻AI图 听话温柔服务好 可配合多种姿势 服务:制服丝袜、无套口 漫游 指滑、老汉推车、观音坐莲 $ 700p~35min $ 1200p~60min 禁 无套手抠、 禁 吃药醉酒、 禁素质低辱骂 TG: @tian9691 频道:https://t.me/tiantian66691

4 Sept 2026, 04:36 UTC133 viewsread 7 September 2026
Photo

艺名:鑫鑫 坐标:地址杭州滨江区聚才路地铁站, 课费:6米P-7米PP,一小时不限次8米,三通一次加2米 标签: 熟女 课表:三通,口爆,毒龙,🐻推,足交,深喉,69,🐍吻,鸳鸯浴,倒挂金钩,颜射(颜射一次加2米,包夜15米不限次,三通一次二米) qq3929266538 微信:kb1998s 与你1996fc 电报: @feng0215 频道: https://t.me/hzxinxin 注意:现金,不是必须

30 Aug 2026, 08:02 UTC314 views1 reactionsread 7 September 2026
Photo

艺名:馨馨,年龄20,高165,体重85.B 项目:洗澡调情69互舔无套口爱爱黑丝乖巧听话 各种姿势配合第一次做时间超20用手打出 禁:无套,吸毒,吃药,口嗨低素质桩机 课费:700lp40。1300/pp90.3000/夜,现金最好一妹妹平时正经工作,兼职接单提前预约 上 pp起外加一张车费 TG: @xin13140 频道:https://t.me/lovex098 双向: @keke99bot

❤1

25 Aug 2026, 03:49 UTC497 views1 reactionsread 7 September 2026
Photo

艺名:鑫鑫 坐标:地址杭州滨江区聚才路地铁站, 课费:6米P-7米PP,一小时不限次8米,三通一次加2米 标签: 熟女 课表:三通,口爆,毒龙,🐻推,足交,深喉,69,🐍吻,鸳鸯浴,倒挂金钩,颜射(颜射一次加2米,包夜15米不限次,三通一次二米) qq3929266538 微信:kb1998s 与你1996fc 电报: @feng0215 频道: https://t.me/hzxinxin 注意:现金,不是必须

❤1

23 Aug 2026, 02:40 UTC≈4,540 viewsread 3 September 2026

https://t.me/HZh6886 【验证留名】: 【验证时间】:8.19 【妹子花名】:鑫鑫 【联系方式】: @feng0215 【所在位置】:滨江 【修车水费】:700 【照片相似】 :一样 【颜值身材】:长的挺好看,身材不错 【凶器罩杯】:B 【服务项目】:和课表一致 【服务详情】:进门后直接脱衣洗澡,然后帮你全身擦干净开始服务,毒龙没有齿感,时间非常长,小穴不是很松,暖暖的,各种姿势老师都是十分配合,第一次结束后休息过程中老师十分健谈不冷场,相处的很舒服,服务不催钟 【优点缺点】:前列腺按摩非常爽,没有缺点

Showing the 12 most recent of 24 posts we hold for @HZH68866. 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.

Forward network

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.

Mentions

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“杭州烟雨城上榜频道” (@HZH68866), 24,721 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/HZH68866.

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.