要玩的抓紧咯!活动没俩天了! 别错过咯
Signed 庐阳区·油压界爱马仕·客服【小宝】

Channel
@YLX8888P
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8,787subscribers
-1,232 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001887227920 |
|---|---|
| Type | Channel |
| Username | @YLX8888P |
| Created | 31 December 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/YLX8888P |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 16 Sept 2026, 04:57 | 8,787 | -945 |
| 12 Sept 2026, 18:16 | 9,732 | -413 |
| 10 Sept 2026, 15:36 | 10,145 | -273 |
| 7 Sept 2026, 11:01 | 10,418 | +31 |
| 4 Sept 2026, 18:37 | 10,387 | +36 |
| 3 Sept 2026, 05:52 | 10,351 | +12 |
| 1 Sept 2026, 22:46 | 10,339 | +20 |
| 1 Sept 2026, 01:35 | 10,319 | +2 |
| 31 Aug 2026, 02:05 | 10,317 | +12 |
| 30 Aug 2026, 00:25 | 10,305 | +18 |
| 29 Aug 2026, 01:03 | 10,287 | +13 |
| 27 Aug 2026, 21:26 | 10,274 | +13 |
| 26 Aug 2026, 23:27 | 10,261 | +4 |
| 26 Aug 2026, 00:17 | 10,257 | +6 |
| 24 Aug 2026, 21:48 | 10,251 | +16 |
| 23 Aug 2026, 05:25 | 10,235 | +7 |
| 21 Aug 2026, 15:54 | 10,228 | +6 |
| 20 Aug 2026, 15:17 | 10,222 | +9 |
| 19 Aug 2026, 15:25 | 10,213 | +19 |
| 18 Aug 2026, 11:56 | 10,194 | first reading |
79 posts held, back to 31 December 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 36 pages of Telegram’s post history, 20 posts per page.
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 3 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 79 (31 December 2022 – 29 August 2026) |
| Views total | 4,414 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 17:20 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.
Measured directly from 20 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.
61 reactions across 20 posts, in 15 distinct kinds. The most used accounts for 37.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 37.7% | |
| 🔥 | 8 | 13.1% | |
| 👍 | 6 | 9.84% | |
| 💋 | 5 | 8.20% | |
| 💯 | 5 | 8.20% | |
| 🍌 | 3 | 4.92% | |
| 🐳 | 2 | 3.28% | |
| 🤩 | 2 | 3.28% | |
| 🍾 | 1 | 1.64% | |
| 🏆 | 1 | 1.64% | |
| 👏 | 1 | 1.64% | |
| 😁 | 1 | 1.64% | |
| 🤗 | 1 | 1.64% | |
| 🤡 | 1 | 1.64% | |
| 🦄 | 1 | 1.64% |
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 21 of the 79 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 61 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 79 most recent posts we hold, published 31 December 2022 to 29 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.
要玩的抓紧咯!活动没俩天了! 别错过咯
Signed 庐阳区·油压界爱马仕·客服【小宝】
新到一位9号小妹妹!抓紧预约了
Signed V✨
新到小妹! 晚上可以预约哦!😍😍
Signed V✨
11号!感谢大哥支持
Signed 庐阳区·油压界爱马仕·客服【小宝】
本店新店开业活动最后一波回馈活动 📱📱📱📱📱📱📱📱📱📱📱 😛✈️✈️✈️✈️😃✈️✈️✈️✈️😝 活动期间全场买单😀🥰😍🙃📱📱 😀🈷️开始恢复原价:😀😀😀😀 一龙二凤只需要➕⚪️◼️⚫️😞 📱📱📱:DB00992211 😕😕:714185588 📱📱📱📱:@YM123450
Signed 庐阳区·油压界爱马仕·客服【小宝】
御龍轩·客户反馈·广告中心· pinned a photo
本店新店开业活动最后一波回馈活动 📱📱📱📱📱📱📱📱📱📱📱 😛✈️✈️✈️✈️😃✈️✈️✈️✈️😝 活动期间全场买单😀🥰😍🙃📱📱 😀🈷️开始恢复原价:😀😀😀😀 一龙二凤只需要➕⚪️◼️⚫️😞 📱📱📱:ssjp1111 😕😕:714185588 📱📱📱📱:@YM123450
❤1🍌1🍾1👍1💋1
Signed 庐阳区·油压界爱马仕·客服【小宝】
御龍剑之神手。明后俩天到位 全新杭州高场引进高颜值🌹红牌 要玩的提前联系客服预约👍👍👍
❤1👍1
Signed V✨
抽中奖的老板。截图联系客服 提前报备!抵用卷不能叠加!谢谢 积分不够每天签到。💦群都可以
Signed V✨
明天05年大奶子可以约了!常驻艺人 有需要过来抓大奶的提前联系客服
Signed V✨
Photo, posted without a caption
Signed V✨
Photo, posted without a caption
Signed V✨
Showing the 12 most recent of 79 posts we hold for @YLX8888P. 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 6 registered channels — 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.
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.
“御龍轩·客户反馈·广告中心·” (@YLX8888P), 8,787 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/YLX8888P.
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.