上海【喜茶】作业报告 👧艺名: #小乔 ⛳️位置: #普陀 圣天地服务式公寓 🤖课表: https://t.me/xichalssh/41818 📒小作文: 【验证时间】:2026 年 11月 9日 【修车水费】:9P 【服务内容】:能🐍 口的很不错 差点口射了 【颜值身材】:高 175+御姐 模特身材没有夸张,颜值也很耐打 【凶器罩杯】:真 B-C纯天然 【体验细节】:小黄文不会写,只写重点 gzs闹市区的日租房,有点危险所以快进快出,真人和照片几乎一模一样,衣服都不带差的,就是在教师里拍的,颜值超级在线,黑色小短裙+大长腿穿着一个黑色靴子,立马看硬了。老师有点害羞,原来在ktv里做的一次做这个有点腼腆,坐下来喝了水聊了下我是第一个客人。然后交钱洗澡,我洗完就迫不及待的扒老师的衣服,脱得精光,老师说要洗一下,我急死了。有点猴急,老师裹着浴巾 有点害羞,我迫不及待扒了添起老师的奶子,老师甜的有感觉了 开始甜我得鸡巴。看不…

Channel
小乔的秘密基地
@Shxiaoqiao52
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
44subscribers
+19 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 | -1004302452472 |
|---|---|
| Type | Channel |
| Username | @Shxiaoqiao52 |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 November 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/Shxiaoqiao52 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 18:10 | 44 | +19 |
| 9 Nov 2026, 15:22 | 25 | first reading |
Engagement
9 posts held, back to 8 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
- 110.2%
- avg views ÷ 44 subscribers
- Avg views / post
- 48.5
- 8 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 (8 November 2026 – 9 November 2026) |
| Views total | 388 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 15: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
- 14s
- Average length
- 7s
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.
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).
还有空位
📊 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 🚩 编号: TE179422729791 📣 艺名: 小乔 🌐 区域: #普陀 💵 价格: 900P 1600PP 🔗 联系: @SSxiaoqiao520 🔗 双向: @SSxiaoqiao_bot 🖥 资料: 年龄27 身高175 体重58KG 胸B ✏️ 服务: 舌吻 六九 鸳鸯浴 简单按摩 📌 标签: 颜值系 身材好 性价比 御姐 📝 评价: https://t.me/shlyddgj_bot?start=commentTeacher-TE179422729791
小乔的秘密基地 pinned «名字:小乔 年龄:27 身高:175 体重: 58 罩杯:B 一次价格: 900\45分钟 两次价格: 1600\80分钟 夜课 3500\8小时 地区:普陀 电报号: @SSxiaoqiao520 双向联系: @SSxiaoqiao_bot 老师频道 https://t.me/Shxiaoqiao52 服务项目:裸吹 👅舌吻 69 口爆 深喉 陪浴 🐻胸推 角色扮演 丝袜制服 情趣 激情啪啪 纯天然无整 温柔听话 调情 AB面 禁 :鸽子 醉酒 后庭…»
Photo, posted without a caption
#小乔 #普陀 #口爆 #大车 #御姐 #新上 #舌吻 ❤️年龄 27 👠身高 175 💃体重 105 🐻胸围 B 费用: 900P 1600PP 服务内容: ❤️ 裸吹 👅舌吻 69 口爆 深喉 陪浴 🐻胸推 角色扮演 丝袜制服 情趣 激情啪啪 纯天然无整 温柔听话 调情 AB面 个人介绍: ❤️皮肤嫩白光滑,身材火辣 身高175 配合程度高, 备注: 无备注 📞 联系方式 📝 提交作业 📍 附近的人 🤝 上榜联系
https://t.me/gongbintuandijiaqu/8491
https://t.me/chungongya03/284
https://t.me/xichalssh/41818?single
Showing the 9 most recent of 9 posts we hold for @Shxiaoqiao52. 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 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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“小乔的秘密基地” (@Shxiaoqiao52), 44 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/Shxiaoqiao52.
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.