露露吃饱了 AI脱衣 抖音 网红 #露露吃饱了 #AI脱衣 脱衣裸舞 2v 📱 在评论区看视频 ⤵️
❤1

Channel
@quyige
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
12,126subscribers
+8,771 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003171025594 |
|---|---|
| Type | Channel |
| Username | @quyige |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/quyige |
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 98% 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, 04:17 | 12,126 | -672 |
| 16 Sept 2026, 20:41 | 12,798 | -463 |
| 14 Sept 2026, 23:17 | 13,261 | -405 |
| 13 Sept 2026, 11:59 | 13,666 | -544 |
| 11 Sept 2026, 12:38 | 14,210 | -566 |
| 8 Sept 2026, 17:35 | 14,776 | +125 |
| 5 Sept 2026, 14:16 | 14,651 | +92 |
| 3 Sept 2026, 17:22 | 14,559 | +65 |
| 2 Sept 2026, 10:45 | 14,494 | +37 |
| 1 Sept 2026, 11:23 | 14,457 | +34 |
| 31 Aug 2026, 13:24 | 14,423 | +44 |
| 30 Aug 2026, 11:45 | 14,379 | +52 |
| 29 Aug 2026, 11:57 | 14,327 | +51 |
| 28 Aug 2026, 10:56 | 14,276 | +57 |
| 27 Aug 2026, 10:57 | 14,219 | +51 |
| 26 Aug 2026, 10:53 | 14,168 | +71 |
| 25 Aug 2026, 07:58 | 14,097 | +51 |
| 24 Aug 2026, 07:04 | 14,046 | +108 |
| 22 Aug 2026, 12:13 | 13,938 | +67 |
| 20 Aug 2026, 23:05 | 13,871 | first reading |
38 posts held, back to 29 July 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 41 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 9 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 38 (29 July 2026 – 2 September 2026) |
| Views total | 33,981 |
| Reactions total | 31 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18:35 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 19 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.
85 reactions across 31 posts, in 3 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 79 | 92.9% | |
| 👍 | 4 | 4.71% | |
| 👏 | 2 | 2.35% |
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 33 of the 38 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 85 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 29 July 2026 to 2 September 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.
露露吃饱了 AI脱衣 抖音 网红 #露露吃饱了 #AI脱衣 脱衣裸舞 2v 📱 在评论区看视频 ⤵️
❤1
又耳少女Bella AI脱衣 抖音 网红 #又耳少女Bella #AI脱衣 脱衣裸舞 📱 在评论区看视频 ⤵️
无敌橙子 AI脱衣 抖音 网红 #无敌橙子 #AI脱衣 脱衣裸舞 2v 📱 在评论区看视频 ⤵️
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7696518386
郑想吃糖 ke08 AI脱衣 抖音 网红 #郑想吃糖 #ke08 #AI脱衣 视频裸舞 📱 在评论区看视频 ⤵️
❤2
独留 AI脱衣 抖音 网红 #独留 #AI脱衣 视频裸舞 2v 📱 在评论区看视频 ⤵️
❤3👍2
我不叫龙虾 AI脱衣 抖音 网红 #我不叫龙虾 #AI脱衣 视频裸舞 2v 📱 在评论区看视频 ⤵️
❤6
wang唐唐 AI脱衣 抖音 网红 #wang唐唐 #AI脱衣 视频裸舞 2v 📱 在评论区看视频 ⤵️
❤3
😳🥵🙁 AI成人短剧资源整合包|低价开放 把分散在各处的资源,一次性整理给你。 我们对市面上的付费、热门AI成人短剧相关资源进行了系统 整理与筛选,集中打包,省去你到处寻找、反复筛选的时间。 📱 会员权益· 会员期内免费看 🏟 会员期限内不限次数观看 🏟 会员资源库全部开放 🏟 持续整理与更新 🏟 多类型 AI 短剧资源分类 🏟 低价会员,降低观看成本 🏟 开通后即可使用会员权益 😛 为什么选择我们? 不需要让你花大量时间到处找资源,帮你把资源集中整理好。 市面上资源分散、质量参差不齐,自己寻找往往需要花费大量时间。 我们负责整理、筛选、分类,你只需要选择适合自己的版本即可。 🎁 首期开售价格更低 后续会根据资源规模与更新内容进行调整。 #AI短剧 #成人短剧 #AI成人短剧 ⬇️ 点击下方机器人观看 ⬇️
👍2❤1
糖醋里脊本脊 AI脱衣 抖音 网红 #糖醋里脊本脊 #AI脱衣 视频裸舞 2v 📱 在评论区看视频 ⤵️
❤3
诗恩恩 AI脱衣 抖音 网红 #诗恩恩 #AI脱衣 口交 后入 6v 📱 在评论区看视频 ⤵️
❤4
西瓜冰a AI脱衣 抖音 网红 #西瓜冰a #AI脱衣 口交 插穴 裸舞 9v 📱 在评论区看视频 ⤵️
❤4
Showing the 12 most recent of 38 posts we hold for @quyige. 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.
@quyige edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 4 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.
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.
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.
“去衣哥 明星网红AI脱衣” (@quyige), 12,126 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/quyige.
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.