Telegram RegisterThe public register of Telegram
Telegram profile photo for 羽 煕

Channel

羽 煕

@yuxiyuxom

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

2,736subscribers

+9 since we began measuring on 9 September 2026

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

Register entry

Telegram ID-1002900111885
TypeChannel
Username@yuxiyuxom
CreatedBetween 1 July 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live26 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/yuxiyuxom

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 34% 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

2,7272,7422,734.59 September 2026 — 2,727 subscribers11 September 2026 — 2,735 subscribers15 September 2026 — 2,742 subscribers26 September 2026 — 2,736 subscribers2,7369 September 202626 September 2026
4 measurements spanning 17 days, net +9. 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 2,725–2,744 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 12:592,736-6
15 Sept 2026, 13:012,742+7
11 Sept 2026, 18:192,735+8
9 Sept 2026, 09:222,727first reading

Engagement

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

ERR · 30 days
25.5%
avg views ÷ 2,736 subscribers
Avg views / post
698
3 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
3
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 September 2026
Posts held20 (18 March 2026 – 9 September 2026)
Views total2,095
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Sept 2026, 09:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
8s
Average length
8s

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

24 reactions across 6 posts, in 1 kind.

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

Measured over the 20 most recent posts we hold, published 18 March 2026 to 9 September 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

14 Aug 2026, 04:40 UTC≈3,260 views0 reactionsread 9 September 2026

【艺名】: 羽熙 【价格】: 700p 【位置】: 静安 【联系方式】: @yuxi88mm 【身材样貌】: 满分10 【服务过程】:接连约了几位ls,今天都没空,问到yuxi,本来也是没约上,ls问了下多少时间能到,可能觉得比较近吧,就接了,果断换衣一路飞驰。总体而言,人照一致,颜值即正义,对比很多大圈3k 5k的,所见即所得。开门紫色包臀裙,灰常御,再加不俗的妆容颜值,一下子就抓住了某这颗骚动的心。从评论里大致也知道ls软件一般,连🐍都没有,不过提前说明,某心里也没有介意,毕竟光这份颜值就够了。常规交水费,然后自行洗浴,有帮擦。拾级而上,三点口的很认真,继而戴雨衣进入正戏。既然ls没有🐍,那就只能怼脸开大,水多滋润,在一波波的cj之下,总算缴枪。总而言之,就ls的颜值,千元内我愿称之女菩萨,如果追求服务系的,就别cj了。ls自述自己也不挂榜,但是如果看得中ls颜值的,某觉得一定物超所值。时间合适还会复刷。 标签: @y…

9 Aug 2026, 10:15 UTC≈2,650 viewsread 9 September 2026

人照9-10分不过分,三点口也挺认真,软妹一个(可能我也比较温柔),身材也不错,对A,整体推荐,有机会复刷

9 Aug 2026, 02:10 UTC≈2,710 views3 reactionsread 9 September 2026
Photo

Photo, posted without a caption

❤3

16 Jul 2026, 06:17 UTC≈5,100 views0 reactionsread 9 September 2026

@yuxi88mm 我心中的700刘亦菲,快餐。好处不催人。身体苗条匀称,皮肤好。最重要的发质也柔顺。和tm用了飘柔一样。非常喜欢的一个老师,700这颜值我不求舌吻了。口的时候看她脸就硬的不行。比较腼腆,应该是i人。可能会觉得比较高冷,我推荐的点就是因为颜值。人照统一度非常高。屁股翘,后入看着很爽,但是我喜欢传道士,毕竟这么好看的脸,不看着草,太可惜了。 标签: @yuxi88mm 羽熙 700p #静安 点击跳转原始报告【需先加群】 反馈狼友: 杰 时间:2026-02-25 20:54:05 报告ID:8582 当前进度:7/22

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“羽 煕” (@yuxiyuxom), 2,736 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/yuxiyuxom.

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.