Channel
@wwixian778
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
128subscribers
-6 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003892827609 |
|---|---|
| Type | Channel |
| Username | @wwixian778 |
| Created | Between 1 February 2026 and 9 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/wwixian778 |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 9 Oct 2026, 20:39 | 128 | -2 |
| 28 Sept 2026, 23:41 | 130 | +1 |
| 15 Sept 2026, 18:59 | 129 | -1 |
| 9 Sept 2026, 02:41 | 130 | -4 |
| 30 Aug 2026, 21:34 | 134 | -1 |
| 23 Aug 2026, 05:18 | 135 | -1 |
| 16 Aug 2026, 02:53 | 136 | +2 |
| 9 Aug 2026, 00:55 | 134 | no change |
| 9 Aug 2026, 00:46 | 134 | first reading |
10 posts held, back to 9 March 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 10 posts for this entry, the most recent from 9 March 2026. An engagement rate over an empty window would be a number about nothing.
💀“带社交”抖音8w粉丝 精品 预告！大饱眼福这一组 女主一看经常锻炼 笔直的长腿掰成M型 饱满的人小穴 充满淫水 感觉一下插到底 第一下得爽死 白丝黑丝 女仆 红色小套装 教师装 啥都有 人骚还喜欢被调教 生活照看着有点御姐感 一到床上纯欲诱惑感拉满 雪白的大屁股对着我 各种姿势不带重复 让我这种老司机都有点压不住枪了 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀女主生活照看着有点富态的千金脸 一看床上特写映入眼帘的雪白的屁股粉嫩的小穴 真是被惊艳到了 操逼地点也无处不在 温泉野外 和服 黑丝 这些情趣小衣服更不用说 让我最喜欢的还是边掐脖子边草有种大草原的征服欲哈哈 不知道有没有人 和我有一样的癖好 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀“带社交”反差纹身妹 长相感觉偏甜美一点细看又带点御姐范 一直听人说是个纹身九个骚 果然名不虚传 对着镜子看自己的骚逼 玩着手机也不忘操着小逼 皮肤白白嫩嫩的被操起来一脸享受 水滴形的奶子 晃起来格外的带感 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀调教出来的极品 两片阴唇都被操黑了 感觉不是在操逼就是在操逼路上 女仆 新娘 萝莉裙各种情趣内衣换不停 这屁眼开放的程度 应该也没少玩肛交 不得不说这个逼型配上大白屁股 真是让人欲望膨胀 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀“带社交”极品少妇 又白又嫩的大奶子 目测得有D 不知道这种胸推得有多爽啊 像是生过孩子 乳晕特别黑 调教多了也有可能 少妇人妻感满满 腰身比例完美 小细腰配上圆润的的大屁股冲撞起开简直哇塞 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀“带社交”每次看到女主都能想到我大学的学姐 阳光开朗热情 在看到女主在床上浪叫幻想感满满 后入视角小穴的特写 完美的逼型听着动人的叫声 幻想着学姐在我身上蠕动哈哈哈别是一番美景 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀你的初恋正在床上饥渴难耐！！这一组可谓是嫩到了极点 校园里多少人的梦中女神 在床上饥渴的呻吟 让我最喜欢的点 是口交时古灵精怪的小眼神 独属于学生时期清纯感 真是让我心痒难耐 俯拍视角的后入猛插 女主的呻吟真让我心疼 只恨男主不是我啊 ！！ 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀超级王炸请求登场！！！俗话说得好人美逼遭罪 这一组可谓展现的淋漓尽致 玫瑰花插肛门 调教完美的同时设备还好4k极致画质的特写 逼上的皱纹都拍的清清楚楚又细又白的大长腿 圆润饱满的白胸 真是让我大饱眼福 这一组真是力荐！！ 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀“带社交”这组脸像是富养的感觉 现实风景与车 床上乳头铃铛 圆润饱满的逼型 逼水满满 一滑就进 这个胸型可以说是我最爱之一 操起来QQ弹弹 装上乳夹简直点晴之笔 别是一般风景在眼前 有这方面癖好的简直不容错过了 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
💀“带社交”女主可以说满足了我对人妻的所有幻想 道具黑丝渔网树洞 一应俱全 姿势更不用说 全剧最精彩的点莫过于那一抹抹白浆 简直点晴之笔 骚穴配上男主的调教可以说完全独一档的存在 不亚于看剧情片 让我最爽的是 骚穴后入被塞得满满的 还得看着自己被操的视频 别出心裁真是 话不多说 长官今夜我以无法返航 ！ 极品中的极品值得品鉴！！！ 👑《老师的家访》订阅群直达链接 💎《命运石之门》订阅群直达链接 作品集： 🔄👑老师家访点此观看 🎚💎命运之门点此观看 🔎点此/start进入🤖
Showing the 10 most recent of 10 posts we hold for @wwixian778. 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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“《危险便利店》🔞（18+）” (@wwixian778), 128 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/wwixian778.
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.