✏️艺名:#元元 📵📵 📱位置:#上城区 👠身材:166 45kg 🧸C 🎀价格:8P 16Pp 🤣服务:剧情扮演,舌吻,69,毒🐲,胸推,制服诱惑,陪浴,按摩,口爆,AB面,爱爱 等 女王:圣水,恋足,调教,辱骂,不过分的要求都可以配合,满满女友感 📱电报: @Suyuen22 📱频道: t.me/Suyuen1 🔖标签: #千元内 #杭州 #上城 #舌吻 #69 #毒龙 #圣水 #SM 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!

Channel
杭州公开认证榜(御女阁)
@hangzhou_888
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
58,874subscribers
+10,698 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001918623688 |
|---|---|
| Type | Channel |
| Username | @hangzhou_888 |
| Description | 杭州最真实最全面楼凤信息资源大全 @hangzhou_buzhang 唯一管理账号(如遇私信不了请私信传话筒 @hzbuzhang_bot )其他主动私聊的都是冒充的骗子,真实楼凤自聊资源参考,主群 t.me/hangzhou_777 Hello @Telegram My channel has not violated the rules and policy of using Telegram. Please pay attention. @rove |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/hangzhou_888 |
Topic
Adult — 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 53% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 22:55 | 58,874 | +293 |
| 11 Nov 2026, 08:58 | 58,581 | -490 |
| 9 Nov 2026, 17:46 | 59,071 | +335 |
| 8 Nov 2026, 09:40 | 58,736 | +25 |
| 7 Nov 2026, 05:31 | 58,711 | +112 |
| 6 Nov 2026, 07:57 | 58,599 | +120 |
| 5 Nov 2026, 07:16 | 58,479 | +163 |
| 4 Nov 2026, 05:27 | 58,316 | +113 |
| 3 Nov 2026, 06:11 | 58,203 | +152 |
| 2 Nov 2026, 06:38 | 58,051 | +111 |
| 1 Nov 2026, 07:35 | 57,940 | +129 |
| 31 Oct 2026, 11:05 | 57,811 | +154 |
| 30 Oct 2026, 07:48 | 57,657 | +137 |
| 29 Oct 2026, 09:51 | 57,520 | +145 |
| 28 Oct 2026, 09:35 | 57,375 | +154 |
| 27 Oct 2026, 07:16 | 57,221 | +116 |
| 26 Oct 2026, 05:47 | 57,105 | +125 |
| 25 Oct 2026, 02:20 | 56,980 | +118 |
| 23 Oct 2026, 23:28 | 56,862 | +147 |
| 22 Oct 2026, 22:39 | 56,715 | first reading |
Engagement
297 posts held, back to 6 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 205 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.98%
- avg views ÷ 58,874 subscribers
- Avg views / post
- 1,160
- 90 posts measured
- Reaction rate
- 0.094%
- reactions ÷ views · ER floor
- Posts in window
- 90
- of 297 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 59 of 90 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 297 (6 August 2026 – 15 November 2026) |
| Views total | 104,824 |
| Reactions total | 67 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 04:54 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,200
- Videos
- ≈328
- Links
- ≈292
Lifetime counters from Telegram’s own channel header, read 16 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
- 27m 26s
- Average length
- 8s
Measured directly from 215 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
306 reactions across 161 posts, in 7 distinct kinds. The most used accounts for 88.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 270 | 88.2% | |
| 👍 | 19 | 6.21% | |
| 🎉 | 6 | 1.96% | |
| 🔥 | 5 | 1.63% | |
| 👏 | 3 | 0.98% | |
| 👀 | 2 | 0.654% | |
| 🤡 | 1 | 0.327% |
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 195 of the 297 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 306 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 297 most recent posts we hold, published 6 August 2026 to 15 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: 4 of 90 posts held from the last 30 days (4.44%) 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).
✏️艺名:#果果 📵📵 📱位置:#拱墅区 👠身材:165 43kg 🧸B 🎀价格:8P 15Pp 🤣服务:可浅亲、一起洗香香~、可口活、乖巧听话、嫩妹三点粉、可cos、制服和丝袜。(服务过程出水算一次) 📱电报: @guoguojiabg9 📱频道: t.me/guosjdjhjguo9 🔖标签: #千元内 #杭州 #拱墅 #cos #萝莉 #嫩妹 #丝袜 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
❤1
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6333257
✏️艺名:#元元 📵📵 📱位置:#上城区 👠身材:162 49kg 🧸B 🎀价格:5P 7Pp 🤣服务:激情,泡泡浴、水中萧、無套口、B面按摩指滑、猴子偷桃、舌吻、(口臭、口气✕)裸口深喉、舔蛋,可69观音坐莲,蚂蚁上树、女上桩机,各种姿势配合、激情拍拍、各种情趣制服、丝袜,高跟鞋,中途可换装,热情,玩的开,可甜可盐,情绪价值必须拉满 📱电报: @yuanyuan12343 📱频道: t.me/YYDehg 🔖标签: #千元内 #杭州 #上城 #舌吻 #69 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
🤡1
✏️艺名:#小幸运 📵📵 📱位置:#萧山区 👠身材:165 49kg 🧸C 🎀价格:8P 15Pp 🤣服务:舌吻(管饱),69,无套口,深喉,胸推,陪浴,水中萧,调情,可以录制不露脸小视频.各种姿势,各种情趣内衣丝袜,等哥哥过来解锁,本人可甜可御 📱电报: @ksvp881 📱频道: t.me/lyue02 🔖标签: #千元内 #杭州 #萧山 #舌吻 #69 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
❤1
✏️艺名:#冷玥 📵📵 📱位置:#萧山区 👠身材:160 45kg 🧸B 🎀价格:7P 14Pp 🤣服务:舌吻 调情69互舔 毒龙 ab面 口爆 胸推 爱爱 📱电报: @lyue99 📱频道: t.me/lyue02 🔖标签: #千元内 #杭州 #萧山 #舌吻 #69 #毒龙 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
❤1👍1
🎰 上城栗子🌰 @tclizi01 冬日福利🎟️ 📮 抽奖条件: 🎫 加入-杭州御女阁(免费上榜) 🎫 加入-杭州公开认证榜(御女阁) 🎫 加入-糖艹栗子 🎁 奖品内容: 半价P优惠卷🎟️ × 2 📅 开奖日期:(UTC+8) 2026年11月17日 13时00分00秒
特色项目:抓龙筋/三起三落/脱敏训练/丝足spa/丝袜责潮喷开发/前列腺高潮开发 纯技术手法操作 欢迎来战 🈺业时间:11:00-1:00 📱微信:hz1154520 📱客服: @zhiyun123 📱双向: @zyun1_bot 😀qq:3965910274 📱频道:https://t.me/jundu123 📱讨论组:https://t.me/zhiyun12233 🏠地址:#萧山区 永瑞轩西区 #萧山区 塘湾名苑b区 地址: #上城区 五堡悦荣湾 🔖标签: #杭州 #抓龙筋 #丝足 #spa
❤2
✏️艺名:#点点 📵📵 📱位置:#萧山区 👠身材:172 47kg 🧸C 🎀价格:8P 15Pp 🤣服务:陪浴,舌吻(口臭不)调情,69、无套口、情趣丝袜 制服。态度好 不催不机车,不过分要求都可以配合,不懂的可以教我,制服丝袜需要可穿。 📱电报: @Mh8ip 📱频道: t.me/HiD6i 🔖标签: #千元内 #杭州 #萧山 #舌吻 #69 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
✏️艺名:#七月 📵📵 📱位置:#滨江区 👠身材:166 56kg 🧸D 🎀价格:7P 13Pp 🤣服务:🈚️套口,舌吻,69,舔蛋,舔咪咪,调情,丝袜激情爱爱 📱电报: @qiyue948 📱频道: t.me/qiyue9467 🔖标签: #千元内 #杭州 #滨江 #舌吻 #69 工兵福利:半价P工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
✏️艺名:#喵小喵(原可可) 📵📵 📱位置:#上城区 👠身材:165 45kg 🧸34B 🎀价格:8P 15Pp 🤣服务:特色淋浴 口交 指滑 漫游胸推 舌吻(要刷牙)69 丝袜 高跟 变装制服(服务暂时可能有些生疏,我会慢慢努力学习的) 📱电报: @keke888888888666 📱频道: t.me/mxmroom 🔖标签: #千元内 #杭州 #上城 #舌吻 #69 工兵福利:半价P工兵1名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
✏️艺名:#优米 📵📵 📱位置:#拱墅区 👠身材:165 48kg 🧸B 🎀价格:8P(时间内可pp) 🤣服务:🐻推 臀推 指划 漫游 足交 冰火两重天 陪浴 无套口69 毒龙🐍吻(先刷牙哦) 丝袜诱惑 情趣敏感型易高潮 女反感觉~ 📱电报: @Yomi0520 📱频道: t.me/Yomi0052 🔖标签: #千元内 #杭州 #上城 #舌吻 #69 #毒龙 工兵福利:半价p工兵2名,群内竞拍,24h内提交报告;群内输入“报告,模版”获取御女阁出击报告模版!
Showing the 12 most recent of 297 posts we hold for @hangzhou_888. 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
@hangzhou_888 edited 7 posts 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
- 5 September 2026
- Most recent edit
- 24 October 2026
Posts recorded as deleted after publishing
We recorded 13 posts on @hangzhou_888 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
- 10 August 2026
- Most recent seen missing
- 18 October 2026
- Median time before seen missing
- 32 hours
- Seen missing in the last 30 days
- 1
Mentions
Named by 5 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
@hangzhou_777 · 42,50433 posts极搜🔍资源搜索@JISOU
@jisou2 · 2,644,15921 posts杭州出击报告
@hangzhou_nenmeibaogao · 84220 posts杭州SPA探花精品spa海选 全裸6T
@hdsshufd · 2,8303 posts杭州独家泰愈控射疗愈
@hztaiyuksp · 8853 posts杭州SPA探花-全裸-6T海选店
@rchgsgscf · 2,7213 posts36D桃桃🍑可拍🎬
@TaoTaov0 · 2,1093 posts波多的朋友圈
@XiaoMeiBa · 7,2503 posts甜甜
@ayaoayaoaa · 1882 posts(杭州)多多相册
@duoduo52071 · 872 posts情人迷 全裸SPA 出击报告
@Hz92mry · 1,4892 posts短租女友(金丝雀包养)
@HZDQNY · 5,6272 posts短租女友(金丝雀包养)
@HZDUNY · 3,4272 postsKiki’s sexy garden
@ladykiki0508 · 2082 posts[劳力士]大众点评
@llsdzdp · 1,0112 posts杭州外围 修车资源库
@llszjzyk · 3,3422 posts洛洛的后花园
@luoll89 · 1,7012 posts困困🫶🏻🧚♀️
@qazyhb1230 · 1852 posts劳力士 [ 全国高端外围交流群 ]
@qg6885 · 6,5132 posts念遥的日常
@shiyue2587 · 2732 posts夏老师🍒朋友圈
@xiakeke521 · 2,4822 posts豆包实时更新空间
@xiaodb90 · 1,0712 posts优米的小屋
@Ym546 · 4492 posts紫萱
@zixuan3652 · 2422 posts
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.
Handles this channel named that no longer answer
- Dead references
- 14
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 11
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@hangzhou_888 named 14 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 2 posts, 4 November 2026 – 5 November 2026 · confirmed gone 12 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 4 September 2026 – 5 September 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 3 September 2026 – 4 September 2026 · confirmed gone 22 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 10 August 2026 – 11 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 24 October 2026 – 24 October 2026 · confirmed gone 30 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 20 October 2026 – 20 October 2026 · confirmed gone 26 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 16 September 2026 – 16 September 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 30 August 2026 – 30 August 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 19 August 2026 – 19 August 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 15 August 2026 – 15 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 12 August 2026 – 12 August 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 7 posts, 10 August 2026 – 4 November 2026
named in 1 post, 6 November 2026 – 6 November 2026
named in 1 post, 14 September 2026 – 14 September 2026
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“杭州公开认证榜(御女阁)” (@hangzhou_888), 58,874 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/hangzhou_888.
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.