Engagement
4 posts held, back to 6 August 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.142%
- avg views ÷ 704 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
6 Aug 2026, 19:01 UTC1 viewsread 6 August 2026 Photo
🔰编号:JF1985(点击编号自动复制)
🦋一键查询验证视频🦋
貂蝉00177
省份:辽宁
城市:大连
年龄:22
身高:174
体重:70kg
罩杯:b
雪历:本科
职业:刚毕业
是否是chu女:否
可不可以口:可
能不能内射:不
能不能无套:能
SM能不能:能
有没有纹身:小臂局部
是否可外省:可
是否可过夜:可
可不可以同居:可
月可陪伴天数:7
大概姨妈日期:10号
找金主的原因:想要一个契合的供养者
短期3天薪资:8k
分几次给生活费:3
自我介绍加分项:有健身习惯 微胖极品 身高比例好看 双商在线唱歌好听 自律
对老板雷点(不接受): 画饼
介绍费:7888
💞下单客服☎️: @QXBYC
💞售后联系📞: @QXBYB
💞狼友交流🐺: @QXBY88
💞双向点击🤖: @QingxinSX_bot
Signed 倾心采集专用
6 Aug 2026, 19:01 UTC1 viewsread 6 August 2026 Photo
🔰编号:MU6076(点击编号自动复制)
🦋一键查询验证视频🦋
貂蝉00176
省份:江苏
城市:南通叠石桥
年龄:19
身高:170
体重:120
罩杯:b
雪历:
职业:网管
是否是chu女:no
可不可以口:👌
能不能内射:no
能不能无套:no
SM能不能:no
有没有纹身:有
是否可外省:价格好👌
是否可过夜:👌
可不可以同居:👌
月可陪伴天数:10
大概姨妈日期:不准
找金主的原因:生活费不够
短期3天薪资:3q
分几次给生活费:2
自我介绍加分项:很乖
对老板雷点(不接受):不要特胖
介绍费:6888
💞下单客服☎️: @QXBYC
💞售后联系📞: @QXBYB
💞狼友交流🐺: @QXBY88
💞双向点击🤖: @QingxinSX_bot
Signed 倾心采集专用
6 Aug 2026, 19:00 UTC1 viewsread 6 August 2026 Photo
🔰编号:TJ6110(点击编号自动复制)
🦋一键查询验证视频🦋
貂蝉00175
省份:浙江
城市:杭州
年龄:23
身高:168
体重:56kg
罩杯:B
雪历:本科
职业:测评博主
是否是chu女:否
可不可以口:否
能不能内射:可
能不能无套:可
SM能不能:轻微可以
有没有纹身:无
是否可外省:可
是否可过夜:可
可不可以同居:否
月可陪伴天数:9
大概姨妈日期:25号
找金主的原因:接触异性比较少
短期3天薪资:9k
月生活费多少:一晚4k 长期1v1每个月分开可陪伴9天 生活费3w
分几次给生活费:3
自我介绍加分项:喜欢吃情趣睡衣水多敏感轻微m属性,不粘人懂事听话,
对老板雷点(不接受):不接受36岁以上的,不喜欢太胖
介绍费:7888
💞下单客服☎️: @QXBYC
💞售后联系📞: @QXBYB
💞狼友交流🐺: @QXBY88
💞双向点击🤖: @QingxinSX_bot
Signed 倾心采集专用
6 Aug 2026, 18:59 UTC1 viewsread 6 August 2026 Photo
🔰编号:GE1133(点击编号自动复制)
🦋一键查询验证视频🦋
抖音杭州30万粉丝博主首出
省份:浙江
城市:杭州
年龄:18
身高:174
体重:100
罩杯:C
xue生/工作:xue生
雷点(不能接受):
是否 chu女:否
例假日期:月初
能否接受SM:轻微可以也可以s
体检后能否接受无套:加米
能否接受口:口
可否过夜/同居:可过夜不同居
可否去其他省份城市:可以
见面双方满意后能否开f:可以
最快出发时间:现在
每月可陪伴天数:3天
预期费用:1.2w
费用分几次付〔2~4次〕:2次
是否有通行证或护照:是
可否异地伴游:可
伴游3天薪资:1.2w
伴游7天薪资:
自我加分项【越详细越好】:抖音30万粉丝博主 小网红 第一次找爹系 腿长 皮肤白 更懂得提前照顾人 床上带反差会跳舞舞蹈一流
介绍费:7888
💞下单客服☎️: @QXBYC
💞售后联系📞: @QXBYB
💞狼友交流🐺: @QXBY88
💞双向点击…
Signed 倾心采集专用
Showing the 4 most recent of 4 posts we hold for @QXBY8. 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.
Citation-graph rank
Citation-graph rank — 385,729 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 23 registered channels — 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 7 August 2026 — this
entry's latest reading, not the date you are reading this.
“🔰【倾心】包养 全国女大 御姐 处女 萝莉 包养” (@QXBY8), 704 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/QXBY8.
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.