Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州硬了么老师榜

Channel

杭州硬了么老师榜

@hangzhoudelaoshi

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

10,436subscribers

+10,363 since we began measuring on 3 September 2026

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

Register entry

Telegram ID-1003830134888
TypeChannel
Username@hangzhoudelaoshi
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live4 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/hangzhoudelaoshi

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 2 October 2026 and assigned it the closest of 31 fixed categories, at 75% 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

7310,4365,254.53 September 2026 — 73 subscribers3 September 2026 — 73 subscribers4 September 2026 — 102 subscribers12 September 2026 — 1,046 subscribers16 September 2026 — 1,247 subscribers2 October 2026 — 2,524 subscribers9 October 2026 — 6,018 subscribers14 October 2026 — 6,871 subscribers16 October 2026 — 7,426 subscribers19 October 2026 — 7,707 subscribers22 October 2026 — 7,945 subscribers25 October 2026 — 8,327 subscribers28 October 2026 — 8,881 subscribers31 October 2026 — 9,745 subscribers4 November 2026 — 10,436 subscribers3 September 20264 November 2026
15 measurements spanning 62 days, net +10,363. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 06:5510,436+691
31 Oct 2026, 20:089,745+864
28 Oct 2026, 10:378,881+554
25 Oct 2026, 20:058,327+382
22 Oct 2026, 18:477,945+238
19 Oct 2026, 15:167,707+281
16 Oct 2026, 21:177,426+555
14 Oct 2026, 00:066,871+853
9 Oct 2026, 09:026,018+3,494
2 Oct 2026, 16:392,524+1,277
16 Sept 2026, 13:361,247+201
12 Sept 2026, 15:181,046+944
4 Sept 2026, 00:41102+29
3 Sept 2026, 10:1573no change
3 Sept 2026, 10:0073first reading

Engagement

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

ERR · 30 days
2.35%
avg views ÷ 10,436 subscribers
Avg views / post
246
13 posts measured
Reaction rate
0.113%
reactions ÷ views · ER floor
Posts in window
13
of 18 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 3 of 13 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 4 November 2026
Posts held18 (2 September 2026 – 4 November 2026)
Views total3,193
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 12:01 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
542
Videos
79
Links
164

Lifetime counters from Telegram’s own channel header, read 4 November 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.

Video runtime
1m 01s
Average length
10s

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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 4 of the 18 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 2 September 2026 to 4 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: 0 of 13 posts held from the last 30 days (0%) 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).

3 Nov 2026, 13:17 UTC191 viewsread 4 November 2026
Photo

双向机器人:@ 🆔艺名:#软绵绵 🚀私聊:@jsfff888999 📍地址:#上城区 💲价格:#1200p #2400pp ⭐️特色:#长腿 #嫩妹 #舌吻 #69 ✍️撰写报告 👀查看报告 🔙返回总榜 ↩️返回交流群 工兵留名: 过程描述:☞(查看软绵绵 的0报告)

3 Nov 2026, 10:28 UTC193 viewsread 4 November 2026
Photo

🎉 筱筱十一月活动 🎁 奖品清单 • 筱筱半价券 × 1 • 红包18.8 × 1 🛡️ 参与条件 • 加入 杭州硬了么 • 加入 杭州硬了么老师榜 • 加入 硬了么报告鉴赏 • 加入 筱筱的圈子 • 参加抽奖后需在 杭州硬了么 内发言58次 └ 群内发送“抽奖进度”查看完成度(每日限5次) • 必须设置用户名 🔮 祝福加持 • 祝福消耗:10抽奖币 • 祝福上限:无上限次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-11-07 12:30:00 📜 抽奖说明 核销流程:通过 榜单 预约老师,完成约课,找报告机器人 @hzylmbot 填写报告后,联系 @hangzhouyinlemebot 核销。 积分抽奖 有效期:3天 积分兑换 有效期:3天 活动抽奖 有效期:5天 报告机器人:@hzylmbot 活动联系核销:@hangzhouyin…

3 Nov 2026, 09:13 UTC155 viewsread 4 November 2026
Photo

双向机器人:@xiaoxiao20030601bot 🆔艺名:#筱筱 🚀私聊:@xiaoxiao20030601 📍地址:#上城区 💲价格:#700p #1400pp ⭐️特色: #舌吻 #69 ✍️撰写报告 👀查看报告 🔙返回总榜 ↩️返回交流群 工兵留名: 过程描述:☞(查看筱筱 的0报告)

3 Nov 2026, 04:30 UTC202 viewsread 4 November 2026
Photo

✨ 命运揭晓时刻 ✨ 小慕十月活动 开奖了 抽奖人数:76,发言达标人数:56,抽奖号数:411 1. 石耳一颗【祝福39次】 中得:小慕半价券 2. 星轨坠入夜【祝福38次】 中得:红包18.8 抽奖说明: 核销流程:通过 榜单 预约老师,完成约课,找报告机器人 @hzylmbot 填写报告后,联系 @hangzhouyinlemebot 核销。 积分抽奖 有效期:3天 积分兑换 有效期:3天 活动抽奖 有效期:5天 报告机器人:@hzylmbot 活动联系核销:@hangzhouyinlemebot 本次活动由赞助:@hangzhouyingleme 🔍 杜绝黑幕,点击查看本次开奖全程验证

2 Nov 2026, 04:30 UTC287 views0 reactionsread 4 November 2026
Photo

