【验证留名】:猛猛 【验证时间】:8.15 【妹子花名】: 茉莉 【联系方式】:✈️ 【联系账号】: @huizhoumoli 频道https://t.me/huizhoumolihua 【所在位置】:河南岸 【修车水费】:600 【身高身材】:158 【颜值相似】:9 【凶器罩杯】:b 【服务过程】:今天放假了!想着没事想着放松一下,联系妹子预约到了!见到人以后觉得妹子挺挺漂亮的,身材苗条屁股也翘,这一趟没白约。一起洗澡吧,妹妹的服务很好,洗澡洗得很仔细!还跟来水中宵!口活很不错很有技巧,舔的酥酥麻麻的。服务很用心一点也不敷衍。早已硬邦邦迫不及待的进去了,妹妹还有点敏感,时不时的全身颤抖一下,搞的我越玩越带劲,茉莉老师爱爱时候姿势很配合,简直就是完美的后入炮架子,最后趴妹子身上疯狂输出的时候,妹妹在耳边的浪叫声骚劲十足。整个流程都很耐心,情绪价值拉满。很愉快的体验。兄弟们冲啊。 ✅已核实聊天记录截图

Channel
惠州同城群报告
@hzcj123
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
9,265subscribers
+354 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001704868745 |
|---|---|
| Type | Channel |
| Username | @hzcj123 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/hzcj123 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 04:48 | 9,265 | +196 |
| 10 Aug 2026, 22:34 | 9,069 | +109 |
| 8 Aug 2026, 04:17 | 8,960 | +49 |
| 7 Aug 2026, 20:30 | 8,911 | no change |
| 7 Aug 2026, 20:18 | 8,911 | first reading |
Engagement
187 posts held, back to 7 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 13 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.27%
- avg views ÷ 9,265 subscribers
- Avg views / post
- 118
- 187 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 187
- of 187 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.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 187 (7 August 2026 – 15 August 2026) |
| Views total | 22,053 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 09:14 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
- Photos
- ≈2
- Links
- ≈2,270
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
【验证留名】:梅西 【验证时间】:8.15 【妹子花名】: 77 【联系方式】: @mama8899001 【联系账号】: 飞机 【所在位置】:河南岸 【修车水费】:5 【身高身材】:10 【颜值相似】:9 【凶器罩杯】:D 【服务过程】:第三次出击老师了 ,进门就嘘寒问暖 ,洗澡还有水中萧一样的各种服务,毒龙 猴子偷桃 一样 360 度口交 ,强烈推荐!!!! ✅已核实聊天记录截图
【妹子花名】:苏禾 【所在位置】:仲恺 【修车费用】: 700 【备注】 :口爆 舌吻 spa 【凶器罩杯】:C 【身高身材】: 165 【大概年纪】: 24 【服务内容】:朋友介绍的,我就自己提前预约,带着制服过来了,老师换上后,把我都看呆了。白色衬衣简单收腰,齐膝短裙魅惑十足,没有穿内衣,隐隐约约看见两个能把我鸡巴裹紧的又嫩又白的奶子,身材比例看着就让人瞬间硬起来了,想立马扑上去羞辱她,把鸡巴放在她两个奶子之间摩擦。服务开始后,老师跪在我面前,把衬衣解开一半,把我的鸡巴先放在嘴里吸了吸,然后又放在自己脸上揉搓,等我的鸡巴涨到老师嘴里已经完全含不下时,又放进奶子中间,紧紧夹住龟头,给我胸推。我闭着眼睛享受着,脑海里全是当年高中时想操的那个校花的模样。老师还贴心的把我的手放在她的奶子上让我抚摸,配合着叫着老公,浪叫着、娇喘着,让我用精液把她的两个奶子都涂满。感觉我快射出来的时候,老师把我的鸡巴放在她的乳头上,轻轻压了…
报告模板 【验证留名】:匿名 【验证时间】:8,14 【妹子花名】:糖小北(小七) 【妹子联系】:@qiqi999995 双向🤖️:@qiqi_7_7Bot 【妹子频道】:@xiaoqi999995 【所在位置】:江北 【 安 全 性 】:安全 【修车水费】:1200pp 【身高身材】:160 【颜值相似】:9 【凶器罩杯】:天然🐻C 【服务内容】:课表一致 【服务详情】:第二次约小七,看到小七本人还是一样好看耐看,人照差距不大 交了水费一起去洗浴。小七老师帮我洗的很认真、一次性浴巾、漱口水都有准备。 老师本人笑起来特别好看,每次看到小七老师笑总是有一种治愈感,服务很认真,态度很好,一起沐浴后进入主题,前戏做足,调情完便戴套慢慢进去老师的身体,老师的反馈也是很强烈,老师会夹会吸,床上体验也是极佳。由于太紧了,换了几个姿势,最终顶不住了,成功出水,简单休息后又继续。老师挺不错,服务态度好。 【…
#惠州出击报告 【验证留名】:避雷哥 【验证时间】:8.14 【妹子艺名】:芊芊 @dandan663333 【场所类型】:自开,课室 【安 全 性】:不出击最安全 【修车水费】:600p 【人照几成】:9 【身高体重】:165 【胖瘦赘肉】:微微胖 【凶器罩杯】:C 【老师类型】:学妹 女友 【服务类型】:全套一条龙 【服务态度】好评 【优点缺点】:无确定 缺点:无 ① ② ③ 优点:很多 ①服务很多 ②胸大 ③温柔 【自由发挥】:进门老师温柔的声音一下就吸引到我了,先缴水费,然后招呼洗澡,洗澡过程温柔擦拭我的全身,然后开始舔舐我的猫条,老师的口活很棒,后面进房间开始服务,波推,吃棒,后面塞进去,老师很多水,噗噗噗就完事了,很棒 【推荐程度(自身主观评分)】:9分满分10分 @dandan663333 ✅已核实聊天记录截图
【老师艺名】骚宝 【联系方式】 @hzxyz11 【所在位置】江北 【验证留名】今日唔陪跑 【验证时间】8.13 【修车费用】600 【颜值身材】人照九分 身材满分 【服务内容】 课表上该有的都有 【服务态度】10分 【优点缺点】说话温柔,口活好,服务都有,🐍个饱 【推荐程度】9.5分 【体验细节】 老师提前一晚跟我联系,约好了时间第二天我就赶往老师的住处。因为刚好下大雨,老师很体贴说不着急可以晚点到也没关系。开门的时候印入眼帘是个高挑的美女,身材很均匀不会很瘦,老师引导我先坐下休息,给我递水然后跟我聊天。交完水费老师就陪着我一起洗浴并给我擦拭后背,进入房间就让我选衣服,不得不说各种战袍一应俱全,选了一套红色的加丝袜就开始进入主题。老师爬上来就给我一个大蟒蛇,我不能示弱,手抓起胸回敬她,然后老师就从两点一路往下,吸我的🥚并且一口把我小头给含了进去,没有齿感,并且老师询问我是否69,我平时不爱69,但老师这个颜值和身材,我必须来一…
【验证留名】:萧战 【验证时间】:8.15 【妹子花名】:叶子 【联系账号】: @yezi8853 【所在位置】:江北 【修车水费】:300 【身高身材】:8 【颜值相似】:8 【凶器罩杯】:C 【服务过程】:进门老师很热情,制服挺多的,换着玩感觉很好,主要提一下服务很好,价格实惠 而且这妹子的战斗力不是一般的强。没有齿感,各种技术运用得不错,像吸,舔,深喉等等,吹得我差点出水,中间各种姿势都脑补吧, ✅已核实聊天记录截图
【验证留名】:皮皮 【验证时间】:8.15 【妹子花名】: 水多多 【联系方式】:✈️ 【联系账号】: @duoduoshui666 【所在位置】:河南岸 【修车水费】:500➕100 【身高身材】:8 【颜值相似】:8 【凶器罩杯】:38D 【服务过程】:之前朋友一直说老师服务好,今天正好有空,提前约了l老师,到了进门正如朋友所言 老师服务很好 进入主题 全程服务不错 水中潇 床上各种前戏 十分哇塞,服务太棒了,推荐推荐 ✅已核实聊天记录截图
【验证留名】:匿名 【验证时间】:8.15 【妹子花名】: 莓莓 【联系方式】:✈️ 【联系账号】: @meimei008866 【所在位置】:江北 【修车水费】:450 【身高身材】:9 【颜值相似】:9 【凶器罩杯】:C 【服务过程】:榜上看妹子很漂亮,就想着过去看看,见到人以后觉得妹子挺清纯。身材苗条屁股也翘,这一趟没白约。服务很用心一点也不敷衍。早已硬邦邦迫不及待的进去了,妹妹时不时的全身颤抖一下,搞的我越插越带劲,简直就是完美的后入炮架子,最后趴妹子身上疯狂输出的时候,妹妹在耳边的浪叫声骚劲十足。情绪价值拉满。够风骚,很愉快的体验。 ✅已核实聊天记录截图
【验证留名】:渣哥 【验证时间】:8.15 【妹子花名】: 西西 【联系方式】:✈️ 【联系账号】: @shuiyun007 【所在位置】:江北 【修车水费】:500+200 【身高身材】:162 【颜值相似】:8 【凶器罩杯】:B➕ 【服务过程】:开了半个小时的车来找西西老师,只为听朋友说她的可以后花园,今天一见感觉人也好漂亮,好爱笑,很开朗,服务做的每一项都很到位,老师的口活让我倍感的好,那后花园,还会夹我,天啊,太爽了,爽爆了,第一次玩后花园,原来这么舒服爽 ✅已核实聊天记录截图
【验证留名】:三藏 【验证时间】:8.15 【妹子花名】: 榴莲 【联系方式】:✈️ 【联系账号】: @liulian85 【所在位置】:江北 【修车水费】:500 【身高身材】:165 【颜值相似】:8 【凶器罩杯】:C 【服务过程】:开门看见老师身材完美 老师的五官很立体,房间干净整洁 淡淡的香味 老师口的超级认真 实在忍不住了 服务完直接后入 很喜欢老师的臂翘 也很喜欢老师雪白的腿 太喜欢这种 整个浪冲下来 老师的叫声越来越猛 直接出水了 又刺激又满足 个人觉得体验感拉满了 ✅已核实聊天记录截图
【验证留名】:蔡徐坤 【验证时间】:8.15 【妹子花名】: 77 【联系方式】: @mama8899001 【联系账号】: 飞机 【所在位置】:河南岸 【修车水费】:500 【身高身材】:162 【颜值相似】:人照一致 【凶器罩杯】:d 【服务过程】:课表上都有,小区安全,遥控上楼,口活是我遇到最好的老师,很紧,耐草,不催钟,服务好 ✅已核实聊天记录截图
Showing the 12 most recent of 187 posts we hold for @hzcj123. 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.
Posts edited after publishing
@hzcj123 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 10 August 2026
- Most recent edit
- 10 August 2026
Citation-graph rank
Citation-graph rank — 43,942 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@anqi2520 · 2,3447 posts清雅报告
@as12258 · 234 posts娜塔莎(加拿大华侨)💋💋
@Mgtasha25 · 5493 posts🎲骰子第七面🤪嘟嘟
@dudu78899 · 1,9612 posts佳妮宝贝~🍇麦地开课🍇
@jiani9987 · 2,5612 posts泰韩混血儿 奶蜜 白虎🥰🥰
@ai1138 · 8371 post雅宁频道
@asasa1558 · 7281 post惠州 🇹🇭泰国淫女咪咪 可3p
@CYMM18 · 5271 post芊芊小花园
@dandan01123 · 1,6761 post琪琪的小花园。😍😍
@qiqi11992 · 4191 post惠州 泰国颜射女王💦小野猫🐱
@YSNWXYM · 6851 post港惠 媛媛抓🐉 95 98
@yuanyuanzljqq · 7161 post
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.
@a125588 · 1,1702 posts清雅报告
@as12258 · 232 posts丝丝的频道
@asz12558 · 692 posts优优鱼塘
@hzyouyouyut · 3,2412 posts🌈🌈一字马舞蹈老师
@jiayang6988 · 682 posts希菲频道
@sdfv855 · 8722 posts雅宁频道
@asasa1558 · 7281 post小婷后宫
@cocodehougo · 3511 post优优
@hzshanshan · 4221 post小婷的朋友圈
@hzxtwan · 2,6331 post云汐95抓🐉筋
@yunxifacai · 1,1591 post
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“惠州同城群报告” (@hzcj123), 9,265 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hzcj123.
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.