#翠芬 #御姐 #健身 #蜜桃臀 #SM #上海 #狼友投稿 📌 健身小只马 📌可轻SM小御姐 评论区输入【翠芬二】【翠芬三】自动获取二份视频 车牌请在下方群聊输入【翠芬】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤1

Channel
@yuputuanluying
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,214subscribers
+1,728 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003915394213 |
|---|---|
| Type | Channel |
| Username | @yuputuanluying |
| Created | Between 1 April 2026 and 3 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/yuputuanluying |
Adult — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 03:07 | 6,214 | +42 |
| 8 Nov 2026, 17:37 | 6,172 | +50 |
| 5 Nov 2026, 09:16 | 6,122 | +40 |
| 2 Nov 2026, 14:58 | 6,082 | +84 |
| 31 Oct 2026, 00:06 | 5,998 | +64 |
| 28 Oct 2026, 06:36 | 5,934 | +50 |
| 25 Oct 2026, 12:27 | 5,884 | +29 |
| 22 Oct 2026, 09:09 | 5,855 | +16 |
| 19 Oct 2026, 00:27 | 5,839 | +81 |
| 15 Oct 2026, 16:41 | 5,758 | +102 |
| 12 Oct 2026, 14:48 | 5,656 | +139 |
| 5 Oct 2026, 21:00 | 5,517 | +215 |
| 28 Sept 2026, 03:39 | 5,302 | +86 |
| 18 Sept 2026, 14:41 | 5,216 | +44 |
| 14 Sept 2026, 05:37 | 5,172 | +64 |
| 10 Sept 2026, 09:14 | 5,108 | +118 |
| 5 Sept 2026, 12:00 | 4,990 | +94 |
| 1 Sept 2026, 21:14 | 4,896 | +69 |
| 30 Aug 2026, 03:11 | 4,827 | +68 |
| 26 Aug 2026, 23:35 | 4,759 | first reading |
21 posts held, back to 3 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 11 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 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 21 (3 July 2026 – 5 November 2026) |
| Views total | 7,983 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 16:45 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 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.
74 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 93.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 69 | 93.2% | |
| 👍 | 2 | 2.70% | |
| 👏 | 1 | 1.35% | |
| 🔥 | 1 | 1.35% | |
| 😁 | 1 | 1.35% |
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 20 of the 21 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 74 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 3 July 2026 to 5 November 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.
Telegram’s own ‘edited’ marker: 2 of 4 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#翠芬 #御姐 #健身 #蜜桃臀 #SM #上海 #狼友投稿 📌 健身小只马 📌可轻SM小御姐 评论区输入【翠芬二】【翠芬三】自动获取二份视频 车牌请在下方群聊输入【翠芬】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤1
#笑笑 #甜妹 #臀控 #三点粉 #闵行 #狼友投稿 📌反差小母狗 📌喜欢挨炮 评论区输入【笑笑】自动获取一份视频 车牌请在下方群聊输入【笑笑】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
#酒窝茉 #第一白 #健身 #蜜桃臀 #广州 #深圳 #狼友投稿 📌极品身材tg第一白 📌细枝硕果的蜜桃臀 评论区输入【酒窝茉】自动获取一份视频 车牌请在下方群聊输入【酒窝茉】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
#叶子 #波霸 #翘臀 #细枝硕果 #AV音 #上海 #狼友投稿 📌AV音不如她 📌细枝硕果身材 评论区输入【叶子】【叶子一】自动获取二份视频 车牌请在下方群聊输入【叶子】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤3👍2🔥1
#林梦梦 #波霸 #御姐 #服务 #上海 #狼友投稿 📌醉生梦死 📌如梦如幻 评论区输入【林梦梦】【林梦梦一】自动获取二份视频 车牌请在下方群聊输入【林梦梦】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤6
#如烟 #身材 #Bbw #御姐 #翘臀 #波霸 #服务 #上海 #狼友投稿 📌丰臀肥乳 📌榨精潮喷 评论区输入【如烟】【如烟一】自动获取二份视频 车牌请在下方群聊输入【如烟】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤2
#芸诗 #身材 #御姐 #翘臀 #服务 #上海 #狼友投稿 📌翘上天的臀 📌后入很美 评论区输入【芸诗】自动获取一份视频 车牌请在下方群聊输入【芸诗】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤2
#夏夏 #波霸 #身材 #御姐 #服务 #上海 #狼友投稿 📌波霸服务软嫩御姐 📌胸很rua rua 评论区输入【夏夏】【夏夏一】自动获取二份视频 车牌请在下方群聊输入【夏夏】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤3
#夹妮 #翘臀 #豹系身材 #嫩妹 #上海 #狼友投稿 📌 豹子一样的身材 📌欧美风慢热女友型 评论区输入【夹妮】自动获取一份视频 车牌请在下方群聊输入【夹妮】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤3
#语夕 #服务系 #御姐 #花活 #上海 #狼友投稿 📌 波霸御姐 📌尽享服务之姿 评论区输入【语夕】自动获取一份视频 车牌请在下方群聊输入【语夕】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
#竹子 #少妇 #欲妇 #波霸 #三通 #潮喷 #杭州 #上海 #狼友投稿 📌 三通潮喷欲烈妇 📌波霸,猩红纯正天然少毛馒头逼 评论区输入【竹子】【竹子一】自动获取两份视频 车牌请在下方群聊输入【竹子】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤6
#Amy #御姐 #白虎 #上海 #狼友投稿 📌 白虎堂 📌每天吃白虎 评论区输入【Amy】自动获取一份图片 车牌请在下方群聊输入【Amy】可查询 https://t.me/modugmdbot?start=i-9JsDdELCI7UxZjMx
❤2
Showing the 12 most recent of 21 posts we hold for @yuputuanluying. 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 3 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.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“玉蒲团录影小厅堂(接投稿)” (@yuputuanluying), 6,214 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/yuputuanluying.
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.