#咪喵 👑 双马尾白丝女儿服露脸自慰 萝莉 白虎 福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤1👍1

Channel
@zhuiwanse
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
28,060subscribers
-1,248 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003762923929 |
|---|---|
| Type | Channel |
| Usernames | @zhuiwan @zhuiwanse |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 50 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/zhuiwanse |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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, 14:21 | 28,060 | -22 |
| 18 Sept 2026, 21:18 | 28,082 | -76 |
| 17 Sept 2026, 02:37 | 28,158 | -18 |
| 16 Sept 2026, 11:59 | 28,176 | -32 |
| 15 Sept 2026, 02:02 | 28,208 | -19 |
| 14 Sept 2026, 13:21 | 28,227 | -41 |
| 13 Sept 2026, 10:38 | 28,268 | -12 |
| 12 Sept 2026, 23:22 | 28,280 | -66 |
| 11 Sept 2026, 12:20 | 28,346 | -17 |
| 10 Sept 2026, 22:01 | 28,363 | -72 |
| 8 Sept 2026, 17:55 | 28,435 | -23 |
| 7 Sept 2026, 23:21 | 28,458 | -66 |
| 5 Sept 2026, 12:57 | 28,524 | -19 |
| 4 Sept 2026, 23:58 | 28,543 | -57 |
| 3 Sept 2026, 12:56 | 28,600 | -2 |
| 3 Sept 2026, 08:36 | 28,602 | -29 |
| 2 Sept 2026, 05:22 | 28,631 | no change |
| 2 Sept 2026, 04:42 | 28,631 | -53 |
| 1 Sept 2026, 04:47 | 28,684 | no change |
| 1 Sept 2026, 03:45 | 28,684 | first reading |
26 posts held, back to 12 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 38 pages 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 16 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 26 (12 August 2026 – 31 August 2026) |
| Views total | 16,081 |
| Reactions total | 33 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Sept 2026, 05:57 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 24 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.
47 reactions across 23 posts, in 2 distinct kinds. The most used accounts for 53.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 53.2% | |
| 👍 | 22 | 46.8% |
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 23 of the 26 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 47 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 12 August 2026 to 31 August 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.
#咪喵 👑 双马尾白丝女儿服露脸自慰 萝莉 白虎 福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤1👍1
#予予宝 #小予宝 👑 小予宝8月23萝莉次元最新750私定版 双马尾白丝jk制服 假几把抽插馒头嫰穴 叫爸爸高潮 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤2👍1
#幸酱 👑 新作情趣护士服自慰 萝莉 白虎 福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤1👍1
电子女友核弹定制 👑 part2 顶美天菜 再次追加重金定制!地表最强颜值震撼出炉!极品S曲线!腰细臀翘,胸部饱满圆润,一双大长腿又直又细,皮肤白得发光 没想到居然是一条反差母狗,女上位弹力插护士装自慰"老公插的再深一点吧!!" “被金主当狗一样按住爆操” 新增9V #电子女友 #顶美 #高颜值 #反差 #美腿 #母狗 #自慰 #独家高定 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤1👍1
女友精选一对一 👑 part47 国产主播 女友精选一对一 第四十七弹!自购多位高颜值美女一对一视频,各种高颜值骚货大尺度阿黑颜自慰潮喷 新增18V #国产主播 #女友精选一对一 #高颜值 #自慰 #反差 #巨乳 #一对一 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤1👍1
神颜少女 👑 part24 电子女友独家严选 神颜少女 第二十四弹!自购资源 亲自一手购入多位顶级颜值爆表露脸反差小母狗 新增395V #电子女友 #神颜少女 #高颜值 #网红 #御姐 #反差 #母狗 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤1👍1
#铃木奈雪 #江东萌虎 👑 铃木奈雪7月28门槛最新作 cos少司缘黑丝 单男金主口交无套超多姿势做爱啪啪 推特极品白虎少萝宝宝 超嫩萝莉福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
👍2❤1
#呆宝 👑 呆宝7月22萝莉次元788私定版 女儿服白丝超嫩白虎馒头嫩穴 假几把玩具插逼高潮叫爸爸漏脚自慰 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
👍1
#幼幼 👑 幼幼7月萝莉次元1550私定版 白丝jk制服逼脸同框模拟口交 假几把蹲姿弹力插m字腿后入视角玩具自慰 单手比耶阿黑颜高潮脸 推特极品白虎少萝宝宝 高颜值萝莉福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
👍1
#小幼 👑 888私定版双马尾女儿服大奶自慰 萝莉 白虎 福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
❤2👍1
#诗诗 👑 双马尾精神小妹白丝体操服自慰 萝莉 白虎 福利姬 🌂完整内容内群观看 🐣 点击加入会员观看完整版 🌼点击查看打包预览群
👍1
SVIP资源预览+防失联@zhuiwan pinned a photo
Showing the 12 most recent of 26 posts we hold for @zhuiwanse. 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.
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.
“SVIP资源预览+防失联@zhuiwan” (@zhuiwanse), 28,060 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zhuiwanse.
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.