代码: @2222所在省份和城市:北京 年龄:20 身高:170 体重:101 罩杯:e 当前职业:雪生 瑜伽教练 是否chu女:不是 能否接受sm(轻中重度):不是 能否接受口:可 能否接受体检后无tao :不是 能否接受体检后内se :不是 能否同居:看相处 能否过夜:没问题 每月可陪伴的天数: 3 期望生活费多少:1.5 生活费分几次付(2-4次):2-3 能否去其他城市:没问题 能否去港/澳:不是 自我加分项(优点优势 如两性技巧等):19/170/108的E 美术生+医学生+瑜伽教练 会做饭/游泳/艾灸/拔罐/推拿/按摩/敷贴/刮痧/康复治疗/游戏 过往干净,无不良历史,无纹身,不抽烟,不喝酒,不去酒吧,不泡夜店,头一次找 会让你很舒服 最快见面时间:明天后天 姨妈日期: 雷点(不能接受的):脾气不好,性格不好,不尊重人,特别特别胖 介绍费:7888KK-T 🌷编号:U9187 (点击编号可复制) 🩷喜乐汇金主…

Channel
喜乐汇包养学生妹
@XLHBY
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4,867subscribers
-1,446 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001736248697 |
|---|---|
| Type | Channel |
| Username | @XLHBY |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/XLHBY |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 12:43 | 4,867 | -268 |
| 27 Aug 2026, 02:35 | 5,135 | -300 |
| 23 Aug 2026, 19:59 | 5,435 | -245 |
| 20 Aug 2026, 13:23 | 5,680 | -217 |
| 17 Aug 2026, 09:55 | 5,897 | -290 |
| 13 Aug 2026, 23:36 | 6,187 | -126 |
| 12 Aug 2026, 19:17 | 6,313 | first reading |
Engagement
4 posts held, back to 12 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.041%
- avg views ÷ 4,867 subscribers
- Avg views / post
- 2.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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 4 (12 August 2026 – 12 August 2026) |
| Views total | 8 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 19:17 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
- 7s
- Average length
- 7s
Measured directly from 1 video 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
代码: @2222省份:重庆 城市:九龙坡 年龄:18 身高:166 体重:106 罩杯:b 学历:高中 职业:雪生 是否是chu女:并非 可不可以kou:OK 能不能内s:并非 能不能无t :OK SM能不能 :OK 有没有纹身:无 是否可外省:行 是否可过夜:行 可不可以同居:行 月可陪伴天数;3 月生活费:1w 自我介绍加分项: 性格好 年轻 对另一半的要求:对我好 对老板雷点(不支持): 无 介绍费7888KK-T 🌷编号:V4715 (点击编号可复制) 🩷喜乐汇金主包养交流群🩷 🎀喜乐汇双向客服🎀 🎀喜乐汇客服媛媛🎀 🌸喜乐汇验证视频🌸 🌸机器人智能选妃🌸 🩷喜乐汇新手交易流程介绍🩷
代码: @0015省份: 湖南 城市: 邵阳 年龄:26 身高: 161 体重: 92 罩杯: c 职业:婚庆 是否chu: 否 能否口:可 能否接受SM:可MS 能否无套:双方体检可 能否内射:否 能否过夜:可 能否同居:可 有没有纹身:无 可否飞外省:否 大姨妈日期:不固定 每月陪伴天数:三天/1w,五天/1.5w 期望零花钱:看金主需求 分几次支付零花钱:1-2 找金主的原因:提高生活水平 最早出发时间:提前一天通知 加分项:懂事,情绪价值高,配合度高 介绍费:7888 七七2 🌷编号:B0400 (点击编号可复制) 🩷喜乐汇金主包养交流群🩷 🎀喜乐汇双向客服🎀 🎀喜乐汇客服媛媛🎀 🌸喜乐汇验证视频🌸 🌸机器人智能选妃🌸 🩷喜乐汇新手交易流程介绍🩷
代码: @2222所在市兰州 现在是什么职业:餐饮 昵称:小Q 年龄:23 身高:167 体重:55kg 学历:专科 👙:B 是否整过:没有 期望每月零花钱:1.5W 可分几次给:2 接不接受飞外地:同意 接不接受同居:同意 接不接受出国:不认可 接不接受無T: 不认可 是否可以常伴,不可以的话说明一下(能)陪伴天数的情况:除姨妈期外 能否sm:并非 近期是否有时间:有 姨妈日期:25号左右 特点:温暖贴心/幽默风趣/ 相处舒服 /懂浪漫/随性 对另一半的要求: 介绍费7888KK-T 🌷编号:V0696 (点击编号可复制) 🩷喜乐汇金主包养交流群🩷 🎀喜乐汇双向客服🎀 🎀喜乐汇客服媛媛🎀 🌸喜乐汇验证视频🌸 🌸机器人智能选妃🌸 🩷喜乐汇新手交易流程介绍🩷
Showing the 4 most recent of 4 posts we hold for @XLHBY. 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 — 439,680 of 1,629,518 entries 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 3 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“喜乐汇包养学生妹” (@XLHBY), 4,867 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/XLHBY.
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.