Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州【认证榜单】

Channel

杭州【认证榜单】

@gzzypd66

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

27,628subscribers

-1,482 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-1001650290703
TypeChannel
Username@gzzypd66
Description认证联系: @TShengdi_bot 杭州交流群: @hangzhoujlq 🎫个人/中介/会所/外围 认证中心 只做最真实的娱乐资源,真实即可认证 认证通过即可公示!
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/gzzypd66

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 81% 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 the other topics.

Growth

26,47930,34028,409.57 August 2026 — 29,110 subscribers7 August 2026 — 29,110 subscribers8 August 2026 — 29,155 subscribers9 August 2026 — 29,254 subscribers10 August 2026 — 29,294 subscribers11 August 2026 — 29,338 subscribers12 August 2026 — 29,413 subscribers13 August 2026 — 29,494 subscribers14 August 2026 — 29,684 subscribers15 August 2026 — 29,764 subscribers17 August 2026 — 29,817 subscribers18 August 2026 — 29,852 subscribers19 August 2026 — 29,897 subscribers20 August 2026 — 29,940 subscribers21 August 2026 — 29,965 subscribers22 August 2026 — 30,047 subscribers24 August 2026 — 30,101 subscribers25 August 2026 — 30,147 subscribers26 August 2026 — 30,176 subscribers27 August 2026 — 30,202 subscribers28 August 2026 — 30,298 subscribers28 August 2026 — 30,340 subscribers30 August 2026 — 30,255 subscribers30 August 2026 — 30,042 subscribers31 August 2026 — 29,891 subscribers2 September 2026 — 29,696 subscribers3 September 2026 — 29,372 subscribers5 September 2026 — 29,043 subscribers8 September 2026 — 28,500 subscribers11 September 2026 — 28,010 subscribers13 September 2026 — 27,637 subscribers15 September 2026 — 27,453 subscribers17 September 2026 — 27,167 subscribers19 September 2026 — 26,835 subscribers26 September 2026 — 26,479 subscribers4 October 2026 — 26,953 subscribers9 October 2026 — 26,909 subscribers13 October 2026 — 27,126 subscribers14 October 2026 — 27,169 subscribers16 October 2026 — 27,172 subscribers16 October 2026 — 27,199 subscribers17 October 2026 — 27,258 subscribers18 October 2026 — 27,307 subscribers19 October 2026 — 27,337 subscribers20 October 2026 — 27,373 subscribers21 October 2026 — 27,423 subscribers22 October 2026 — 27,506 subscribers23 October 2026 — 27,598 subscribers25 October 2026 — 27,614 subscribers26 October 2026 — 27,628 subscribers27 October 2026 — 27,565 subscribers28 October 2026 — 27,600 subscribers29 October 2026 — 27,451 subscribers30 October 2026 — 27,494 subscribers30 October 2026 — 27,382 subscribers31 October 2026 — 27,428 subscribers1 November 2026 — 27,488 subscribers2 November 2026 — 27,605 subscribers3 November 2026 — 27,640 subscribers4 November 2026 — 27,628 subscribers27,6287 August 20264 November 2026
60 measurements spanning 89 days, net -1,482. 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 25,900–30,919 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
4 Nov 2026, 23:2027,628-12
3 Nov 2026, 20:5427,640+35
2 Nov 2026, 20:2727,605+117
1 Nov 2026, 22:4527,488+60
31 Oct 2026, 20:1027,428+46
30 Oct 2026, 21:3627,382-112
30 Oct 2026, 01:1027,494+43
29 Oct 2026, 03:2827,451-149
28 Oct 2026, 00:1927,600+35
27 Oct 2026, 03:3627,565-63
26 Oct 2026, 01:0827,628+14
25 Oct 2026, 02:5927,614+16
23 Oct 2026, 23:2727,598+92
22 Oct 2026, 20:4527,506+83
21 Oct 2026, 13:4627,423+50
20 Oct 2026, 10:0627,373+36
19 Oct 2026, 13:0927,337+30
18 Oct 2026, 15:5627,307+49
17 Oct 2026, 19:1827,258+59
16 Oct 2026, 22:1027,199first reading

