Channel
@yulehuisuo00
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,209subscribers
-416 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003735565959 |
|---|---|
| Type | Channel |
| Username | @yulehuisuo00 |
| Created | Between 1 February 2026 and 19 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/yulehuisuo00 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 16:58 | 1,209 | -1 |
| 13 Sept 2026, 22:41 | 1,210 | -1 |
| 10 Sept 2026, 09:02 | 1,211 | -3 |
| 5 Sept 2026, 03:00 | 1,214 | +995 |
| 28 Aug 2026, 11:13 | 219 | -1,395 |
| 25 Aug 2026, 09:36 | 1,614 | +4 |
| 22 Aug 2026, 02:04 | 1,610 | -18 |
| 18 Aug 2026, 22:34 | 1,628 | +2 |
| 16 Aug 2026, 08:35 | 1,626 | +1 |
| 14 Aug 2026, 21:15 | 1,625 | no change |
| 14 Aug 2026, 21:02 | 1,625 | first reading |
7 posts held, back to 19 June 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.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 19 June 2026 to 8 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.
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 深圳94.95会所环境奢华舒适，私密大床房灯光柔和、香氛满屋。18-24岁00后年轻技师多位，青春水嫩任挑选。服务诱惑尺度顶级，手足胸大胆缠绵、口爆出水强烈，专业细致又过瘾，兄弟们狂赞！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服: CSZD5200 QQ客服:1228355104 双向联系：@Bahs666888bot
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 深圳94.95会所环境优美私密，高端大床、柔和灯光、玫瑰香氛，情调直接拉满。00后18-24岁年轻技师数量多、任选不重样。服务好又专业，尺度大胆诱惑，手足胸出水与口爆出水爽感一波接一波，好评如潮！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服: CSZD5200 QQ客服:1228355104 双向联系：@Bahs666888bot
❤1
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 深圳94.95环境高端大气，私密大床房柔光浪漫、舒适度爆棚。00后18-24岁年轻技师数量充足、皮肤滑嫩如出水。服务好到极致，黑丝御姐、制服甜妹手足胸+口爆出水尺度大胆奔放，诱惑力拉满，体验后直呼过瘾！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服: it11579 QQ客服:1228355104 双向联系：@Bahs666888bot
❤1
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 深圳94.95顶级会所，00后年轻技师阵容强大。环境美、氛围佳，黑丝、御姐、制服各种类型满足你。手足胸出水+口爆出水服务专业大胆、诱惑爆棚，爽感顶级！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服:CSZD5200 QQ客服:1228355104 双向联系：@Bahs666888bot
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 环境一流、技师年轻！深圳94.95会所00后水嫩妹子多，黑丝长腿、御姐风情、制服诱惑应有尽有。手足胸出水与口爆出水服务大胆细腻，尺度大又过瘾，好评刷屏！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服:CSZD5200 QQ客服:1228355104 双向联系：@Bahs666888bot
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 深圳94.95重磅！18-24岁00后极品年轻技师，黑丝御姐高冷诱人、制服学生清纯放开。环境奢华优美，服务尺度顶级，手足胸+口爆出水玩法诱惑力强，老顾客狂赞！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服:CSZD5200 QQ客服:1228355104 双向联系：@Bahs666888bot
#深圳会所 #深圳宝安 #深圳光明 #深圳龙华 #深圳龙岗 #深圳罗湖 #深圳福田 #深圳南山 深圳94.95顶级会所，18-24岁年轻00后技师数量多。奢华私密环境，暧昧大床超舒适。特色黑丝、御姐、制服玩法大胆开放，服务尺度顶级诱惑，体验后直呼太爽！ 咨询美女客服立即享受极致帝王服务 ✈️客服:@vwo88yuan 微信客服:CSZD5200 QQ客服:1228355104 双向联系：@Bahs666888bot
Showing the 7 most recent of 7 posts we hold for @yulehuisuo00. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳会所94-95” (@yulehuisuo00), 1,209 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/yulehuisuo00.
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.