Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州911报告📮

Channel

杭州911报告📮

@chaodaoD

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

45,409subscribers

+13,008 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001602691456
TypeChannel
Username@chaodaoD
Descriptionهایی
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 live26 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/chaodaoD

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

32,40145,40938,9057 August 2026 — 32,401 subscribers7 August 2026 — 32,476 subscribers8 August 2026 — 32,726 subscribers10 August 2026 — 33,053 subscribers10 August 2026 — 33,200 subscribers11 August 2026 — 33,454 subscribers12 August 2026 — 33,719 subscribers14 August 2026 — 34,254 subscribers15 August 2026 — 34,753 subscribers17 August 2026 — 35,164 subscribers18 August 2026 — 35,532 subscribers19 August 2026 — 35,930 subscribers20 August 2026 — 36,430 subscribers21 August 2026 — 36,576 subscribers23 August 2026 — 37,063 subscribers24 August 2026 — 37,581 subscribers25 August 2026 — 37,927 subscribers26 August 2026 — 38,185 subscribers28 August 2026 — 38,354 subscribers29 August 2026 — 38,679 subscribers30 August 2026 — 38,780 subscribers31 August 2026 — 38,958 subscribers1 September 2026 — 39,184 subscribers2 September 2026 — 39,465 subscribers3 September 2026 — 39,698 subscribers5 September 2026 — 40,331 subscribers8 September 2026 — 41,327 subscribers11 September 2026 — 42,238 subscribers13 September 2026 — 42,310 subscribers15 September 2026 — 42,694 subscribers17 September 2026 — 43,095 subscribers19 September 2026 — 43,694 subscribers26 September 2026 — 45,409 subscribers7 August 202626 September 2026
33 measurements spanning 50 days, net +13,008. 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,450–47,360 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
26 Sept 2026, 14:3745,409+1,715
19 Sept 2026, 16:5543,694+599
17 Sept 2026, 04:1943,095+401
15 Sept 2026, 02:5942,694+384
13 Sept 2026, 11:1742,310+72
11 Sept 2026, 12:5442,238+911
8 Sept 2026, 21:2041,327+996
5 Sept 2026, 12:0240,331+633
3 Sept 2026, 11:3739,698+233
2 Sept 2026, 05:2539,465+281
1 Sept 2026, 06:3839,184+226
31 Aug 2026, 06:2638,958+178
30 Aug 2026, 04:2738,780+101
29 Aug 2026, 02:1538,679+325
28 Aug 2026, 00:3338,354+169
26 Aug 2026, 23:5838,185+258
25 Aug 2026, 20:4537,927+346
24 Aug 2026, 17:4337,581+518
23 Aug 2026, 03:4837,063+487
21 Aug 2026, 16:3536,576first reading

Engagement

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

ERR · 30 days
0.594%
avg views ÷ 45,409 subscribers
Avg views / post
270
93 posts measured
Reaction rate
0.145%
reactions ÷ views · ER floor
Posts in window
93
of 180 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 7 of 93 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 29 September 2026
Posts held180 (25 July 2026 – 29 September 2026)
Views total25,067
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 23:45 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
18
Videos
1
Links
218

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. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

22 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 86.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1986.4%
👍29.09%
💯14.55%

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

Measured over the 180 most recent posts we hold, published 25 July 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, 14:35 UTC45 viewsread 29 September 2026

(报告模板) 【老师艺名】小诺诺 【联系方式】@xiaonuo97 【上课地址】萧山 【上课价位】900 【验证留名】kk 【验证时间】9.30 【颜值身材】s丰满性感 【服务内容】课表安排到位 【服务态度】很好满意👍 【体验细节】【过程描述】:竞拍中了七七的半价 本来还有点犹豫 因为频道图片有点网红 但是看到真人发现还挺像的 就是化不化妆的区别 老师挺i的 不过不会偷懒 身材也很好 附近的水友来不会后悔 不过科室确实有点隔音不好 施展不开 备注: 报告出自911

29 Sept 2026, 14:16 UTC45 viewsread 29 September 2026

