Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州瓜田

Channel

杭州瓜田

@HangZhouGT

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

21,706subscribers

+4,718 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-1003105402119
TypeChannel
Username@HangZhouGT
Description吃瓜群: @HZGUATIAN 接投稿: @Zxj_123 @FLOAT_xyz
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/HangZhouGT

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 71% 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

16,98821,70619,3477 August 2026 — 16,988 subscribers7 August 2026 — 16,996 subscribers9 August 2026 — 17,016 subscribers10 August 2026 — 16,994 subscribers11 August 2026 — 17,037 subscribers12 August 2026 — 17,075 subscribers13 August 2026 — 17,141 subscribers14 August 2026 — 17,204 subscribers16 August 2026 — 17,292 subscribers17 August 2026 — 17,349 subscribers18 August 2026 — 17,374 subscribers19 August 2026 — 17,402 subscribers20 August 2026 — 17,404 subscribers21 August 2026 — 17,484 subscribers22 August 2026 — 19,541 subscribers24 August 2026 — 19,660 subscribers25 August 2026 — 19,716 subscribers26 August 2026 — 19,768 subscribers27 August 2026 — 19,814 subscribers28 August 2026 — 19,912 subscribers29 August 2026 — 19,958 subscribers30 August 2026 — 20,101 subscribers31 August 2026 — 20,292 subscribers1 September 2026 — 20,450 subscribers2 September 2026 — 20,497 subscribers4 September 2026 — 20,588 subscribers6 September 2026 — 20,742 subscribers9 September 2026 — 21,270 subscribers12 September 2026 — 21,318 subscribers13 September 2026 — 21,405 subscribers15 September 2026 — 21,495 subscribers17 September 2026 — 21,662 subscribers27 September 2026 — 21,706 subscribers7 August 202627 September 2026
33 measurements spanning 51 days, net +4,718. 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 16,280–22,414 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
27 Sept 2026, 16:4121,706+44
17 Sept 2026, 13:5721,662+167
15 Sept 2026, 13:4121,495+90
13 Sept 2026, 20:4121,405+87
12 Sept 2026, 06:4021,318+48
9 Sept 2026, 22:1521,270+528
6 Sept 2026, 12:2120,742+154
4 Sept 2026, 04:0020,588+91
2 Sept 2026, 14:4620,497+47
1 Sept 2026, 15:0920,450+158
31 Aug 2026, 17:2520,292+191
30 Aug 2026, 18:1620,101+143
29 Aug 2026, 19:4419,958+46
28 Aug 2026, 17:4919,912+98
27 Aug 2026, 14:3419,814+46
26 Aug 2026, 14:4319,768+52
25 Aug 2026, 13:3219,716+56
24 Aug 2026, 14:3519,660+119
22 Aug 2026, 23:3519,541+2,057
21 Aug 2026, 12:2817,484first reading

Engagement

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

ERR · 30 days
14.2%
avg views ÷ 21,706 subscribers
Avg views / post
3,090
14 posts measured
Reaction rate
0.116%
reactions ÷ views · ER floor
Posts in window
14
of 41 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 September 2026
Posts held41 (5 August 2026 – 29 September 2026)
Views total43,275
Reactions total50
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 17:06 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,220
Videos
≈24
Links
≈73

Lifetime counters from Telegram’s own channel header, read 29 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
5m 00s
Average length
1m 15s

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

289 reactions across 39 posts, in 5 distinct kinds. The most used accounts for 74.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤21474.0%
💩4415.2%
👍165.54%
🤮144.84%
🥰10.346%

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

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

29 Sept 2026, 16:02 UTC519 views0 reactionsread 29 September 2026
Photo

2026年9月29日杭州瓜田讯: 外地网黄向瓜台控诉其在杭州拱墅区的恶劣踩雷遭遇。当事人根据榜单推荐预约标价1500元/P的从业者“尚尚”(TG:@sbx520),线上沟通时对方态度生硬且百般设防,付定后仅给模糊地址,致使其在楼下“罚站”近半小时。 随后进门照面,现场女生(自称05年艺术生)货不对板严重——身材扁平、脚踩人字拖,与频道精修照判若两人。当事人当场拒绝接受服务并要求退还定金,女生口头答应后却未履约。下楼交涉期间,线上中介反诬当事人没上楼是骗子,强索大堂拍照自证后,迅速将聊天记录“双向清空并拉黑”;当事人下楼堵到该女生追讨时,对方则直接甩锅“定金是代聊收的,找中介退”。 事后,当事人将材料同步投诉给上榜的三个群组群主。“捕蛇大队”群主在核实女方已读不回后,已下架其轮播推荐;但另两家榜单群主对此反应消极。 该老师同时出现在韩信优选榜、捕蛇大队采仙阁等多个榜单,内容高度一致。模式与此前假冒半岛频道、真假混杂1500…

