不小心把安慕希弄腿上啦😏 💌私聊客服 📕双向限制 🍓聊天大群 🍩女仆总览

Channel
昆明奶芙萌屋恋爱桌游
@naifu668866
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,898subscribers
+1,093 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002814148965 |
|---|---|
| Type | Channel |
| Username | @naifu668866 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/naifu668866 |
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 14 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 |
|---|---|---|
| 15 Sept 2026, 22:41 | 2,898 | -542 |
| 11 Sept 2026, 21:40 | 3,440 | -393 |
| 7 Sept 2026, 05:37 | 3,833 | +913 |
| 2 Sept 2026, 11:05 | 2,920 | -59 |
| 30 Aug 2026, 05:44 | 2,979 | +516 |
| 26 Aug 2026, 21:54 | 2,463 | +23 |
| 24 Aug 2026, 02:54 | 2,440 | +51 |
| 20 Aug 2026, 10:22 | 2,389 | +30 |
| 17 Aug 2026, 17:03 | 2,359 | +512 |
| 14 Aug 2026, 10:25 | 1,847 | +15 |
| 11 Aug 2026, 09:15 | 1,832 | +24 |
| 8 Aug 2026, 09:08 | 1,808 | +3 |
| 7 Aug 2026, 20:48 | 1,805 | no change |
| 7 Aug 2026, 19:00 | 1,805 | first reading |
Engagement
19 posts held, back to 16 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 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 19 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 05s
- Average length
- 13s
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.
Reaction mix
6 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 83.3% | |
| 😁 | 1 | 16.7% |
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 9 of the 19 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 16 July 2026 to 7 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
降价啦哥哥们,这是本店新套餐哦,服务不打折😏😏
听说你们都喜欢这种💕💕💕 💌私聊客服 📕双向限制 🍓聊天大群 🍩女仆总览
❤️云南昆明司机加油站报告❤️ 9分以上为优质,8分以上为中等,7分以下为差超过2次下架黑榜处理! 【时间】:2026-08-05 【老师】: 奶芙女仆MMK 【评价人】:匿名用户 【人照】:10 【颜值】:10 【身材】:9 【服务】:9 【态度】:10 【环境】:8 【综合评分】:9.33 【过程描述】:看到群友们反馈的 mmk,也是立刻出发了,因为昆明的 mmk 实在烂得一塌糊涂,经常吃屎,跟客服小姐姐约好以后到了目的地果真像群友说的那种,要经过两道门禁,安全方面做得不错,这样玩着安心,然后环境就是普通公寓环境,接待的小哥说后期会升级环境等等的,不重要,接下来就是选人环节,一眼看中了人群中的婵婵,长得有御姐又可爱,很合我的口味,全程不冷场,没给满分的原因就是小姐姐舌吻一会就要喘,我本身喜欢大蟒蛇,总之妹妹不错很听话,细节做的很到位,打完飞机卫生处理这一块也很细心,不会像之前别的一打出来就一股嫌弃的样子,走之前还给我送到电梯…
现在都喜欢这么玩吗💕💕💕 💌私聊客服 📕双向限制 🍓聊天大群 🍩女仆总览
帮你撕下标签🤍🤍 💌私聊客服 📕双向限制 🍓聊天大群 🍩女仆总览
❤2
❤️云南昆明司机加油站报告❤️ 9分以上为优质,8分以上为中等,7分以下为差超过2次下架黑榜处理! 【时间】:2026-08-01 【老师】: 奶芙女仆MMK 【评价人】:花开富贵 【人照】:9 【颜值】:10 【身材】:9 【服务】:10 【态度】:10 【环境】:8 【综合评分】:9.33 【过程描述】:各方面都很好,美中不足的就是店铺环境我不是很喜欢,这是我个人原因,有一点洁癖;果断选好妹妹带去附近酒店上钟,两个人躺在床上,妹妹香香软软的,身上味道很好闻,穿着jk和肉丝更是性张力拉满,不一会我的铁棍就坚硬如铁,让妹妹给我打了出来,妹妹服务很给力,颜值也很顶,希望店铺环境改进一下
❤️云南昆明司机加油站报告❤️ 9分以上为优质,8分以上为中等,7分以下为差超过2次下架黑榜处理! 【时间】:2026-07-31 【老师】: 奶芙女仆MMK 【评价人】:vvxz 【人照】:9 【颜值】:9 【身材】:9 【服务】:9 【态度】:10 【环境】:7 【综合评分】:8.83 【过程描述】:看到有新店铺,也顾不上那么多,到店看吧,毕竟也是个 mmk 老客户了,别的店铺妹子也基本玩个遍了,还没到店就震惊到我了,需要门禁才能过去,就在我刚进去第一道门禁,第二道门禁又出现了,咱就是说虽然安全第一,这也太安全了点,然后到了以后就是一系列流程,寒暄几句选妹子,一眼看中了婵婵,有点御姐又有点可爱,穿着一身白裙子,很有初恋的感觉,全程服务也很主动,飞机手法也没有不舒服,总之店铺安全有保障,妹子有很多,后面我慢慢探索
此刻万事俱备,只差你啦🤍🤍 💌私聊客服 📕双向限制 🍓聊天大群 🍩女仆总览
https://t.me/kmds_1 本群新建群组,免费上榜,需要互推一下,把链接发到你频道
😁1
🙋🏻♀️ 奶芙女仆MMK #km37 ☎️联系方式: @wuhannaifu 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: # 所在区域:#官渡,官渡区 🏷️分类标签 #角色扮演,制服,会所,MMK,情趣丝袜,商家榜,舌吻,92,丝足,足交 💌评价奶芙女仆MMK 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
❤2
此刻万事俱备,只差你啦🤍🤍 💌私聊客服 📕双向限制 🍓聊天大群 🍩女仆总览
Showing the 12 most recent of 19 posts we hold for @naifu668866. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“昆明奶芙萌屋恋爱桌游” (@naifu668866), 2,898 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/naifu668866.
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.