(报告模板) 【老师艺名】小诺诺 【联系方式】@xiaonuo97 【上课地址】萧山 【上课价位】900 【验证留名】aa 【验证时间】9月28 【颜值身材】175s+ 【服务内容】课表安排到位 【服务态度】很好满意👍 【体验细节】【过程描述】:今天是二刷妍妍,能在众多妹子的诱惑下坚持来老师这里,含金量不用多说了吧? 老师站着是温柔体贴的诱惑美女,跪着就是闷骚妩媚的风情少女 妍妍用红唇吻遍你的全身,最后把头埋在你的会私处,用舌头挑逗你敏感的头头,等你受不了了,就会从你的小腹下面去口鸡巴。随便动几下腰,就能在老师的口腔中大肆进攻,老师的头在你的小腹下方,好像变成了只属于你的飞机杯.飞机杯粉嫩粉嫩的.这种征服感是别的老师给不了的。 这样一套操作下来,虽然我很想继续,但是火已经被点燃,只想带上套对她的骚穴横冲直撞。一边操一边舌吻,灵魂好像融为了一体,最后用后入姿势顺利出水。 老师在被后入的时候,老师特会,自己动,哎呦我去,我喜欢,缩几…

29 Sept 2026, 12:51 UTC26 viewsread 29 September 2026

(报告模板) 【老师艺名】露小露 【联系方式】@LLll3678 【上课地址】拱墅 【上课价位】1500p 【验证留名】我是大王 【验证时间】9.29 【颜值身材】9.5 【服务内容】课表有写 【服务态度】热情主动 【优点缺点】嫩,服务态度好 【体验细节】:忽然就很想约个嫩妹,翻到了榜上露小露小美女,一看还挺对眼。进门看到本人照片一致。心里踏实了。来到沙发上聊了一会天,就看到她对着我一直在傻笑,感觉是个萌妹子。跟妹妹聊着聊着我就一把搂住她手已伸入衣内爱抚… 两人一同宽衣洗澡,然后移步床上。妹妹上来先骑坐我身上开始舔胸,之后开始含住小弟。几下吞吐我感觉坚持不了,提出我来“服务”。翻身一手抚摸奶子一口含住小奶头,吮吸+舌尖打转。把妹妹服务的直哼唧,口硬之后带套传教士入。阴道口兴奋到张开,进入很丝滑,一下一下感受到交融…我托着屁股让她把腿搭在我肩膀…接着我又来到床边继续深入,我们互相注视着对方… 一次一次深入交流…最后顺利出货,整个人…

29 Sept 2026, 09:02 UTC42 viewsread 29 September 2026

【老师艺名】沈雪雪 【联系方式】 @Smendbna 【上课地址】拱墅 【上课价位】1500/p 【验证留名】vv 【验证时间】9/28 【颜值身材】好看 清纯嫩妹 【服务内容】自觉服务,嫩妹三件套 【服务态度】配合度高,反馈极佳 【优点缺点】女朋友一样 【体验细节】户型正常,紧度偏紧,水量足 很漂亮,身高168,颜值和身材都很耐打,腿长胸大腰细,胸C+脂肪胸很软,手感非常好。被群友们一直安利小雪妹妹,于是敲开了她的闺房,入眼则是一位颜值气质俱佳,身材曼妙的美人儿,陪浴时那对圆润挺拔的3D豪乳极其吸睛,美腿翘臀,那臀肥美得沟深如渊,臀推估计就能让人一泻千里,穿上我给她配的女仆装白丝袜,衬托得肌肤晶莹如玉。口活儿还是稍显生涩,但是服务态度很好,我提出乳交,立马就捧起玉女峰把我肉棒埋进去了,日感很不错,拉起奶茶的双手撞击,胸前顿时波涛汹涌,画面感十足👍。后入时肥臀展现出威力了,软嫩Q弹,让人不舍得停下来,爱不释手!最后手握珠峰,…

29 Sept 2026, 08:18 UTC136 viewsread 29 September 2026

