Telegram RegisterThe public register of Telegram
Telegram profile photo for 沈阳M spa 全裸服务

Channel

沈阳M spa 全裸服务

@shenyangspacb

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

248subscribers

+27 since we began measuring on 1 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004360287951
TypeChannel
Username@shenyangspacb
Created20 August 2026measured — dated from the channel’s first post
First recorded1 September 2026
Last confirmed live1 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/shenyangspacb

Growth

221248234.51 Sept 2026, 10:30 — 221 subscribers1 Sept 2026, 10:45 — 221 subscribers1 Sept 2026, 12:55 — 248 subscribers1 Sept 2026, 10:301 Sept 2026, 12:55
3 measurements taken within a single day, net +27. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 217–252 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 12:55248+27
1 Sept 2026, 10:45221no change
1 Sept 2026, 10:30221first reading

Engagement

13 posts held, back to 20 August 2026the 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
170.9%
avg views ÷ 248 subscribers
Avg views / post
424
7 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 2 of 7 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held13 (20 August 20261 September 2026)
Views total2,966
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 10:45 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
27s
Average length
27s

Measured directly from 1 video 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

1 Sept 2026, 09:03 UTC21 viewsread 1 September 2026
Forwarded from @shenyangspajishiPhoto

三号技师 身高:168 体重:95 🐻C 顶级颜值,年轻嫩,大学实习阶段,私影出身,服务好(直接套餐ABD) 欢迎预约https://t.me/CB111118888

30 Aug 2026, 15:49 UTC698 views0 reactionsread 1 September 2026
Forwarded from @shenyangspajishiPhoto

三号技师 身高:168 体重:95 🐻C 顶级颜值,年轻嫩,大学实习阶段,私影出身,服务好(只接套餐A或者C) 欢迎预约https://t.me/CB111118888

29 Aug 2026, 12:14 UTC688 viewsread 1 September 2026
Forwarded from @shenyangspajishiPhoto

二号技师 身高:165 体重:95 🐻C,圆的 真实在读女大,年轻嫩,只有小部分时间可约,大部分时间在校 欢迎预约https://t.me/CB111118888

29 Aug 2026, 12:14 UTC667 views0 reactionsread 1 September 2026
Forwarded from @shenyangspajishiVideo

一号技师 身高:165 体重:100 🐻C 服务拉满,百分百好评 欢迎预约https://t.me/CB111118888

29 Aug 2026, 12:08 UTCviews —

沈阳M spa 全裸服务 pinned «套餐A 598:60分钟 半裸 闻香 指滑 胸柔 臀柔 果冻漫游 抓龙筋 免费淋浴 丝袜诱惑 套餐B 798:75分钟 套餐A+释放 套餐C 998:套餐B+全裸 品鲍 阴推(可吃扎、吃鲍鱼) 套餐D 1498:90分钟 套餐C+情趣制服骑士服务 恋足 男士私护 浴缸泡浴助浴 本店无口无大 本店所有技师照片均为朋友圈生活照实拍»

29 Aug 2026, 12:08 UTC653 viewsread 1 September 2026

套餐A 598:60分钟 半裸 闻香 指滑 胸柔 臀柔 果冻漫游 抓龙筋 免费淋浴 丝袜诱惑 套餐B 798:75分钟 套餐A+释放 套餐C 998:套餐B+全裸 品鲍 阴推(可吃扎、吃鲍鱼) 套餐D 1498:90分钟 套餐C+情趣制服骑士服务 恋足 男士私护 浴缸泡浴助浴 本店无口无大 本店所有技师照片均为朋友圈生活照实拍

Showing the 12 most recent of 13 posts we hold for @shenyangspacb. 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.

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.

“沈阳M spa 全裸服务” (@shenyangspacb), 248 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/shenyangspacb.

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.