Engagement

81 posts held, back to 4 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 140 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.90%
avg views ÷ 27,628 subscribers
Avg views / post
1,080
53 posts measured
Reaction rate
0.266%
reactions ÷ views · ER floor
Posts in window
53
of 81 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 51 of 53 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 5 November 2026
Posts held81 (4 August 2026 – 5 November 2026)
Views total57,036
Reactions total145
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 14:55 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,820
Videos
≈248
Links
≈140

Lifetime counters from Telegram’s own channel header, read 5 November 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
3m 10s
Average length
8s

Measured directly from 23 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

227 reactions across 79 posts, in 4 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8135.7%
❤7834.4%
👍5825.6%
🥰104.41%

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

Measured over the 81 most recent posts we hold, published 4 August 2026 to 5 November 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

Telegram’s own ‘edited’ marker: 1 of 53 posts held from the last 30 days (1.89%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 07:12 UTC27 views1 reactionsread 5 November 2026
Photo

【老 师 艺 名】#呆小雨 【所 在 位 置】#杭州 #上城 【茶 位】#14P #24PP 【服 务 类 型】#胸推 #丝袜 #舌吻 【联 系 方 式】@dafxiaoyu 【老 师 频 道】@fshhstt 【双向机器人】@faggayabot 备注: #个人老师

🔥1

4 Nov 2026, 14:12 UTC≈1,050 views2 reactionsread 5 November 2026

【老师艺名】#奶茶 【联系方式】@hzNaicha12 【上课地址】上城 【上课价位】1600p 【验证留名】汤 【验证时间】11.3 【颜值身材】大奶 【服务内容】课表 【服务态度】会摇,特别骚 【优点缺点】身材火辣 【体验细节】进门第一眼看到的是奶茶老师的胸器,好大好亮眼,身穿性感衣服,车灯巨亮眼,身材火辣的很,跟图片上本人9分像,心底暗暗开心。房间看着也干净整洁,进门很有礼貌问好,聊了一下天交水费,老师拿了一次性浴巾给我去洗个澡,在床上等着老师,看着老师光溜溜的身体那对大奶子对我杀伤力最大,小弟弟马上竖起来了,奶子上手真不错又圆又大,一只手真覆盖不了,摸起来好得劲。真实体验奶子是真实的,不是那种科技来的,口活也好!!最主要还是老师的车灯真值了!敏感身体老师水特别多,摸到老师受不了,她说我好多水受不了呢,要我干她,还张开大腿让我看说水都流在她的大腿上了,受不了她的请求,叫老师带上套干她,插进去挺紧的好爽,老师叫声好迷人,看着…

❤2

4 Nov 2026, 14:00 UTC≈1,050 views3 reactionsread 5 November 2026
Photo

【老 师 艺 名】#奶茶飘香 【所 在 位 置】#杭州 #上城 【茶 位】#16P #30PP 【服 务 类 型】#陪浴 #胸推 #调情 【联 系 方 式】@hzNaicha12 【老 师 频 道】@Himalayas223 【双 向 联 系】@Piaoxiang_bot 备注: #个人老师 报告一

❤1👍1🔥1

4 Nov 2026, 11:26 UTC≈1,060 views3 reactionsread 5 November 2026

【验证留名】:78 【验证时间】:2026-11-4 【妹子花名】:鑫鑫 【联系方式】: @feng0215 【所在位置】:滨江区 【修车水费】:700 【照片相似】:9.5 【颜值身材】:9.5 【凶器罩杯】:9.5 【服务项目】:pp 【服务详情】:服务细致,态度好,老师很亲切,说话温柔,口活很好,人图一致,很漂亮有气质,毒龙很舒服,值得一试。 【优点缺点】:无缺点

❤1👍1🔥1

3 Nov 2026, 02:31 UTC≈2,100 views3 reactionsread 5 November 2026
Photo

【老 师 艺 名】#洛洛 【所 在 位 置】#杭州 【茶 位】#8P #15PP 【服 务 类 型】#陪浴 #胸推 #调情 【联 系 方 式】@pc0288 【老 师 频 道】@zzwm008 【双 向 联 系】@ls0288_bot 备注: #个人老师

❤1🔥1🥰1

2 Nov 2026, 04:30 UTC≈2,110 views5 reactionsread 5 November 2026
Photo

省份:#浙江 城市:#湖州 年龄:20 身高: 162 体重: 84 罩杯: b 职业:刚休学 能否口:可 能否SM:可 测试后能否无套:否 能否内射:否 能否过夜:可 能否同居:可 有没有纹身:有 能否飞外省:可近一点 雷点(不接受): 大姨妈日期:不准 每月陪伴天数:3天—7天 期望零花钱:8K—1.5W 分几次支付零花钱:2次 最早出发时间:很听话 给老板提供情绪价值 老板是天老板是地 说一不往二 是小m 被爸爸打骂绝不说二 介绍费:7888 木槿花 #包养 🌸真实反馈成交 🌸 尊贵VIP权益 🌸主动私聊强拉均为骗子切勿上当 🌺点击查看>新手必看和地区资源 唯一包养客服 @Baoyxin 双向私聊限制 @Baoyxin_bot

❤2🔥2👍1

2 Nov 2026, 04:30 UTC≈1,110 views3 reactionsread 5 November 2026
Photo

省份:#浙江 城市:#杭州 年龄:18 身高: 165 体重: 102 罩杯: B 职业:雪生 是否chu: 否 能否口:可 能否SM: 可 测试后能否无套: 可 能否内射: 否 能否多人: 否 能否过夜: 可 能否同居: 可 有没有纹身: 无 能否kiss: 可 能否飞外省: 可 雷点(不接受): 情绪不稳定 大姨妈日期: 月初 每月陪伴天数: 7天 期望零花钱: 2W 分几次支付零花钱: 2次 最早出发时间: 随时 自我加分项:艺术生学过美术摄影舞蹈钢琴竹笛 情绪稳定性格好有活力可清纯可性感风格多变 介绍费:7888 木槿花 #包养 🌸真实反馈成交 🌸 尊贵VIP权益 🌸主动私聊强拉均为骗子切勿上当 🌺点击查看>新手必看和地区资源 唯一包养客服 @Baoyxin 双向私聊限制 @Baoyxin_bot

❤1👍1🔥1

1 Nov 2026, 11:27 UTC≈1,960 views4 reactionsread 4 November 2026
Photo

【老 师 艺 名】#静静妹吖 【所 在 位 置】#杭州 #上城 【茶 位】 #8P #16PP 【服 务 类 型】#全套 【联 系 方 式】@q6756322 【老 师 频 道】@wen52052 【双向机器人】@Wexnlybot 备注: #个人老师 #视频认证

🔥2❤1👍1

31 Oct 2026, 02:36 UTC≈1,120 views4 reactionsread 2 November 2026
Photo

【极致欢愉】 换装女仆spa. #杭州 ⭐ 主人~来极致欢愉spa私密馆,让骚浪极品女仆跪在你面前侍奉 ! ⭐ 在这里,黑丝、短裙、娇喘、湿滑小手……全部为您敞开,榨干你的每一滴~ ⭐️ 799元 · 60分钟 极致榨精服务 ⭐️ (导航):点击>>观看 (服务流程) :点击 >> 观看 https://t.me/xnlspahhh/41 (预约流程) : 1️⃣ 店内常驻金牌技师3-4位,兼职主播模特5位以上随叫随到可选到满意。 2️⃣ 预约好时间后可到店选人,也可线上指定技师,因为保证服务质量,一小时20分钟一位,所以请提前预约时间安排房间。 🍎【兼职可加联系方式可私约】 房间私密安全氛围极佳,单独房间配置独立卫浴和浴缸 🛁 【位置请私信可以查看】 ❗️ 【注意】❗️:无任何类型的会员卡,充值卡,次数卡。 🌷 预约客服 : @nacney ⭐ 双向机器人 :@xnlspabot 🌷 QQ号…

❤2👍1🔥1

30 Oct 2026, 05:58 UTC≈2,120 views4 reactionsread 2 November 2026
Photo

昵称:圆子 所在省份:#浙江 所在城市:#杭州 年龄:21 身高:170 体重:94 罩杯:B 是否雪生:模特 是否是处:否 可不可以口:能 可不可以无套:否 可不可以内设:否 可以不以Sm:能 是否有纹身/抽烟:否 大姨妈日期:15号左右 是否可以省外:能 是否可以港澳:能 是否可以出国:仅新加坡 是否可以过夜:能 是否可以同居:看情况 可陪伴天数:3天 生活费多少:1.5万 分几次给:2次 自我加分项:敏感体质。反差,笑起来有酒窝。听话性格好。情商高情绪价值足,女友感满满,可御可甜,超级配合,是个小M 对老板的雷点(不接受): 介绍费7888 发财-多金 D #包养 🌸真实反馈成交 🌸 尊贵VIP权益 🌸主动私聊强拉均为骗子切勿上当 🌺点击查看>新手必看和地区资源 唯一包养客服 @Baoyxin 双向私聊限制 @Baoyxin_bot

❤2👍1🔥1

30 Oct 2026, 05:58 UTC853 views3 reactionsread 31 October 2026
Photo

昵称:咖啡 省份:#浙江 城市:#杭州 年龄:22 身高:172 体重:100 罩杯:b 职业:雪生 是否是处女:不是 可不可以口:可以 能不能内射:➕💰 能不能无套:能 SM能不能:可以 是否可外省:可以 是否可出国:可以 是否可过夜:可以 可不可以同居:可以 可陪伴天数:3/7天 大概姨妈日期:月底 生活费多少: 3天8000/七天1.3 分几次给生活费:2次 自我介绍加分项:kou活可以, 身材比例模特身材 穿衣比较气质 床上会让老板舒心 对老板雷点(不接受):gang门 不暴躁都没问题 介绍费6888 发财-多金 D #包养 🌸真实反馈成交 🌸 尊贵VIP权益 🌸主动私聊强拉均为骗子切勿上当 🌺点击查看>新手必看和地区资源 唯一包养客服 @Baoyxin 双向私聊限制 @Baoyxin_bot

❤1👍1🔥1

30 Oct 2026, 05:58 UTC891 views3 reactionsread 1 November 2026
Photo

省份:#浙江 城市:#杭州 年龄:20 罩杯:c 身高:163 体重:98 目前职业:雪生 是否可去外省:可 能否出国伴游:否 可见面时间:都可以 每月所需生活费:1w/2万 每月可陪伴几天:3天/7天 是否处女:否 能否同居:可 生理日期:15号 能否无tao:能 (体检/试纸后) 能否kou:可 能否SM(哪种程度):m 中等 对金主要求:大方 尊重我 加分项(自身优点):骚 听话懂事 纯天然 奶子大可以蹂躏 可以调教 喜欢刺激 介绍费6888 发财-多金 D #包养 🌸真实反馈成交 🌸 尊贵VIP权益 🌸主动私聊强拉均为骗子切勿上当 🌺点击查看>新手必看和地区资源 唯一包养客服 @Baoyxin 双向私聊限制 @Baoyxin_bot

❤1👍1🔥1

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

Posts edited after publishing

@gzzypd66 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.

First edit seen
17 October 2026
Most recent edit
17 October 2026

Posts recorded as deleted after publishing

We recorded 1 post on @gzzypd66 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
19 August 2026
Most recent seen missing
19 August 2026
Median time before seen missing
13 days
Seen missing in the last 30 days
0

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

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

“杭州【认证榜单】” (@gzzypd66), 27,628 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/gzzypd66.

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.