Telegram RegisterThe public register of Telegram
Telegram profile photo for 🥇【珠海 澳门】水床会所直营店

Channel

🥇【珠海 澳门】水床会所直营店

@ZHshuihui

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

5,357subscribers

-767 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-1002023871899
TypeChannel
Username@ZHshuihui
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live2 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/ZHshuihui

Growth

5,3576,1245,740.518 August 2026 — 6,124 subscribers18 August 2026 — 6,124 subscribers18 August 2026 — 6,121 subscribers21 August 2026 — 5,974 subscribers24 August 2026 — 5,811 subscribers27 August 2026 — 5,686 subscribers31 August 2026 — 5,479 subscribers2 September 2026 — 5,357 subscribers18 August 20262 September 2026
8 measurements spanning 16 days, net -767. 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 5,242–6,239 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 21:035,357-122
31 Aug 2026, 04:495,479-207
27 Aug 2026, 20:145,686-125
24 Aug 2026, 23:035,811-163
21 Aug 2026, 12:285,974-147
18 Aug 2026, 02:326,121-3
18 Aug 2026, 00:156,124no change
18 Aug 2026, 00:006,124first reading

Engagement

20 posts held, back to 30 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.53%
avg views ÷ 5,357 subscribers
Avg views / post
135
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
16
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 (30 July 202617 August 2026)
Views total1,083
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 00: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.

What this channel posts

Video runtime
17s
Average length
9s

Measured directly from 2 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.

Recent posts

17 Aug 2026, 19:30 UTC7 viewsread 18 August 2026

#频道互推 #相似推荐 ------------------------------ 📢 🥇【澳门/珠海/中山】 水床会所选妃 📢 东莞足浴按摩城 📢 杭州商K KTV 真空游戏场 📢 深圳本地 SPA 会所|95/96 专属服务 高端臻选 📢 广州【会所】 📢 SM约炮交友群 📢 重庆品茶 📢 上海各区spa按摩红灯区 📢 芜湖♞水磨 📢 临沂风情 ------------------------------ ☁️ 互推入口:@sooo

17 Aug 2026, 19:10 UTC8 viewsread 18 August 2026
Photo

在 Telegram 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。

17 Aug 2026, 05:05 UTC72 viewsread 18 August 2026
Photo

TG必备搜索引擎,新币搜🔍@xbso @xbso 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇

16 Aug 2026, 19:31 UTC92 viewsread 18 August 2026
Video

#珠海会所 #中山会所 礼拜六早点预约 世间装潢千篇一律,难得一份走心款待。 珠海人气休闲会所,靠品质与服务收获满满好评。 装潢可以模仿,定价能够跟风,唯独发自本心的温柔,难以复刻。 不做潦草短暂的体验,每一段时光都精心打磨; 以专业为底气,把细致体贴融进全程。 真正治愈疲惫的放松,是直抵心底的舒适感。 我们深耕细节、打磨服务,只为给你一段流连忘返的静谧时光。 客服:@HG201891 @XHGJ123bot

16 Aug 2026, 05:02 UTC126 viewsread 18 August 2026
Photo

TG必备搜索引擎,新币搜🔍@xbso @xbso 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇

15 Aug 2026, 09:24 UTC164 viewsread 18 August 2026
Video

#珠海会所 #中山会所 检验是最好的证明,恭迎各位老板亲临。您所追求的,我们都能提供,请直接说明,欢迎随时垂询。 客服:@HG201891 @XHGJ123bot

15 Aug 2026, 04:46 UTC167 viewsread 18 August 2026
Photo

TG必备搜索引擎,新币搜🔍@xbso @xbso 轻松帮您找到有趣的群、频道、视频、音乐、电影、新闻。 👇👇点击下方按钮,快速搜索👇👇

Showing the 12 most recent of 20 posts we hold for @ZHshuihui. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“🥇【珠海 澳门】水床会所直营店” (@ZHshuihui), 5,357 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/ZHshuihui.

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.