Channel
@hznm66
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2subscribers
+1 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004359147045 |
|---|---|
| Type | Channel |
| Username | @hznm66 |
| Created | 2 August 2026 — measured — dated from the channel’s first post |
| First recorded | 16 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/hznm66 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 15:40 | 2 | +1 |
| 17 Aug 2026, 15:08 | 1 | no change |
| 16 Aug 2026, 18:30 | 1 | first reading |
3 posts held, back to 2 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
@#报告模板 【所属群组】惠州嫩妹甄选府 【所在地区】江北 【老师艺名】曦曦 【联系方式】@HuizhouLi88 【验证留名】 狗哥 【验证日期】 8-2 【上课价位】1200/pp 【人照几分】9 【服务过程】 看见才上傍第一时间毫不犹豫上车 挺好看的女孩子，提前预约了老师留位，老师遥控上楼在电梯等，值得推荐 写出击报告可获得50嫩妹币！（为了避免恶意刷好评或者差评，需要截图与老师聊天记录，还请各位真实评价吧） 打分标准:9分 ⚠️报告提交给嫩妹婉儿 @hui089bot） 并须附：确认可添加的联系方式聊天等截图，遥控上楼部分聊天截图、付款截图（如现金，请说明)交流群： https://t.me/hznmzx
@#报告模板 【所属群组】惠州嫩妹甄选府 【所在地区】 【老师艺名】 【联系方式】 【验证留名】 【验证日期】 【上课价位】 【人照几分】 【服务过程】 写出击报告可获得50嫩妹币！（为了避免恶意刷好评或者差评，需要截图与老师聊天记录，还请各位真实评价吧） 打分标准:9分 ⚠️报告提交给嫩妹婉儿 @hui089bot） 并须附：确认可添加的联系方式聊天等截图，遥控上楼部分聊天截图、付款截图（如现金，请说明)交流群： https://t.me/hznmzx
Channel created
Showing the 3 most recent of 3 posts we hold for @hznm66. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“惠州嫩妹报告榜” (@hznm66), 2 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/hznm66.
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.