老师昵称:#66 老师电报: 出鸡时间:8-17 出鸡地址: 吴中 人照对比:9(满分10分/人照一致) 上课花费:320 安全程度:感觉私密性很好 出击学生:小啊giao(请写目前的网名) 推荐指数:5(满分5分,不可恶意打分) 服务详情::老师数学不大好,我两个钟好像多了十分钟左右 兼了,惜字如金的我给她写个好评。一见面先要了个拥抱,之后我洗桑,洗澡出来老师给我擦干,先b面,之后a面。此处省略。主要是那个 真大乃子,一个乃子怼进去就可以包裹 很壮观 优点:大乃子,服务系 缺点: 分数评价:8.8(10分此生必吃!) 评分标准 6分为及格,7分为一般(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),9.9分(极品) 苏州硬了么主群(点击进入主群) (https://t.me/SuZhouZZJ) 请写真实报告以供各位狼友参考!

Channel
苏州醉心池选妃频道
@mmaoSpa
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
18,819subscribers
+998 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 | -1003174888593 |
|---|---|
| Type | Channel |
| Username | @mmaoSpa |
| Description | 客服: @hebqwn 双向: @wgdyw_bot 选妃频道: @mmaoSpa 大群链接: @bitfwgq |
| Created | Between 1 September 2025 and 31 December 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/mmaoSpa |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 18:19 | 18,819 | +48 |
| 16 Aug 2026, 14:45 | 18,771 | +216 |
| 14 Aug 2026, 21:25 | 18,555 | +199 |
| 13 Aug 2026, 10:05 | 18,356 | +131 |
| 12 Aug 2026, 06:32 | 18,225 | +26 |
| 11 Aug 2026, 03:28 | 18,199 | +16 |
| 10 Aug 2026, 01:05 | 18,183 | +21 |
| 8 Aug 2026, 22:20 | 18,162 | +70 |
| 8 Aug 2026, 00:06 | 18,092 | +250 |
| 7 Aug 2026, 00:40 | 17,842 | +21 |
| 6 Aug 2026, 20:05 | 17,821 | first reading |
Engagement
54 posts held, back to 25 April 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 28 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.58%
- avg views ÷ 18,819 subscribers
- Avg views / post
- 674
- 45 posts measured
- Reaction rate
- 0.129%
- reactions ÷ views · ER floor
- Posts in window
- 45
- of 54 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 14 of 45 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 August 2026 |
|---|---|
| Posts held | 54 (25 April 2026 – 17 August 2026) |
| Views total | 30,332 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Aug 2026, 05:40 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
- 34
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 18 August 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.
Reaction mix
16 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 93.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 93.8% | |
| 🔥 | 1 | 6.25% |
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 17 of the 54 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 16reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 54 most recent posts we hold, published 25 April 2026 to 17 August 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
『推荐指数:⭐️⭐️⭐️⭐️⭐️(五星满分,一星差评)』 【验证人 】:( @yixx_22) 【日 期】:8.17 【美女昵称】:#12 【联系方式】: 【所属频道】:(公开榜/必品榜) 【地 区】:吴中 【上课花费】:320 【口渴关怀】:矿泉水 【人照相似】:本人比照片好看,老师不太上镜 【服务内容】:口 洗澡 舌吻 【服务过程】::听说店内来了新老师,在一周最乏味的周一选择果断出 击,看到12老师的图片备注(真人比照片好看),抱着不信邪的心态必 须亲自来探探路,跟小哥约好时间后也是准时准点的约到了老师,老师 进来后常规叫我先洗个澡,听到老师一开口的声音就被甜化了,真的就 是动漫里那种可爱萝莉的声音。老师长得也确实比照片好看,这种情况 老司机们肯定知道照片多少带点水分,但这个老师真的是比照片好看, 身材匀称纤细又有肉感,皮肤就跟剥了壳的鸡蛋一样。随后我就去洗澡 了,洗的时候心中不停窃喜这次…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
出击报告 (出击证明/牵手照 任选其一) 上课时间:08/15 验证留名:#无尘 老师花名: #66 地 区: 吴中 联系方式: @hebqwn 上课花费:350(优惠 50) 所属频道:#苏州寻春榜 人照相似: 9 颜值身材: 9 服务内容: 门店位置隐蔽,按指引到了门店。本来想选 8 号的结果要等2 个钟,于是临时换成 66 了。提前和技师沟通让她穿了黑丝,她推门进来的时候昏暗的灯光烘托着她 venus 般的身材顿时就硬了。她俯身帮我压在身下胸口半裸贴着往前送,又湿又热,节奏不急不慢,磨得我越来越紧。最后让她躺好,让老师腿夹出货,暴力撕开的黑丝包裹的大腿又滑又有弹性,夹得特别到位,射的时候整个人都松了一口气。 洗完澡后还有点时间,技师主动给按摩了背和腿,当然我的手也没闲着! 出击体验: 推荐 优点缺点:御姐情绪价值高 推荐程度:9 报告提交:@SexySoul_bot 寻春榜同城交流群:@SZXC…
今日出勤!12-66
吴中新人66号真实实拍!纯正少妇,新人红牌!皮肤白焖,身高1.68米 胸D+高山流水,助浴! 需要助浴提前和老师沟通! 吸皮过水,舍漫,舔🥚吸🥚,纯🐍毒龙,顶缸!熊滑,黑丝诱惑,!水多,易高潮!能骚能可爱!熊挺,可亲可摸可69! 能舌吻、 情绪价值拉满!
吴中新人12号真实实拍!纯正少妇,新人红牌!皮肤白焖,身高1.68米 胸D+高山流水,助浴! 需要助浴提前和老师沟通! 吸皮过水,舍漫,舔🥚吸🥚,纯🐍毒龙,顶缸!熊滑,黑丝诱惑,!水多,易高潮!能骚能可爱!熊挺,可亲可摸可69! 能舌吻、 情绪价值拉满!
坐标:吴中区 营业时间 12:00~02:00 服务流程: 吸皮过💦;漫游;🐍漫;助浴!需要助浴提前告知老师,很多客户不需要!鼻息;毒🐲;💅滑;🐻推;亲咪咪! 👅蛋蛋;猴子偷🍑;高山流水!海底捞🌙;蛟龙出海🐲最后 胸推🐻 臀推🍑 手推👋 ,足推,腿推!可亲可摸!上下可摸,黑丝诱惑,需要妹子穿黑丝提前告知老师!部分妹子可69! 原价💰599新店开业特惠预约价💰 400 欢迎预定! 💰 800 比翼双飞,刺激体验帝王班的享受! (50分钟限时不限次) 营业时间 12:00~02:00 吴中区区微信:jawkqb 吴中电报客服:@hebqwn 频道: https://t.me/mmaoSpa 群组: https://t.me/bitfwgq
❤2
Showing the 12 most recent of 54 posts we hold for @mmaoSpa. 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
@mmaoSpa 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
- 9 August 2026
- Most recent edit
- 14 August 2026
Citation-graph rank
Citation-graph rank — 727,252 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 4 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@mmaoSpa named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 4 posts, 10 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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“苏州醉心池选妃频道” (@mmaoSpa), 18,819 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/mmaoSpa.
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.