Engagement
4 posts held, back to 30 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
- 0.168%
- avg views ÷ 594 subscribers
- Avg views / post
- 1.0
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 4 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.
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.
Recent posts
1 Oct 2026, 00:30 UTC1 viewsread 1 October 2026 Photo
编号:2609274466 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
:691
省份:山西
城市:太原
职业: 前台
年龄:24
身高:161
体重:85
罩杯:b
是否Chu女: 否
是否接受SM: 轻微
金主体检后是否接受无t: 是
是否接受内: 否
是否接受口: 是
是否接受同居: 否
是否接受过夜: 是
是否接受外地: 协商
每月姨妈时间及天数: 月下旬
绝对禁忌的事项: 脾气暴躁
对金主的要求: 身体健康 正常友善
找金主的原因: 多赚钱
对恋爱费用的预期: 3000
恋爱费分次支付能否接受:接受
每个月可陪伴的天数: 2天
自我评价: 情绪稳定 听话 性格还可以 接受无套 性价比
介绍费: 7888 as
联系客服:小熙
联系客服:小甜
联系客服:小萌
【便捷选妃-地区分类】
Signed 红楼上架机器人
30 Sept 2026, 23:59 UTC1 viewsread 1 October 2026 Photo
编号:2609274394 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
y5948
省份:江苏z148
城市:无锡
年龄:28
身高:160
体重:95
🐻杯: B
职业:瑜伽老师
能否飞外地:附近城市,山西可以
能否过夜/同居:过夜可以,同居暂时不考虑
是否抽烟/纹身:不抽烟不喝酒没纹身
能否kou:可
能否体检后不d/🐍:熟悉后做决定
预期费用:5w
每🈷️可陪天数:3天1w 满月5w
能否接受sm :不接受
是否chu女: 不是
可分2-3次付:可以
姨妈时间:不准会提前五天
是否可去港澳;暂时不考虑
自我加分项:温柔,脾气好
雷点(不接受):说脏话,脾气不好,不讲卫生,邋遢的
介绍费:7888 y A5…
Signed 红楼上架机器人
30 Sept 2026, 23:59 UTC1 viewsread 1 October 2026 Photo
编号:2609274393 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
y6379
省份:山西b231
城市:榆次
年龄:28
身高:166
体重:115
🐻杯: c
职业:上班
能否飞外地:可
能否过夜/同居:可
是否抽烟/纹身:手臂
能否kou:可
能否体检后不d/🐍: 可不带 内看情况
预期费用:6k
每🈷️可陪天数: 3天6k
能否接受sm :否
是否chu女: 否
可分几次付: 2
姨妈时间:不准
是否可去港澳;没证
自我加分项:爱旅游 知性 事少 听话
雷点(不接受):
介绍费:7888 y A5
联系客服:小熙
联系客服:小…
Signed 红楼上架机器人
30 Sept 2026, 23:56 UTC1 viewsread 1 October 2026 Photo
编号:2609274387 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
y6504
省份;山西a860
城市;太原
年龄:98
身高:173
体重:56
🐻杯: b
职业:自媒体 模特
能否飞外地:可
能否过夜/同居:可过夜
是否抽烟/纹身:否
能否kou:不太行
能不能无🍑(体检后):否
能不能内🐍(体检后):否
预期费用:1.5w
每🈷️可陪天数: 3天1.5w
能否接受sm : 否
是否chu女: 否
可分几次付:2
姨妈时间:不准
是否可去港澳;没证
自我加分项:性格好 脾气好 没心眼 好相处
雷点(不接受): 不爱干净
介绍费:7888 y A5…
Signed 红楼上架机器人
Showing the 4 most recent of 4 posts we hold for @honglousx. 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.
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 October 2026 — this
entry's latest reading, not the date you are reading this.
“山西包养伴游【红楼选妃馆】” (@honglousx), 594 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/honglousx.
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.