Channel
@JUZIWH
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,271subscribers
+39 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004322282640 |
|---|---|
| Type | Channel |
| Username | @JUZIWH |
| Created | Between 1 June 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/JUZIWH |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 19 Sept 2026, 06:21 | 1,271 | +3 |
| 14 Sept 2026, 19:41 | 1,268 | -1 |
| 11 Sept 2026, 13:15 | 1,269 | +3 |
| 6 Sept 2026, 22:16 | 1,266 | +5 |
| 2 Sept 2026, 01:42 | 1,261 | +3 |
| 30 Aug 2026, 05:37 | 1,258 | +3 |
| 27 Aug 2026, 12:47 | 1,255 | +2 |
| 24 Aug 2026, 10:18 | 1,253 | +3 |
| 20 Aug 2026, 16:44 | 1,250 | +5 |
| 17 Aug 2026, 18:55 | 1,245 | +6 |
| 14 Aug 2026, 13:58 | 1,239 | +3 |
| 10 Aug 2026, 23:36 | 1,236 | +3 |
| 8 Aug 2026, 06:10 | 1,233 | +1 |
| 8 Aug 2026, 00:33 | 1,232 | first reading |
5 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 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
欢迎您来到桔子全国高端外围女预约平台 【十年信誉靠谱老牌】 🔍全网任何平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有验证视频 【严格把好质量关】 实力 诚信 真实 靠谱 明码实价 —— 认准桔子外围 💥官方客服24小时在线 随时咨询💥 预约流程： ⚡️加入会员-会员专属客服会针对会员一对一服务，私发当天实时资源进行挑选，实时更新状态 🐾因外围女孩【大圈】基本都是兼职的，有空才会接单，不是上班制，群内无法实现实时更新所有资源状态（全国每天十几万个女孩开工）也是更好的服务真正有需要的人，为过滤口嗨 ⚡️ 查询所需城市当天的实时资源，挑选心仪的女孩 🐾确定你去女孩那里（自带房间）还是女孩上门来你这（酒店、家里、办公室、车里都可以），及预约时间 ⚡️ 到达地点后，【如电梯需要刷卡…
🦜质量3开 🈲挂圈 ！🉑指定验证 全身零整容 喜整容科技网红脸绕道！ 性感翘臀 无纹身 无疤痕 无不良嗜好 ·Hight身高172 · ·Weight体重/90 ·TBust胸围/ D 明星长相模特身材，A4腰，蜜桃臀，给人眼前一亮的感觉 脾气性格超级好，超级健谈，会哄人情商高 善解人意一流体验好感满满可纯可欲 推荐指数5颗★ 纯兼职 短期开遇到便是缘！ 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
清纯精致款兼职学妹 •Height 身高/ 173cm •Weight体重/ 50kg • Bust. 胸围/E •Age. 年龄/ 07年 🎀 纯新人首次下💦，圈外兼职，紧致水多，敏感体质，易高chao。 🎀礼貌有素质，乖巧听话，服务好 不事不催。配合度百分百，胜任各种姿势。 🎀待客如初恋 提供情绪价值 最好的灵魂伴侣 是你的完美女友。🥢腿 完美腰臀比。无赘肉 🎀天真无邪脸 无辜小鹿眼 眉眼盈盈 楚楚动人 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
武汉 兼职 学生 白幼瘦 乖巧懂事 162/c 小范围在线 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
武汉 06年 学生 优优 假期首次兼职 Age：06 Height： 170cm Cup：D 🍓真胸 妈生脸 🍓清新自然 乖巧礼貌 🍓高素质 性格好 🍓筷子腿 刚破处会夹 • 爱好/看书 听音乐打球爬山 给你难忘的邂逅体验 ✨待客如初恋👍🏻 超好的女友性格 ✨服务好 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
Showing the 5 most recent of 5 posts we hold for @JUZIWH. 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 12 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“武汉外围/桔子资源/高端预约” (@JUZIWH), 1,271 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/JUZIWH.
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.