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.133%
- avg views ÷ 752 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:00 UTC1 viewsread 1 October 2026 Photo
编号:2609274538 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
加菲猫1464
省份: 上海
城市: 上海
职业: 上班
年龄: 20
身高: 160
体重: 52kg
罩杯: B
是否Chu女: 否
是否接受SM:是
金主体检后是否接受无t: 是+2k
是否接受内: 是+2k
是否接受口: 是
是否接受同居: 是
是否接受过夜: 是
是否接受外地: 是
每月姨妈时间及天数: 月底
绝对禁忌的事项: 无
对金主的要求: 温柔体贴 大方
找金主的原因: 缺钱
对恋爱费用的预期: 三天6k 5天1w
恋爱费分次支付能否接受: 2
每个月可陪伴的天数: 都行
自我评价: 接受程度高 温柔 会开车
介绍费7888
加菲猫-9…
Signed 红楼上架机器人
1 Oct 2026, 00:47 UTC1 viewsread 1 October 2026 Photo
编号:2609274504 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
:八方来财042
省份: 上海
城市: 上海
年龄:19
身高: 162
体重: 88
罩杯: b
职业:生
是否chu: chu chu chu (支持检测)
能否口:不能
能否sm:不能
能否无套(试纸体检后):可
能否内射:可
能否过夜:可
能否同居:否
有没有纹身:🈚️
可否飞外省:可
雷点(不接受):
大姨妈日期:记不住
每月陪伴天数:1
期望零花钱:15000
分几次支付零花钱:1
找金主的原因: 因为一些原因,急用钱,希望找个好金主
最早出发时间:提前说
自我加分项:嗯对 声音很萌 没谈过恋爱
介绍费:10888
八方来财
联系客服:小熙
联系客服:小甜
联系客服:小萌
【便捷选妃-地区分类】
Signed 红楼上架机器人
1 Oct 2026, 00:37 UTC1 viewsread 1 October 2026 Photo
编号:2609274480 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
sun198
名称:xty-z247
省份:上海
城市:上海
年龄:05
身高: 166
体重: 86
罩杯: c
职业: 雪生
学历:本科
是否chu: 否
能否口:可
能否无套:不
能否内射 否
能否SM::不
能否过夜:可
能否同居:可
有没有纹身:无
能否飞外省:可
能否出国:可新马泰
每月陪伴天数:7
期望零花钱:5w
分几次支付零花钱:2
找金主的原因:缺钱
自我评价:大二 活泼可爱 不高冷 本人比照片好看 皮肤巨好很白暂
介绍费:7888小太阳…
Signed 红楼上架机器人
1 Oct 2026, 00:36 UTC1 viewsread 1 October 2026 Photo
编号:2609274479 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
y5664
省份:上海 V73-v74
城市:上海
年龄:23(双胞胎姐姐)23(双胞胎妹妹)
身高:165 163
体重:55 50
🐻杯: c c
职业:礼仪 礼仪
能否飞外地:不
能否过夜/同居:能过夜
是否抽烟/纹身:否/否
能否kou:能
能否体检后不d/🐍:否
预期费用:1天8k共 3天2.1w共
每🈷️可陪天数:10天之内
能否接受sm :否
是否chu女:否
可分几次付:2
姨妈时间:10号左右
是否可去港澳:否
自我加分项:乖巧听话 能配合 给你不一样的体验
只能接受两个人一起
雷点(不接受):不接受喝酒,身上有异味
介绍费:7888 y …
Signed 红楼上架机器人
Showing the 4 most recent of 4 posts we hold for @hongloushanghai. 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 6 October 2026 — this
entry's latest reading, not the date you are reading this.
“上海包养伴游【红楼选妃馆】” (@hongloushanghai), 752 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/hongloushanghai.
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.