Channel
@chuhangebaoyang
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3,673subscribers
-482 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001357004218 |
|---|---|
| Type | Channel |
| Username | @chuhangebaoyang |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/chuhangebaoyang |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 16:58 | 3,673 | -176 |
| 13 Aug 2026, 10:28 | 3,849 | -116 |
| 10 Aug 2026, 16:42 | 3,965 | -154 |
| 7 Aug 2026, 18:45 | 4,119 | -36 |
| 6 Aug 2026, 22:46 | 4,155 | first reading |
7 posts held, back to 21 June 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 5 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 7 (21 June 2026 – 27 July 2026) |
| Views total | 1,780 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:18 UTC |
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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
中大圈预约流程： 1：我司是会员安排制度（适当筛选真正的客户，有需要会员权益的精准客户。目前会员档位有，288白金会员，888钻石会员，1688至尊会员，5888帝皇至尊。详情了解 会员权益 ） 2：发送需求，客服人员拿取最新资料，提供一下信息：什么时候需要（现在或者是某个时间段的大体精准时间，多次鸽子会取消会员资格。）+预算（2500pp中圈。3000p大圈，5k，1.5w）+需要的次数（大圈的价格多数是次数*单价）+具体省市区 （广东省深圳市宝安区，最好有具体的酒店或者家里位置）+理想的妹子（御姐，少妇，空姐，洋酒，萝莉，身高，体重，罩杯），禁止中圈的价格，大圈极品的要求，没有这种 3：确定了妹子以及距离，安排车车费出发（正常都是100以内，个别100-150） 4：等妹子到达酒店见面，带妹子上楼 满意付款 接受服务 注意事项：飞机上骗子多，没有见面之前，禁止再付款任何费用，有任何问题需要客户自己承担。…
应广大客户要求，花了一个多月时间更新了全国一部分地区的妹子资料 有需要的老板可以看一下： https://t.me/+rV3Ww5L7KSYwODlk 中大圈均需 加会员 ，介意的老板可以多在群里观察 ，欢迎监督！！ 目前楚汉阁只做全球中大圈外围，地陪，包养，以及一些明星定制业务。有任何客服以能安排小圈的方式联系各位老板欢迎举报，奖励多多！！！ —————楚汉阁运营部
蕭景萱 21 162公分 50公斤 B罩杯 首次新下海，首次新下海，首次新下海 全国可飞，价格到位，可驻点 有需要的老板滴滴，手慢无系列！！！
Video, posted without a caption
TX102 省份:上海 城市:上海 年龄:23 罩杯:B 身高:164 体重:86 目前职业:自媒体 是否可去外省:可 能否去港澳:可 能否出国:可 可见面时间:随时 是否chu女:否 能否过夜:可 能否同居:可 生理日期:20 能否无tao（体检/试纸后）:可 能否内she（体检/试纸后）:否 能否kou:可 是否有纹身/抽烟:无 能否sm（哪种程度）:轻微 对金主要求:抠 要健康干净 短期报价:3\1.5W 7\3W 生活费可否分2次支付:🉑 加分项（自身优点）:名校毕业，真人更灵动漂亮，皮肤白，精致秀气，身材比例好，爱跳舞柔韧性强，清纯甜美性格大方，高学历高认知，雅思6.5，爱看书，研究心理学玄学，有催眠师证 介绍费:7888 介绍人；甜心 包养选妃频道：https://t.me/chuhangebaoyang 包养导航频道： https://t.me/chuhangeby 人工客服：@ww3584 双向客…
Video, posted without a caption
TX104 省份:上海 城市:上海 年龄:23 罩杯:c 身高:168 体重:52 目前职业:短剧演员 是否可去外省:可以 能否去港澳:可以 可见面时间:随时 是否chu女:否 能否过夜: 可以 能否同居:可以 生理日期:月初 能否无tao（体检/试纸后）:不 能否内she（体检/试纸后）:不 能否kou:可以 是否有纹身/抽烟:否 能否sm（哪种程度）:轻微 对金主要求: 不要邋遢 短期报价: 3天1W 生活费可否分2次支付:可以 加分项（自身优点）:胸大腿长温柔体贴，声音像林志玲，氵多ko🔥好 介绍费；7888 介绍人；甜心 包养选妃频道：https://t.me/chuhangebaoyang 包养导航频道： https://t.me/chuhangeby 人工客服：@ww3584 双向客服：@chuhangexuanfeibot ✅公群担保 ✅安全隐私 ✅全国包养 ✅全球可飞 ✅专属顾问 ✅商务接待
Showing the 7 most recent of 7 posts we hold for @chuhangebaoyang. 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 — 161,412 of 1,481,306entries 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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“楚汉阁包养选妃” (@chuhangebaoyang), 3,673 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/chuhangebaoyang.
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.