Telegram RegisterThe public register of Telegram
Telegram profile photo for 苏州spa会所信息

Channel

苏州spa会所信息

@suzhouhsgk

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

13,769subscribers

+328 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002481641621
TypeChannel
Username@suzhouhsgk
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/suzhouhsgk

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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

13,44113,76913,6057 August 2026 — 13,441 subscribers7 August 2026 — 13,441 subscribers8 August 2026 — 13,443 subscribers9 August 2026 — 13,450 subscribers10 August 2026 — 13,456 subscribers11 August 2026 — 13,453 subscribers12 August 2026 — 13,476 subscribers13 August 2026 — 13,499 subscribers14 August 2026 — 13,514 subscribers16 August 2026 — 13,528 subscribers17 August 2026 — 13,544 subscribers18 August 2026 — 13,540 subscribers19 August 2026 — 13,569 subscribers20 August 2026 — 13,585 subscribers21 August 2026 — 13,604 subscribers22 August 2026 — 13,618 subscribers24 August 2026 — 13,631 subscribers25 August 2026 — 13,639 subscribers26 August 2026 — 13,641 subscribers27 August 2026 — 13,656 subscribers28 August 2026 — 13,668 subscribers29 August 2026 — 13,667 subscribers30 August 2026 — 13,664 subscribers31 August 2026 — 13,675 subscribers1 September 2026 — 13,685 subscribers2 September 2026 — 13,683 subscribers3 September 2026 — 13,705 subscribers5 September 2026 — 13,724 subscribers8 September 2026 — 13,740 subscribers11 September 2026 — 13,743 subscribers13 September 2026 — 13,752 subscribers15 September 2026 — 13,760 subscribers16 September 2026 — 13,763 subscribers19 September 2026 — 13,769 subscribers7 August 202619 September 2026
34 measurements spanning 43 days, net +328. 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 13,392–13,818 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 09:0213,769+6
16 Sept 2026, 19:5613,763+3
15 Sept 2026, 00:5913,760+8
13 Sept 2026, 10:3913,752+9
11 Sept 2026, 11:3913,743+3
8 Sept 2026, 14:4013,740+16
5 Sept 2026, 09:5513,724+19
3 Sept 2026, 12:3513,705+22
2 Sept 2026, 04:5213,683-2
1 Sept 2026, 06:5613,685+10
31 Aug 2026, 03:2313,675+11
30 Aug 2026, 04:5613,664-3
29 Aug 2026, 02:1313,667-1
28 Aug 2026, 05:4313,668+12
27 Aug 2026, 08:3313,656+15
26 Aug 2026, 10:4813,641+2
25 Aug 2026, 12:0313,639+8
24 Aug 2026, 13:1113,631+13
22 Aug 2026, 17:1413,618+14
21 Aug 2026, 10:4713,604first reading

Engagement

54 posts held, back to 4 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 50 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.17%
avg views ÷ 13,769 subscribers
Avg views / post
161
21 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
21
of 54 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 2 September 2026
Posts held54 (4 August 20262 September 2026)
Views total3,386
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 19:51 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
6s
Average length
6s

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

2 Sept 2026, 16:00 UTC50 viewsread 2 September 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

2 Sept 2026, 04:00 UTC66 viewsread 2 September 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

1 Sept 2026, 12:00 UTC60 viewsread 1 September 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

31 Aug 2026, 20:00 UTC3 viewsread 31 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

31 Aug 2026, 16:01 UTC427 viewsread 2 September 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

31 Aug 2026, 04:00 UTC70 viewsread 31 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

30 Aug 2026, 16:00 UTC41 viewsread 30 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

30 Aug 2026, 04:00 UTC73 viewsread 30 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

29 Aug 2026, 16:00 UTC37 viewsread 29 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

29 Aug 2026, 04:01 UTC37 viewsread 29 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

28 Aug 2026, 16:00 UTC45 viewsread 28 August 2026
Photo

以下为榜上合作商家,点击下方按钮进行跳转👇👇👇

28 Aug 2026, 08:39 UTC936 viewsread 2 September 2026
Photo

#广告 #苏州 #推油 #定制 #桃花岛海选SPA 😀😀高铁🚅新城 高端定制🥰🥰 🍎🍎🍎🍎🍎😎😎😎😎 全场🔥🥚🥚后🥰🔹 服务内容🥰 ♥️鼻息💗指划💓胸划💗 ♥️滚水💓漫游💗胸臀推💓 ♥️毒龙💗蚂蚁上树💓 ♥️海底捞月💗高山流水💗 ♥️可摸💗可揉💗可亲💗 ♥️独立淋浴💗 停车方便💗 高颜COS变装SPA ☀️ 每天出勤 10➕主打00后 模特网红 空姐车模 大学生 大胸 A4腰 蜜桃臀 筷子腿 安全💕稳定💕可靠💕超值💕 服务释放 手🐻🦶配合 可摸可揉可亲 🌈环境优雅,颜值巅峰服务天花板 🌈停车方便 安全可靠 独立浴室 🌈无套路 不办卡 没有任何隐形消费 🌈先体验后买单 用心做口碑 营业时间中午12:00-晚上2:00 📱📱📱📱📱📱📱📱📱📱📱📱 📍地址:荣辉街小东北烧烤上三楼 📞微信同:19962653005 客服:@huaxiangSPA888 交流群:https://t.me/hezil

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

@suzhouhsgk 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
13 August 2026
Most recent edit
13 August 2026

Mentions

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

“苏州spa会所信息” (@suzhouhsgk), 13,769 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/suzhouhsgk.

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.