❤️ #熙熙 @xixi5200315 🤖 #双向 @xixi52000315_bot 📍 #拱墅区 #万达 💰 #1500p #2800pp 22岁 162cm 44kg B杯 #嫩妹 #颜值 #白皮 #白虎 #颜射 #蜜桃臀 #一字马 #cos #口爆 #轻SM 📌 童颜骚萝莉超会玩 一张六五折券群内兑换 19:00

Channel
杭州一哥严选认证榜单
@yigeyanxuan007
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
25,869subscribers
+2,263 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002890813779 |
|---|---|
| Type | Channel |
| Username | @yigeyanxuan007 |
| Description | 一哥严选性价比优质好菜 聊天主群 @yigechat |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/yigeyanxuan007 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:40 | 25,869 | -61 |
| 16 Sept 2026, 12:21 | 25,930 | +303 |
| 14 Sept 2026, 18:55 | 25,627 | -44 |
| 13 Sept 2026, 04:00 | 25,671 | -175 |
| 11 Sept 2026, 09:16 | 25,846 | +414 |
| 8 Sept 2026, 16:15 | 25,432 | +114 |
| 5 Sept 2026, 07:18 | 25,318 | +63 |
| 3 Sept 2026, 12:19 | 25,255 | +46 |
| 2 Sept 2026, 06:07 | 25,209 | +30 |
| 1 Sept 2026, 05:14 | 25,179 | +13 |
| 31 Aug 2026, 02:35 | 25,166 | +4 |
| 30 Aug 2026, 05:38 | 25,162 | +18 |
| 29 Aug 2026, 04:55 | 25,144 | -78 |
| 28 Aug 2026, 06:34 | 25,222 | +18 |
| 27 Aug 2026, 08:23 | 25,204 | +103 |
| 26 Aug 2026, 10:28 | 25,101 | +34 |
| 25 Aug 2026, 11:22 | 25,067 | -137 |
| 24 Aug 2026, 12:38 | 25,204 | +107 |
| 22 Aug 2026, 21:34 | 25,097 | +110 |
| 21 Aug 2026, 14:08 | 24,987 | first reading |
Engagement
170 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 61 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.91%
- avg views ÷ 25,869 subscribers
- Avg views / post
- 752
- 58 posts measured
- Reaction rate
- 0.129%
- reactions ÷ views · ER floor
- Posts in window
- 58
- of 170 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 25 of 58 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 170 (6 August 2026 – 22 September 2026) |
| Views total | 43,620 |
| Reactions total | 25 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 05:52 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
- 623
- Videos
- 188
- Links
- 177
Lifetime counters from Telegram’s own channel header, read 23 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
- 16m 58s
- Average length
- 7s
Measured directly from 139 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
70 reactions across 54 posts, in 3 distinct kinds. The most used accounts for 95.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 67 | 95.7% | |
| 💩 | 2 | 2.86% | |
| 👍 | 1 | 1.43% |
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 79 of the 170 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 70 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 170 most recent posts we hold, published 6 August 2026 to 22 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
❤️ #依依 @yybabys 🤖 #双向 @yybabysbot 📍 #上城区 💰 #1200p #2200pp 20岁 170cm 48kg D杯 #嫩妹 #胸大 #长腿 #肤白 #cos #野战 #小视频 #情绪价值 📌 标准建模细枝硕果 📌 推特网黄~澳州留子 视频榜单 https://t.me/yigeavi/444
❤️ #幺幺 @yaoyao99011 📍 #拱墅区 💰 #600p #1200pp 30岁 170cm 48kg B杯 #少妇 #长腿 #服务系 #性价比 📌 长发细腰大长腿 📌 导师级莞式服务~口粮好菜 报告1 2 3 4 5 6 7 8 9 10 11 12 13 14
❤️ #安娜 @annazaixc 📍 #西湖区 💰 #900p #1600pp 26岁 177cm 58kg C杯 #骚御 #白种人 #胸大 #长腿 📌 进口葡萄酒~纯种俄罗斯妞 📌 杭州短开~家门口的大洋马
❤️ #彤彤 @tong5691 📍 #上城区 💰 #800p 23岁 173cm 58kg G杯 #温御 #BBW #大奶 #大车 📌 超级G杯大奶牛
❤️ #小丸子 @Xwz2344 🤖 @Xwz6868bot 📍 #萧山区 💰 #600p #1500pp 视频 https://t.me/yigeavi/136 #熟御 #初下海 #性价比 #良家 📌 素人~约炮感强烈 📌 服装店老板娘报告1 报告2 降价2张后真的香
❤1
❤️ #安妮『中介』 @Anniee638 📍 #拱墅区 💰 #1500p #2800pp #御姐 #欧洲妞 #舌吻 #轻服务 📌 进口葡萄酒~每周定时更新 📌 中文水平有限 📌 回头客将享受优惠中介也是老外~洋酒资源多! 不便发图,出击前确认下最新照片
❤️ #祁祁 @qiqi666777 🤖 @QTZ77777 📍 #拱墅区 💰 #800p #1500pp #温御 #大奶 #肤白 #毒龙 #深喉 📌 颜值服务系报告1|报告2|报告3|报告4 报告5|报告6|报告7|报告8 报告9|报告10 一哥报告
❤️ #珠珠(95) @YuHangzhuzhu 🤖 @YuHangzhuzhu_bot 📍 #余杭区 #EFC 💰 #600 #温御 #全裸 #气质 #毒龙 📌 精品颜值95报告1 2 3 4 5 6 7
💐 #媛媛 @yuani902 🤖 @yuan871_bot 📍 #上城区 💦 #700p #1300pp 23岁 166cm 46kg B+杯 #温御 #良家 #KB #邻家 #反馈 📌 高性价比爱爱系御姐报告1 2 3 4 5 全家桶 | 视频区 | 群组
❤2
💓心动spa 全裸/5T💓 💘颜值&嫩妹&巨乳&00后💘 颜值嫩妹 魅惑少妇 极品御姐 可爱萝莉 洋妞尝鲜 极致服务 手推❤️胸推🧡足推💛臀推💚阴推 漫游💙指滑💜丝足🤎毒龙🤍捞月 一口价落地无任何加钟 售后有保障 💸服务价格:699 💕点击咨询心动客服💕
❤️ #悦悦 @yueyueyue12345678 🤖 @yueyueyueyue1234567_bot 📍 #拱墅区 💰 #700p #1400pp 23岁 165cm 50kg C杯 #温御 #服务系 #初下海 #大奶 📌 刚落地杭州~头炮还在500p 3名 群内兑换 速来
Showing the 12 most recent of 170 posts we hold for @yigeyanxuan007. 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
@yigeyanxuan007 edited 2 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
- 12 August 2026
- Most recent edit
- 28 August 2026
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 7 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.
@yigeyanxuan001 · 4,46591 posts杭州一哥视频认证榜单
@yigeavi · 19,25845 posts杭州一哥课堂
@yigechat · 31,23034 posts杭州一哥传媒
@yigechuanmei2 · 21,08618 posts杭州大本营资源库
@hzCc87 · 1,2322 posts大头鸭福利社
@Q1850888 · 3,3842 posts大头鸭 每日更新
@zzzz18580 · 3,6932 posts[查身份证 查手机号 查法人 查医疗记录]
@chashenfenzhen · 7,2581 post杭州💎橙橙茶馆
@chenchenchaguan1 · 7,2911 post杭州顶美SPA选妃频道(5.0)
@Fiffj8888 · 11,0761 post杭州顶美SPA交流群(5.0T)
@Hsjjsj888 · 3,0331 post杭州白金翰spa 选妃
@hzbjhxf · 15,5131 post奶茶妹妹嘉倩小可爱
@jiaqian124 · 1,4461 post倩倩的小屋
@jiaqianmaimai528 · 5861 post姐妹自营柔式SPA/抓龙筋/sm
@jundu123 · 3,4341 post澳门会所莞式🐉服务(梦甜)🌞
@kjqt88 · 17,8851 post米雪的男友们(👩❤️💋👨聊天群)
@mixue7750 · 3,3131 post亲姐妹双飞新频道
@mmjyza · 1,2221 post滨江天花板大莞式Fw💥米雪
@mx11122 · 4,1721 post桃子幺幺
@taozi530 · 8931 post杭州精品SPA- 5T海选店
@wzjdmkhnsns · 6,1481 post杭州SPA-推油5T会所
@xwceaa · 12,5681 post一哥视频交流群
@yigeavchat · 19,0441 post抓龙筋🐉姐妹自聊/可上门
@zhiyun12233 · 2,1891 post
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
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@yigeyanxuan007 named 3 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 1 post, 18 August 2026 – 18 August 2026 · confirmed gone 20 August 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 1 post, 29 August 2026 – 29 August 2026
named in 1 post, 18 August 2026 – 18 August 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“杭州一哥严选认证榜单” (@yigeyanxuan007), 25,869 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yigeyanxuan007.
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.