1号真实客返 颜值服务都是没有问题的 流程做的很仔细 有需要的老板可以联系 @yuzhiji6767

Channel
上海SPA各区浦东修车高端海选榜单
@shspa998
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
35,255subscribers
+20,291 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002253859436 |
|---|---|
| Type | Channel |
| Username | @shspa998 |
| Description | 上海推油总群组https://t.me/shanghaispa66 上海客服 @spa67890 |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/shspa998 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 71% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 20:42 | 35,255 | -118 |
| 15 Sept 2026, 19:02 | 35,373 | -259 |
| 14 Sept 2026, 05:59 | 35,632 | -181 |
| 12 Sept 2026, 16:56 | 35,813 | -360 |
| 10 Sept 2026, 15:01 | 36,173 | +6,329 |
| 7 Sept 2026, 09:58 | 29,844 | +6,512 |
| 4 Sept 2026, 15:41 | 23,332 | -301 |
| 3 Sept 2026, 00:43 | 23,633 | +10,324 |
| 1 Sept 2026, 20:48 | 13,309 | -172 |
| 31 Aug 2026, 18:47 | 13,481 | -317 |
| 30 Aug 2026, 21:36 | 13,798 | -319 |
| 29 Aug 2026, 19:13 | 14,117 | -131 |
| 28 Aug 2026, 20:06 | 14,248 | -82 |
| 27 Aug 2026, 21:48 | 14,330 | -22 |
| 27 Aug 2026, 00:47 | 14,352 | -59 |
| 25 Aug 2026, 21:23 | 14,411 | -52 |
| 24 Aug 2026, 18:39 | 14,463 | -169 |
| 23 Aug 2026, 04:26 | 14,632 | -115 |
| 21 Aug 2026, 13:39 | 14,747 | -79 |
| 20 Aug 2026, 11:56 | 14,826 | first reading |
Engagement
24 posts held, back to 12 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 37 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.57%
- avg views ÷ 35,255 subscribers
- Avg views / post
- 554
- 19 posts measured
- Reaction rate
- 0.273%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 24 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 4 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 24 (12 August 2026 – 18 September 2026) |
| Views total | 10,524 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Sept 2026, 14: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
- 221
- Videos
- 203
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 21 September 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
10 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 50.0% | |
| 🥰 | 5 | 50.0% |
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 5 of the 24 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 12 August 2026 to 18 September 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
上海SPA全区域出击相册 https://shanhaiagan.com/ 🥰📱联系客服认准上海阿甘 😀 🥰📱上海spa海选修车推油总群 双向机器人🤖 @SHAMSDT_bot
🥰5❤4
上海浦东新人到一位 99年 37号。KTV下海小姐姐一枚 颜值OK 净身高168。大长腿。🐻C 服务颜值在线。 大哥们放心体验 @SPA67890
浦东商城路 上新一位03年嫩妹 需要的老板可以联系 @yuzhiji6767
不止是一次spa 而是身心的短暂出逃。 在这个快节奏的城市里你有多久没有好好听过自己的身体了紧绷的肩膀、酸胀的腰背昏沉的大脑它们都在替你承受着生活的重量 走进这里请把世界关在门外全身精油spa ✋推🐻推 腿推 臀推在轻柔的音乐与恰到好处的放松让呼吸慢下来让时间静下来 上海SPA认准阿甘 #上海SPA #上海4T #上海2T 你不会被打扰,也不用强撑聊天, 只需要闭上眼睛感受身体慢慢变轻 🥰📱联系客服认准上海阿甘 😀 🥰📱上海spa海选修车推油总群 🌙 认准阿甘 不迷路不踩坑
上海SPA 去除一天的疲惫 享受身体精神的双重美好😀 清晨被闹钟叫醒挤进地铁对着屏幕一整天晚上躺下时身体很累脑子却停不下来我们总是把时间分给工作家庭责任却很少留一段完整的时间给自己 来找阿甘 我们想做一件事让你暂时放下外面的世界只关注自己的身体和呼吸推开门的瞬间空气中是淡淡的植物香气耳边是轻柔的音乐技师会用温柔的手法为你去掉疲惫然后用恰到好处的力度一点点松开紧绷的肩颈腰背和四肢 你不会被打扰,也不用强撑聊天, 只需要闭上眼睛感受身体慢慢变轻 #SPA #上海4T #上海2T 📱📱📱 🤗🤥🫥 🥰📱联系客服认准上海阿甘😀 🥰📱上海spa海选修车推油总群 🌙 认准阿甘 不迷路不踩坑
❤1
浦东商城路 上新两位00后美女 需要的老板 联系 @yuzhiji6767
徐汇门店上新乌克兰🇺🇦美女 599 无套路 @Spa67890
瞬搜这边不只有一个入口,搜索、音乐、新闻、工具全都帮你整合好了。 想少踩坑、走捷径,先从精选导航开始最省心。 👇 点下面直接进入
TG必备搜索引擎,新币搜🔍@xbso @xbso 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇
瞬搜这边不只有一个入口,搜索、音乐、新闻、工具全都帮你整合好了。 想少踩坑、走捷径,先从精选导航开始最省心。 👇 点下面直接进入
— 创作者中心 · 发视频赚USDT — 将超级引擎 @CJYQ 设置成管理员可收录您的频道/群组/让您的视频内容展现在小程序曝光获得流量 👇点击按钮体验视频号MiniApp吧👇
Showing the 12 most recent of 24 posts we hold for @shspa998. 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
@shspa998 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
- 18 September 2026
- Most recent edit
- 18 September 2026
Mentions
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“上海SPA各区浦东修车高端海选榜单” (@shspa998), 35,255 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/shspa998.
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.