Telegram RegisterThe public register of Telegram
Telegram profile photo for 🌸猫小狐De后宫🌸

Channel

🌸猫小狐De后宫🌸

@mxh5531

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

273subscribers

+138 since we began measuring on 14 September 2026

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

Register entry

Telegram ID-1003912109007
TypeChannel
Username@mxh5531
Created11 September 2026 — measured — dated from the channel’s first post
First recorded14 September 2026
Last confirmed live29 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 29 September 2026
On Telegramt.me/mxh5531

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 29 September 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

13527320414 September 2026 — 135 subscribers14 September 2026 — 171 subscribers29 September 2026 — 273 subscribers14 September 202629 September 2026
3 measurements spanning 15 days, net +138. 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 114–294 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Sept 2026, 06:58273+102
14 Sept 2026, 17:56171+36
14 Sept 2026, 03:22135first reading

Engagement

7 posts held, back to 11 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
239.0%
avg views ÷ 273 subscribers
Avg views / post
653
6 posts measured
Reaction rate
0.111%
reactions ÷ views · ER floor
Posts in window
7
of 7 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 4 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 13 September 2026
Posts held7 (11 September 2026 – 13 September 2026)
Views total3,915
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Sept 2026, 03: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
18s
Average length
18s

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

3 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤133.3%
🔥133.3%
😁133.3%

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 4 of the 7 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 11 September 2026 to 13 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

13 Sept 2026, 16:20 UTC235 views1 reactionsread 14 September 2026

男神开心交流群报告榜 (活跃群友可信度较高) 【工兵报告】 『推荐指数:⭐️⭐️⭐️⭐️⭐️』 【日期】:9.13 【美女昵称】:猫小狐 【验证人】:guiss 【地 区 】:鄞州 【联系方式】: @ke6636 【见面感觉】:气质御姐,笑起来很邻家姐姐 【属性标签】:御姐,服务 【技术含量】:全身漫游,嘴吸 【价格 】:6p工兵 【安 全 性】:不出击最安全 【年龄】:01年 【身高】:163 【体重】:刚刚好,全身柔软 【凶器,是否假奶】:b 【肤色,手感】:手感非常滑嫩。正常色 【BB味道】:无 【三点】:略黑 【课表,特色】:全身漫游 【人照相似】:8分 【服务过程】:来到一处隐蔽的公寓,见到了心仪的狐小妖老师,见面照片上的俏皮还多了一丝气质。一番畅谈,老师来自重庆。一身白柔的连衣裙遮不住的是呼之欲出的小白兔。老师很畅谈。聊起了重庆的美食与人文。到点了,一番洗浴之后老师开始了全身漫游,舌,👄胸依次拂过全身的每一…

❤1

13 Sept 2026, 05:20 UTC666 viewsread 14 September 2026

(正式工兵报告,可信度较高。) 【工兵报告】 『推荐指数:⭐️⭐️⭐️⭐️』 【日期】:9月12日 【修车编号】:#NBTG1138 【美女昵称】:#猫小狐 【验证人】:查尔斯 【地 区 】:#鄞州 【联系方式】:@ke6636 【见面感觉】:7 【室内光线】:较暗 【属性标签】:御姐 【身材曲线】:苗条 【技术含量】:8 【价格 】:600/p(工半) 【安 全 性】:公寓 【年龄】:26左右 【身高】:161左右 【体重】:88斤左右 【凶器,是否假奶】B左右 【胸型】:馒头 【肤色,手感】:白 较滑 【B内温】:温热 【BB户型】:小蝴蝶 【BB味道】:无明显 【三点】:较粉 【课表,特色】:莞式特色 【人照相似,真人打几分】:7.5 【服务过程】: 硬件: 外表有点像是邻家娇妻 身材可以打7.5分 较小可爱型,不过手感可以 下体毛少,翘臀 体重不过百 软件: 态度热情 健谈 服务霸道 你…

13 Sept 2026, 05:19 UTC607 views0 reactionsread 14 September 2026

(正式工兵报告,可信度较高。) 【工兵报告】 『推荐指数:⭐️⭐️⭐️⭐️⭐️』 【日期】:9月12日 【修车编号】:#NBTG1138 【美女昵称】:#猫小狐 【验证人】:feng 【地 区 】:#鄞州 【联系方式】:@ke6636 【见面感觉】:8(满分10分) 【室内光线】:较暗 【属性标签】:御姐 【身材曲线】:苗条 【技术含量】:9 【价格 】:600/p(工半) 【安 全 性】:公寓 【年龄】:23左右 【身高】:161左右 【体重】:88斤左右 【凶器,是否假奶】B左右 【胸型】:馒头 【肤色,手感】:白 较滑 【B内温】:温热 【BB户型】:小蝴蝶 【BB味道】:无明显 【三点】:较粉 【课表,特色】:舌吻+课表外的吸皮过水刮痧 【人照相似,真人打几分】:7.5 【服务过程】: “本来看课表以为只是个嫩妹!没想到还是个服务系老师!” 和老师约好时间,遥控上楼,进门有点暗,老…

Showing the 7 most recent of 7 posts we hold for @mxh5531. 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 29 September 2026 — this entry's latest reading, not the date you are reading this.

“🌸猫小狐De后宫🌸” (@mxh5531), 273 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/mxh5531.

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.