Telegram RegisterThe public register of Telegram
Telegram profile photo for 月月

Channel

月月

@moonlight_yueyue

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

20subscribers

+4 since we began measuring on 21 August 2026

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

Register entry

Telegram ID-1003629514552
TypeChannel
Username@moonlight_yueyue
CreatedBetween 1 December 2025 and 12 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live5 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/moonlight_yueyue

Growth

16201821 August 2026 — 16 subscribers22 August 2026 — 16 subscribers5 September 2026 — 20 subscribers21 August 20265 September 2026
3 measurements spanning 15 days, net +4. 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 15–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 13:4020+4
22 Aug 2026, 14:4616no change
21 Aug 2026, 23:0216first reading

Engagement

9 posts held, back to 12 January 2026the 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
no view readings in window
Avg views / post
no view readings
Reaction rate
this channel exposes no reaction counts
Posts in window
1
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held9 (12 January 202614 August 2026)
Views total
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Aug 2026, 23:02 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
49s
Average length
10s

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.

Recent posts

12 Jul 2026, 06:32 UTC846 viewsread 21 August 2026
Photo

#月月 ▶️测评 18岁大一顶颜甜妹~ 🏆青春荷尔蒙爆棚,爱不释手! 🌹店花🌹集万千宠爱于一身 ➡️聊天群 ➡️客服1 ➡️客服2 双向机器人 ➡️ @ygtl_bot

6 May 2026, 07:22 UTC905 viewsread 21 August 2026
Forwarded from @yuxi9258Photo

#月月 无敌甜妹,各种好 客人主动给好评~~

5 May 2026, 09:32 UTC958 views0 reactionsread 21 August 2026
Photo

#月月 超甜超甜青春洋溢甜妹 T1班花级,百分百真人真照~~

15 Mar 2026, 06:08 UTC≈1,330 viewsread 21 August 2026
Forwarded from @yuxi9258Photo

【妹子花名】:#月月 【妹子年龄】:18 【所属店铺】:#月光逃离 【验证留名】:阿虹 【验证时间】:3月15日 【大概位置】:中南未来里 【人照相似】:人照九分相,可爱精致 【身高身材】:160,细腰,屁股圆润有肉,手足纤细精巧 【凶器罩杯】:B- 【个人标签】:带点异域风的甜妹 【环境细节】:干净整洁无异味 【个人爱好】:应该不抽烟,没问,反正没有烟味,无纹身 【推荐程度】:9分 【流程小文】:进门时穿着jk的妹妹已经在房间等我,将撕好的漱口水递给我,我吐完漱口水又贴心的递上纸巾,是个懂事的好妹妹。仔细端详妹妹面庞,眼睛很有灵气,有点新疆人的感觉,活脱标准甜妹,惹人怜爱。手和脚非常好看,腰非常细,胸有个B-吧,屁股有肉很好摸。十分能聊,配合度很高很乖,总之就是好妹妹的感觉,不抽烟无纹身,挑不出毛病。

12 Jan 2026, 08:12 UTC≈1,630 views0 reactionsread 21 August 2026
Forwarded from @xinmenbangVideo

编号:30 女仆:月月 店铺:月光逃离 https://t.me/yuxi00788 客服: @hzMoonFlight 星级:五星plus 属性:甜妹! 所属系列:西施系 评语:月月,完全符合对于甜美型妹妹的想象,实在是太甜,太甜了!下沙大一学生,聊天中,感觉的出来是个爱学习的小妹妹。亲吻和舔🐻的时候,很投入,很享受,皮肤白而滑。尝试了一下,属于标大系。毕竟太甜美了,标大也不缺单子的妹妹。按照之前的评价标准给出五星plus的好评,现在流行的标准等于T1前水平。 ps:妹妹要期末考试了,就下周五和周末在。

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

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 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.

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

“月月” (@moonlight_yueyue), 20 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/moonlight_yueyue.

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.