Channel
@Mushu8899
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
374subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003040545321 |
|---|---|
| Type | Channel |
| Username | @Mushu8899 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/Mushu8899 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 18:10 | 374 | +5 |
| 8 Aug 2026, 06:20 | 369 | no change |
| 7 Aug 2026, 18:30 | 369 | first reading |
12 posts held, back to 7 June 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 pageof Telegram’s post history, 20 posts per page.
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 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 12 (7 June 2026 – 27 July 2026) |
| Views total | 1,270 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:20 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.
Measured directly from 3 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.
10 reactions across 6 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 100.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 6 of the 12 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 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 7 June 2026 to 27 July 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.
「#惠城高端实体店会所」 只做惠城高端实体店会所，安全可靠，不忽悠，不发假图，惠城找会所认准洛甜足矣，别人的价格可能比我便宜，频道假图比我的更诱惑，但是阿健始终不忘初心，坚持走真实路线，用真诚对待每一位客人。 📱项目内容， 陪伴洗澡 🔥按摩放松🔥指尖调情🔥舌尖调情🔥舌尖环游🔥胸推全身🔥半裸服务🔥刮痧过水🔥高山流水🔥舔蛋蛋🔥舔奶头🔥果冻毒龙🔥猴子偷桃🔥上下可摸，时间内可起飞两次 📱价格：（每家店价格不同） 🥰🥰手出/足交🥰🥰🥰至🥰🥰🥰元 ， 🥰🥰胸出🥰🥰🥰元至🥰🥰🥰， 全程一对一私密服务🥰🥰分钟。（瑶浴泡澡加50元） 惠城最靠谱频道，只做高端实体店，店铺资料最真实最前面，以下是各分店资料频道，欢迎订阅。 🔥麦地店（沐夕） @muxispa 此店性价比高，技师颜值高，极品少妇多，服务好，环境好，回头率高， 🔥旗舰店（汝梦） @Mushu8899 此店比其他店价格贵一点，主打零零后嫩妹，环境高端，技师年轻，惠城颜值天花板，应…
❤3
[#惠州会所 #零零后 #童颜巨乳 ] 红牌预约直通车，添加技师微信，直接预约，高效预约不等待 昵称： 兜儿 工号： 521 身高： 160 真胸： D 年龄： 24 特色项目 收费1: 👍👍👍元（艾草牛奶泡澡另加👍👍元），70分钟 服务类型：精品顶级94 时间内可出水2次（2次需提前说明） 可选 ✋ 🐻 🦵 🦶 四推出水方式 课程内容包含： 小姐姐帮忙洗澡，浴缸泡澡，十指弹琴，比翼双飞，柔情似水，高山流水，花式毒龙，刮痧过水，波推，全身调情，舌尖环游全身，舔蛋吸蛋，猴子偷桃，上下可摸，与身体激情碰撞。 热门项目 收费1: 👍👍👍（艾草牛奶泡澡加👍👍）70分钟 课程内容包含： 美女帮冲凉搓澡，十指弹琴，真胸调情，高山流水，果冻毒龙，丝足诱惑可撕，胸推全身，舔蛋亲奶，猴子偷桃，上下可摸， 私信： @nrmo521 朋友圈： @Dedpyq521 本人微信： S329448089 (添加微信备注纸飞…
#惠州会所 ，#清纯嫩妹 #零零后 红牌预约直通车，添加技师微信，直接预约，高效预约不等待 昵称： 小不点（888号） 身高： 160 真胸： B 年龄： 23 特色项目 收费1: 👍👍👍元（艾草牛奶泡澡另加👍👍元），70分钟 服务类型：精品顶级94 时间内可出水2次（2次需提前说明） 可选 ✋ 🐻 🦵 🦶 四推出水方式 课程内容包含： 小姐姐帮忙洗澡，浴缸泡澡，十指弹琴，比翼双飞，柔情似水，高山流水，花式毒龙，刮痧过水，波推，全身调情，舌尖环游全身，舔蛋吸蛋，猴子偷桃，上下可摸，与身体激情碰撞。 热门项目 收费1: 👍👍👍（艾草牛奶泡澡加👍👍）70分钟 课程内容包含： 美女帮冲凉搓澡，十指弹琴，真胸调情，高山流水，果冻毒龙，丝足诱惑可撕，胸推全身，舔蛋亲奶，猴子偷桃，上下可摸， 私信： @Xiaobdu888 朋友圈： https://t.me/xbudian 本人微信： Gaosa558800…
#惠州会所， 洛甜旗舰店 #大长腿 #零零后 #嫩妹 红牌预约直通车 扫码添加技师微信 预约直通车，不排不等 昵称： 乖乖 （666号） 身高： 170 真胸： B 年龄： 24 特色项目 收费1: 👍👍👍元（艾草牛奶泡澡另加👍👍元），70分钟 服务类型：精品顶级94 时间内可出水2次（2次需提前说明） 可选 ✋ 🐻 🦵 🦶 四推出水方式 课程内容包含： 小姐姐帮忙洗澡，浴缸泡澡，十指弹琴，比翼双飞，柔情似水，高山流水，花式毒龙，刮痧过水，波推，全身调情，舌尖环游全身，舔蛋吸蛋，猴子偷桃，上下可摸，与身体激情碰撞。 热门项目 收费1: 👍👍👍（艾草牛奶泡澡加👍👍）70分钟 课程内容包含： 美女帮冲凉搓澡，十指弹琴，真胸调情，高山流水，果冻毒龙，丝足诱惑可撕，胸推全身，舔蛋亲奶，猴子偷桃，上下可摸， 私信： @Ggdxm666 朋友圈： @Ggdpyq666 本人微信： w04852 (…
📱📱📱📱 #河南岸 #帝景店 521号 服务内容92/94 年轻漂亮零零后 肤白貌美，波涛汹涌 服务好 放得开 在岗时间，晚上7点半至凌晨五点
❤1
📱📱📱📱 「#惠州惠城 #河南岸 857号」 服务内容92 身高： 160 体重： 98 胸：C 在岗时间中午2点至凌晨二点
❤2
📱📱📱📱 #惠城区 #河南岸 866号 服务内容 92 在岗时间晚上七点至凌晨五点
❤1
📱📱📱📱 #惠城 #河南岸 833号 服务内容92 在岗时间晚上七点至凌晨五点
😀😀😀😀 #河南岸帝景店 #888号 服务内容92 身高: 162 体重：90 胸 B 在岗时间晚上七点至凌晨五点
❤1
📱📱📱📱 #河南岸 #帝景店 521号 服务内容92/94 年轻漂亮零零后 肤白貌美，波涛汹涌 欢迎预约 在岗时间，晚上7点半至凌晨五点
❤2
😀😀😀😀 #河南岸帝景店 #222号 服务内容92/94 身高: 165 体重：98 胸 B+ 在岗时间中午12点至凌晨12点
😀😀😀😀 #河南岸帝景店 #333号 服务内容92/94 身高:167 体重：96 胸：B 在岗时间中午12点至晚上六点
Showing the 12 most recent of 12 posts we hold for @Mushu8899. 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 — 322,671 of 1,478,351entries 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.
Named by 7 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“惠城旗舰店（汝梦SPA）真实照片” (@Mushu8899), 374 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Mushu8899.
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.