艺名:#粥粥 地址:#宝安 价格:1000P 1800PP 联系:@qazcctv 频道:https://t.me/f168168fff 标签:舌吻 69 嫩妹 调情 鸳鸯浴 无套口 (已视频认证)
❤3🥰2

Channel
@XSJYYZ888
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
19,394subscribers
-1,725 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001711402661 |
|---|---|
| Type | Channel |
| Username | @XSJYYZ888 |
| Description | 🌆最真实的选妃榜🎑 合作/推广联系: @SZXSJ888 群聊: @XSJLTQ888 榜单: @XSJYYZ888 报告: @XSJBG888 中转: @XSJZZZ888 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/XSJYYZ888 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 01:48 | 19,394 | -1,422 |
| 13 Aug 2026, 18:07 | 20,816 | -327 |
| 12 Aug 2026, 16:58 | 21,143 | +53 |
| 11 Aug 2026, 13:41 | 21,090 | +54 |
| 10 Aug 2026, 11:51 | 21,036 | -120 |
| 9 Aug 2026, 14:13 | 21,156 | -67 |
| 8 Aug 2026, 15:08 | 21,223 | +39 |
| 7 Aug 2026, 18:40 | 21,184 | +65 |
| 6 Aug 2026, 21:02 | 21,119 | no change |
| 6 Aug 2026, 20:05 | 21,119 | first reading |
40 posts held, back to 6 August 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 23 pagesof 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 37 of 40 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 40 (6 August 2026 – 15 August 2026) |
| Views total | 8,328 |
| Reactions total | 163 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 19:43 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.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 22 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.
163 reactions across 37 posts, in 9 distinct kinds. The most used accounts for 76.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 125 | 76.7% | |
| 🥰 | 15 | 9.20% | |
| 🎉 | 7 | 4.29% | |
| 👍 | 6 | 3.68% | |
| 💋 | 4 | 2.45% | |
| 🤩 | 3 | 1.84% | |
| 🍓 | 1 | 0.613% | |
| 🐳 | 1 | 0.613% | |
| 👏 | 1 | 0.613% |
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 37 of the 40 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 163reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 6 August 2026 to 15 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.
艺名:#粥粥 地址:#宝安 价格:1000P 1800PP 联系:@qazcctv 频道:https://t.me/f168168fff 标签:舌吻 69 嫩妹 调情 鸳鸯浴 无套口 (已视频认证)
❤3🥰2
艺名:波霸 地址:#罗湖 东门 价格:1000P 联系:@xiaxueyay 频道:https://t.me/baixueerya 标签:御姐 服务好 大胸 (已视频认证)
❤5🎉2
艺名:小妮 地址:#龙华 价格:600P 1100PP 联系:@xiaon181688 频道:https://t.me/xiaoni0012 标签:陪浴 舌吻 口交 嫩妹 (已视频认证)
❤5
艺名:琳琳 地址:#南山 价格:800P 1400PP 联系:@linlin0160 频道:https://t.me/linlin0161 标签:口吹 69 舌吻 陪浴 (已视频认证)
❤4🥰1
艺名:纯纯 地址:#龙岗 价格:700P 1200PP 联系:@szchunchun 频道:https://t.me/szchunc 标签:嫩妹 口吹 鸳鸯浴 69 舌吻 (已视频认证)
❤7🍓1🐳1👍1
艺名:小妮子 地址:#宝安 价格:800P 1500PP 联系:@aimm1314520 频道:https://t.me/xlz123 标签:嫩妹 萝莉 69 kiss 舔咪咪 (已视频认证)
❤5👍1
艺名:茶茶 地址:#罗湖 价格:900P 1700PP 联系:@camellia0723 频道:https://t.me/camellia0820 标签:巨乳E 嫩妹 无套吹箫 丝袜 制服诱惑 (已视频认证)
❤4🥰1
艺名:林林 地址:#龙华 价格:1000P 1800PP 联系:@tianli0707 频道:https://t.me/rhikhf 标签:👄交 足交 舌吻 69 情趣制服 高跟鞋 (已视频认证)
❤3👍2👏1
艺名:原得一人心 地址:#龙岗 大亚湾 价格:400P 800PP 联系:@fhcfe5869 频道:https://t.me/dgfhg_586 标签:洗吹做 鸳鸯浴 34C (已视频认证)
❤3
艺名:火灵儿 地址:#福田 价格:1000P 1600PP 联系:@qz198911 频道:https://t.me/zyzy52022 标签:69 毒龙 舌吻 鸳鸯浴 情趣 (已视频认证)
❤2🥰1
艺名:婷婷 地址:#宝安 价格:700P 1300PP 联系:@ting8110 频道:https://t.me/tingting248 标签:花式吹箫 口爆 毒龙 69 深喉 情趣 (已视频认证)
❤2
艺名:兔兔酱 地址:#福田 价格:900P 1600PP 联系:@yyyhhh123451 频道:https://t.me/yiyiyijy 标签:嫩妹 舌吻 69 角色扮演 事后按摩 (已视频认证)
❤4🎉1
Showing the 12 most recent of 40 posts we hold for @XSJYYZ888. 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.
Citation-graph rank — 80,516 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 12 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“深圳新世界已验证” (@XSJYYZ888), 19,394 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/XSJYYZ888.
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.