Telegram RegisterThe public register of Telegram
Telegram profile photo for 西安云溪丝足朋友圈

Channel

西安云溪丝足朋友圈

@QSszcp

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

1,807subscribers

+135 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-1002571183528
TypeChannel
Username@QSszcp
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/QSszcp

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

1,6721,8921,7827 August 2026 — 1,672 subscribers7 August 2026 — 1,672 subscribers8 August 2026 — 1,676 subscribers11 August 2026 — 1,677 subscribers14 August 2026 — 1,679 subscribers17 August 2026 — 1,703 subscribers20 August 2026 — 1,754 subscribers24 August 2026 — 1,833 subscribers27 August 2026 — 1,873 subscribers30 August 2026 — 1,838 subscribers3 September 2026 — 1,805 subscribers8 September 2026 — 1,853 subscribers12 September 2026 — 1,892 subscribers16 September 2026 — 1,807 subscribers1,8077 August 202616 September 2026
14 measurements spanning 39 days, net +135. 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,639–1,925 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 03:181,807-85
12 Sept 2026, 13:591,892+39
8 Sept 2026, 16:191,853+48
3 Sept 2026, 17:401,805-33
30 Aug 2026, 23:281,838-35
27 Aug 2026, 21:041,873+40
24 Aug 2026, 11:251,833+79
20 Aug 2026, 19:181,754+51
17 Aug 2026, 18:041,703+24
14 Aug 2026, 18:151,679+2
11 Aug 2026, 12:241,677+1
8 Aug 2026, 18:401,676+4
7 Aug 2026, 21:021,672no change
7 Aug 2026, 19:311,672first reading

Engagement

18 posts held, back to 14 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.

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

What this channel posts

Video runtime
18s
Average length
18s

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.

Reaction mix

5 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.

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

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

31 Jul 2026, 04:25 UTC≈1,160 viewsread 7 August 2026

在岗四位😛 小雪05年气质嫩妹 小柒03年🉑接隐藏 朵朵06年E🐻嫩妹 果果98年气质少妇🉑接隐藏 电报客服 @QS6933

30 Jul 2026, 15:28 UTC≈1,160 views1 reactionsread 7 August 2026

车评 今日在北郊发现有个离很近的spa店 正好有工兵名额便去体验一下 我看评价好的悦悦 果断选了她小妹妹 我非常中意这一款 细枝硕果 然后废话少说直接进入正题 洗完后便趴在床上进行指滑一系列的流程 妹妹很专业 给我感觉很好 特别是正面舔熊环节让我感觉非常好 忍不住哼出来了 妹妹的小手也很美妙 一会儿就没忍住出货了 后面也是妹妹帮洗 总体来说很满意 妹妹颜值 身材和手法都好 推荐悦悦妹妹

👍1

29 Jul 2026, 14:52 UTC≈1,210 views1 reactionsread 7 August 2026

刷到群里都说悦悦不错的 本来准备动身出击 客服又说来了个新人 一看觉得也相当不错 妹妹家是南方的 说话相当温柔长相也很嫩 胸也相当挺 才来西安不久 之前做足疗的 按摩手法相当专业 也是非常到位 全程也是没有一点冷场 情绪价值相当高 唯一美中不足就是业务流程不太熟练 毕竟第一次来这边做 各位哥可以来 调教一番

1

24 Jul 2026, 10:12 UTC≈1,650 viewsread 7 August 2026

这次出击算是意外之喜了,我感觉真的挺不错的。首先环境是我去过的丝足里最好的,进去后布置程设都很赏心悦目 这次点的是悦悦,学生兼职,想去的兄弟们要抓紧了,长的就很乖的感觉,萝莉型的,服务的话不管是前面的按摩还是后面的服务水平都很不错。 而且服务过程中也会一直询问你的意见,体验感很好。总之我觉得这么好的店真的值得被更多人看到,这次确实相当满意哈哈。

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

“西安云溪丝足朋友圈” (@QSszcp), 1,807 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/QSszcp.

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.