🔰编号:CLGB9688(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 KL4879 省份:湖南 城市:长沙 年龄:25 身高:160 体重:88 罩杯:B 职业:设计 是否chu:否 能否口:ok 能否SM:否 能否检测无套:否 能否内射:否 能否过夜:ok 能否同居:ok 是否抽烟:否 有没有纹身:否 可否飞外省:本地 亲戚日期:月底 每月陪伴天数:2 期望零花钱:5k 零花钱分几次:2 加分项:圈子干净 0179 介绍费:7888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot

Channel
【甜心包养】包养伴游选妃·高性价比
@baomei088
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7,966subscribers
-758 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002213412421 |
|---|---|
| Type | Channel |
| Username | @baomei088 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/baomei088 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 20:48 | 7,966 | -62 |
| 30 Aug 2026, 09:27 | 8,028 | -101 |
| 27 Aug 2026, 19:06 | 8,129 | -58 |
| 24 Aug 2026, 11:54 | 8,187 | -58 |
| 20 Aug 2026, 17:43 | 8,245 | -89 |
| 17 Aug 2026, 14:07 | 8,334 | -125 |
| 14 Aug 2026, 07:24 | 8,459 | -121 |
| 10 Aug 2026, 21:45 | 8,580 | -126 |
| 8 Aug 2026, 02:26 | 8,706 | -18 |
| 7 Aug 2026, 20:02 | 8,724 | first reading |
Engagement
105 posts held, back to 7 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 22 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.019%
- avg views ÷ 7,966 subscribers
- Avg views / post
- 1.6
- 105 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 105
- of 105 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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 105 (7 August 2026 – 28 August 2026) |
| Views total | 163 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 18:36 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.
What this channel posts
- Video runtime
- 4m 52s
- Average length
- 11s
Measured directly from 27 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.
Recent posts
🔰编号:CLCS0616(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 KL4877 省份:云南 城市:昆明 年龄:22 身高:161 体重:97 罩杯:C 职业:雪生 是否chu:否 能否口:没毛病 能否SM:否 能否检测无套:没毛病 能否内射:否 能否过夜:没毛病 能否同居:没毛病 是否抽烟:否 有没有纹身:否 可否飞外省:没毛病 亲戚日期:3号 每月陪伴天数:2天 期望零花钱:4k 零花钱分几次:2 加分项:性格好 情绪稳定 能提供情绪价值 圈子小 干净。 0186 介绍费:7888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
🔰编号:CLNG2962(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 省份:湖南 城市:长沙 年龄:18 身高:166 体重:80 罩杯:B 职业:雪生 是否chu: 否 能否SM:轻微 能否口:可以 测试后能否无套:否 能否过夜:可以 能否同居:可以 有没有纹身:无 能否飞外省:可以 能否出村:安全国家 雷点(不接受) :无 大姨妈日期:17号 每月陪伴天数:3天 期望的零花钱:15000 分几次支付零花钱:2次 最早出发时间:提前说 自我加分项: 性格主动活泼 调皮幽默 介绍费:6888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
🔰编号:CLLJ4266(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 kk12068 所在省;湖南省 所在市:长沙 现在是什么职业:雪生 年龄:18 身高:158 体重:95 雪历:在读目前休雪状态 👙:b 是否整过:否 期望每月零花钱:8-9千 短期三天期望薪资:6 可分几次给:2 接不接受飞外地:👌 接不接受同居:否 接不接受出国:否 接不接受🈚T: 🉑➕💰 是否可以常伴,不可以的话说明一下陪伴天数的情况:👌 能否sm:👌 近期是否有时间:有 姨妈日期:月底 特点:乖巧可爱 对另一半的要求:无 介绍费:7888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
🔰编号:CLTO1031(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 国家/城市:洛阳 河南 可否去异地城市:🉑 年龄:18 身高:162 体重:100 罩杯:粉嫩 B+ 职业:雪生 是否可以过夜:可 有无纹身: 无 是否抽烟: 偶尔 可否口:可 姨妈期:18号 可否无套:否,戴套 陪伴的天数:3天 💰:3天1w 可否SM调教:可,看表格 加分项:甜妹 清纯 粉嫩 身材好 皮肤白皙 毛少 又紧又润 会吞精💦 会弹钢琴 会唱歌 乖巧懂事 让金主爸爸爽! 客户反馈:清纯嫩妹 全身粉嫩 白皙 很听话 插入紧润💦 配合度很好 边草边舌吻 体验感拉满 还会吞精 这次体验简直爽翻了! 介绍费:6888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinba
🔰编号:CLFI6219(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 NX 795 地区:陕西 西安 年龄:24 身高:169 体重:95 罩杯:b 能否接受口:🉑 可过夜:🉑 可否其他城市:🉑 可否飞往外省:🉑 最快多久出发:随时 生活费要多少:三天1.5w (生活费短期2次 长期3-4次能否接受):🉑 自我加分项:腿长 皮肤白 性格好 事少 6888 风 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
🔰编号:CLPJ5398(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 省份: 安徽 城市: 合肥 年龄:19 身高:156 体重:79 罩杯: b 职业:🈚 是否chu: 否 能否口:🉑 能否SM:m 能否无套: 能 能否内射:否 能否过夜:🉑 能否同居:🉑 有没有纹身:🈚 可否飞外省:可 雷点(不接受):年龄超过40 大姨妈日期:月底 每月陪伴天数:满月 每月期望零花钱:2w(短期约会3天5000) 分几次支付零花钱:2 找金主的原因:找伴侣 最早出发时间:随时 自我加分项:可爱 乖 听话 介绍费:7888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
🔰编号:CLTP7860(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 KL1789 省份:河北 城市:石家庄 年龄:18 身高:171 体重:86 罩杯:C 职业:雪生 是否是chu女:并非 可不可以口:能 能不能内s:并非 能不能无套:检测后可以(一天+1k) SM能不能:轻微可以 有没有纹身:无 是否可外省:没毛病 是否可过夜:没毛病 可不可以同居:没毛病 月可陪伴天数:3 大概姨妈日期:月末 找金主的原因:缺米 月生活费多少:3天1.5w 分几次给生活费:2 自我介绍加分项:漂亮 身材好 对老板雷点(不支持):内 最快什么时候出发:4月 KLk 介绍费:7888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot
🔰编号:CLMT4619(点击编号自动复制) 🦋一键查询验证视频🦋 🌷点击收藏此资源🌷 kk12463 KL5864 省份:福建 城市:涵江 雪生还是工作:雪生 年龄:19 身高:163 体重:87 罩杯:真c胸 是否chu:否 体检后能否无t:没毛病 能否内之:没毛病 能否口:没毛病 SM能不能:没毛病 能否同居:没毛病 能否过夜:没毛病 能否去其他省份:没毛病 例假日期:月初 有没有纹身:无 是否抽烟:否 最早出发时间:随时 每月陪伴天数:3天 每月到手:8k 个人优点:听话乖巧 白KL 床上骚 会喷真会喷。真会喷。可口爆 真会喷 喷的老高了 不能接受金主:性病,baoli 介绍费:7888 包养指南老板必看 ❤️甜心包养 专注包养行业 ✅包养规则 🎯地区导航 💯新人必看 🏆入会看视频认证 均在新人频道➡️➡️@txxr888 😍甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_
Showing the 12 most recent of 105 posts we hold for @baomei088. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“【甜心包养】包养伴游选妃·高性价比” (@baomei088), 7,966 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/baomei088.
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.