Channel
@tianyenvpu
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,262subscribers
+1,248 since we began measuring on 9 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003959170627 |
|---|---|
| Type | Channel |
| Username | @tianyenvpu |
| Created | 5 September 2026 — measured — dated from the channel’s first post |
| First recorded | 13 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/tianyenvpu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 11:01 | 1,262 | +1,245 |
| 13 Sept 2026, 14:23 | 17 | no change |
| 11 Sept 2026, 11:20 | 17 | +3 |
| 9 Sept 2026, 14:47 | 14 | first reading |
6 posts held, back to 5 September 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 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 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 September 2026 |
|---|---|
| Posts held | 6 (5 September 2026 – 11 September 2026) |
| Views total | 4,239 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Sept 2026, 14:23 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.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 1 of the 6 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 5 September 2026 to 11 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.
有趣的灵魂万里挑一，淼淼进来给我的感觉和照片有点小差距，因为照片以为是个御姐，实际是个非常甜美的妹子，笑起来很好看，非常活泼，她一进来就坐到我腿上，穿着红色 jk，抱着我就亲，我双手捧着她的屁股，给我搞的有点不知所措，我好像猎物一样，期间好多次都把我整的不好意思，玩着飞行棋问我下面大不大，还让我脱裤子给她看看，还主动把我手放到她胸上，妹子太活泼了，我这种有点脸红，招架不住，我野猪品不了细糠😂😂全程都在脸红之中度过，我比较社恐的人，妹子还会跳舞，放了一曲 dj，给我笑的肚子疼，这个活宝大家值得一试
感谢哥哥的好评 哥哥的好评就是最好的宣传❤️
杭州甜野·X 女仆测评模板： 【出击人】：131 【出击女仆】：淼淼 【价格】：899（工兵半价） 【人照】（满分 10）：10 本人更好看 【环境】：公寓类型 【服务过程】：本身已经决定岸了，但是突然看到了这家店，一眼看中了淼淼，这个颜值真的是我非常喜欢的类型，我后来想想算了，但是天意啊，半价出击，那还寻思啥呢，直接找客服预约好时间，到了地方很好找，就是高级公寓，隐私做得很好，到了以后妹子早早在里面等候，本人瘦瘦的，上衣紧身白体恤，胸显得很大，立马忍不住就摸了上去，妹子害羞的不好意思，第一次体验这种不知道什么流程，妹子就拿来拖鞋，邀请我一起洗浴，我当时心想这么刺激，这不就是全裸差不多了，上来就看这么美的画面，然后妹子也一起来洗澡，我想到了刺激的，让妹子穿着黑丝来洗澡，妹子奶子挺挺的，这个颜值我是太喜欢了，瞬间我的鸡鸡硬如刚铁，让妹子用沐浴露立马开始了打飞机模式，先是让他跪着打，看着她如此荡气的模样，然后让她在我的背后，胸贴着我…
❤2
杭州甜野·X 女仆测评模板： 【出击人】：131 【出击女仆】：淼淼 【价格】：899（工兵半价） 【人照】（满分 10）：10 本人更好看 【环境】：公寓类型 【服务过程】：本身已经决定岸了，但是突然看到了这家店，一眼看中了淼淼，这个颜值真的是我非常喜欢的类型，我后来想想算了，但是天意啊，半价出击，那还寻思啥呢，直接找客服预约好时间，到了地方很好找，就是高级公寓，隐私做得很好，到了以后妹子早早在里面等候，本人瘦瘦的，上衣紧身白体恤，胸显得很大，立马忍不住就摸了上去，妹子害羞的不好意思，第一次体验这种不知道什么流程，妹子就拿来拖鞋，邀请我一起洗浴，我当时心想这么刺激，这不就是全裸差不多了，上来就看这么美的画面，然后妹子也一起来洗澡，我想到了刺激的，让妹子穿着黑丝来洗澡，妹子奶子挺挺的，这个颜值我是太喜欢了，瞬间我的鸡鸡硬如刚铁，让妹子用沐浴露立马开始了打飞机模式，先是让他跪着打，看着她如此荡气的模样，然后让她在我的背后，胸贴着我…
Channel photo updated
Channel created
Showing the 6 most recent of 6 posts we hold for @tianyenvpu. 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 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“甜野女仆测评” (@tianyenvpu), 1,262 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/tianyenvpu.
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.