Telegram RegisterThe public register of Telegram
Telegram profile photo for 园区✈️境空间SPA频道

Channel

园区✈️境空间SPA频道

@jxspa456

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

1,379subscribers

+75 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002354700493
TypeChannel
Username@jxspa456
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 live4 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/jxspa456

Growth

1,3031,3791,3417 August 2026 — 1,304 subscribers7 August 2026 — 1,304 subscribers8 August 2026 — 1,303 subscribers10 August 2026 — 1,304 subscribers14 August 2026 — 1,312 subscribers17 August 2026 — 1,322 subscribers20 August 2026 — 1,330 subscribers24 August 2026 — 1,342 subscribers26 August 2026 — 1,349 subscribers29 August 2026 — 1,361 subscribers1 September 2026 — 1,372 subscribers4 September 2026 — 1,379 subscribers7 August 20264 September 2026
12 measurements spanning 28 days, net +75. 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 1,292–1,390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 15:001,379+7
1 Sept 2026, 01:371,372+11
29 Aug 2026, 07:431,361+12
26 Aug 2026, 17:241,349+7
24 Aug 2026, 02:581,342+12
20 Aug 2026, 16:481,330+8
17 Aug 2026, 15:271,322+10
14 Aug 2026, 13:291,312+8
10 Aug 2026, 20:351,304+1
8 Aug 2026, 01:281,303-1
7 Aug 2026, 22:321,304no change
7 Aug 2026, 19:361,304first reading

Engagement

8 posts held, back to 5 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 05s
Average length
8s

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

Reaction mix

3 reactions across 3 posts, in 1 kind.

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

Measured over the 8 most recent posts we hold, published 5 August 2026 to 7 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

7 Aug 2026, 06:33 UTC301 views1 reactionsread 7 August 2026
Video

👉👉✅👍♥️♥️🤘👈👈 苏州😑园区湖东高端海选SPA😑 💗 主打高颜值服务一流💗 ❤️原价999现价599❤️ 💖双飞+300一共899享受一龙二凤 ♥️💯无套路、不办卡、没有任何隐型消费 💖客服:@jxspa66 💖技师照片:https://t.me/jxspa466 💝频道:https://t.me/jxspa456 ❤️电话:13057491914同步V ❤️QQ:3939065256 ❤️地址:园区湖东方洲路599号境空间SPA

1

6 Aug 2026, 07:10 UTC364 viewsread 7 August 2026
Video

👉👉✅👍♥️♥️🤘👈👈 苏州😑园区湖东高端海选SPA😑 💗 主打高颜值服务一流💗 ❤️原价999现价599❤️ 💖双飞+300一共899享受一龙二凤 ♥️💯无套路、不办卡、没有任何隐型消费 💖客服:@jxspa66 💖技师照片:https://t.me/jxspa466 💝频道:https://t.me/jxspa456 ❤️电话:13057491914同步V ❤️QQ:3939065256 ❤️地址:园区湖东方洲路599号境空间SPA

6 Aug 2026, 04:25 UTC290 viewsread 7 August 2026
Video

👉👉✅👍♥️♥️🤘👈👈 苏州😑园区湖东高端海选SPA😑 💗 主打高颜值服务一流💗 ❤️原价999现价599❤️ 💖双飞+300一共899享受一龙二凤 ♥️💯无套路、不办卡、没有任何隐型消费 💖客服:@jxspa66 💖技师照片:https://t.me/jxspa466 💝频道:https://t.me/jxspa456 ❤️电话:13057491914同步V ❤️QQ:3939065256 ❤️地址:园区湖东方洲路599号境空间SPA

5 Aug 2026, 06:57 UTC354 views1 reactionsread 7 August 2026
Video

👉👉✅👍♥️♥️🤘👈👈 苏州😑园区湖东高端海选SPA😑 💗 主打高颜值服务一流💗 ❤️原价999现价599❤️ 💖双飞+300一共899享受一龙二凤 ♥️💯无套路、不办卡、没有任何隐型消费 💖客服:@jxspa66 💖技师照片:https://t.me/jxspa466 💝频道:https://t.me/jxspa456 ❤️电话:13057491914同步V ❤️QQ:3939065256 ❤️地址:园区湖东方洲路599号境空间SPA

1

5 Aug 2026, 06:57 UTC229 views1 reactionsread 7 August 2026
Video

新🍵133号 06N 168 C 皮肤雪白纯天然小妹妹 身材S型 纯欲天花板,服务热情周到!

1

5 Aug 2026, 06:35 UTC207 viewsread 7 August 2026
Video

新🍵177号 03N 168 C 肤色白嫩 身材高挑 服务热情周到!热烈推荐

5 Aug 2026, 06:34 UTC178 viewsread 7 August 2026
Video

今日推荐 66 167/04/B 精美颜值 大长腿 服务细腻 大学生兼职 强力推荐

5 Aug 2026, 06:33 UTC162 viewsread 7 August 2026
Video

新🍵122号 04N/165/C➕ 身材丰满一流 朱粉不深匀 闲花淡淡春 服务手法好 热烈推荐!

Showing the 8 most recent of 8 posts we hold for @jxspa456. 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.

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

“园区✈️境空间SPA频道” (@jxspa456), 1,379 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/jxspa456.

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.