Channel
@xigonggongzhu8885
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
402subscribers
+319 since we began measuring on 22 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003448137350 |
|---|---|
| Type | Channel |
| Username | @xigonggongzhu8885 |
| Created | 22 October 2026 — measured — dated from the channel’s first post |
| First recorded | 22 October 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/xigonggongzhu8885 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 08:20 | 402 | +319 |
| 22 Oct 2026, 19:22 | 83 | first reading |
17 posts held, back to 22 October 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 1 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 October 2026 |
|---|---|
| Posts held | 17 (22 October 2026 – 22 October 2026) |
| Views total | 759 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Oct 2026, 19:22 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.
Measured directly from 2 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.
杭州嫩妹馆报告：https://telegram.me/hznmg23 【推荐程度】： #好评 【优势】嫩妹，态度热情，情绪价值高 【出击时间】：10月9日 【老师花名】：#司令令（@kuangye5322221） 【出击留名】：guhh 【开课位置】：拱墅 【修车水费】：工兵400p 【高端服务】：有的打✅ ① 舌吻 ✅ ② 69舔逼 （个人不喜欢没问） ③ 情绪价值 ✅ ④ 毒龙 （个人不喜欢没问） 【人照评价】：照片还没本人好看 【身材评价】：有肉的萌妹，一点也不胖，刚刚好 【胸部评价】：b-c 天生丽质 【鲍鱼评价】：嫩，水多 【服务评价】：全 【态度评价】：（不机车，不催、不赶，无罚站行为等） 【环境评价】：课堂干净，有一次性换洗 【过程描述】： #流程细节：无聊打开纸飞机一看，好家伙，嫩妹馆又上新了，一看杭州读书的大一妹子，刚刚接单，OK，马上去。现场到了之后，好家…
半岛嫩妹会报告模板： https://telegram.me/hangzhoubandao 【优势】 【不足】 【妹子花名】：#司令令 【联系方式】：@kuangye5322221 【妹子年龄】：18 【验证留名】：蹭jin 【验证时间】：10月9日 【大概位置】：拱墅 【修车水费】：工兵p 【高端服务】：有的打✅ ① 舌吻 ✅ ② 69舔逼 ③ 情绪价值 ✅ ④ 毒龙 【人照相似】：人照相似程度9分，颜值好看，可可爱爱非常粉嫩的嫩妹 【身高身材】：身材很不错是我喜欢的类型，有胸腰细。 【凶器罩杯】：胸型大小感觉有d，乳头颜色粉嫩，整体手感一级棒👍 【湿度紧度】：比比户型颜色粉红粉红的，湿度很不错紧度也很棒，周围毛量正常 【环境细节】：交通有点不方便停车有点麻烦房间整洁。 【个人卫生】：不抽烟，有漱口水有牙刷有浴巾，事前事后有清洗 【时间管理】：开课是准时，排课是宽松，课时是做完 【服务点…
杭州嫩妹馆报告：https://telegram.me/hznmg23 【推荐程度】：#超级好评 【优势】很嫩 态度 很好 胸大 屁股大 身材好 【不足】 照片拍得没本人好看 【出击时间】：10月10日 【老师花名】:#司令令 （@kuangye5322221） 【出击留名】：匿名 【开课位置】：拱墅回迁房 【修车水费】：700 【高端服务】：有的打✅ ① 舌吻 ✓ ② 69舔逼 ✓ ③ 情绪价值 ✓ ④ 毒龙 【人照评价】：（本人更好看 不会拍照 ） 【身材评价】：（身高1米六左右吧 没纹身 很白反正不错） 【胸部评价】：（c罩杯，超级软） 【鲍鱼评价】：（正常户形，正常毛量，正常水量，非常紧 进去有点困难） 【服务评价】：（服务做完） 【态度评价】：（过程无机车，催、赶，无罚站行为等 很准时） 【环境评价】：（老式装修 还可以的 ） 【过程描述】： #流程细节：其实这也算二刷了…
杭州同学会报告模板： https://telegram.me/Hz_txh 【推荐程度】：#超级好评 【优势】 很嫩 性价比高 态度很好 【不足】 🈚️ 【出击时间】：10 月 10 日 【老师花名】：#司令令 【联系方式】：@kuangye5322221 【老师类型】：嫩妹 【出击留名】：lov 【开课位置】：拱墅 【修车水费】：工兵 pp 【高端服务】：有的打✅ ① 舌吻 ✅ 有我没要 ② 69舔逼 ✅有我没要 ③ 情绪价值 ✅ ④ 毒龙 🈚️ 【人照评价】：本人比照片好看 【身材评价】：身高腿长1.63 该有肉的地方有肉 【胸部评价】：纯天然罩杯C 【户型评价】：没仔细看，水多 【服务评价】：（服务做全） 【态度评价】：态度非常好 【环境评价】：干净卫生 【过程描述】： 在群里抢到最后一个工兵，兴致勃勃的和老师预约了晚上 12 点的时间 遥控上楼，看到老师颜值，完全就是比频道里…
令令不爱化妆
真实年龄
福利1
Channel photo updated
Channel name was changed to «t.me/xigonggongzhu8885»
https://t.me/hz_dx
t.me/xigonggongzhu8885 pinned a photo
🎰 @kuangye5322221 司令令福利抽奖 📮 抽奖条件: 🎫 加入-t.me/xigonggongzhu888 🎫 加入-杭州嫩妹馆 🎫 加入-杭州嫩妹馆新人工兵 🎫 加入-杭州嫩妹馆榜单 🎟️ 要求活动期间群内发言数 1 🍀 每1分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: 半价p × 1 💡 活动说明: 中奖五日内兑换，超时作废 📅 开奖日期:(UTC+8) 2026年10月25日 18时34分00秒
Showing the 12 most recent of 17 posts we hold for @xigonggongzhu8885. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's 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.
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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“t.me/xigonggongzhu8885” (@xigonggongzhu8885), 402 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/xigonggongzhu8885.
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.