Engagement
3 posts held, back to 29 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.661%
- avg views ÷ 454 subscribers
- Avg views / post
- 3.0
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 3 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
30 Sept 2026, 03:12 UTC3 viewsread 1 October 2026 Photo
编号:2609271587 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
︂H16031
省份: 西藏
城市: 林芝
年︀龄:20
身︅高︇:174
体︅重︁:108
罩︅杯︍:B͏
是否︂chu:不是︃
职︊业︆:雪︌生︃
学️历:本科︌
体︊检︎后能︄否无︅t:可︆以︉͏͏
能︅否nei射:不︌能︇͏
能︉否︋口︇:是︂͏
SM能︋不︋能:轻︈微︃
能否同︊居︆:不︇可以︎
能否️过︇夜:是︁͏
能️否✈️其他︅省️份︇:可︍以͏͏
例︍假日期︋:每︃月︃中︅旬
有︀没有︋纹︎身︀:没︄有︂͏͏
是︂否︆抽︊烟︋🚬:抽︃͏
最︇早出︋发︀时︎间:7月10号͏͏
每︎月️陪︅伴天︎数:2-3-5天️
每月到手︌:3K-4.5K-7K
个人︊优︇点︀:幽︈默︋体︋贴︍,身︌…
Signed 红楼上架机器人
29 Sept 2026, 17:51 UTC3 viewsread 1 October 2026 Photo
编号:2609270261 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
y5813
省份:西藏L93
城市:灵芝
年龄:22岁
身高:162
体重:90
🐻杯: a
职业:雪生
能否飞外地:不飞
能否过夜/同居:可
是否抽烟/纹身:否
能否kou:可 不熟练
能否体检后不d/🐍: 可
预期费用:8k
每🈷️可陪天数:3天8k
能否接受sm :可轻微sm 不能太凶
是否chu女: 否
可分几次付: 2
姨妈时间:不准
是否可去港澳;否
自我加分项:
雷点(不接受):不接受拍视频
介绍费:7888 y A5
联系客服:小熙
联系客服:小甜
…
Signed 红楼上架机器人
29 Sept 2026, 14:09 UTC3 viewsread 1 October 2026 Photo
编号:2609262433 (点击复制)
🔍 点击查看验证视频
⭐ 点击收藏该资源 ⭐
:李逍遥2053
豆︂豆︉e
省份:西藏
城市:拉萨
雪︊生︂还︍是︋工︋作︁:工作︃͏
学︉历︆:大︀专͏
年︁龄︇:19͏
身︁高:167͏͏
体︌重︁:86͏
罩︍杯︎:B
是︂否︂chu:否︄͏
体检︃后️能︃否︋无️t:否︂
能︃否口:能︃͏͏
SM能︆不︃能:不︀能͏
能否︆同︀居:不︁能︄
能否过︈夜️:能︄
能否︎去︆其︇他︁省份︉:能︁͏
例️假︇日期︄:每︀个︃月︎不︃稳定
有没有︂纹︈身︊:没︂有͏͏
最︎早︎出发时间︃:都︉可以
每︊月陪︀伴天︂数︈:3͏
每︁月︀零︈花钱:8888
个︊人︂优︍点:听话︍
不︆能接︍受︎金︎主︇:变︇态︄
介绍费7888
联系客服:小熙
联系客服:小…
Signed 红楼上架机器人
Showing the 3 most recent of 3 posts we hold for @honglouxizang. 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.
“西藏包养伴游【红楼选妃馆】” (@honglouxizang), 454 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/honglouxizang.
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.