Channel
@zhhsgkb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,823subscribers
+5,106 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001509617863 |
|---|---|
| Type | Channel |
| Username | @zhhsgkb |
| Created | Between 1 July 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/zhhsgkb |
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 |
|---|---|---|
| 18 Sept 2026, 22:42 | 6,823 | +1,192 |
| 14 Sept 2026, 08:56 | 5,631 | +403 |
| 10 Sept 2026, 23:21 | 5,228 | +1,124 |
| 6 Sept 2026, 11:22 | 4,104 | no change |
| 6 Sept 2026, 05:21 | 4,104 | +911 |
| 2 Sept 2026, 03:34 | 3,193 | +732 |
| 30 Aug 2026, 01:13 | 2,461 | +324 |
| 27 Aug 2026, 05:17 | 2,137 | +523 |
| 24 Aug 2026, 05:37 | 1,614 | -2 |
| 20 Aug 2026, 22:36 | 1,616 | -37 |
| 17 Aug 2026, 17:38 | 1,653 | -9 |
| 14 Aug 2026, 22:16 | 1,662 | -38 |
| 11 Aug 2026, 11:16 | 1,700 | -18 |
| 8 Aug 2026, 03:27 | 1,718 | +1 |
| 7 Aug 2026, 11:00 | 1,717 | first reading |
20 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 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 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 20 (1 September 2026 – 6 September 2026) |
| Views total | 7,962 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Sept 2026, 11:22 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 10 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.
4 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 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 20 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 1 September 2026 to 6 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.
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 还在犹豫今晚去哪放松、去哪直接爽？ 四个字就够——「留个房间」。 发给我，剩下全部我来安排。客服秒回对接，快速确认，随时能约。 店里全是极品货色：清纯甜美反差大的、高冷御姐直接骑的、温柔会舔会吸的、火辣胸翘逼紧的……你点哪种就上哪种，保证一眼就硬。 环境私密安静，灯光暧昧，隔音拉满，音乐低调，门外谁都不知道你在里面被吃得有多狠。 从进门开始她就上手：摸硬、深喉、舔蛋、口爆到你腿软，再把湿热小穴坐上来又夹又摇，用温度、技巧和耐心把你从头到脚的压力和精液全部榨干净。 懂享受的别再一个人憋着。 今晚不想空着手打？直接私信我，我帮你安排最舒服、最能射的夜晚。 悄悄来，射完再走，尽兴为止。 私信「留个房间」，位置现在就能给你留。 营业门店：📍📍📍📍 ①尊贵桑拿 ②玖号水疗 ③八汤御桑 ④尚品水疗 ⑤漫豪水疗 ⑥巨享水疗 ⑦凯旋桑拿 ⑧英皇极品 ⑨利奥荟所 ⑩皇家金宝 😮唯一客服点…
澳门98桑拿 珠海94水床 认准置顶联系方式秒安排
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 故事从私信开始； 放纵从见面那一刻直接点燃； 沉沦从她唇舌贴上来、湿热小嘴把你整根吞进去的瞬间彻底陷落。 这里全是各路极品：清纯邻家妹妹反差超大，高冷御姐骑上来就榨，温柔似水的会一直舔到你腿软，火辣勾魂的直接把胸和逼送到你脸上。想操哪种，随便挑。 店里私密安静，灯光暧昧，隔音拉满，门外再吵里面也能让你大声喘、用力干。服务又骚又专业：从前戏摸硬、深喉口爆、舔蛋吸到你发抖，再到湿热小穴直接坐上来又夹又摇，每个动作都只为把你伺候到颤抖、射到腿软、欲仙欲死。 懂享受的你，别再憋着。 来98，把所有欲望一次性释放干净。 让她用最软最热的嘴和逼，把你直接干上巅峰。 私信预约，位置随时留，来了就能开操。 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 想操真正懂男人的货？今晚别错过。 这里全是极品女：性感御姐骚得要命，甜妹萝莉清纯反差，身材爆乳翘臀前凸后翘，要什么有什么。一进门，暧昧灯光+浓香直接把你围住，鸡巴硬、心跳炸、血往下涌。 零压力，纯放松。随便聊、随便摸、随便操。她们专业又骚，从细致前戏、深喉口爆、舔蛋吸到你射，到湿热小穴直接骑上来夹，每个动作都精准伺候到位，让你被伺候得彻底爽翻。 今晚就狠狠放纵一次。 让那个懂操的她，用最软最热的嘴和逼，把你直接操上天。 私信预约，位置随时给你留，来了就能干。 营业门店：📍📍📍📍📍 ①尊贵桑拿 ②玖号水疗 ③八汤御桑 ④尚品水疗 ⑤漫豪水疗 ⑥巨享水疗 ⑦凯旋桑拿 ⑧英皇极品 ⑨利奥荟所 ⑩皇家金宝 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 📱📱📱📱夜深了还硬着熬？别再自己撸到空虚。 这里有懂伺候的小妖精——会骚聊、会撒娇、会全身按摩，更会用又湿又热的嘴和身体，把你从头吃到尾，伺候到你腿软站不起来。 指尖游走、唇舌缠绕、深喉吞到底，奶子夹、穴里绞，每一寸都按你最爽的节奏来，直接干到你射到没力气。 环境私密暧昧，灯光刚好方便动手动嘴。 进门你就是被舔被操的贵客，出门只剩满身牙印、精味和还想再射一发的余韵。 烟酒算个屁，把火都交给她。 让她用舌头、奶子、骚穴帮你彻底泄火，干到你囊袋空、腿发软为止。 今晚别忍了。 来澳门98，选个最骚的，把精液全射她身上，尽情操到爽。 营业门店：📍📍📍📍📍 ①尊贵桑拿 ②玖号水疗 ③八汤御桑 ④尚品水疗 ⑤漫豪水疗 ⑥巨享水疗 ⑦凯旋桑拿 ⑧英皇极品 ⑨利奥荟所 ⑩皇家金宝 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 澳门桑拿营业中，一手对接澳门所有大型98全套水汇！ 新人不定时上新，喜欢哪个直接挑，不满意当场换人，零扯皮！ 主打高性价比口技会所，干净安全、明码实价，绝无任何隐形加收。 来过一次你就懂：什么叫真正把钱花在刀刃上的服务。 专业客服在线，只给你安排最对味、最舒服的组合。 我们的技师才是真·实力派——舌技细腻灵活、深喉稳准狠，节奏把控拉满，直接把你送上云端，爽到腿软才算合格。 放松、尽兴、花得值，这是我们写在脸上的承诺。 别再犹豫了，现在就进来选最合眼缘的妹妹，把极致快乐一次兑现～ 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#珠海 #珠海会所 #珠海水床 #珠海SPA 半夜一个人待着最难受，是不是也想找点只属于自己的温柔？ 这儿的妹妹早就等着了。会甜着嗓子跟你撒娇、陪你扯几句闲话解压，更会用细细的、不着急的手法和水床，一点点把你身上的累卸掉。话说得暖、手碰得轻，全是冲你一个人来的。 别再自己硬撑着了。今晚直接过来，让她好好宠你一回，重新体会被偏爱、被哄着的感觉。 门一推开，里面就是放松和温柔，够你整晚缓过来。 珠海本地水床会所，懂的自己来。 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#珠海 #珠海会所 #珠海水床 #珠海SPA 人来人往，多是匆匆过客。真正懂你累、懂你想放松的，其实就那么一点舒服。 推开这扇不起眼的门，外面的吵和烦都先停在门外。屋里灯不刺眼，暖得刚好，空气里有点淡淡的香，干净又私密，专门给想好好享受一下的人准备的。 水床一躺，整个人就软了。服务细到骨头缝里——轻一点、重一点、湿润的包裹、灵巧的节奏，全按你的反应来。佳人手法稳、眼神专注，唇舌又热又会，帮你把一天的憋闷一点点卸干净，直接把人送到最爽的那个点。 不用说太多废话。足交那一下的紧和颤、69时的彻底释放，都会变成今晚脑子里最清楚的画面。 压力全丢给我们，快乐自己留着就行。 珠海本地水床水疗，懂的来。私密、干净、到位。 550体验全裸日式水床，高质量技师30多个就位，来到直接安排海选！ 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
🎰 珠海澳门专群VIP福利🧧 📮 抽奖条件: 🎫 加入-珠海澳门【会所专群】 🎫 加入-珠海|澳门95-98水疗会所 🎫 加入-珠海澳门95-98水床会所 🎁 奖品内容: 澳门会所通用优惠卷300元 × 3 珠海会所通用优惠卷30元 × 5 💡 活动说明: 中奖联系: @ZAOM888 中奖者需提交中奖截图 兑奖有效期3天 群组内每发言数10条可增加中奖概率 中奖福利不可叠加使用 📅 开奖日期:(UTC+8) 2026年09月07日 23时00分00秒
❤2
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 为什么澳门桑拿98会所这么火？ 因为真正年少有为的男人早就看透了：再成功，不来会所爽一把，人生照样缺一块。 成年人的世界其实就这么直接—— 一个极品嫩模在眼前，一张又湿又会吃的嘴，再配上专业技师按你喜好量身定做的全套流程。从头舔到脚，从外玩到里，整个人彻底泡在极致快感里，想射就射，想再来就再来。 压力、疲惫、憋了很久的欲望，全部在这里被吸干净、射透、释放到软。 今晚别再忍了。 找个真正懂怎么伺候男人的地方，好好犒劳自己。 会赚钱更要会享乐，这才是成功男人该有的样子。 想要的，直接来98会所。 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 澳门98会所·私定制高端体验 推开门，奢华私密的气息直接扑面而来。 等着你的全是精挑细选的顶级美女：脸蛋甜、身材爆，S曲线又软又翘，眼睛勾人，笑起来就让人想马上动手。修长美腿一夹，眼神一撩，瞬间硬到发疼。 这里只做真正的私定制： 你想怎么玩就怎么玩。从温柔舌吻、深喉猛吸，到边吃边摸、边插边叫，全程不赶时间，服务到位又放得开。湿热的嘴、紧致的身体、毫不掩饰的呻吟，专门把你积了很久的欲望一次次吸干、射透。 澳门会所桑拿，不玩虚的，只给你最直接、最爽的极致释放。 今晚就来，把人带走，把精射干净，享受属于你的奢华淫靡之夜。 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
#澳门 #澳门会所 #澳门水疗 #澳门桑拿 都市节奏太快，人很容易把自己掏空。 给自己留一段真正慢下来的时光，推开那扇不起眼的门，木质香气混着暖昧柔光慢慢漫过来。闭上眼，只有舒缓的背景音，和渐渐变得急促的呼吸、湿热的包裹。 从环境到服务，每个细节都为极致放松而生：柔软灵活的唇舌、精准又大胆的技巧、一次次深喉般的紧密吸吮，把身体里积压的紧绷彻底卸掉。在反复湿热的冲击与释放里，欲望和心灵一起被掏空，最后只剩下原始的平静与满足。 这里不只是减压，更是一场专属于感官的盛宴。 预约你的专属技师，享受私密空间里最直接的口舌服务，让每一次喷发都清晰、强烈、难忘。 今晚就来澳门，把最极致的轻松和高潮带回家。 😮唯一客服点击联系😮 ➡️ 会所经理 ➡️ 经理机器人 进群查看技师报告➡️会所专群
Showing the 12 most recent of 20 posts we hold for @zhhsgkb. 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 2 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“珠海|澳门95-98水疗会所” (@zhhsgkb), 6,823 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/zhhsgkb.
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.