29 Sept 2026, 08:43 UTC≈1,750 views3 reactionsread 29 September 2026
Photo

9.29日杭州瓜田讯-接狼友投稿 某位叫财财的老师,目前没看到杭州大群在榜,但是狼友之前经过某位大群管理推荐该位老师,狼友便在9月18日已经开始约课而当时老师频道说在宁波,约课失败。紧接着老师9.28日发频道在杭州开课,狼友便9.29日中午进行约课,从一开始的老师说自己在萧山,再到后面“我在宁波还没去呢”,随着老师时间跟狼友无法同步,定金也由200升级为1000,可能是觉得这个pp也不少钱可以一试,老师也是相对比较执念再次将定金下降为500也可以,但是狼友也机警的表示定金过于多,没有轻易给出大额定金,同时认为萧山到拱墅200定金绰绰有余,随着老师城市一会儿在这一会儿在哪,定金忽上忽下,并且课表随机应变根据狼友反应是25p 45pp随后又更改为26p 52pp,到后面老师已经对这个定金执迷不悟甚至说狼友是同行(狼友为真实出击狼友有多篇报告佐证),狼友感觉事有不妙,果断终止本次约课。记者根据id搜索老师,先是看到该老师曾经25年已…

❤3

28 Sept 2026, 11:49 UTC≈2,890 views8 reactionsread 29 September 2026
Photo

瓜台杭州9月28日电 9月28日晚,杭州修车圈因一桩“被闲聊拖掉第二发”的投诉案,引起全网狼友关于“双P服务标准到底归谁管”的大辩论。当事人“半山猛虎”在繁花荟售后群发难,称预约老师2800元的双P套餐后,首发刚完女方便全程拉着闲聊,丝毫不提时间进度,临近尾声才以“下个客人要到了”为由拒绝打第二发,且最终只肯退还半P费用700元。 这桩纠纷迅速在瓜田讨论组发酵,核心争议在于“老师到底有没有主动把控时间与提醒第二发的义务”。支持狼友的网友认为,双P是花高价买的定额服务,老师明知后序有客却不把控节奏,靠聊天硬生生“油掉”一发纯属消极怠工的套路;而站台管理方与老师的网友则反驳,90分钟课时已完全给足,很多客人自身CD跟不上还不主动要求,临近下钟才压哨索取,本质是“超时白嫖时间”,既然有需求就该自己开口。双方各执一词,将灰色交易缺乏行业标准的遮羞布彻底扯开。 小编说: 花了两发的银子,最后听了半宿闲话,这冤大头当得确实窝火;但既指望…

❤8

27 Sept 2026, 15:01 UTC≈2,270 views2 reactionsread 28 September 2026
Photo

瓜台杭州9月27日电 9月27日,某老师使用小号向瓜台大吐苦水,曝光针对从业女生的恶性侵害与诈骗连环案。据透露,她在短短数日内接连遭遇黑手:先是在前两天的课次中被客人趁乱盗走现金4400元;未料今日再度上工时,又碰上一名蓄意做局的嫖客。 该男客进门时假意掏出厚叠真钞付款博取信任,随后在过程中故意拔套霸王硬上弓;趁女生完事去卫生间冲洗的间隙,男方迅速将原本的真钞全数调包为银行“练功券”,随即夺路而逃。事后女生线上追讨,男方不仅拒不认账,还百般推脱并试图诱骗女生夜间孤身前往临平“当面解决”,最终直接玩起赖账拖延。碍于涉黄不敢报警的法治软肋,当事人不仅身心受创、钱财尽失,还只能自认倒霉。 小编说:以前大家钱包鼓的时候,消费图个省心痛快,圈子里讲究点“体面”和“行规”;现在各行各业都卷,兜里越掏不出银子,戾气就越重,牛鬼蛇神也全冒出头了。 灰产本身就没有任何法律兜底,当道德约束在经济压力下彻底崩塌,下限就被无限拉低——前有偷钱拔套…

❤2

25 Sept 2026, 13:15 UTC≈3,880 views9 reactionsread 28 September 2026
Photo

