Channel
@xiaoxuedpyq1
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
828subscribers
+79 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004295871877 |
|---|---|
| Type | Channel |
| Username | @xiaoxuedpyq1 |
| Created | Between 1 May 2026 and 16 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/xiaoxuedpyq1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 08:53 | 828 | +79 |
| 6 Aug 2026, 23:06 | 749 | no change |
| 6 Aug 2026, 20:05 | 749 | first reading |
15 posts held, back to 16 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 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. It is computed over the 7 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 15 (16 July 2026 – 4 August 2026) |
| Views total | 34,060 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 20:05 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.
13 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 76.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 76.9% | |
| 💩 | 2 | 15.4% | |
| 😁 | 1 | 7.69% |
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 8 of the 15 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 13reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 16 July 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.
【时间】：2026-07-16 【老师】：嘉怡 【留名】：匿名 【评价】： 好评 【人照】：9.0一致 【颜值】：9.0 【身材】：9.5 【服务】：9.0 【态度】：10.0 【环境】：8.0 【综合】：9.08 【过程】：再电报上看到嘉怡老师，看照片很年轻漂亮，就过来了，人照一致，本人比照片还好看。还是童颜巨乳，很大，很嫩。陪洗完开始服务，毕竟嫩妹那些活儿就那样，但是态度特别好，性格也很开朗。带上雨伞开始妹妹坐上来的时候，发现有点新疆人的感觉，而且特别耐看，随后换了传教，最后在后入的时候出货了。妹妹不催，也比较耐，配合的很好。很满意的一次出击！
最近一直看群里嘉怡报告，今天决定线下真实她，约好时间驱车前往，嘉怡在电梯口迎接，一身白纱裙配上亮闪闪高跟鞋好生可爱，拉手一起前往教室。 进入教室先交了水费，因为时间不着急又和嘉怡一起抽了烟聊了一会天，和线上一样的活泼开朗，是一个爱笑的女孩。有点害羞，我也没要求陪浴，分别洗完澡，还贴心的给我擦了脚，然后又拿出漱口水漱了口方便一会的🐍。 来到床上，换上了黑色蕾丝裙，与刚才的可爱不同，现在更多的是性感。趴在我身上，小脑袋探过来主动索吻，我也不客气的一口吻上，该说不说嘉怡的红唇香甜粉舌绵软，让人沉溺其中流连忘返，我不禁用手抱住的小脑袋让我们的舌更紧密的交织在一起。一番蛇吻结束后，嘉怡开始舔咪咪然后一路向下，一边夸我好大一边趁我不备突然含住，口活真的很好，毫无齿感，包裹感很强，温热柔软。我提出69，但是嘉怡不想在上面，那就只能我给她服务了，下面很干净，嘉怡很敏感，下面已经湿成一片了，舔了没几下就说受不了啦，于是带上雨伞开始战斗。 经典传教…
【老师名字】：嘉怡 【车牌】@jiayiz2 【人照评分】：9 【颜值评分】：9 【身材评分】：9 【服务评分】：8 【态度评分】：10 【环境评分】：8 【过程描述】：刚出电梯，一声清脆的招呼便传了过来。 “来啦，哥哥。” 循着声音望去，她正站在那里迎接我。简单的白色T恤搭配一条小短裙，显得格外青春利落。 频道里的照片当时让我没报太大期望，但真正见到本人时，不得不说，果然名声在外并非毫无道理。是那种越看越好看的类型，有灵气。 简单寒暄几句后，招呼我坐下。同时她也坐下钻到我怀里，对视时，脸上的笑意里带着几分羞涩。没有着急进行下一步，只是在沙发上初步了解着对方。 汗意渐渐退去，洗净来到屋里。胸很大，把玩的过程中发现没有一点科技。对比身材，胸大的犯规了，而且还能摸到里面包含胶原蛋白。 在大大的落地窗面前，不断变化着姿势，靠在床上，嘉怡主动询问要不要69，通过小缝隙，可以看到镜子中的浅浅享受的品尝着牛牛。耳边轻缓的音乐夹杂…
❤1
【妹子花名】：嘉怡 【验证留名】：匿名 【人照得分】: 9.0 【颜值得分】: 9.2 【身材得分】: 9.4 【服务得分】: 9.5 【态度得分】: 9.5 【环境得分】: 9.0 【综合得分】: 9.27 【验证时间】：2026-07-28 【过程描述】：按照约定的时间到达目的地，易找，老师来接的，我看见的第一眼果然没让我失望，非常可爱，皮肤白嫩，一对大胸让人挪不开眼，坐下闲谈一会，交了水费，和老师一起脱衣洗澡，白白的身子大大的胸，二弟一下就有反应了，帮我认真的洗着澡，有备一次性毛巾，很细心，房间温度适宜，帮忙擦干一起躺床上，开始老师的服务，老师一开始乖巧可爱，床上风骚，这反差我喜欢，口的很舒服，感觉可以了就让老师戴套 女上位，这视角根本受不了，在这样坐下去就要 123 了，然后换我来，老师下面很紧水多，没两下还是交代了，感觉没有让老师尽兴，下次再好好表现，完事后躺下一起聊天，休息一会，流连忘返下次必须重整…
💩2❤1😁1
今天开课了哦哥哥们
休息几天哦哥哥们
【日 期】: 0723 【验 证 人】: 小阿斗 【美女昵称】: 嘉怡 【地 区】: 中原区 【水 费 】: 500 【身材曲线】: 嫩妹三件套 【风情指数】: 开朗活泼型 【技术含量】: 刚入行 【人照相似】: 8 【服务过程】:连着约了三天的妹子，第一天回复的晚了点来不及出击，第二天没回复，第三天说昨天没开，就赶紧约了时间。到了熟悉的地方，妹子出来接的。在这个地方第一次被接。进门付了水费，看了眼妹子，黑衣显瘦，和照片8分像，微肉的小脸特别精致。付完水费妹子脱衣，我去，太有料了！我感觉得c-d之间，身上肉肉但没有多余的赘肉，而且乳头还没立正，一看还在发育中，这以后绝对是大凶器，没有热水，简单冲洗，妹子简单服务，我还是比较拘谨，被妹子调侃了一下，顿感害羞。了解妹子甘肃的，皮肤却还白皙的不多见。片刻提枪上马，想和美女多多温存，奈何123选手，经过传统，女上的简单动作，最后后入，感觉太好，…
❤2
我会继续努力的哥哥们
谢谢哥哥好评
谢谢哥哥好评
❤3
【时间】：2026-07-16 【老师】：嘉怡 【留名】：匿名 【评价】：👍 好评 【人照】：9.0 【颜值】：9.0 【身材】：9.5 【服务】：9.0 【态度】：10.0 【环境】：8.0 【综合】：9.08 【过程】：约了嘉怡的头课，提前到了嘉怡还没睡醒害我罚站了一会儿，本来有点不高兴，但是看到她的时候就烟消云散了，就是这么没有原则。妹妹脱完衣服，突然发现还是童颜巨乳，很大，很嫩。陪洗完开始服务，课表上除了丝袜制服其他都有，毕竟嫩妹那些活儿就那样，但是态度特别好，性格也很开朗。带上雨伞开始妹妹坐上来的时候，发现有点新疆人的感觉，而且特别耐看，随后换了传教，最后在后入的时候出货了。妹妹不催，也比较耐，配合的很好。很满意的一次出击！
❤1
优惠100活动还在哦 哥哥们约起来😘😘😘
❤1
Showing the 12 most recent of 15 posts we hold for @xiaoxuedpyq1. 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 — 638,239 of 1,480,688entries 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.
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 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“嘉怡的朋友圈” (@xiaoxuedpyq1), 828 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/xiaoxuedpyq1.
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.