Channel
@huichengyuanyuan
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,647subscribers
+117 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003195657937 |
|---|---|
| Type | Channel |
| Username | @huichengyuanyuan |
| Created | 8 October 2025 — measured — dated from the channel’s first post |
| First recorded | 29 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/huichengyuanyuan |
Giveaways & airdrops — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 09:40 | 1,647 | -7 |
| 11 Sept 2026, 21:00 | 1,654 | +4 |
| 7 Sept 2026, 07:01 | 1,650 | +9 |
| 2 Sept 2026, 20:44 | 1,641 | +71 |
| 30 Aug 2026, 15:37 | 1,570 | +40 |
| 29 Aug 2026, 22:30 | 1,530 | first reading |
15 posts held, back to 8 October 2025 — 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.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 15 (8 October 2025 – 29 August 2026) |
| Views total | 1,540 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 22:30 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 2 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.
🎉 惠州逍遥阁赞助【元元】 🎁 奖品清单 • p 半价减免劵 × 1 🛡️ 参与条件 • 加入 惠州逍遥阁 • 加入 元元的老公们 • 加入 惠州逍遥阁新公开榜 • 需消耗嫩妹币：22 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：22嫩妹币 • 祝福上限：35次 • 祝福一次增加一个抽奖号，提高中奖率 ⌛ 开奖时间 • 2026-08-31 16:19:00 📜 抽奖说明 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等，一律视为无效发言，不计入统计！ 再次重申：灌水无意义发言都不兑奖！请用心交流。 活动最终解释权归 惠州逍遥阁 管理团队所有。 中奖的联系（@yuanyuansese00）约时间 24小时内预约时间，七天内出击，过时自动作废，老师休息，自动延期 炸号需找管理验证，无法验证，奖品放回奖池重新抽奖 中奖需本人出击不得转让 用了优惠劵要写报告！ 不去不要参加 ✨ 愿好运伴随每一位参与者，祝大家好运！
🎉 元元的半价 🎁 奖品清单 • （@yuanyuansese00）1p半价 × 1 🛡️ 参与条件 • 加入 惠州出击大队3.0群 • 加入 惠州出击大队2.0群 • 加入 惠州出击大队1.0群 • 加入 惠州公开榜1.0 • 加入 元元的老公们 • 需消耗积分：5 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：100积分 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-09-03 17:30:00 📜 抽奖说明 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等，一律视为无效发言，不计入统计！ 再次重申：灌水无意义发言都不兑奖！请用心交流。 活动最终解释权归本群管理团队所有。 中奖的12小时内联系管理员领取 @Ajk1233 24小时内预约时间，72小时内出击，过时自动作废 炸号作废放回奖池重新抽奖 用了优惠劵要写报告！ ✨ …
🐷艺名：元元 👩🦰年龄：97年体重49kg 👠身高：163 胸：36B 🧚♀️少妇服务系：毒🐲 胸推 指滑 制服丝袜👠裸吹 水中萧 kiss😘 69☯️ 调情 鸳鸯浴 深喉 爱啪啪啪（配合度极高）任意姿势。能夹会吸 逼💦多。 p-400. (45fz） pp800. （90fz） 夜🎑：2000。 (禁无套） 上课中途不退💰噢 联系TG✈️：@yuanyuansese00。 双向TG🤖️：@yuanyuansese00bot
报告模板 #惠州出击报告 【验证留名】： 【验证时间】：4月28号 【妹子花名】：元元#@yuanyuansese00 【所在位置】：港汇 【 安 全 性 】：安全 【修车水费】：400p 【身高身材】：胸大 160cm 【颜值相似】：9分 【凶器罩杯】：C 【服务内容】：毒龙舔屁眼 69 水中潇 【服务详情】：#熟悉的路程，跟元元老师联系好了就马上出发，进门看见老师身穿性感衣服，房间也干净整洁，交水费、一阵寒暄后就洗澡；来个水中萧，然后叫我趴在床上享受服务，背部漫游好舒服，那舌头也灵活，弄的我差点顶不住了，舔的痒痒的，感觉那对胸在背上软乎乎嫩嫩的好喜欢；柔软的舌头轻轻舔遍身体，翻个面，然后毒龙！毒龙独有的慢节奏让人心情放松，很舒服！进入后很紧，稍稍抽动几下后开始润滑了，有很多水，交换各种姿势，叫声很骚很撩人，不一会就交货了，休息聊天氛围也很好，还按摩、太棒了。而后又休息了几分钟一起去洗澡，穿好衣服和元元老师来个拥抱撤退！ …
报告模板 #惠州出击报告 【验证留名】：杆帆 【验证时间】：4月24号 【妹子花名】：元元#@yuanyuansese00 【所在位置】：港汇 【 安 全 性 】：安全 【修车水费】：400p 【身高身材】：胸大 160cm 【颜值相似】：9分 【凶器罩杯】：C吧 摸起来很爽 【服务内容】：毒龙舔屁眼 69舔 洗澡的时候舔鸡鸡 【服务详情】：#跟老师约好时间，到了位置，遥控上楼，进门以后交了水费去洗澡，老师陪洗得认真，还有水中箫，舌头不停的在龟头上括，令人血脉喷张，令人难以忍耐，赶紧擦干上床，老师换回一套性感战衣，突出那双霸气侧漏的大奶，一爬上床先用双乳漫游全身，人间乐事也，特别是老师的口技，嗦得牛子嗒嗒声，还用舌头在龟头上打转，时不时弹舌一下，然后开始毒龙舔菊花！最后用温柔的舌头舔蛋也非常爽，把小兄弟无微不至，赶紧戴上小雨衣吧，先来一个传统姿势，一边揉搓那大奶，又大又软，忍不住一起含两个大葡萄，身下挺腰狂插，水花四溅，床单…
想念不如相见🙃
⭐️⭐️⭐️🌟🌟🌟
惠州逍遥阁报告模板-叁 【出击老师】：@yuanyuansese00 【提交学生】：@qtqx1 贱哥哥 【服务日期】： 11.13 【服务地区】：港汇附近 【环境与卫生】公寓 环境好 【人照片相符度】：7 【身高与体型参考】：符合介绍 【目测年龄（估计）】：介绍一样吧 【服务节奏与体验舒适度评分】（1–10分）：8 【态度/沟通】： 态度很不错 【性价比】：性价比可以 【是否愿意回访/推荐】：可以回访 【建议与出击体验总结】：服务很不错，态度好，有服务的，真毒龙，灵活，熟妇，喜欢可上，感觉很好
【出击报告】：https://t.me/+4fsonAbER3YwNzhh 【妹子花名】：惠城元元 【联系方式】：@yuanyuansese00 【妹子年龄】：97 【验证留名】：一只小嫖虫 【验证时间】：10.31 【大概位置】：五星国墅园 【修车水费】：400 【人照相似】：8 【身高身材】：160 【凶器罩杯】：C 【湿度紧度】紧 会夹 【环境细节】：公寓 【个人卫生】：优 【时间管理】： 【服务点评】：课表说的都有 【推荐程度】：四星 【评分标准】：8 【流程小文】：进门热情接待递水 交费之后洗澡洗的很仔细 上上下下洗个遍 上床简单按摩之后开始做B面 真毒龙做的很仔细 回转A面舔一遍开始口 热身结束开始女上 女上会夹 1 2 3直接给我秒了。。。
【出击报告】：https://t.me/+4fsonAbER3YwNzhh 【妹子花名】：惠城元元 【联系方式】：@yuanyuansese00 【妹子年龄】：29左右 【验证留名】：Funny Sophia 【验证时间】：10.15 【大概位置】：港惠附近 【修车水费】：200p（半价券） 【人照相似】：7分 【身高身材】：158左右有符文 【凶器罩杯】：B 【湿度紧度】：湿 【环境细节】：环境不错 【个人卫生】：干净 【时间管理】：不催，我123 【服务点评】：服务很好，课表写的都有，毒龙体验很爽 【推荐程度】：喜欢服务的不要错过，性价比高 【评分标准】：综合8分 6分差，7分及格，8分良好，9分优秀，10分完美 【流程小文】：难得中了半价，果断联系老师约定好时间出发，进门交完水费，老师看我脱衣服突然笑起来了，问了后才知道说我比她还白，老师。洗澡过程有水中萧，口的很舒服，洗完老师还帮我擦干。来到床上老师先叫我趴好，开始熊推…
【出击报告】：https://t.me/+4fsonAbER3YwNzhh 【妹子花名】：元元 【联系方式】：@yuanyuansese00 【妹子年龄】：27～8 【验证留名】：牛 【验证时间】：10.15 【大概位置】：河南岸 【修车水费】：400（半价） 【人照相似】：7 【身高身材】：165左右 微肉 【凶器罩杯】：B+ 【湿度紧度】：水多 【环境细节】：干净无异味 【个人卫生】：干净 【时间管理】：准时，不催钟 【服务点评】：服务没得挑 【推荐程度】：7 【评分标准】：7 【流程小文】：整体是美熟妇风，看这样的价格还以为没啥服务呢，没想到有惊喜，有水中萧，波推，不喜欢毒龙，所以没做，口的很久，戴套开干，女上很久，不催钟，奶子有下垂，但是绝对大。整体比对价格，在不宽裕的情况下，绝对超高性价比
【老师花名】：@yuanyuansese00 【课室位置】：#港惠新天地附近 【上课费用】：200p 【出击时间】：11.25 【人照几分】：8 【身高身材】：目测160 【沟通态度】：比较友好 【项目细节】：服务内容都有 【是否超时】：否 【卫生环境】：良好 【自由评论】：水群那么久，终于轮到我中半价了，出发到老师的住所楼下，老师说上一个老哥要加一次，因为有点凶不好拒绝。我想来都来了又是半价，打算等40分钟，结果没一会老师就叫我上楼。 我怕房间留着上一个老哥的味道，在楼下又坐了5分钟才上去。进门后，发现老师并没有频道那么胖，容妆还挺精致的。洗澡很仔细，屁屁和鸡鸡反复洗。但我不喜欢毒龙和口，叫老师不用洗的那么多遍。 开始服务了，老师身材是肚子又点赘肉的，不过服务还是不错的，能做的服务基本都做了，我摸她下面她也没拒绝，配合度极高。后面老师说她屁股大，还撅过来给我玩。我双手持股，那大屁股在我面前摇啊摇，我恨不得像av一样，把脸埋进…
Showing the 12 most recent of 15 posts we hold for @huichengyuanyuan. 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“元元的老公们” (@huichengyuanyuan), 1,647 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/huichengyuanyuan.
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.