瓜台杭州9月25日接狼友投稿 9月23日,修车大群“杭州肯德基”新上榜老师“小沫”(@zxiaomo / @hxiaomo)引爆舆论质疑。 多名狼友发现其存在严重的“阴阳课表”行为:两个账号两个频道,加入不同的群组且在同步更新。其历史频道及郑州常驻期间标价为单次800元,但此番挂牌杭州后,单价竟直接暴涨至1200元。群内狼友就两份相差400元的课表提出质询时,管理方仅强硬回应“以我发的为准,你可以退工兵”。 随着瓜台记者深挖,该从业者在郑州时期的“黑历史”也相继浮出水面。据“郑州避雷俱乐部”公开记录,其在郑州期间就频遭避雷差评:不仅长期存在“照片过度高P导致狼友现场退定、多次借口红休前后矛盾放鸽子”等劣迹,更曾在服务中,因狼友调侃其假体胸部,盛怒之下直接掌掴狼友两巴掌,事后还自称“打人挺爽”。 此外,记者调查发现该人还同步活跃于福利姬与包养门槛圈。私聊咨询,对方直接索要“188元门槛费”;待追问有何福利时,对方仅冷冷抛出“…

❤8👍1

25 Sept 2026, 06:16 UTC≈3,350 views2 reactionsread 28 September 2026

开奖啦!但愿人长久,千里共婵娟(TL179031564570)已成功开奖。 🎰参与人数:99 📋中奖名单如下: StuartYung(奖品为口令红包50) 鸡管所所长(奖品为口令红包50) 你说一二三(奖品为口令红包66) meteorPisces(奖品为口令红包66) 鱼鱼(古灵精怪,拱墅区)(奖品为口令红包88) YOLO(奖品为口令红包88)

👍2

25 Sept 2026, 05:54 UTC≈3,220 views2 reactionsread 28 September 2026

🎟️ 抽奖标题:但愿人长久,千里共婵娟 抽奖编号:TL179031564570 🎁 奖品内容: - 口令红包50*2 - 口令红包66*2 - 口令红包88*2 🪧 抽奖说明:达到条件的用户自动参与抽奖 🎫 参与条件: - 从2026-09-05 08:00:00起发言数量不少于28 ​🕒​ 开奖时间:2026-09-25 14:00自动开奖 🎰已参与人(0):

❤2

24 Sept 2026, 13:20 UTC≈3,700 views3 reactionsread 28 September 2026
Forwarded from @chujian901Photo

🎰 🌕 【初见 ✖️ 频道联合】中秋国庆双节大放送 🚩 📮 参与条件: 🪪 必须设置用户名 🎫 加入-【初见】福利涩涩群 └ 🔑 发送口令﹝初见包养中秋国庆双节大放送﹞ 🎫 加入-【初见 】全国包养中转站 🎫 加入-【初见】萝莉包养交流群 └ 🎟️ 发言数大于 30 条 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 520现金红包 × 1 💰️ 5折介绍费抵扣券 × 2 💰️ 88现金红包 × 8 💰️ 初见VIP会员 × 3 ⚠️ 抽奖说明: 🌕 【初见 ✖️ 频道联合】2026 双节解压礼包,全网空投! 🏮 看腻了流水线外围,受够了老师诈骗?【初见全国包养】坚持 纯净素人定制 ,携手各大频道开启双节联合福利: 👑 VIP 群特惠(入会送大礼): 🎟 9月24日-10月7日入会即送288、588、888、 1,888 元抵扣券 🏆 双节特许破格席位: 抽取 1 人享 “实充 5W 破格享有 …

❤2👍1

22 Sept 2026, 14:43 UTC≈5,280 views3 reactionsread 28 September 2026
Photo