(报告模板) 【老师艺名】小希 【联系方式】@xiaoxi520666 【上课地址】拱墅 【上课价位】2700pp 【验证留名】萧 【验证时间】9.28 【颜值身材】10 【服务内容】课表 【服务态度】夯 【优点缺点】无 【体验细节】:午间找老师玩玩,小希离得近评价不错。遥控上楼,一个肤白貌美的妹子展现出来,洗澡洗得仔细,口技真不错,看着妹子的口舌在JJ和蛋上下纷飞,爽歪歪了。然后女上,包裹性强,差点座爆,赶快传统体位,侧位,一条白腿架起来,忍不住亲亲。最后后日,在娇踹中怒出,不小心还弄疼妹子的妹妹,罪过。整个过程非常满意,超值一次出击。 温馨提示: 报告仅供参考 备注: 报告出自911

28 Sept 2026, 12:33 UTC327 viewsread 29 September 2026

(报告模板) 【老师艺名】大一妍妍 【联系方式】@ubhdii 【上课地址】上城区 【上课价位】1500一次 【验证留名】域名 【验证时间】9月28 【颜值身材】165/B➕ 【服务内容】课表安排到位 【服务态度】很好满意👍 【体验细节】【过程描述】:今天是二刷妍妍,能在众多妹子的诱惑下坚持来老师这里,含金量不用多说了吧? 老师站着是温柔体贴的诱惑美女,跪着就是闷骚妩媚的风情少女 妍妍用红唇吻遍你的全身,最后把头埋在你的会私处,用舌头挑逗你敏感的头头,等你受不了了,就会从你的小腹下面去口鸡巴。随便动几下腰,就能在老师的口腔中大肆进攻,老师的头在你的小腹下方,好像变成了只属于你的飞机杯。这种征服感是别的老师给不了的。 这样一套操作下来,虽然我很想继续,但是火已经被点燃,只想带上套对她的骚穴横冲直撞。一边操一边舌吻,灵魂好像融为了一体,最后用后入姿势顺利出水。 老师在被后入的时候,老师特会,自己动,哎呦我去,我喜欢,缩几下我就把持不…

28 Sept 2026, 11:12 UTC69 viewsread 29 September 2026

(报告模板) 【老师艺名】小怡 【联系方式】 @xiaoyima9999 【上课地址】拱墅 【上课价位】1600p 【验证留名】小廖 【验证时间】9.28 【颜值身材】要是胸还能大一点就好了,不过瘦瘦的这样也合适了哈哈哈 皮肤很白,腿也长,腰上没有赘肉,长得也很好看 【服务内容】只选了几样,有些没要 【服务态度】不催,态度拉满 【优点缺点】非常赞 【体验细节】本来最开始只是打算一次解决下的,开门的瞬间就改变注意了,真人比照片好看,而且身材颜值没得说。皮肤很白,身材很哇撒,女神款! 进去之后洗澡老师指引洗澡帮忙擦干,开始的时候很主动,尤其服务过程中眼神会跟你互动,很勾人,老师很敏感,还没开始插就已经很多水了,做的过程中看老师时而皱眉、时而咬唇,很有成就感!不像耍过其他的,只会抓紧服务,巴不得你抓紧出了离开,感受最深的就是老师的身材咯了,后入尤其巴适,抓着老师的小白兔后入, 视觉冲击极强,老师十分健谈,中途休息还会和你聊很多“奇闻趣…

28 Sept 2026, 05:34 UTC377 views1 reactionsread 29 September 2026

【老师艺名】茗儿 【联系方式】 @waiwai0718 【上课地址】拱墅小区 【上课价位】1500/p 【验证留名】xinch 【验证时间】9.27 【颜值身材】甜美反差 【服务内容】老师课表都有 【优点缺点】温柔体贴 【服务态度】特别棒 【体验细节】强烈推荐茗儿老师,真的太值了!性感身材挂着大灯,风骚感满满,太喜欢了,直接给到夯评!像女朋友一样温柔贴心,服务态度好到没话说,服务也不敷衍,不是那种随便两下就完事,很周到。口的时候舌头灵活又耐心,老师配合得恰到好处,整个人放松又投入,技巧娴熟舒服到直接上头。下面更是惊喜,小逼又紧又湿润,进去就感觉被紧紧包裹住,弹性超好,摩擦感强烈又舒服,越动越紧,夹得人欲罢不能,体验感直接拉满。整体服务到位,满意而归,绝对好评!

❤1

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

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

“杭州911报告📮” (@chaodaoD), 45,409 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/chaodaoD.

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.