Telegram RegisterThe public register of Telegram
Telegram profile photo for 悠米成都私影_mmk

Channel

悠米成都私影_mmk

@yunmeng_mmk

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

418subscribers

+15 since we began measuring on 5 November 2026

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

Register entry

Telegram ID-1004460983639
TypeChannel
Username@yunmeng_mmk
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 November 2026
Last confirmed live6 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/yunmeng_mmk

Growth

403418410.55 Nov 2026, 17:22 — 403 subscribers6 Nov 2026, 06:26 — 418 subscribers5 Nov 2026, 17:226 Nov 2026, 06:26
2 measurements taken within a single day, net +15. 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 401–420 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 06:26418+15
5 Nov 2026, 17:22403first reading

Engagement

6 posts held, back to 28 October 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
130.1%
avg views ÷ 418 subscribers
Avg views / post
544
6 posts measured
Reaction rate
0.264%
reactions ÷ views · ER floor
Posts in window
6
of 6 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 2 of 6 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 5 November 2026
Posts held6 (28 October 2026 – 5 November 2026)
Views total3,264
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 17: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

Video runtime
20s
Average length
10s

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

4 reactions across 2 posts, in 1 kind.

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

Measured over the 6 most recent posts we hold, published 28 October 2026 to 5 November 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

Telegram’s own ‘edited’ marker: 0 of 6 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 08:10 UTC217 viewsread 5 November 2026
Photo

近期限时返场预告: 😈小铃 05年 167cm 44kg 大学生 ,温柔听话,可甜可御,白瘦高,大长腿,小蛮腰,真实无高p无网图

Signed 烟花要绽放在黑夜

5 Nov 2026, 08:00 UTC216 viewsread 5 November 2026
Photo

近期新人妹妹预告: 😍厌冬 165 90 B➕ 极度挑食、爱追点脑残网剧、爱玩游戏:金铲铲 打瓦

Signed 烟花要绽放在黑夜

4 Nov 2026, 10:00 UTC426 views1 reactionsread 5 November 2026

抽奖成都悠米-私影高颜值mmk活动来袭(编号L179354060467)已成功开奖: 创建人:💎清欢💎[6957672512] 已参与人数:77 中奖名单如下: 放牛*[6863158**](奖品为悠米私影优惠券50) 打飞老师*[7364346**](奖品为悠米私影优惠券50) sunshin*[11858372**](奖品为悠米私影优惠券50) M*[18348088**](奖品为工兵350体验券) 伊*[58222842**](奖品为悠米私影优惠券50) 纯爱战*[59323946**](奖品为悠米私影白嫖券) insan*[63481842**](奖品为悠米私影优惠券100) Th*[71262474**](奖品为工兵350体验券) Itachi*[73967801**](奖品为悠米私影优惠券50) Riddle*[84424087**](奖品为悠米私影优惠券100) Rachma63*[85632449**](奖品为悠…

❤1

Signed ✨超级幸运星🥁

3 Nov 2026, 14:18 UTC527 viewsread 5 November 2026
Photo

🎰 悠米私影新店福利送白嫖啦 📮 参与条件: 🎫 加入-悠米成都私影_mmk 🎫 加入-悠米_成都私影 恋爱体验馆 └ 🔑 发送口令﹝悠米私影新店福利送白嫖啦﹞ 🎫 加入-BBW成都群🧸[大胸大屁股万岁] └ 🔑 发送口令﹝悠米私影新店福利送白嫖啦﹞ 🎫 加入-成都大白菜出击指南 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ bbw群积分500 × 8 💰️ 悠米私影100元优惠券 × 2 💰️ 悠米私影50元优惠券 × 8 💰️ 悠米私影工兵350元体验券 × 2 💰️ 悠米私影白嫖券 × 1 ⚠️ 抽奖说明: 1.中奖后需要在开奖后72时内找兑奖人兑奖,超时均不予兑奖。 2.奖品均只能本人领取和使用,不可转让不可买卖; 3.所有的优惠券,白嫖券需要在领取后一周内出击使用,逾期则失效。 4、成都bbw群积分领取请联系 @fuhuodbc 🔋 人品加成:⚡️× 9 规则 📅 开奖日…

Signed LotteryBest Bot

1 Nov 2026, 15:31 UTC788 viewsread 5 November 2026
Photo

🥁活动主题:成都悠米-私影高颜值mmk活动来袭 🎖️参与条件: 🎫 加入-成都欢乐星期⑧推荐官 🎫 加入-悠米_成都私影 恋爱体验馆 🎫 加入-悠米成都私影_mmk 🎁 奖品内容: 💰️ 悠米私影优惠券50 × 8 💰️ 悠米私影优惠券100 × 2 💰️ 工兵350体验券 × 2 💰️ 悠米私影白嫖券 × 1 📃活动说明:中奖后请及时联系兑换 💬兑奖联系:@xm2373 📌服务介绍:点击预览 兑奖截止开奖后7天内有效,过期不补。 📅 开奖时间:2026-11-04 18:00自动开奖 🎉🎉祝您幸运常伴🎉🎉

Signed ✨超级幸运星🥁

28 Oct 2026, 10:36 UTC≈1,090 views3 reactionsread 5 November 2026
Photo

奶茶 06年160/95 胸C+,不照骗,真人比照片好看 在校大学生,甜美可爱,性格好服务好,情绪价值高

❤3

Showing the 6 most recent of 6 posts we hold for @yunmeng_mmk. 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 1 registered channel — 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.

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

“悠米成都私影_mmk” (@yunmeng_mmk), 418 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/yunmeng_mmk.

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.