✨ 命运揭晓时刻 ✨ 玉小白十月活动~ 开奖了 抽奖人数:77,发言达标人数:56,抽奖号数:549 1. Beth駬柿參【祝福10次】 中得:玉小白半价券 2. 天you天【祝福41次】 中得:红包18.8 抽奖说明: 核销流程:通过 榜单 预约老师,完成约课,找报告机器人 @hzylmbot 填写报告后,联系 @hangzhouyinlemebot 核销。 积分抽奖 有效期:3天 积分兑换 有效期:3天 活动抽奖 有效期:5天 报告机器人:@hzylmbot 活动联系核销:@hangzhouyinlemebot 本次活动由赞助:@hangzhouyingleme 🔍 杜绝黑幕,点击查看本次开奖全程验证

2 Nov 2026, 03:52 UTC248 viewsread 4 November 2026
Photo

双向机器人:@yingying789bot 🆔艺名:#莹莹 🚀私聊:@ying667788 📍地址:#上城区 💲价格:#700p #1300pp ⭐️特色:#嫩妹 #69 #舌吻 ✍️撰写报告 👀查看报告 🔙返回总榜 ↩️返回交流群 工兵留名: 过程描述:☞(查看莹莹 的0报告)

2 Nov 2026, 01:14 UTC243 viewsread 4 November 2026
Photo

双向机器人:@Xrumeng_bot 🆔艺名:#如梦 🚀私聊:@Xrumeng00 📍地址:#上城区 💲价格:#800p #1500pp ⭐️特色: #接吻 #69 ✍️撰写报告 👀查看报告 🔙返回总榜 ↩️返回交流群 工兵留名: 过程描述:☞(查看如梦 的0报告)

1 Nov 2026, 08:12 UTC212 views0 reactionsread 3 November 2026
Photo

双向机器人:@Lean001_bot 🆔艺名:#乐安 🚀私聊:@lean239 📍地址:#上城区 💲价格:#1200p #2400pp ⭐️特色:#长腿 #御姐 #舌吻 #69 ✍️撰写报告 👀查看报告 🔙返回总榜 ↩️返回交流群 工兵留名: 过程描述:☞(查看乐安 的0报告)

1 Nov 2026, 04:30 UTC253 viewsread 3 November 2026
Photo

✨ 命运揭晓时刻 ✨ 果果十月活动 开奖了 抽奖人数:74,发言达标人数:54,抽奖号数:334 1. 快速回本【祝福6次】 中得:果果半价券 2. 有安博【祝福1次】 中得:红包18.8 抽奖说明: 核销流程:通过 榜单 预约老师,完成约课,找报告机器人 @hzylmbot 填写报告后,联系 @hangzhouyinlemebot 核销。 积分抽奖 有效期:3天 积分兑换 有效期:3天 活动抽奖 有效期:5天 报告机器人:@hzylmbot 活动联系核销:@hangzhouyinlemebot 本次活动由赞助:@hangzhouyingleme 🔍 杜绝黑幕,点击查看本次开奖全程验证

30 Oct 2026, 14:18 UTC350 viewsread 3 November 2026
Photo

杭州硬了么月末硬币刮刮乐活动开启! 🎉 杭州硬了么月末硬币活动 火热来袭! 月末福利大放送,快来试试你的手气,把丰厚奖品带回家! 🎁 活动奖品一览: ● 🎫 通用优惠券 300 × 1 ● 🎫 通用优惠券 200 × 1 ● 🧧 现金红包 18.8 × 3 ● 🧧 现金红包 28.8 × 2 ● 🧧 现金红包 38.8 × 1 ● ✈️ TG会员 3个月 × 1 ● ✈️ TG会员 6个月 × 1 📅 活动时间: 每月月末 📍 参与方式: 加入我们的频道,参与刮刮乐活动! 👉 快来加入 @hangzhouyingleme,一起刮出好运!

29 Oct 2026, 14:30 UTC415 viewsread 3 November 2026
Photo

🎉 向晚十月活动 🎁 奖品清单 • 向晚半价券 × 1 • 红包18.8 × 1 🛡️ 参与条件 • 加入 杭州硬了么 • 加入 向晚家苑 • 加入 杭州硬了么老师榜 • 加入 硬了么报告鉴赏 • 参加抽奖后需在 杭州硬了么 内发言58次 └ 群内发送“抽奖进度”查看完成度(每日限5次) • 必须设置用户名 🔮 祝福加持 • 祝福消耗:10抽奖币 • 祝福上限:无上限次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-11-05 12:30:00 📜 抽奖说明 核销流程:通过 榜单 预约老师,完成约课,找报告机器人 @hzylmbot 填写报告后,联系 @hangzhouyinlemebot 核销。 积分抽奖 有效期:3天 积分兑换 有效期:3天 活动抽奖 有效期:5天 报告机器人:@hzylmbot 活动联系核销:@hangzhouyinle…

Showing the 12 most recent of 18 posts we hold for @hangzhoudelaoshi. 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 recorded as deleted after publishing

We recorded 3 posts on @hangzhoudelaoshi 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
3 November 2026
Most recent seen missing
4 November 2026
Median time before seen missing
15 hours
Seen missing in the last 30 days
3

Mentions

Named by 4 registered channels — 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.

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.

“杭州硬了么老师榜” (@hangzhoudelaoshi), 10,436 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/hangzhoudelaoshi.

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.