Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海徐汇5T高端SPA油压

Channel

上海徐汇5T高端SPA油压

@gz533

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,520subscribers

-129 since we began measuring on 18 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002488279502
TypeChannel
Username@gz533
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live3 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/gz533

Growth

3,5203,6493,584.518 August 2026 — 3,649 subscribers18 August 2026 — 3,649 subscribers18 August 2026 — 3,634 subscribers21 August 2026 — 3,618 subscribers25 August 2026 — 3,611 subscribers28 August 2026 — 3,606 subscribers31 August 2026 — 3,552 subscribers3 September 2026 — 3,520 subscribers18 August 20263 September 2026
8 measurements spanning 17 days, net -129. 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 3,501–3,668 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 18:563,520-32
31 Aug 2026, 18:043,552-54
28 Aug 2026, 12:023,606-5
25 Aug 2026, 04:373,611-7
21 Aug 2026, 18:473,618-16
18 Aug 2026, 23:563,634-15
18 Aug 2026, 02:153,649no change
18 Aug 2026, 02:003,649first reading

Engagement

20 posts held, back to 25 July 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
2.52%
avg views ÷ 3,520 subscribers
Avg views / post
88.9
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held20 (25 July 202617 August 2026)
Views total711
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 02:15 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 1 of the 20 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 25 July 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

17 Aug 2026, 05:24 UTC25 viewsread 18 August 2026
Photo

#徐汇 #5推 #核心商圈 #地铁口 天色不错,微风正好。在这个惬意的时段,给身心安排一场温柔的养息。 身姿娉婷,温柔相倾 全场精选高质量高颜值技师,曼妙娉婷、气质优雅。柔情款款相伴,用真诚与细致为你抚平所有的浮躁与疲惫。 丝滑精油,沉浸解压 优质精油轻拂肌肤,细腻顺滑的手法刚柔并济。由浅入深层层推压,带你体味极致的沉浸与舒畅。 私密包厢,到店即享 独立包厢洗淋设施全备,恒温舒适。提前私聊锁留专属空档,到店无缝衔接,无需排队。 冰饮相随,出行无忧 清凉冰饮与精选茶饮免费畅享。各店均配有免费隐蔽停车位,隐私保护极佳,尽享无压力消费。 营业中欢迎光临🎉 类型:全裸5推👅👅 价格:电报预约价499(美团价599) 地址:徐汇— 徐家汇地铁站2号口 亚都商务楼 🔒无法私聊联系 💬点击私聊预约

16 Aug 2026, 13:35 UTC40 viewsread 18 August 2026
Photo

SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。

14 Aug 2026, 18:10 UTC62 viewsread 18 August 2026

#频道互推 #相似推荐 ------------------------------ 📢 重庆品茶 📢 广州 深圳 东莞 佛山 选妃总汇 📢 佳佳1v1视频陪聊(可验证) 📢 约炮实战记录 📢 深圳 95/96SPA 精品会所|同城推荐 📢 深圳便民 📢 修车|站街|扫街 📢 汕头女园 📢 青楼 大连花魁榜 @qlql 📢 郑州 郑州外围🔥郑州上门🔥 娇女阁 ------------------------------ ☁️ 互推入口:@sooo

11 Aug 2026, 13:02 UTC102 viewsread 18 August 2026

营业中欢迎光临🎉 #徐汇 #5推 类型:全裸5推👅👅 价格:电报预约价499(美团价599) 地址:徐汇— 徐家汇地铁站2号口 亚都商务楼 🔒无法私聊联系 💬点击私聊预约

8 Aug 2026, 12:28 UTC119 viewsread 18 August 2026
Photo

#全裸 #5推 #不限次 #50分钟 #499体验 一周里最迷人的时刻,莫过于周六的夜晚。 工作早已远去,而充实的周末正处于最惬意的中场。 没有明早催促的闹钟,没有心头悬挂的焦虑, 此时此刻,连空气里都飘着自由与轻松的气息。 在这个完全属于自己的夜晚, 与其在喧嚣里透支精力,不如给身体一场体面而彻底的“大修”。 晚上继续营业中。 类型:全裸5推👅👅 价格:电报预约价499(美团价599) 地址:徐汇— 徐家汇地铁站2号口 亚都商务楼 🔒无法私聊联系 💬点击私聊预约

7 Aug 2026, 18:05 UTC125 viewsread 18 August 2026

#频道互推 #相似推荐 ------------------------------ 📢 北京太子 📢 深圳会所95优质店 在线频道 📢 同城约炮.学生少妇 📢 惠州爽炮 📢 深圳青楼 📢 上海艳遇 📢 沈阳|偷情 📢 西安逍遥宫 📢 北京游戏场 📢 昆明花园 ------------------------------ ☁️ 互推入口:@sooo

2 Aug 2026, 14:29 UTC197 viewsread 18 August 2026
Photo

#徐汇 #全裸 #5T #不限次 《华灯初上,在夜色深处归隐》 夜幕完全张开,霓虹与车流在街头交织成一片耀眼的星海。 结束了一天繁重的工作与应酬, 当喧嚣渐退,今晚最好的去处,不是喧闹的酒吧,而是一处能让身心归位的静谧天地。 推开这扇门,外界的嘈杂被瞬间隔绝。 暗光柔和,水汽氤氲,空气里飘散着让人安心的沉香与草木气息: 夜间的感官沉浸:在极具私密感的暗光包厢里,卸下假面与防备,享受纯粹的私人时光; 深层助眠理疗: 温热的精油顺着经络漫过久坐僵硬的肩颈,将积攒的酸痛与焦虑逐一化解; 安神与能量重构: 伴着低频舒缓的音疗,任由意识在半梦半醒间游离,为今夜的优质睡眠做足铺垫。 今夜,不谈KPI,不系琐碎事。 把时间留给身体,把安宁还给灵魂。 做完这场理疗,带一身清香与轻盈入睡,梦里都是舒展与自由。 周日,晚上继续营业中。#全裸 #5推 #不限次 #50分钟 类型:全裸5推👅👅 价格:电报预约价499(美团价59

31 Jul 2026, 14:22 UTC188 views1 reactionsread 18 August 2026

周日,晚上继续营业中。#全裸 #5推 #不限次 #50分钟 类型:全裸5推👅👅 价格:电报预约价499(美团价599) 地址:徐汇— 徐家汇地铁站2号口 亚都商务楼 🔒无法私聊联系 💬点击私聊预约

1

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

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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“上海徐汇5T高端SPA油压” (@gz533), 3,520 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/gz533.

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.