👩🏫【老 师】:#西西子 😀【位 置】:#洪山区 🪙【课 费】:#600P/1100PP ⚡【身 材】:170cm、45KG、🐻C 🚀【电 报】:@Tissjsc 🤖【双 向】:@Tisseibot 😵【频 道】:@xxdghe 📝 🔣🔣🔣 武汉骑兵团 🔣🔣🔣 🔣🔣🔣 老师导航板 🔣🔣🔣

Channel
西施子的小家
@xxdghe
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
74subscribers
+58 since we began measuring on 9 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004327484958 |
|---|---|
| Type | Channel |
| Username | @xxdghe |
| Created | 6 November 2026 — measured — dated from the channel’s first post |
| First recorded | 9 November 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/xxdghe |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 09:45 | 74 | +58 |
| 9 Nov 2026, 16:22 | 16 | first reading |
Engagement
9 posts held, back to 6 November 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 · 30 days
- 61.4%
- avg views ÷ 74 subscribers
- Avg views / post
- 45.4
- 7 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 9
- of 9 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.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 9 (6 November 2026 – 9 November 2026) |
| Views total | 318 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 16: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.
What this channel posts
- Video runtime
- 29s
- Average length
- 29s
Measured directly from 1 video 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
Telegram’s own ‘edited’ marker: 0 of 9 posts held from the last 30 days (0%) 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).
Photo, posted without a caption
Photo, posted without a caption
Channel photo updated
【时间】:2026-11-01 【老师】:西西子 【留名】:匿名 【人照】:8 【身材】:9 【服务】:8 【环境】:9 【综合】:8.5 【过程】:除了服务,其他都可以,看得出来是新人,很多还不会,还是需要调教调教,洗澡后就在床上等待,然后简单的调情,吹一下,再深入交流,最后舒服的一下,还是可以的
【时间】:2026-11-04 【老师】:西西子 【留名】:匿名 【人照】:10 【身材】:10 【服务】:10 【环境】:9.5 【综合】:9.88 【过程】:老师身材超好,长得美美哒!女友感十足,很热情会聊天,一进门就帮我拿了拖鞋,又帮我放了水洗了澡澡,擦干身体就开始做服务了,老师服务很舒服,性格也好,也很活泼,娇小可爱也挺漂亮,是我喜欢的类型,还会再去!
【时间】:2026-10-31 【老师】:西西子 【留名】:A 【人照】: 【身材】:9 【服务】:10 【环境】:8 【综合】:9 【过程】:下班刷到新上榜的西西,本来没抱太大期望,就想着去碰碰运气。约好时间直接过去,一开门真的愣了一下——比照片还好看。小脸精致甜,皮肤白得能掐出水,两个大奶 子整个人清清爽爽的,完全是那种刚出社会不久的年轻妹子感觉。 进门她很自然地递了杯水,一点都不尴尬。聊了两句就一起进浴室,水温调好后她帮忙擦洗,手法很轻,边洗边软软地聊天,气氛一下子就放松了。洗完出来互相擦干,她直接凑过来给了个很缠绵唇舌软软的,顺势把我拉到床边。 看得出来是刚入行不久的新人,花活不算特别多,但做起来特别认真。口的时候很投入,节奏拉得很有感觉。正式开始后她主动坐上来配合,里面又紧又热,包裹感特别强,没坚持多久就差点缴枪。后来换成后背位,搂着她软软的身子,耳边全是细细的哼哼声,越来越带劲,最后直接在她怀里释放了。事后还主动陪着…
⏰ 出击时间:2026-11-4 👩🏫 老师名称:#西西子 🎂 目测年龄:18 📍 所在位置:白沙洲天街A馆 💰 修车水费:活动价 💃 身高身材:高挑匀称(166-172cm 标准身材) 👩 颜值相似:8 🍈 罩杯胸型:C 🧼 卫生评价:干净 🛡️ 安全评价:安全 📋 服务项目:与课表一致 📝 服务详情:刚进门就是先嘘寒问暖一下然后会给你拿一次性浴巾,然后会询问你要不要一起洗澡,然后就是帮你洗澡洗完躺在床上,还是嫩妹三件套可以要求69,提一嘴妹子很敏感,另外妹子的声音很嗲,叫床真实,嫩妹的下面还是很紧的,可惜没有实力桩满钟但是做完妹子会让你休息一会然后主动和你聊天,这一点还是很好的不是做完就赶人,聊天的时候还可以把玩老师的胸部,另外和老师聊天方得知老师来上班是为了攒钱以后回老家买房。总之以后还是会二刷的 ⭐ 评价程度:#好 👍 优缺点:老师很健谈,漂亮
Channel created
Showing the 9 most recent of 9 posts we hold for @xxdghe. 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
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 2 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“西施子的小家” (@xxdghe), 74 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/xxdghe.
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.