Telegram RegisterThe public register of Telegram
Telegram profile photo for 福州壹园SPA双飞699

Channel

福州壹园SPA双飞699

@yyspa22

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

116subscribers

+3 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1004451474454
TypeChannel
Username@yyspa22
CreatedBetween 1 June 2026 and 10 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live22 October 2026
Measurements held10
Confirmed unchanged2 times, most recently 22 October 2026
On Telegramt.me/yyspa22

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

113122117.514 August 2026 — 113 subscribers14 August 2026 — 113 subscribers15 August 2026 — 114 subscribers23 August 2026 — 118 subscribers29 August 2026 — 120 subscribers6 September 2026 — 122 subscribers14 September 2026 — 118 subscribers28 September 2026 — 115 subscribers9 October 2026 — 117 subscribers16 October 2026 — 116 subscribers11614 August 202616 October 2026
10 measurements spanning 62 days, net +3. 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 112–123 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Oct 2026, 06:16116-1
9 Oct 2026, 13:37117+2
28 Sept 2026, 23:56115-3
14 Sept 2026, 05:00118-4
6 Sept 2026, 09:56122+2
29 Aug 2026, 11:38120+2
23 Aug 2026, 07:58118+4
15 Aug 2026, 18:03114+1
14 Aug 2026, 19:31113no change
14 Aug 2026, 19:25113first reading

Engagement

7 posts held, back to 10 August 2026 — the 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 7 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
38s
Average length
13s

Measured directly from 3 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

14 Aug 2026, 12:39 UTC33 viewsread 14 August 2026
Photo

晚场预约开始啦,还没预约的哥哥抓紧时间咯 地址:仓山万达SPA会所 价格:预约特价399双飞699 预约客服: @csspa999 双向联系: @fzyyspakbot 仓山区万达SPA会所 价格不变 服务不变 技师团队更新

12 Aug 2026, 06:50 UTC103 viewsread 14 August 2026
Video

要上课的大哥预约咯 地址:仓山万达SPA会所 价格:预约特价399双飞699 预约客服: @csspa999 双向联系: @fzyyspakbot 仓山区万达SPA会所 价格不变 服务不变 技师团队更新

11 Aug 2026, 07:22 UTC126 viewsread 14 August 2026
Photo

要上课的大哥预约咯 地址:仓山万达SPA会所 价格:预约特价399双飞699 预约客服: @csspa999 双向联系: @fzyyspakbot 仓山区万达SPA会所 价格不变 服务不变 技师团队更新

10 Aug 2026, 07:26 UTC146 viewsread 14 August 2026
Photo

要上课的大哥快来咯 地址:仓山万达SPA会所 价格:预约特价399双飞699 预约客服: @csspa999 双向联系: @fzyyspakbot 仓山区万达SPA会所 价格不变 服务不变 技师团队更新

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

“福州壹园SPA双飞699” (@yyspa22), 116 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/yyspa22.

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.