海南茶院专属报告模板 @hainanchayuan 🏷基础信息 【老师艺名】:露思 【榜单来源】:茶艺榜 @hainanchayi 【验证留名】:匿名 【验证时间】:2026-09-01 【品茶费用】:p(茶院优惠-1) 【位置地区】:美兰 💯综合评价 【总体评价】:8.83 【颜值评分】:9 【服务评分】:8 评分标准:5及以下差, 6分为良,7分为精,8分为优,9分为佳,10分为绝 👙软硬配置 【熊器尺寸】:C 【紧度湿度】:水润紧致 【优点缺点】:生涩颜值不错 💋自由发挥 【过程描述】:新上妹子👀颜值不错,还有工兵券,果断约上一探。妹子跟照片9分相似,颜值不错,之前做过半年主播。由于刚做这个,妹子开始有点局促,就跟她闲聊了一会,妹子态度还行,聊天也很自然。升温后,一起去洗澡,妹子洗澡是我见过差不多最认真的了,前前后后,连脚脖子都涂上沐浴露洗了。在床上妹子虽说只有三件套,但对提出的需求基本也不抗拒,配合得也不错。 …

Channel
露思的后援会
@lusihouyuanhui
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
251subscribers
+209 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004475149693 |
|---|---|
| Type | Channel |
| Username | @lusihouyuanhui |
| Created | 1 September 2026 — measured — dated from the channel’s first post |
| First recorded | 1 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/lusihouyuanhui |
Topic
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 21:00 | 251 | +146 |
| 11 Sept 2026, 05:20 | 105 | +46 |
| 2 Sept 2026, 13:23 | 59 | +17 |
| 1 Sept 2026, 16:00 | 42 | no change |
| 1 Sept 2026, 15:45 | 42 | first reading |
Engagement
7 posts held, back to 1 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 · 30 days
- 47.6%
- avg views ÷ 251 subscribers
- Avg views / post
- 119
- 5 posts measured
- Reaction rate
- 0.521%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 7 held
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 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 7 (1 September 2026 – 1 September 2026) |
| Views total | 597 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 16:00 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.
What this channel posts
- Video runtime
- 9s
- Average length
- 9s
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.
Reaction mix
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 1 of the 7 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 7 most recent posts we hold, published 1 September 2026 to 1 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.
Recent posts
海南茶院专属报告模板 @hainanchayuan 🏷基础信息 【老师艺名】:露思 【榜单来源】:茶艺榜 @hainanchayi 【验证留名】:匿名 【验证时间】:2026-09-01 【品茶费用】:1000p 【位置地区】:美兰区 💯综合评价 【总体评价】:9.5 【颜值评分】:10 【服务评分】:9 评分标准:5及以下差, 6分为良,7分为精,8分为优,9分为佳,10分为绝 👙软硬配置 【熊器尺寸】:c+,很嫩很软,手感很好 【紧度湿度】:水多舒服刚下海 【优点缺点】:老师刚做,会的不多,颜值拉满,不过分的要求都可以提,别的自己开发 💋自由发挥 【过程描述】:老师配合度很好,但是刚做,需要你们自己去沟通 凡出击榜单上的老师提供约课记录截图联系 辅导员 @hainanpc 进入 打桩机内部群 每日抽百元红包
❤1
0️⃣9️⃣0️⃣1️⃣ 🆕🆕 海南茶院·海口三亚万宁 海口美兰嫩妹🍑🍑 👉 #露思 @Lusi759 限量工兵 三个名额 根据接头暗号领取名额:海南茶院,品当季茶 boss 难度 ⭐️ (满⭐️3颗,⭐️越少代表踩雷风险越低) 颜值服务 ⬇️⬇️⬇️ #嫩妹 #kiss #鸳鸯浴 #丝袜 #臀腿 #熊推 老师频道 https://t.me/lusihouyuanhui 往期勇士留下的反馈 参考 👉 https://t.me/HaiNanXObot?start=ugc_-1002560770194_good_lusi759 活动奖励 🔥⤵️ 一次100软妹币/两次200软妹币 💰返现 正常付课费提交报告后找老师可获得奖励 更多白嫖福利活动,尽在海南茶院茶艺榜 https://t.me/hainanchayi/2925 海南茶院永久域名 @hainanchayuan 全拼音 任何时间任何地点可搜索
📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 #海口 #视频已认证 【老师花名】:#露思 【专属标签】:#嫩妹 【区域位置】:#美兰区 【品茶价格】:1000p/1800pp #10/18 【联系方式】: @Lusi759 双向 @Lusi759bot 【教师频道】:https://t.me/lusihouyuanhui 【茶院备注】:请各位狼友积极踊跃投稿,要定金的谨慎出击 聊天群组 | 提交报告 【温馨提醒】: 评论区可查看报告反馈再选择出击
Channel photo updated
期待第一位哥哥
Channel created
Showing the 7 most recent of 7 posts we hold for @lusihouyuanhui. 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.
Forward network
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.
Mentions
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.
Cite this entry
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“露思的后援会” (@lusihouyuanhui), 251 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lusihouyuanhui.
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.