Engagement
4 posts held, back to 1 October 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.131%
- avg views ÷ 762 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, 01:22 UTC1 viewsread 1 October 2026 Photo
编号:2609274603 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
名称:小太阳z89
省份:山东
城市:青岛
年龄: 04
身高: 165
体重: 46
罩杯: c
职业:雪生
学历:本科
是否chu: 否
能否口:可
能否无套:否
能否内射否
能否SM:否
能否过夜:可
能否同居:可
有没有纹身:否
能否飞外省:可
能否出村:否
每月陪伴天数:3
期望零花钱:2w
分几次支付零花钱:2
找金主的原因:缺钱
自我评价: 身材苗条 温柔乖巧态度好
介绍费:7888小太阳
联系客服:小熙
联系客服:小甜
联系客服:小萌
【便捷选妃-地区…
Signed 红楼上架机器人
1 Oct 2026, 01:03 UTC1 viewsread 1 October 2026 Photo
编号:2609274547 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
加菲猫1468
省份: 山东
城市: 青岛
职业: 学生
年龄: 19
身高: 156
体重: 125
罩杯: c
是否Chu女: 否
是否接受SM: 一点点
金主体检后是否接受无t: 否
是否接受内: 否
是否接受口: 一半一半
是否接受同居: 否
是否接受过夜: 接受
是否接受外地: 接受
每月姨妈时间及天数: 不准确
绝对禁忌的事项: 在我明确拒绝后还要硬来
对金主的要求: 暂无
找金主的原因: 缺钱
对恋爱费用的预期: 两天4k 三天6k 五天9k
恋爱费分次支付情况: 两次
每个月可陪伴的天数: 还是学生得周末
自我评价: 学生妹 喜欢cosplay 二次元 胸大 口爆 颜设 情趣玩具
介绍费7888
加菲猫-9…
Signed 红楼上架机器人
1 Oct 2026, 00:39 UTC1 viewsread 1 October 2026 Photo
编号:2609274485 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
sun181
名称:xty-z255
省份:山东
城市:济南
年龄:06
身高: 163
体重: 85
罩杯: b
职业: 本科
学历:雪生
是否chu: 否
能否口:可
能否无套:可+5k
能否内射 否
能否SM::不
能否过夜:可
能否同居:可
有没有纹身:无
能否飞外省:可
能否出国:可新马泰
每月陪伴天数:3
期望零花钱:1.5w
分几次支付零花钱:2
找金主的原因:缺钱
自我评价: 超嗲娃娃音 叫爸爸超狠
主动型榨汁机 软萌小甜心
希望能与素质哥哥一起开心
介绍费:7888小太阳…
Signed 红楼上架机器人
1 Oct 2026, 00:16 UTC1 viewsread 1 October 2026 Photo
编号:2609274433 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
:八方来财030
:
省份:山东
城市:济宁
年龄:17
身高:168
体重:105
罩杯:
学历:高中
职业:
是否是处女:只自己弄过算吗
可不可以口:可
能不能内射:不能
能不能无套:能
SM能不能:能
有没有纹身:没有
是否可外省:不可以
是否可过夜:不可以
可不可以同居:不可以
月可陪伴天数:3
大概姨妈日期:不规律
找金主的原因:
月生活费多少:3k
分几次给生活费:2次
自我介绍加分项: 第一次找,还没做过
对老板雷点(不接受):
介绍费:7888
八方来财
联系客服:小熙
联系客服:小甜
联系客服:小萌
【便捷选妃-地区分类】
Signed 红楼上架机器人
Showing the 4 most recent of 4 posts we hold for @honglousd. 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.
“山东包养伴游【红楼选妃馆】” (@honglousd), 762 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/honglousd.
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.