好看扣1不好看扣眼珠子 入门联系:@xiaoxibeibb
❤5💩4🤡3

Channel
@xiaoxibeiYY
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
24,247subscribers
+1,014 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003822143049 |
|---|---|
| Type | Channel |
| Username | @xiaoxibeiYY |
| Description | 成都萝莉jk少女 专注线下全国可✈️ 找我入门约会 : @xiaoxibeibb 双向限制: @xiaoxibeBot 推特账号: x.com/submsubms |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/xiaoxibeiYY |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 10:15 | 24,247 | +211 |
| 12 Aug 2026, 22:55 | 24,036 | +84 |
| 11 Aug 2026, 20:31 | 23,952 | +128 |
| 10 Aug 2026, 17:32 | 23,824 | +190 |
| 9 Aug 2026, 16:01 | 23,634 | +90 |
| 8 Aug 2026, 14:03 | 23,544 | +156 |
| 7 Aug 2026, 16:54 | 23,388 | +155 |
| 6 Aug 2026, 21:00 | 23,233 | no change |
| 6 Aug 2026, 20:48 | 23,233 | first reading |
23 posts held, back to 27 July 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 23 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 14 August 2026 |
|---|---|
| Posts held | 23 (27 July 2026 – 14 August 2026) |
| Views total | 327,540 |
| Reactions total | 219 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 04:38 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.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 4 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.
219 reactions across 23 posts, in 9 distinct kinds. The most used accounts for 65.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 143 | 65.3% | |
| 💩 | 49 | 22.4% | |
| 🤮 | 14 | 6.39% | |
| 🎉 | 3 | 1.37% | |
| 👍 | 3 | 1.37% | |
| 🤡 | 3 | 1.37% | |
| 😍 | 2 | 0.913% | |
| 👎 | 1 | 0.457% | |
| 👏 | 1 | 0.457% |
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 23 of the 23 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 219reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 27 July 2026 to 14 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
❤5💩4🤡3
长沙明天下午有人约吗📢
🤮10❤4💩4😍2👎1
现在在长沙噢 13号白天和14号白天可以约宝宝们 【长沙】 8.11星期二:🈵 8.12星期三:🈵 8.13星期四:🈵 8.14星期五:🈵 8.15星期六:🈵 8.16星期天:🈵 #长沙 #flj #jk #反差
💩35❤7🤮4🎉1👍1
杭州的甜美萝莉姐妹,她叫幼小欲,不高p 朋友圈动态就是她真实的自己 人照合一 皮肤白嫩光滑,乖巧可爱,服务很多!玩法很多!配合度高!!🐻大三点粉 性欲强!喜欢研究新的玩法,极度敏感易喷水💦,有在江浙沪的哥哥 想线下约会,线上视频嘟可以联系联系她噢!! 幼小欲:@youxiaoyu1 双向:@shuishuiOBot 频道:@youxiaoyusoo
❤7💩3
今天晚上杭州最后一晚顶风作案有人约吗
❤2
【杭州】现在已被台风困住😭 8.10星期一:🈵 【长沙】 8.11星期二:🈵 8.12星期三:🈵 8.13星期四:白天🈳夜🈵 8.14星期五:2-6🈳夜🈵 8.15星期六:🈵 8.16星期天:🈵
❤9💩3🎉2👏1
明天9号晚上还在杭州可以约 10号去长沙咯
❤2
7/8号杭州最后两天还有宝宝想要约的快联系我哦 9号去长沙,长沙的宝宝现在也可以联系我预约了 #杭州 #福利姬 #线下 #jk反差
❤1
杭州白天还可以约
❤5
足底按摩 (现在还在杭州,下午可以约会都🈳哦) 谁想试试我的足底按摩不舒服不收钱 🔗:https://t.me/xiaoxibeiya_Bot?start=9666946F 👈 点击链接观看完整版视频 入门解锁线下约会 联系: @xiaoxibeibb 双向🤖:@xiaoxibeBot 自助入门🤖:@xiaoxibeiYabot
❤10
杭州最近还可以约噢马上要离开杭州了最后几天 #杭州 #线下 #福利姬 #jk #反差
❤6
好评➕1 【仙女昵称】:小西贝 @xiaoxibeibb 【评价时间】:八月上旬 【约会价格】:入门解锁线下表 【服务项目】:pp 【凶器罩杯】:A 【颜值身材】:颜值9.0身材8.9 【优点缺点】:反差学生感宝宝 【推荐程度】:超级好评 【过程描述】: 始见之刻,唯觉其呆萌娇憨,双眸澄澈如水,极具青衿学子之稚气。彼独伫大堂之中,纤手提携重箱,形单影只,娇小之躯与重器相映,令人生怜。 及至同入闺房,虽微存拘谨疏离之态,然于举手投足、一颦一笑之间,隐现反差之妙趣,格外讨喜。彼极尽认真,净手盥洗、严谨刷牙,事事井然有条,憨态可掬。 待至华灯半昏,罗帷低垂,正题始进。凝望其稚嫩如玉之容颜,抚其娇小玲珑之身躯,余心陡生恻隐,怜香惜玉之情油然而生,一度竟踌躇犹豫,不忍痛下楚楚之手,生怕惊损娇花。 然彼极尽温柔,体贴入微,曲意逢迎之间,引余缓缓融入佳境。及至被余压于身下,婉转承欢,杏眼含情,主动索求爱抚与温存,那般娇羞动人之态,直令余心神俱…
❤10
Showing the 12 most recent of 23 posts we hold for @xiaoxibeiYY. 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.
@xiaoxibeiYY edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 1,149,294 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“💘小西贝Yaの甜蜜日记💕” (@xiaoxibeiYY), 24,247 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/xiaoxibeiYY.
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.