❤️ #小米 @xiashaxiaomi781 📍 #钱塘区 #下沙 💰 #800p #1500pp 26岁 170cm 52kg C杯 #骚御 #兼职 #大奶 #商K 📌 床上反馈拳拳到位报告1 报告2 报告3

Channel
下沙❤️小米❣️个人频道❣️❣️
@xiaomi721
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,617subscribers
+0 since we began measuring on 21 November 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001771016295 |
|---|---|
| Type | Channel |
| Username | @xiaomi721 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 November 2026 |
| Last confirmed live | 21 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xiaomi721 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Nov 2026, 11:22 | 2,617 | no change |
| 21 Nov 2026, 10:47 | 2,617 | first reading |
Engagement
17 posts held, back to 5 June 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
- 21.3%
- avg views ÷ 2,617 subscribers
- Avg views / post
- 558
- 5 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 17 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 1 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 November 2026 |
|---|---|
| Posts held | 17 (5 June 2026 – 21 November 2026) |
| Views total | 2,791 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Nov 2026, 11: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
- Photos
- 15
- Videos
- 16
- Links
- 10
Lifetime counters from Telegram’s own channel header, read 21 November 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
- 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.
Reaction mix
13 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 61.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 61.5% | |
| 👍 | 4 | 30.8% | |
| 😍 | 1 | 7.69% |
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 8 of the 17 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 5 June 2026 to 21 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: 0 of 5 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).
开课啦,让宝宝们久等了😘😘相约下沙❤️
新号机器人 @xiaomi2801_bot
下沙开课🀄️,有🈳🉑约,有教室可上🚪,可🐍纹,69,服务天花板🌸🌸
@xiaomi2801_bot
开课啦🤗宝宝们❤️❤️
【评分标准】:9 【妹子花名】:#小米 【联系方式】:@xiaomi7618 【妹子年龄】:26 【验证留名】:呦呦鹿鸣 【验证时间】:10月3日 【大概位置】:下沙 【修车水费】:竞拍p 【服务内容】:有的打✅ ① 陪浴 ② 舌吻 ✅ ③ 69舔逼 ✅ ④ 情绪价值 ✅ ⑤ 毒龙 【人照相似】:人照8分,颜值耐看,气质良家 【身材皮肤】:身高170,无纹身,皮肤还行 【凶器罩杯】:胸C杯,乳头粉嫩 rua感很好 【户型湿紧】:户型大蝴蝶,水量充沛,毛不多 【课室环境】:公寓楼 【个人卫生】:是抽烟,有漱口水 浴巾/事前事后有清洗 【时间管理】:开课准时,排课宽松,课时做完 【服务总结】:课表服务和实际一致,没啥流程化感 【过程描述】:竞拍捡漏拿下下沙小米,路程是有点远,地铁都一个小时,遥控上楼见到了小米,不得不说小米安全意识很强。 颜值好看,比较有气质,用四个字形容就是 英姿飒爽,长腿,大奶,硬件在800档靠前了,很亲切的问候…
❤1
开课啦🤗让大家等久了哦
🍀森林公园老师报告🍀 9分以上为优质,8分以上中等,7分以下黑榜踢出 🐳【时间】:2026-08-02 🌸【老师】:小米 🐺【评价人】:Passersby 🐝【人照】:10 🦄【颜值】:9.8 🦋【身材】:9.8 🐍【服务】:10 🐞【态度】:10 🐼【环境】:9.8 ❤️🔥【过程】:小米难得开课一次,抓紧时间约上立马就去找,刚进门我就来了个熊抱表达思念之情,然后小米贴心到水和给我换拖鞋,随后我俩就开始侃侃而谈,无话不聊,由于我不老实,边聊边摸小米的大长腿,惹得小米难耐,催促我抓紧去洗,她提前洗过,所以我是自己洗,洗完就躺在床上抱着小米又聊了一会,随后开始服务,从上到下👅个遍,她也知道我的喜好,就口的时间比较久,随后我想反向服务,奈何小米比我快一步,已经给我戴上小雨伞坐了上来,这次女上没有你秒我,待小米又点累了,我翻身就把她压在身下,传教士输出,边做边亲,亲不够啊,传了一会,换了后入,慢慢两个人站立后入,边做边逗她,她都后悔让…
❤2👍1
开课🤗啦🤗 下沙
最近暂时不开课哦,具体开课时间请留意后续通知啦🤗🤗
🍀森林公园老师报告🍀 9分以上为优质,8分以上中等,7分以下黑榜踢出 🐳【时间】:2026-07-15 🌸【老师】:小米 🐺【评价人】:Jay 🐝【人照】:9.1 🦄【颜值】:9.1 🦋【身材】:9.1 🐍【服务】:9.9 🐞【态度】:9.6 🐼【环境】:9.1 ❤️🔥【过程】:二刷小米 今天也是得闲,恰巧小米老师也又空,遂相约而出发,待到再次与熟悉的相遇也是见面先来上一个大大的拥抱,阔别良久也是聊了会天。之后便开始了双人洗浴环节,诱人的身姿已经让人按耐不住。于是速速转战床榻之上,现实小米起头一番挑逗,然后是炉火纯青的一番深喉👄,到这时二弟已经顶天立地,于是戴上雨伞开始了小火车进洞环节,伴随着老师的抓紧与放松,双方都达到了快乐的顶峰,最终也不得不感叹时间过的真快
❤1
Showing the 12 most recent of 17 posts we hold for @xiaomi721. 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 21 November 2026 — this entry's latest reading, not the date you are reading this.
“下沙❤️小米❣️个人频道❣️❣️” (@xiaomi721), 2,617 subscribers as measured 21 November 2026. Telegram Register, tgregister.com/channel/xiaomi721.
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.