Channel
@JUZIZZ8
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,248subscribers
+25 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004397837836 |
|---|---|
| Type | Channel |
| Username | @JUZIZZ8 |
| 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 | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/JUZIZZ8 |
Adult — 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 53% 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, 13:41 | 1,248 | +1 |
| 11 Sept 2026, 01:38 | 1,247 | +2 |
| 6 Sept 2026, 03:01 | 1,245 | +2 |
| 2 Sept 2026, 02:58 | 1,243 | +4 |
| 30 Aug 2026, 11:25 | 1,239 | +2 |
| 27 Aug 2026, 17:29 | 1,237 | +1 |
| 24 Aug 2026, 18:13 | 1,236 | +2 |
| 20 Aug 2026, 16:13 | 1,234 | +2 |
| 18 Aug 2026, 02:02 | 1,232 | +3 |
| 15 Aug 2026, 03:04 | 1,229 | +3 |
| 12 Aug 2026, 05:33 | 1,226 | +3 |
| 8 Aug 2026, 23:50 | 1,223 | no change |
| 8 Aug 2026, 00:32 | 1,223 | first reading |
4 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 4 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.
極®品姓感尤物 𝗴𝗶𝗿𝗹𝘀 天然巨e 马甲线蜜桃🍑 𝗠𝗢𝗥𝗦𝗘 𝗖𝗢𝗗𝗘 𝗢𝗙 𝗟𝗢𝗩𝗘 𝐁𝐨𝐫𝐧 𝐢𝐧 𝐅𝐔𝐉𝐈𝐀𝐍. 𝐇𝐄𝐈𝐆𝐇𝐓:172CM 𝐀𝐆𝐄: 2000 𝐁𝐔𝐒𝐓: 𝐄 𝐜𝐮𝐩 身材窈窕 皮肤细腻光滑温柔且贴心 良家女友风初恋的感觉 不一般的体验 拥有A4腰 腿很长 有马甲线 性格好 情商高 会聊天 配合度高 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
郑州· 北电在校兼职 清纯邻家妹妹脸 不接急 硬5条件短暂开3 清纯气质无整容 不抽烟不喝酒本人无任何一丝风尘气 A4腰筷子腿175 94斤 真🐻c 03年的 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
•Age/年龄03 ”Bust/胸围/D •Height/净高172 •Weight/体重45Kg 完美腰臀比 蜜桃臀 前凸后翘，肉欲刚刚好 又纯又欲。🌊汪汪，私密紧致 皮肤细腻 滑嫩，无风尘味圈外兼职 可69🐍吻，制服 丝袜 身体柔软 配合默契度极高 偶尔上课 有gzs可外出 敏感体质，易湿会吸娇喘 外纯内骚 易抽搐 高潮， 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
07新人下海 真实学生短期兼职 皮肤细腻 雪白 性格温柔 讨课喜欢 • Age年龄2007年 • Height 身高163cm Weight体重80斤 Bust胸围 B 身材均匀，娇小萝莉 初恋女友感 纯白净清秀幼态小孩通.体.雪.白. 三点粉 bb紧致粉嫩如chu 性格超温柔体贴可爱 上课热情超级配合，不催不事 等刚破处 体质敏感 易湿会吸娇喘 主动配合100%自动摇摇机 榨汁机 🟥🟪🟧🟨🟩🟦⬛️⬜️🟥🟪🟧🟨🟩 确保真人真照 本平台合作女孩都带有视频验证【严格把好质量关】 🔍全网任何其他外围平台资源都可带图来咨询 全网所有外围资源桔子都可以安排🛡 实力 诚信 真实 靠谱—认准桔子外围
Showing the 4 most recent of 4 posts we hold for @JUZIZZ8. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“郑州外围/桔子资源/高端预约” (@JUZIZZ8), 1,248 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/JUZIZZ8.
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.