Channel
@melo_xiaoyu
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
86subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004370856950 |
|---|---|
| Type | Channel |
| Username | @melo_xiaoyu |
| Description | 这是我们家玉宝的频道哦 |
| Created | Between 1 June 2026 and 7 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/melo_xiaoyu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 16:18 | 86 | no change |
| 8 Aug 2026, 05:20 | 86 | first reading |
14 posts held, back to 7 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 pageof 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 2 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 14 (7 July 2026 – 5 August 2026) |
| Views total | 2,075 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 16:18 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 9 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 11 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.
4 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 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 4 of the 14 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 7 July 2026 to 5 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.
#牌局复盘 【麻友】：冰红茶 【棋牌室】：#melo麋鹿家 【麻将搭子】：#玉宝 【搭子链接】：https://t.me/melo_8899 【台费】：0筹码+1200费用 【胡牌牌型】： #超大班 【牌局特点】：#高颜 #bbw #蜜桃臀 #微胖御姐 出击时间：2026.07.021 【各项得分】：（0-10，6 为及格，对应大班） 环境：外派 人照：10 身材：10 皮肤：9 态度：9.5 敏感度: 10 抽烟：无 纹身：无 各种钉：无 【综合得分】：10 【牌局体验】： 二刷玉宝 玉宝今天是职业装cos 相遇已不用确认 玉宝主动的坐上了我的接送后座 说我今天穿的衣服跟她的包颜色很搭 转眼来到床上 玉宝主动奖励香吻后两个人就开始闲聊 慢慢靠近 逐渐卸甲 玉宝精致的妆容 一颗一颗的解开白衬衫的扣子 就一个字 涩 褪去上衣之后 开始经典的洗澡环节 从额头开始逐渐往下亲 亲到正面每一个角落 …
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选）还有少量空位 预约私聊老登 🥰🥰 玉宝今日ot 频道链接 测评1 测评2 测评3 测评4 测评5
❤1
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选） 🥰🥰 （10点半后还有位置 预约从速） 频道链接 测评1 测评2 测评3 测评4 测评5
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选）还有少量空位 预约私聊老登 🥰🥰 （9点后还有空位 滴滴私聊老登预约） 频道链接 测评1 测评2 测评3 测评4 测评5
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选）还有少量空位 预约私聊老登 🥰🥰 今日ot 频道链接 测评1 测评2 测评3 测评4 测评5
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选）还有少量空位 预约私聊老登 🥰🥰 今日ot 频道链接 测评1 测评2 测评3 测评4 测评5
【妹子花名】：麋鹿#玉宝 【出击日期】：26.07.05(1h) 【个人标签】：甜御双休、绝美翘臀、全自动 【烟纹身钉】：不抽烟、无纹身、无钉 【班型尺度】：超大，身体接触主动且配合，最大接受度好像是超大＋（需要指套） 【颜值/主动性】颜值 8.5 主动性 9 【内容简述】：麋鹿是原异次元的老登开的新店，去年有段时间很喜欢去异次元，在异次元吃过bbbw,遭遇过快把我干退役的油姐，也遇到过让我上头的妹妹，承载着我许多的回忆。所以当得知老登开了新店后也是趁着七月初空的时候去了三次，尝试了两个素人和一个满姐，素人颜值都还可以，但素人往往很难兼顾尺度和情绪价值，相较之下玉宝的体验确实好很多，满姐确实有满的道理。 玉宝的模样与镜头里的模样并无出入，那日她一身粉调女仆裙搭配透色白丝，干净软嫩里裹着几分撩人的风情，曲线绝美，丰盈性感。刚倚上床沿，便主动朝我靠了过来，慢慢闲谈间化开初见的生分，知晓她是杭州本地人，已走完大学学业。玉宝对待这份工作…
❤3
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选）还有少量空位 预约私聊老登 🥰🥰 玉宝今日ot 频道链接 测评1 测评2 测评3 测评4
店铺：麋鹿 女仆：玉宝 类型：甜美型 出击人：- 出击时间：2026.07 首次服役时间：未知 环境：公寓 人照相似度：8 罩杯：b 身材:前凸后翘 身高：165 体重：99 皮肤：滑嫩 态度：害羞 敏感处: 胸 纹身：无 唇钉舌钉：无 吻技：中蟒蛇 过程：玉宝妹妹真是顶中顶，刷到妹妹一眼喜欢，看着频道的照片和视频后特别心动，就直接约了，遥控上楼一切顺利，开门第一眼就觉得这次血赚。可人是嫩感十足又很耐看的类型，皮肤白滑细腻，身材前凸后翘，腰细腿长，比例很诱人。简单聊了几句，性格温柔体贴，就进入正题，妹妹的屁股很翘。服务细节很到位。手指夹住妹妹的乳头，妹妹开始发出轻哼的声音，从妹妹耳朵到嘴到脖子，一路往下，妹妹化身抖抖怪，敏感度拉满。手在妹妹的屁股上拍打，妹妹也会有反应，稍微带点小m属性，但不多。经过我的一段操作，妹妹化身女骑士直接反客为主，压住我，在我身上起伏驰骋，两只手握住妹妹雪白的大臀抛动着，视觉感拉满，不一会妹妹就没电了，…
😏玉宝 御萝双修 绝美巨臀 🈵姐 配合度超高 千万别错过（老登严选）还有少量空位 预约私聊老登 🥰🥰 今日玉宝ot 频道链接 测评1 测评2 测评3 测评4
店铺：麋鹿 女仆：玉宝 类型：甜美型 出击人：不知名小玩家 出击时间：2026.07 首次服役时间：未知 环境：外派 人照相似度：8 罩杯：b 身材:前凸后翘 身高：165 体重：99 皮肤：滑嫩 态度：害羞 敏感处: 胸 纹身：无 唇钉舌钉：无 吻技：中蟒蛇 过程：这妹妹真的顶啊。身材正好，前凸后翘。脸看着越看越好看。🐻的话要是再大一些就好了。身材也正好，尤其屁股，超级大顶。妹妹很配合。妹妹超大拉满。水也很多。她真的是抖抖怪，而且不是那种装出来的夸张反应，是身体本能型。嘴上说没事，想继续嘴硬，但身体已经先一步露馅。耳朵很敏感，脖子也很敏感，胸也有反应。你靠近耳边，她会一下子绷住。轻轻吹一下，整个人就像被电了一下，肩膀先缩，腰再软，腿跟着乱。她不是那种只发声音的妹妹，她是整个人会抖。一个钟下来我给妹妹服务的很满意。妹妹给我也服务的很满意。 这个绝对超值。以我两月的cj经验。这种妹妹真的很少。
😏玉宝 今天8.30后还有位置哦💝💝 快来塞满她💐💐 玉宝明天休息去拍美美的艺术照了哦🙂🙂 频道链接 测评1 测评2 测评3 测评4
Showing the 12 most recent of 14 posts we hold for @melo_xiaoyu. 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 — 527,395 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“melo麋鹿_玉宝” (@melo_xiaoyu), 86 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/melo_xiaoyu.
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.