各门店按区域划分: 浦东新区: 世博地区: 📍浦三路附近 价格599[2T颜值场] 陆家嘴区域: 📍商城路桃林路 价格599「2T高颜值场」[性价比之王] 📍张杨路桃林路 价格599「目前浦东4T天花板」 📍张杨路民生路 价格599「4T」 静安普陀 📍静安普陀交界处 价格599/799「中端天花板」 📍普陀新静安交界处 价格698「海选性价比之王」[中端天花板] 📍普陀长宁交界处 价格1000/1300[高端店]「虹桥机场北最近」 📍杨浦区 国定东路331号 价格598「海选店」 以上门店不是全部,详情咨询客服@shptspa 各区域门店陆续更新中,浦东均为排选,浦西均为海选 备注:任何店价格与服务无关,只与颜值挂钩 ⚠️👀所有会所无大无口,不了解SPA内容的,请点击⬇️ 科普贴 魔都总群🔽 总群 ‼️鉴于目前VPN不稳定,可能造成登录🛫不稳定,如有消息没有回复直接☎️:15121028359…

Channel
上海魔都美女推油海选SPA会所指南总频道
@mlshspa
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
9,237subscribers
+168 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001913462300 |
|---|---|
| Type | Channel |
| Username | @mlshspa |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/mlshspa |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 11:23 | 9,237 | -177 |
| 29 Aug 2026, 14:26 | 9,414 | -200 |
| 26 Aug 2026, 14:05 | 9,614 | +369 |
| 23 Aug 2026, 07:46 | 9,245 | -55 |
| 19 Aug 2026, 18:22 | 9,300 | -277 |
| 16 Aug 2026, 17:57 | 9,577 | -148 |
| 13 Aug 2026, 11:23 | 9,725 | +320 |
| 10 Aug 2026, 06:30 | 9,405 | -174 |
| 7 Aug 2026, 15:17 | 9,579 | +510 |
| 6 Aug 2026, 20:17 | 9,069 | first reading |
Engagement
36 posts held, back to 1 August 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 34 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.18%
- avg views ÷ 9,237 subscribers
- Avg views / post
- 756
- 33 posts measured
- Reaction rate
- 0.17%
- reactions ÷ views · ER floor
- Posts in window
- 33
- of 36 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 9 of 33 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 36 (1 August 2026 – 29 August 2026) |
| Views total | 24,935 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 05:42 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
- 4m 44s
- Average length
- 15s
Measured directly from 19 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
14 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 92.9% | |
| 😁 | 1 | 7.14% |
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 10 of the 36 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 1 August 2026 to 29 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
8月29日 · 周六午后 周六的阳光, 不必催促你去往哪里。 把时间留给自己, 把脚步放慢一点, 让身体在温柔的舒缓里慢慢松开。 周末的浪漫, 从来不需要太多理由。 一段安静的时光, 一次舒服的 SPA, 就足以让今天变得特别。 🌿 周六,慢一点 🫧 放下这一周的疲惫 ✨ 好好享受属于自己的午后 今天没有那么多必须, 只有此刻,值得被好好享受。
8月28日 · 周五晚 这一周的忙碌, 就到今晚为止吧。 城市渐渐安静下来, 灯光变得柔和, 而你,也终于可以不用赶时间。 把疲惫留在这一晚, 让身体在舒缓里慢慢放松, 让心情在这一刻重新变得轻盈。 🌙 周五夜晚,适合卸下疲惫 🫧 也适合享受一段不被打扰的时光 ✨ 给自己一个温柔的周末开始 这一周辛苦了。 今晚,什么都不用想, 只管好好享受。
民生路6号,本人视频,提前预约
民生路22,本人视频,提前预约
❤2
8月28日 · 周五午后 午后的阳光, 提醒我们——这一周,终于快要结束了。 忙碌了五天, 不妨把时间还给自己一点。 让身体慢下来, 让心情柔软下来, 在一段安静而舒服的时光里, 提前感受周末的浪漫。 🌿 周五,适合放下疲惫 🫧 也适合好好宠爱自己 ✨ 给忙碌的这一周,留一个温柔的句号 周末还未正式开始, 但属于你的放松,可以从现在开始。
8月27日 · 周四晚 白天的喧嚣,留在白天。 夜晚,留一点时间给自己。 忙了一周, 不妨让脚步慢下来, 让柔和的灯光与舒缓的音乐, 一点一点带走身体的疲惫。 有时候,真正的浪漫, 不是去哪里,而是有人懂得让你放松。 🌙 今晚,卸下疲惫 🫧 让身体慢慢松弛 ✨ 给自己一段温柔、不被打扰的时光 周四的夜晚, 愿你褪去一身疲惫, 在温柔里,重新找回自己。
8月27日 · 周四午后 阳光落在午后的城市, 忙碌依旧,而时间也可以温柔一点。 不必等到周末, 今天就给自己留一段属于自己的时光。 让身体在舒缓中慢慢放松, 让心情在音乐与香气里重新变得柔软。 🌿 午后,适合慢下来 🫧 给身体一点温柔的呵护 ✨ 也给忙碌的生活,留一点浪漫 周四,距离周末还有一点时间。 不如先把自己照顾好。
8月26日 · 周三晚 一周过半, 城市依旧忙碌,而夜晚终于属于自己。 卸下白天的疲惫, 把手机放在一旁, 让身体慢下来,让心情也慢下来。 柔和的灯光,舒缓的音乐, 还有一段不被打扰的时光。 有时候,生活的浪漫就是这么简单。 🌙 今晚,给自己一点温柔 🫧 让疲惫慢慢散去 ✨ 让身体与心,都重新松弛下来 周三的夜晚, 不必赶路,好好享受这一刻。
商城路新上,工号:100,原黄浦100号,真实年纪04年 🐻器B➕ 净身高172,红牌选手
浦东精品推荐: 浦三路推荐:8,22,66 商城路推荐:00,18,19 民生路推荐:6,11,22,18
商城路近期出勤更新一波,有需要的联系,价格:599,颜值场,浦东第一性价比颜值场
Showing the 12 most recent of 36 posts we hold for @mlshspa. 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
@mlshspa edited 1 post 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
- 19 August 2026
- Most recent edit
- 19 August 2026
Mentions
Named by 7 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“上海魔都美女推油海选SPA会所指南总频道” (@mlshspa), 9,237 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/mlshspa.
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.