Channel
@xiaoxibeHB
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
114subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003768117584 |
|---|---|
| Type | Channel |
| Username | @xiaoxibeHB |
| Created | Between 1 February 2026 and 29 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/xiaoxibeHB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 06:27 | 114 | +2 |
| 9 Aug 2026, 06:31 | 112 | no change |
| 6 Aug 2026, 21:00 | 112 | first reading |
14 posts held, back to 29 May 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 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 4 August 2026 |
|---|---|
| Posts held | 14 (29 May 2026 – 4 August 2026) |
| Views total | 49,200 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 06:31 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.
10 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 14 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 10reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 29 May 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
好评➕1 【仙女昵称】：小西贝 @xiaoxibeibb 【评价时间】：八月上旬 【约会价格】：入门解锁线下表 【服务项目】：pp 【凶器罩杯】：A 【颜值身材】：颜值9.0身材8.9 【优点缺点】：反差学生感宝宝 【推荐程度】：超级好评 【过程描述】： 始见之刻，唯觉其呆萌娇憨，双眸澄澈如水，极具青衿学子之稚气。彼独伫大堂之中，纤手提携重箱，形单影只，娇小之躯与重器相映，令人生怜。 及至同入闺房，虽微存拘谨疏离之态，然于举手投足、一颦一笑之间，隐现反差之妙趣，格外讨喜。彼极尽认真，净手盥洗、严谨刷牙，事事井然有条，憨态可掬。 待至华灯半昏，罗帷低垂，正题始进。凝望其稚嫩如玉之容颜，抚其娇小玲珑之身躯，余心陡生恻隐，怜香惜玉之情油然而生，一度竟踌躇犹豫，不忍痛下楚楚之手，生怕惊损娇花。 然彼极尽温柔，体贴入微，曲意逢迎之间，引余缓缓融入佳境。及至被余压于身下，婉转承欢，杏眼含情，主动索求爱抚与温存，那般娇羞动人之态，直令余心神俱…
标准报告模板如下 【验证留名】：匿名 【验证名称】：小西贝@xiaoxibeibb 【验证时间】：7.31 【线下费用】：私聊 【服务内容】：18🚫 【年龄身高】：05，165 【颜值身材】：清纯可爱的小美女，一对A🙈🙈🙈 【机车行为】：无 【优点缺点】：全是优点，满满女友感。 【推荐程度】：夯，无脑冲就行 【过程描述】：从甲帝第一次约小西贝，就开始关注了，奈何时间和空间一直不合适，没有机会，这次终于盼来了心仪已久的西贝。 初见小西贝，一身深蓝色JK，黑色丝袜，亮亮的小黑皮鞋，扎着两个马尾，清纯甜美的颜值，配上一个大大的行李箱，尽显可爱呆萌。接到西贝，开车前往酒店，美好的时刻开始了，细节不想描述，如西贝之前的好评报告，没有一丝丝的夸大水分，床上极度反差，激情过后，又会主动钻到怀里，让我抱着她，满满的女友感。一起吃完晚饭后，将西贝送到了目的地，马路旁，车来人往，分别时，西贝走到我面前，相拥而抱，主动送上了两个深深的舌…
标准报告模板如下 【验证留名】：匿名 【验证名称】：小西贝@xiaoxibeibb 【验证时间】：7.27 【线下费用】：私聊 【服务内容】：满足你的一切幻想 【年龄身高】：05 【颜值身材】：对A，还没我的大，哈哈。颜值没的说，9.9分。 【机车行为】：无 【优点缺点】：情绪价值拉满 【推荐程度】：顶格 【过程描述】二刷小西贝了，作为一个资深老吃家，在我cj过的所有老师中最顶格的一个，呆呆傻傻的，在我眼里，这是她的必杀技。在这个圈子呆久了，对很多东西都麻木了，但是她不一样，每次都能给你带来不一样的体验。相对于其他人而言，她能带给你的不是那种激烈的刺激，更像是一种渗入骨髓里的甜蜜。就像喝酒一样，你会享受那种酒精慢慢渗透进身体里面的感觉，当你回过神来，才发现原来自己不知不觉已经沉浸在其中。就是这种感觉让人很上头，抽烟可以分泌多巴胺，喝酒可以分泌多巴胺，健身也可以分泌多巴胺，而小西贝带给你的多巴胺是不同的。从认识她，开始接触她的那一…
标准报告模板如下 【验证留名】：匿名 【验证名称】：小西贝@xiaoxibeibb 【验证时间】：7.30 【线下费用】：私聊 【服务内容】：xxx 【年龄身高】：05 【颜值身材】：人照合一，163左右 【机车行为】：无 【优点缺点】：情绪感十足，只是小熊饼干，大熊控勿扰 【推荐程度】：不推荐，好物要私藏啊嘿嘿 【过程描述】：反馈来了:一个字顶，女友感十足，小小一只超可爱，但是不要被她的外貌欺骗了，纯纯榨汁姬。还有兄弟们出击前千万不要练臀腿啊，奋战一晚，第二天根本直不起腰来。 欢迎小姐姐来到济南，大明湖畔，惊鸿一瞥，流连忘返！
【仙女昵称】：小西贝@xiaoxibeibb 【评价时间】：2026年6月 【约会价格】：入门解锁线下表 【服务项目】：天，双飞 【凶器罩杯】：A? 【颜值身材】：没有赘肉，高高瘦瘦纯纯的大只萝莉，无关清秀，有种小家碧玉的感觉 【优点缺点】：反差，绝对的反差，你无法想象到这张呆呆傻傻的脸在床上能如此反差，还能主动A上来，激发你原始的欲望，根本要不够，没有极限 【推荐程度】：十分推荐，绝对有着最佳体验 【过程描述】：
标准报告模板如下 【验证留名】：匿名 【仙女名称】： 小西贝 @xiaoxibeibb 【验证时间】： 6.30 【线下约会价格】：私聊线下，包时2h/pp 【服务内容】： 入门线下课表 【年龄身高】：05年 身高165 【颜值身材】： 身材顶 臀大腰细 【机车行为】： 无 【优点缺点】： 【推荐程度】： ❤️❤️❤️❤️❤️ 【过程描述】：小西贝连夜从厦门飞来，飞机晚点 等了一个半小时，看到本人的时候感觉等的值了。性格很可爱 人照无差可以看频道的小电影。 妹子女上体力超好，后入可以全自动，准备隔天再战
❤1
【仙女昵称】：小西贝@xiaoxibeibb 【评价时间】：2026.06.07 【约会价格】：入门解锁线下表 【服务项目】：包天 【凶器罩杯】：对A,要不起 【颜值身材】：真人比照片好看，满分。身材属于那种娇小可爱性 【优点缺点】：女友感拉满，口技٩(•̤̀ᵕ•̤́๑)ᵒᵏᵎᵎᵎᵎ 【推荐程度】：不推荐，都给别人点了我怎么点。 【过程描述】：一接到小西贝，就看到她穿着一身jk制服➕白色裤袜，配合着可爱的她，瞬间就打动了我的心。 一进电梯小西贝就开始贴贴，用屁屁摩擦下体，配合着可爱的容颜以及甜甜的声音，让人根本无法忍耐。 一进房间先跟小西贝聊了会儿天，她就开始主动跟你亲吻，非常主动，小舌头非常灵活，虽然不是那种大蟒蛇。但小嘴和舌头配合的超级好，让我欲罢不能，后面多次跟小西贝亲嘴。进入正题前，小西贝会仔细的清理一下，再直接含入，灵活的小舌头不停舔着鬼头，不管是深喉还是其他的，小西贝都会主动配合。小西贝的口技简…
❤2
仙女昵称】：小西贝 @xiaoxibeibb 【评价时间】：2026.06.06 【约会价格】：入门解锁线下表 【服务项目】：5小时包时 【凶器罩杯】：AA 【颜值身材】：颜值🆙身材修长 【优点缺点】：优点颜值高口活🆙 【推荐程度】：满分💯我打99，留一分的进步空间 没赶上五一的贝贝，想不到又来杭州了，早早预约了极具性价比的包时，待周末之际，马不停蹄的坐上高铁从金华出发杭州。 初次见面在酒店大堂，映入眼帘是修长的腿，就是路人也要多嫖几眼，近来端详贝贝的脸是让人忍不住想捏捏的，且娇小可爱。嗲嗲的声线让人酥酥麻麻的，贝贝还想主动贴贴，奈何上下电梯人太多，自己太怂没放的开。 进了房间，美团上选好了道具，稍作修整，便开始了第一次大战。此处谴责自己没能给贝贝宽衣解带哈，但是贝贝脱衣的背影也绝佳了。陪浴的时候也是全自动，不需要自己出力。期间我还突然的索吻，也是很配合的舌尖交缠。战线转移至床上，真要夸夸其口活，快…
❤4
【仙女昵称】：小西贝 @xiaoxibeibb 【评价时间】：6.3号 【约会价格】：入门解锁线下表 【服务项目】： 【凶器罩杯】：A 【颜值身材】：唯一缺点就是🐻有点小 【优点缺点】：太能榨了 【推荐程度】：10/10 【过程描述】：在高铁上刷到小西贝 感觉颜值和身材都是我喜欢的类型 果断过了个5200的🚪 约了小西贝的✌️ 由于前几天滑雪摔得不轻 于是特意缓了两天准备 顺便多回一点血嘿嘿 知道小西贝可以拍视频 于是专门看了长沙几家高空酒店的套房 想着用环境来弥补我拍照技术的短板 还在美团买了一大堆小道具 期间贝贝也一直在和我聊天 几乎秒回我tg的消息 也是情绪价值拉满了 到了正式见面当晚 天气又热又有小雨 于是在楼下给贝贝买了个小礼物 没想到贝贝8点多就出发了 于是收拾了一下自己 去酒店大堂坐着等她 见到小西贝的那一刻感觉真人甚至比照片还漂亮 那么热的天气还穿着厚厚的lo裙 整个人水淋淋的 一进电梯就和我在角落亲起来了 …
❤3
Photo, posted without a caption
长沙好评加1
原来kfc还有其他含义
Showing the 12 most recent of 14 posts we hold for @xiaoxibeHB. 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 — 340,717 of 1,478,351entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“小西贝の好评日记” (@xiaoxibeHB), 114 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/xiaoxibeHB.
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.