成都最新中圈相册:https://link.zhihu.com/?target=http://57846.tn4ec114.shop 密码:222 频道内基本为大圈真实资料 中圈请看此相册 详情看置顶,咨询专属客服

Channel
成都外围 【网红 模特 学生】
@waiweisn66688
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
17,312subscribers
-12,634 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001552324462 |
|---|---|
| Type | Channel |
| Username | @waiweisn66688 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/waiweisn66688 |
Topic
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 03:41 | 17,312 | -131 |
| 15 Sept 2026, 20:37 | 17,443 | -302 |
| 14 Sept 2026, 01:21 | 17,745 | -270 |
| 12 Sept 2026, 10:17 | 18,015 | -325 |
| 10 Sept 2026, 06:38 | 18,340 | -407 |
| 7 Sept 2026, 00:20 | 18,747 | -344 |
| 4 Sept 2026, 08:35 | 19,091 | -147 |
| 2 Sept 2026, 22:15 | 19,238 | -259 |
| 1 Sept 2026, 20:44 | 19,497 | -427 |
| 31 Aug 2026, 21:56 | 19,924 | +147 |
| 30 Aug 2026, 19:37 | 19,777 | -593 |
| 29 Aug 2026, 23:04 | 20,370 | -363 |
| 28 Aug 2026, 23:54 | 20,733 | -406 |
| 27 Aug 2026, 20:37 | 21,139 | -79 |
| 26 Aug 2026, 21:45 | 21,218 | -292 |
| 25 Aug 2026, 19:28 | 21,510 | -272 |
| 24 Aug 2026, 22:49 | 21,782 | -479 |
| 23 Aug 2026, 11:48 | 22,261 | -213 |
| 22 Aug 2026, 01:48 | 22,474 | -455 |
| 20 Aug 2026, 17:48 | 22,929 | first reading |
Engagement
26 posts held, back to 1 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 58 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.35%
- avg views ÷ 17,312 subscribers
- Avg views / post
- 926
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 26 held
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.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 26 (1 August 2026 – 30 August 2026) |
| Views total | 3,703 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:19 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.
What this channel posts
- Video runtime
- 1m 52s
- Average length
- 7s
Measured directly from 15 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.
Reaction mix
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 5 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 3 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 1 August 2026 to 30 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.
Recent posts
#成都外围 08甜妹刚下水 冰清玉洁 清纯可爱 一次牵手 回味无穷 你的初戀情人𝗶𝗻𝗴...✨ Age:08年 身高:168胸围:D 身材高挑 五官精致 皮肤雪白 性格温柔 ⚠️拒绝低素质、议价
#成都外围 传媒学院校花 纯兼职 170C 声音甜美 皮肤雪白 性格温柔 最佳女友款👩 -热爱🫶健身 瑜伽🧘♀️普拉提 -筷子腿 腰臀比超级好 -只见高素质导
#成都外围 极品萝莉 162C 06年 身高:162 🐻:C 体重45kG ·穿着打扮洋气 💓只接待素质客户 温柔体贴 懂事 智慧有内涵 我希望我不是被選擇 而是被熱愛 遇见的都是天意 拥有的都是幸运🌸
#成都外围 予沐精品🍵极品嫩汁纯欲少女 初恋的感觉 千载难逢的顶级少女~可 🎀08年 B+ 杯 18岁 体重80斤 可验sfz纯情 小甜妹 🎀165cm身材匀称 🎀甜度严重超标,想被哥哥抱起来doi 🎀后入超级大屁屁 细腰翘臀 绝佳视觉享受 🎀bb紧致粉嫩如chu 🎀全身无整 皮肤超白嫩 🌸性格超温柔体贴可爱 🌸上课热情超级配合,不催不事 🌸有制服,丝袜,jk 🍓双商高 乖巧听话 不催不事♡ (好评选手 🈶真实好评图) 🎀刚破处 体质敏感 易湿会吸娇喘 🎀主动配合100% 自动摇摇机 榨汁机 🍹 痉挛高潮一触即发♡ 🎀 待哥哥如初恋般热情 主动口 主动求干 爱爱叫声超甜🥰
成都最新中圈相册:https://link.zhihu.com/?target=http://57846.tn4ec114.shop 密码:222 频道内基本为大圈真实资料 中圈请看此相册 详情看置顶,咨询专属客服
❤1
成都最新中圈相册:https://link.zhihu.com/?target=http://57846.tn4ec114.shop 密码:222 频道内基本为大圈真实资料 中圈请看此相册 详情看置顶,咨询专属客服
#成都外围 艺名:果冻 💐身高/163 💐体重/40kg 💐胸围/C 💐年龄/06年重庆人 🉑颜🉑甜,🉑纯🉑欲,全身雪白,乖巧听话,女友感觉,男友待遇 🉑kiss🉑69 🉑足交 会聊天,腰细臀圆翘,解锁各种姿势,服务一流,听话温柔,丝袜配合各种姿势 会聊天,善解人意。
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6630833138
成都最新中圈相册:https://link.zhihu.com/?target=http://57846.tn4ec114.shop 密码:222 频道内基本为大圈真实资料 中圈请看此相册 详情看置顶,咨询专属客服
❤1
频道内均为大圈资料,小圈到中大圈资料都在相册里,不懂得请咨询客服
#成都外围 成都❤️人 体验抱起来的感觉🌺 温柔懂事, •𝐇𝐞𝐢𝐠𝐡𝐭身高/,173 • 𝐁𝐮𝐬𝐭胸围/C • 𝐀𝐠𝐞年龄/07 .weight体重/ 49kg ✔ 女友feel.白嫩细腻.三点粉, 性格好,🉑舌吻🉑鸳鸯浴 吹箫,乖巧听话配合度高
Showing the 12 most recent of 26 posts we hold for @waiweisn66688. 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.
Forward network
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.
Mentions
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.
Cite this entry
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.
“成都外围 【网红 模特 学生】” (@waiweisn66688), 17,312 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/waiweisn66688.
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.