Telegram RegisterThe public register of Telegram

Channel

梦馨小屋

@mengxinxwu

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

302subscribers

+1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003987289463
TypeChannel
Username@mengxinxwu
CreatedBetween 1 April 2026 and 17 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/mengxinxwu

Growth

301302301.512 Aug 2026, 22:58 — 301 subscribers12 Aug 2026, 23:00 — 301 subscribers13 Aug 2026, 03:19 — 302 subscribers12 Aug 2026, 22:5813 Aug 2026, 03:19
3 measurements taken within a single day, net +1. 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 301–302 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:19302+1
12 Aug 2026, 23:00301no change
12 Aug 2026, 22:58301first reading

Engagement

19 posts held, back to 17 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
237.6%
avg views ÷ 302 subscribers
Avg views / post
718
18 posts measured
Reaction rate
0.104%
reactions ÷ views · ER floor
Posts in window
19
of 19 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 18 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 12 August 2026
Posts held19 (17 July 202612 August 2026)
Views total12,915
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 23:00 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
14s
Average length
14s

Measured directly from 1 video 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

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.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 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 2reactions 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 17 July 2026 to 12 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

10 Aug 2026, 12:17 UTC274 viewsread 12 August 2026

哥哥们好久不见明天回郑州啦 现在可以提前预约啦

21 Jul 2026, 14:12 UTC991 viewsread 12 August 2026

哥哥们妹妹我来这里两个星期了马上也快红休了回家了 为了感谢哥哥们的支持现在特价夜1600可约 仅限今天和明天 @meng00xin 双向 @xiaox1x1_bot

21 Jul 2026, 10:08 UTC≈1,010 views1 reactionsread 12 August 2026
Photo

哥哥们喜欢胸大的可以找妹妹来约啦 @meng00xin 双向 @xiaox1x1_bot

1

21 Jul 2026, 05:23 UTC944 viewsread 12 August 2026

哥哥们马上快红休了 要来约课的抓紧来约哦 @meng00xin 双向 @xiaox1x1_bot

19 Jul 2026, 11:13 UTC912 viewsread 12 August 2026
Forwarded from @zzclbgPhoto

【时间】:2026-07-19 【老师】:馨儿 【留名】:匿名 【人照】:8 【颜值】:8 【身材】:8 【服务】:8 【态度】:10 【环境】:8 【综合】:8.33 【过程】:照片是本人,验证过是真🐻,看起来就是刚做没多久的,比较腼腆,业务不是特别熟练,好在比较听话,需要有大神再来调教,总之这个价位的嫩妹还是很划算的,有想玩的狼友可以冲了! 优点:听话,不催,bbw的身材很棒,💦很多 缺点:教室浴室小,老师也没陪浴

19 Jul 2026, 08:33 UTC746 viewsread 12 August 2026
Forwarded from @zzclbgPhoto

【时间】:2026-07-19 【老师】:馨儿 【留名】:匿名 【人照】:9 【颜值】:8.5 【身材】:8 【服务】:8 【态度】:9 【环境】:8 【综合】:8.42 【过程】:拿下老师的工兵之后就跟老师约时间。最后确定了一个很晚的时间。老师的位置很好找,交通也方便,就是公寓,可能安全性有点差。见面之后,跟照片很像。只有部分美颜瘦脸。但是很好看,也确实是嫩妹。洗澡之后,看到老师身材,肉肉的,但不算胖。胸大屁股大,笑起来很好看。过程不细表,课表有的都有。过程也很配合,态度不错。整个做完之后,很舒服。以后可能会二刷。

Showing the 12 most recent of 19 posts we hold for @mengxinxwu. 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.

Citation-graph rank

Citation-graph rank — 1,132,484 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“梦馨小屋” (@mengxinxwu), 302 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/mengxinxwu.

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.