Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州老余杭白金翰spa选妃

Channel

杭州老余杭白金翰spa选妃

@lyhspa

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

307subscribers

+59 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003956509859
TypeChannel
Username@lyhspa
CreatedBetween 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/lyhspa

Topic

Adult — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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

248307277.56 August 2026 — 248 subscribers7 August 2026 — 248 subscribers7 August 2026 — 252 subscribers16 August 2026 — 260 subscribers22 August 2026 — 276 subscribers29 August 2026 — 285 subscribers6 September 2026 — 304 subscribers13 September 2026 — 307 subscribers6 August 202613 September 2026
8 measurements spanning 38 days, net +59. 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 239–316 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 12:55307+3
6 Sept 2026, 03:56304+19
29 Aug 2026, 23:33285+9
22 Aug 2026, 19:12276+16
16 Aug 2026, 06:58260+8
7 Aug 2026, 21:10252+4
7 Aug 2026, 02:30248no change
6 Aug 2026, 21:00248first reading

Engagement

7 posts held, back to 31 July 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

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

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

6 Aug 2026, 13:05 UTC278 viewsread 7 August 2026
Photo

杭州老余杭(鼎创)小婷年龄04年 熊🐻B+ 身高164cm 体重45kg 🉑 开发度 👏🦶🐻🐬 🎶五种出水方式 甜蛋 🍭 广州小美女 三点粉 身材真的是勾魂 舌吻海鲜看人 (超级换装)透视 真实描述:身材一级棒 尺度绝对到位 比例超级好 特色:骚 骚 骚

3 Aug 2026, 10:13 UTC144 views0 reactionsread 7 August 2026
Photo

杭州老余杭(仓梦合寓)18号(红牌主力[玫瑰]) 06年,身高165,体重50kg,🐻围B,大学生下海,极品小蛮腰身材,天生敏感圣体‼️,服务态度温柔,配合度无敌棒,会聊天,情商高,情绪价值拉满🥰 🉑5T(🐻🐬🦅🖐🦶) 🉑🦞🉑亲(看人) 🉑助🐟 🉑丝🦶 🉑果冻🐲

2 Aug 2026, 05:54 UTC162 views1 reactionsread 7 August 2026
Photo

杭州老余杭(富力中心) 88号,好评选手⭐️⭐️⭐️⭐️⭐️包满意 01年小姑娘,🐻小C,可纯可欲,服务态度拉满,身高167体重49,KG大长腿,性格温柔,一套莞式手法服务超一流 🉑4T(🐻🐬👋🦶) 🉑🦞🉑🐍(看人) 🉑助🐠 🉑丝🦶 🉑果冻龙🐉

❤1

2 Aug 2026, 05:53 UTC153 viewsread 7 August 2026
Photo

杭州老余杭(富力中心) 77号,01年 身高167,体重46lg 🐻C完美身材皮肤又白又嫩又滑,温柔体贴,技术流,配合度高 🉑5T(🐻🐬🦅👋🦶) 🉑🐍吻🦐(看人) 🉑助🐠 🉑丝🦶 🉑果冻🐲

31 Jul 2026, 11:25 UTC459 views1 reactionsread 7 August 2026
Photo

杭州老余杭(仓梦合寓)33号(18岁超嫩)🌟🌟🌟👍 08年 身高165 体重50K G 🐻围C 微胖型身材 手感超好 皮肤白皙 😍😍少女感满满 胶原蛋白十足 Q弹 服务💯 情绪价值拉满 🉑69式✈️ 🉑4T(🐻🐬🦶👋) 🉑🦞🉑亲(看人) 🉑助🐟 🉑丝🦶 🉑果冻🐲 699价格

❤1

31 Jul 2026, 11:25 UTC462 viewsread 7 August 2026
Photo

杭州老余杭(仓梦合寓)22号(御姐)🌟🌟🌟 04年身高165 体重48kg 🐻围C➕ 极品完美身材 天生敏感圣体 皮肤超白超嫩 服务配合度无敌棒 超级温柔 😍 🉑5T(🐻🐬🦅🖐🦶) 🉑🦞🉑🐍 🉑助🐟 🉑丝🦶 🉑果冻🐲 699价格

31 Jul 2026, 11:24 UTC454 viewsread 7 August 2026
Photo

杭州老余杭(仓梦合寓)11号(童颜巨🐻)🌟🌟🌟🌟 06年 身高168 🐻围C➕ 体重50kg 身材堪称完美😍 🐻大 皮肤超白 一手🐻推堪称一绝 超嫩超嫩 💦多多 手法娴熟者🉑喷 温柔体贴 服务绝对顶❗️❗️❗️ 🉑5T(🐻🐬🖐🦶🦅) 🉑🦞 🉑助🐟 🉑丝🦶 🉑果冻🐲 699价格

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“杭州老余杭白金翰spa选妃” (@lyhspa), 307 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/lyhspa.

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.