Channel
@dhuwvwyxv
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
385subscribers
+260 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004455926110 |
|---|---|
| Type | Channel |
| Username | @dhuwvwyxv |
| Created | 28 August 2026 — measured — dated from the channel’s first post |
| First recorded | 28 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/dhuwvwyxv |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 17:57 | 385 | +178 |
| 29 Aug 2026, 14:47 | 207 | +82 |
| 28 Aug 2026, 16:45 | 125 | no change |
| 28 Aug 2026, 16:30 | 125 | first reading |
4 posts held, back to 28 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 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 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 4 (28 August 2026 – 28 August 2026) |
| Views total | 1,092 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 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 1 video 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 2 of the 4 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 28 August 2026 to 28 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.
【时间】：2026-08-28 【老师】：夏荷 【留名】：八戒 【评价】：👍 好评 【人照】：9 【颜值】：9 【身材】：9 【服务】：9 【态度】：10 【环境】：9 【综合】：9.17 【过程】：按照约定，来到老师教室，见到老师是个嫩妹，皮肤好，身材比例好、看起来很乖巧，觉得还挺不错，寒暄几句，就一起去洗澡了，洗完澡老师换上战袍，就开始服务，先是胸推，感觉酥酥麻麻的，接着开始口，不能说很熟练吧，但非常认真，能感觉到老师刚来，接着我要求69，老师很配合，姿势切换很丝滑，舔着老师的香逼，太过瘾了，一会会老师浑身颤抖，发出哼唧的声音，反馈很好，声音很好听，感觉差不多了就戴套开始，入侵感很强，爽歪歪，小黄文就不写了，老师的反馈感很强，整个过程老师都表现的非常好，各种姿势都会去配合，值得出击！厉害的ly可以来调教调教，多开发几个姿势！
厦门工兵推荐榜 t.me/renzhenggongkaiban ❤️萝卜青菜各有所爱，出击感受仅代表个人喜好以及观点，请各位自行斟酌考量❗️ 【出击日期】：8.28 【验证人】：Hilary 【老师艺名】：夏荷 【老师账号】：@yuiopiop1 【地 区 】：思明区 【水费/次】：p700 【人照相似】：90 【目测年龄】：19 【颜值妆造】：90 【身材曲线】：90 【乳房状态】：b+ 【臀部形态】：小翘 【皮肤状态】：手感很好 【服务评分】：95 【情绪价值】：90 【日☀️后感/详细描述】： 看到新上榜的夏荷老师是我喜欢的类型，但就是太好看了，就怕期望值太高，纠结半天最后又是二弟战胜理智的一次，约了课立马驱车前往，开门见到老师突然感觉有点不知所措，老师拉起我的手就往沙发那走，瞬间缓解了我当时的尴尬，老师跟我预期的一样，身材超好没有赘肉而且下面特别紧，跟处女的感觉一样，验证过了，确实刚下海，身体光滑女友好满…
用户名：@yuiopiop1 双向机器人：@xiahezbshs_bot
❤1
Channel created
Showing the 4 most recent of 4 posts we hold for @dhuwvwyxv. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“夏荷🐳（思明区）” (@dhuwvwyxv), 385 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/dhuwvwyxv.
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.