2026年9月22日杭州瓜田讯: 接狼友投稿之可可巧克力包夜跑路记:中途借口买东西直接消失 狼友今日投稿称,约了可可巧克力(@chocolateke,频道“可可的外卖小屋”)包夜。过程中对方借口出去买东西,随后直接失联跑路。 关键异常点: 频道单条内容浏览量高达 13.4万、12.8万,订阅数仅1万左右(当然这1w也是刷的),数据严重不匹配,典型刷量特征。 此前已有类似“中途离开再也不回”的案例,属于当前常见跑路手法之一。 狼友表示希望曝光,避免更多人上当,并询问遇到视频里面这种“滚刀肉”(拖延、装死、耗着不退不回应)时该怎么办呢。(视频是相同套路的老视频了,与该狼友无关) 小编说:这种套路确实屡见不鲜。 这种肯定是没上靠谱修车群的,应该立刻固定证据:完整保存聊天记录、转账记录、通话记录、位置信息、时间线。能录音录像尽量保留(注意合法范围)。然后携带材料到派出所报案(当然,有些会跟你做一次然后再偷,这种没办法了,你可以换个小号…

❤3

22 Sept 2026, 14:28 UTC≈6,170 views2 reactionsread 27 September 2026

如何识别TG骗子老师(杭州及常见修车圈适用) 新手避雷贴很难写,新手看不见(tg踩雷真是不得不品的一环),老手用不着。写起来可以说是吃力不讨好。不过记者在这里还是结合前期大量投稿案例和常见套路,整理一份实用检查清单。真正靠谱的老师一般不会踩太多这些点,踩得越多,风险越高。当然最重要的是从靠谱榜单上获得老师的联系方式,不要加了老师联系人,加了老师的频道就不看大群频道榜单了,老师被盗号之后还傻乎乎去送钱 !!! 1. 位置与沟通方式 主动问你在哪个城市/区:正规楼凤或本地老师通常直接发自己的大致位置或小区范围,很少先反问你在哪。骗子喜欢广撒网,先确认你在目标城市再推进。 位置含糊或频繁更换:今天说上城,明天说萧山,后天又说在外地“刚回来”。 拒绝视频验证或只发旧视频:真正在本地的通常愿意做简单实时验证(遮脸、做指定动作)。死活不视频、只发相册的,风险高。 2. 价格异常 包夜/PP价格明显低于市场:杭州正常包夜普遍在3.5P–5P…

❤2

22 Sept 2026, 09:02 UTC≈4,330 views10 reactionsread 27 September 2026
Photo

《竞拍约课,罚站两小时》 接狼友投稿 事情是从颜值群的一个竞拍开始,@wandoudo1 安安老师做了一个拍卖活动,被狼友竞拍所得,约定好上课时间狼友如约而至,甚至也是提前到了临近时间老师告知忘记了这一课,狼友也是耐心的等待哪怕是罚站一小时,一小时后又告知还要等待30分钟,结果看聊天记录是一直等待了2小时,将近九点钟才告诉狼友楼栋。。整个过程狼友都没有无理取闹或者说任何不素质行为,一步步的从一个小时等到一个半小时再到最终两个小时,等到见到老师本人后,老师轻飘飘一句:不好意思忘了时间就打发了没有什么歉意,自顾自的玩手机,狼友没有提出什么过分的要求也没有要补偿或者什么的,但是这种轻飘飘的态度实在令人下头,最终狼友实在忍无可忍选择果断转身,说实话狼友算挺有耐心了。记者不理解的是为什么忘记了连一个道歉都不会一个宽慰都给不了,老师的时间是时间,狼友的时间也同样是的时间啊,并且时间是一拖再拖,毫无信誉可言把狼友当猴耍。 最后狼友向颜值群管理…

❤10

3 Sept 2026, 02:10 UTC416 views2 reactionsread 3 September 2026
Photo

《代发避雷讯息,老师否认,系列》 事情是这样的,在杭州小东西群有一个狼友帮一个群友发了一个避雷的讯息,并且艾特肯德基说是看肯德基频道去的,可能当时狼友也没想什么觉得这是个玩家交流群,说说就说说得了大家都避雷一下。但是呢岂不料老师追过来了,否认了一些事情,并且记者也采访了老师和狼友几点: 1.肚子上有疤用透明胶带贴着不知道啥情况 后背靠下面生长纹可明显 一缕一缕的 老师答:个人原因 狼友本人:这我可不敢乱说 不知道怎么造成的 2.毛巾收费的事情 老师答:给他说了一次性浴巾在哪,那是我自己新买来用的,他给我用了,我找他赔钱 狼友本人:她没跟我说浴巾在哪里,但是我看到她在摆弄那个毛巾,以为是给我准备的我就顺手拿来用了,最后赔了没几个子儿 3.不让亲 老师:让亲的一直都是让亲的 狼友本人:一开始是让亲的,但是做的时候不让亲 4.态度问题 老师:可能情绪管理没有特别好,给他带了不好的体验(我认错) 狼友本人:她催课赶人,我知道我可…

❤2

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“杭州瓜田” (@HangZhouGT), 21,706 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/HangZhouGT.

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.