Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州798

Channel

杭州798

@hangzhou_798

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

35,111subscribers

+3,714 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1002204675374
TypeChannel
Username@hangzhou_798
Description上榜联系 @hz798_Admin 群务管理 @hangzhou798bot 杭州798交流群 @hangzhou798
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live17 September 2026
Measurements held24
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/hangzhou_798

Topic

Giveaways & airdrops — 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 87% 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

31,39739,98935,69316 August 2026 — 31,397 subscribers17 August 2026 — 31,489 subscribers18 August 2026 — 31,592 subscribers19 August 2026 — 31,771 subscribers20 August 2026 — 31,876 subscribers21 August 2026 — 31,988 subscribers22 August 2026 — 32,134 subscribers24 August 2026 — 32,331 subscribers25 August 2026 — 32,427 subscribers26 August 2026 — 32,533 subscribers27 August 2026 — 32,621 subscribers28 August 2026 — 32,835 subscribers29 August 2026 — 32,961 subscribers30 August 2026 — 33,061 subscribers31 August 2026 — 33,268 subscribers1 September 2026 — 33,357 subscribers2 September 2026 — 33,499 subscribers3 September 2026 — 33,701 subscribers6 September 2026 — 33,969 subscribers9 September 2026 — 38,238 subscribers12 September 2026 — 39,834 subscribers13 September 2026 — 39,921 subscribers15 September 2026 — 39,989 subscribers17 September 2026 — 35,111 subscribers35,11116 August 202617 September 2026
24 measurements spanning 32 days, net +3,714. 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 30,108–41,278 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
17 Sept 2026, 10:3835,111-4,878
15 Sept 2026, 10:2139,989+68
13 Sept 2026, 20:2039,921+87
12 Sept 2026, 03:5639,834+1,596
9 Sept 2026, 17:5838,238+4,269
6 Sept 2026, 07:1833,969+268
3 Sept 2026, 23:5633,701+202
2 Sept 2026, 11:0333,499+142
1 Sept 2026, 14:0533,357+89
31 Aug 2026, 12:1533,268+207
30 Aug 2026, 13:4233,061+100
29 Aug 2026, 14:5432,961+126
28 Aug 2026, 15:4332,835+214
27 Aug 2026, 13:4632,621+88
26 Aug 2026, 16:2332,533+106
25 Aug 2026, 15:3732,427+96
24 Aug 2026, 16:0632,331+197
22 Aug 2026, 22:1932,134+146
21 Aug 2026, 09:1531,988+112
20 Aug 2026, 08:5531,876first reading

Engagement

11 posts held, back to 9 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 57 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.61%
avg views ÷ 35,111 subscribers
Avg views / post
2,320
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 11 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 15 September 2026
Posts held11 (9 August 202615 September 2026)
Views total11,600
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Sept 2026, 13:43 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
577
Videos
118
Links
151

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

Video runtime
39s
Average length
7s

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.

Recent posts

15 Sept 2026, 12:22 UTC≈1,260 viewsread 20 September 2026
Photo

👑 :#可乐 📍: #西湖区 💰:500P 1000PP 💌:@lele86869 🪩:杭州西湖区三墩 🏷: #西湖区 #舌吻 #69互舔 #上门 #包时 点击返回

12 Sept 2026, 08:06 UTC≈1,880 viewsread 20 September 2026
Photo

👑 :#可儿 📍: #余杭区 💰:500P 900Pp 💌:@h520hjj 🪩:杭州余杭水景苑东区 🏷: #69互舔 #舌吻 #上门 #口爆 交流群: @hangzhou798

8 Sept 2026, 05:38 UTC≈2,150 viewsread 20 September 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5995864524

31 Aug 2026, 02:40 UTC≈3,290 viewsread 20 September 2026
Photo

👑 :#不吃香菜 📍: #滨江区 💰:1500P 2500PP 💌:@Nxiangcai 🪩:杭州滨江滨康路 🏷: #裸吹 #69互舔 #制服 点击返回

30 Aug 2026, 06:09 UTC≈3,020 viewsread 20 September 2026
Photo

👑 :#苏菲 📍: #西湖区 💰:500P 900Pp 💌:@xxxis520 🪩:杭州西湖 🏷: #69互舔 #舌吻 #上门 #性价比 #车震 #野战 交流群: @hangzhou798

21 Aug 2026, 06:52 UTC≈3,040 viewsread 14 September 2026
Photo

👑 :#悦悦 📍: #拱墅区 💰:800P 1500Pp 💌:@yue481 🪩:杭州拱墅区依山路 🏷: #69互舔 #舌吻 #上门 #嫩妹 #双飞 交流群: @hangzhou798

15 Aug 2026, 12:14 UTC≈3,410 viewsread 11 September 2026
Photo

#杭州 #萧山 #绍兴 #柯桥 9️⃣5️⃣门店 特色服务:❤️服务如下👇 服务。无套 口爆 全裸四推(胸手足臀) 按摩指划 鼻吸 漫游 毒龙 双凤戏龙:7️⃣4️⃣0️⃣ 单人预约优惠价:4️⃣0️⃣0️⃣ 加钟优惠活动价:7️⃣4️⃣0️⃣ 👍私密安全 🛡停车方便 📱位置:杭州萧山跟绍兴交界 🚀电报客服:@youyou9863 客服电话 : 18857573769 客服微信: 15695858979 🚀直达店铺:https://t.me/tianxinjiedai 私信限制联系:https://t.me/youyou9863bot 营业时间 中午12:00-凌晨03:00 激情无限。诱惑丝袜随便撕! ✅高服务高评价先服务后买单

12 Aug 2026, 07:51 UTC≈3,450 viewsread 11 September 2026
Photo

👑 :#林琪琪 📍: #拱墅区 💰:800P 1500Pp 💌:@linqiqi 🪩:杭州拱墅区半山 🏷: #69互舔 #舌吻 #上门 #嫩妹 #颜值 交流群: @hangzhou798

11 Aug 2026, 05:10 UTC≈2,650 viewsread 29 August 2026
Photo

👑 :#兔兔 📍: #上城区 💰:700P 1300Pp 💌:@cc1789789 🪩:杭州上城区聚英公寓 🏷: #69互舔 #舌吻 #上门 #性价比 交流群: @hangzhou798

9 Aug 2026, 05:48 UTC≈2,170 viewsread 22 August 2026
Photo

👑 :#月月 📍: #余杭区 💰:1000P 1800Pp 💌:@xmxm_wtnb 🪩:杭州余杭区未来科技城 🏷: #69互舔 #舌吻 #车震 #上门 交流群: @hangzhou798

9 Aug 2026, 05:20 UTC≈1,840 viewsread 21 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_5995864524

Showing the 11 most recent of 11 posts we hold for @hangzhou_798. 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.

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

“杭州798” (@hangzhou_798), 35,111 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hangzhou_798.

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.