Telegram RegisterThe public register of Telegram
Telegram profile photo for 成都梦幻私影女仆频道

Channel

成都梦幻私影女仆频道

@mmk921

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

20subscribers

+0 since we began measuring on 25 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004492374779
TypeChannel
Username@mmk921
Description交流群链接:https://t.me/knn920 客服:@ayue1113
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 September 2026
Last confirmed live25 September 2026
Measurements held2
On Telegramt.me/mmk921

Growth

2025 Sept 2026, 14:47 — 20 subscribers25 Sept 2026, 15:22 — 20 subscribers25 Sept 2026, 14:4725 Sept 2026, 15:22
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 15:2220no change
25 Sept 2026, 14:4720first reading

Engagement

9 posts held, back to 24 September 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.

ERR · 30 days
693.8%
avg views ÷ 20 subscribers
Avg views / post
139
8 posts measured
Reaction rate
1.11%
reactions ÷ views · ER floor
Posts in window
9
of 9 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. It is computed over the 1 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 September 2026
Posts held9 (24 September 2026 – 25 September 2026)
Views total1,110
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Sept 2026, 15:22 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

Photos
20
Videos
8
Links
5

Lifetime counters from Telegram’s own channel header, read 25 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
16s
Average length
8s

Measured directly from 2 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 9 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 24 September 2026 to 25 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.

Recent posts

25 Sept 2026, 12:51 UTC90 views1 reactionsread 25 September 2026
Video

💝成都梦幻私影|体验馆💝 贵宾您好,欢迎您的到来🎉 本店妹妹年龄均为18-23岁🌸 兼职女大职场御姐,可爱萝莉,高颜女大,性感美女,全职倾心,均是一对一包间私密陪伴💋 💗本店安全保障,深度解压,甜蜜互动主打火热激情的恋爱体验让您找回初恋的感觉💗 ❗❗本店郑重承诺:❗❗ 所有妹妹真人与照片相似度达到90% 到店后发现人照不符!包来回车费! 交流群请进:https://t.me/knn920 妹妹资料频道:https://t.me/mmk921 唯一客服/:t.me/ayue1113 📍地址:锦江区春熙路商圈大熊猫对面,到了客服会引导进店 ⏰营业时间:14:00-2:00

❤1

25 Sept 2026, 11:28 UTC162 viewsread 25 September 2026
Photo

哥哥你好: 梦幻私影欢迎你的到来💋 我们店有兼职学生妹,高颜值御姐,可爱萝莉,恋爱式私影1V1陪伴 ⚜简介:我们是妹妹陪伴的私人影院,具有独立私密房间,温柔可爱的妹妹,1V1私密陪伴,可以选择妹妹服装,有女仆、超短裙,蕾丝袜…… 🔮 套餐推荐🔮 💫推荐套餐: 499/60分钟 💫外派套餐:1200/120分钟 💋服务内容:女友助教一对一陪玩游戏观影,私密空间,安全有保障,深度解压,甜蜜互动,🉑摸🦵,摸🐻 ,😙🐻,🉑亲亲🐍吻, 🉑骑乘式抱抱 ,情趣丝袜,女仆jk制服诱惑💝哥哥有什么要求可以提出来只要不过分妹妹们都可以满足哦~我们主打火热激情的恋爱体验,让您找回初恋的感觉! ❗❗本店郑重承诺:❗❗ 所有妹妹真人与照片相似度达到90%到店后发现人照不符!包来回车费! 妹妹资料频道:https://t.me/knn920 交…

25 Sept 2026, 11:15 UTC163 viewsread 25 September 2026
Photo

昵称:鹿鹿 身高体重:160cm 115 三围:D 兴趣爱好:睡觉,发呆,玩游戏,吃美食 擅长风格:甜妹,性感 服务宣言:等待和你相遇,一起制造专属我们的回忆

25 Sept 2026, 10:26 UTC154 viewsread 25 September 2026
Photo

哥哥你好: 梦幻私影欢迎你的到来💋 我们店有兼职学生妹,高颜值御姐,可爱萝莉,恋爱式私影1V1陪伴 ⚜简介:我们是妹妹陪伴的私人影院,具有独立私密房间,温柔可爱的妹妹,1V1私密陪伴,可以选择妹妹服装,有女仆、超短裙,蕾丝袜…… 🔮 套餐推荐🔮 💫推荐套餐: 499/60分钟 💫外派套餐:1200/120分钟 ❗❗本店郑重承诺:❗❗ 所有妹妹真人与照片相似度达到90%到店后发现人照不符!包来回车费! 妹妹资料频道:https://t.me/knn920 交流群请进:https://t.me/mmk921 唯一客服/:t.me/ayue1113 我们的位置:春熙路大熊猫对面到达之后客服会引导进店💋 💫群里每天都有福利抽奖活动哦~

25 Sept 2026, 10:10 UTC133 viewsread 25 September 2026
Photo

💝成都私影|体验馆💝 贵宾您好,欢迎您的到来🎉 本店妹妹年龄均为18-23岁🌸 兼职女大职场御姐,可爱萝莉 高颜女大,性感美女,全职倾心 均是一对一包间私密陪伴💋 💗本店安全保障,深度解压,甜蜜互动主打火热激情的恋爱体验让您找回初恋的感觉💗 ❗❗本店郑重承诺:❗❗ 所有妹妹真人与照片相似度达到90% 到店后发现人照不符!包来回车费! 交流群请进:https://t.me/knn920 妹妹资料频道:https://t.me/mmk921 唯一客服/:t.me/ayue1113 📍地址:锦江区春熙路商圈大熊猫对面,到了客服会引导进店 ⏰营业时间:14:00-2:00

24 Sept 2026, 18:47 UTC122 viewsread 25 September 2026
Photo

小之 刚满十八岁~ 清纯大学生挂学籍可(验 陪玩只为买更好电子设备 163。 90 自幼沐诗书雅韵,怀澄心揽山河意趣,秉温良之质,求索风雅,于岁月中沉淀才情与风骨。

24 Sept 2026, 18:46 UTC118 viewsread 25 September 2026
Photo

娃娃04 身高161体重86 胸围C 大二在读学生 娇小玲珑 五官精致 性格好 听话

Showing the 9 most recent of 9 posts we hold for @mmk921. 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.

Mentions

Named by 2 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.

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“成都梦幻私影女仆频道” (@mmk921), 20 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/mmk921.

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.