再开几天就要红休了!🥵哥哥们提前预约!自聊回复不及时😭
❤1

Channel
@paofuaichao111
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,556subscribers
+354 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003847225812 |
|---|---|
| Type | Channel |
| Username | @paofuaichao111 |
| Created | Between 1 February 2026 and 18 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/paofuaichao111 |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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, 06:36 | 2,556 | +84 |
| 14 Sept 2026, 15:01 | 2,472 | +1 |
| 11 Sept 2026, 11:21 | 2,471 | +56 |
| 6 Sept 2026, 20:39 | 2,415 | +6 |
| 30 Aug 2026, 06:56 | 2,409 | -15 |
| 27 Aug 2026, 13:12 | 2,424 | +19 |
| 24 Aug 2026, 08:24 | 2,405 | +51 |
| 20 Aug 2026, 12:58 | 2,354 | +159 |
| 17 Aug 2026, 19:38 | 2,195 | -5 |
| 14 Aug 2026, 09:49 | 2,200 | -19 |
| 10 Aug 2026, 15:08 | 2,219 | +18 |
| 7 Aug 2026, 12:00 | 2,201 | -1 |
| 6 Aug 2026, 20:33 | 2,202 | first reading |
15 posts held, back to 18 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 2 pages 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 15 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
17 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 94.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 94.1% | |
| 👍 | 1 | 5.88% |
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 10 of the 15 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 18 July 2026 to 28 July 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
(小泡芙的江景房)对着东方明珠干我 pinned Deleted message
Video, posted without a caption
❤3👍1
【时间】:2026-07-25 【老师】:小泡芙(自聊版) 【评价人】:匿名用户 【颜值评分】:9 【人照评分】:10 【身材评分】:9 【科室环境】:10 【服务评分】:10 【态度评分】:10 【出击金额】:p1000 【推荐指数】:⭐⭐⭐⭐⭐ 【约课记录】: 【服务过程】人照10分,参考视频一模一样,混血小美女,美术生毕业,有学生气,青春活力;很能聊天,平时还看书,嗲纯反文静型御姐,声音嗲嗲的,黄白皮偏白,皮肤软很顺滑,C奶,沙漏身材,曲线不错,视觉效果完美,腰两侧无赘肉;有腰窝,大宽臀,手感很好,很翘,会主动亲,会主动抱着你,叫床也不是那种假叫;骚话也有;水越干越多,姿势配合;女上会跪坐,可要求舌吻,会对视,眼中有欲望,有反差感。换姿势配合,后入屁股大过肩,会下腰,双手互动多,叫床声好听,偶尔会有骚话。课室环境好,楼下随意进出没有保安,没有监控摄像头,一层楼多户很安全,观景房可以看到东方明珠塔,卧室天花板有镜子,做爱像看…
Video, posted without a caption
上海艺术展览会报告模板: https://t.me/+nFnE0wANtSRkMjEx 【体验评分】:9 【人照几成】:9 【验证留名】:@Lustful_Kumamon 【验证时间】:7.21 【妹子艺名】:小泡芙 【联系方式】:@x_paofu520 【所在位置】:虹口 【上课水费】:p 【身材描述】:人工白虎,粉嫩酥胸 【凶器罩杯】:c 【服务类型】: 舌吻共浴轻sm等 【服务态度】:玩的开放的开 【优点缺点】:偏m,很骚,敏感水多 【整体补充】: 雨声淅沥,我推门进入房间,她已微笑迎接。服务从共浴开始,她认真细致地帮我冲洗全身,动作温柔耐心。之后进入轻SM环节,用丝巾轻绑我双手,温柔鞭打翘臀,那种被掌控的刺激感让人血脉贲张。 她颜值9分,大眼睛水灵灵,少数民族异域风情,163cm前凸后翘,黄白嫩肤,C杯软软脂肪胸手感爆棚,吃起来甜美可口,嗲嗲夹子音特别撩人。口活一流,牙齿舌头口腔慢慢摩擦,舔蛋蛋、深喉湿热吸吮,欲仙欲…
❤5
课表和课室环境 江景情趣大床房 天花板有镜子
(小泡芙的江景房)对着东方明珠干我 pinned Deleted message
【嫩妹社报告】https://t.me/+u-GY30ilDX4xYjJh 【所在位置】虹口 【老师艺名】小泡芙 【联系方式】@x_paofu520 【老师类型】嫩妹 【验证留名】nihility 【验证时间】2026.7.21 【上课价位】工兵p 【颜值身材】颜值9 身材9 【服务内容】yyy 三点口 做 【服务态度】嗲嗲的嫩妹,服务态度蛮好的 【优点缺点】工作室太有特色了,混血感,人照10,一般要求都满足,不机车,没啥可说道的缺点 【推荐程度】9 推荐9-10分 一般7-8分 差评1-5分 【体验细节】拍卖抢到了工兵p,约课上门,工作室和东方明珠隔了一天河,安全隐蔽,停车可以在对面大厦停。 遥控上门,老师披着睡袍,眼睛很大,颜值不错,人照一致,就是频道的样子,原以为整过,但实际没整容痕迹。个子娇小,小萝莉身材御姐脸,声音嗲嗲的。 坐在沙发上休息了一下,老师直接贴过来舌吻,睡袍一打开,全真空,摸了几下就硬邦邦了,交了水费…
❤2
Video, posted without a caption
❤2
💃艺名:小泡芙 ✈️资料:https://t.me/shxyls/27104 ⛳️位置: #虹口区 🙍♂️学生:瑞瑞芮 ———————————————— 和老师约了好几次了,可惜都因为时间冲突没有成行,今天终于碰好时间,虽然最近出货比较多状态不是最佳,还是决定不能再拖了。老天爷也给面子,我到了科室刚好开始打雷下暴雨,本来老师科室就藏在繁华闹市比较隐蔽,这一下雨更安全了。科室不难找,一进门就被一张精致的脸迎了上来,人照十分,赞的。沉溺在老师的夹子音里面,帮洗很用心,感觉自己一直被照顾。随后的流程老师都很听话,技巧也不错。本人比较喜欢掌握主动,所以泡芙老师还在卖力服务,我就直接翻身上马,变换了几个姿势后123结束,老师叫着爸爸确实撩人。意犹未尽,老师送到门外,约好下次再来。
(小泡芙的江景房)对着东方明珠干我 pinned Deleted message
Showing the 12 most recent of 15 posts we hold for @paofuaichao111. 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 15 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.
“混血美术生奶油泡芙的朋友圈” (@paofuaichao111), 2,556 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/paofuaichao111.
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.