手机号∶18790270162 这个人没妈妈了,有没有人去安慰他一下?
👍2
Signed 小 天

Channel
@XiaoYipd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16,000subscribers
-868 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001833836879 |
|---|---|
| Type | Channel |
| Username | @XiaoYipd |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/XiaoYipd |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 12:59 | 16,000 | -35 |
| 8 Sept 2026, 20:59 | 16,035 | -68 |
| 5 Sept 2026, 15:41 | 16,103 | -32 |
| 3 Sept 2026, 18:00 | 16,135 | -30 |
| 2 Sept 2026, 10:16 | 16,165 | -23 |
| 1 Sept 2026, 09:43 | 16,188 | -16 |
| 31 Aug 2026, 12:36 | 16,204 | -21 |
| 30 Aug 2026, 14:05 | 16,225 | -16 |
| 29 Aug 2026, 12:18 | 16,241 | -7 |
| 28 Aug 2026, 10:03 | 16,248 | -22 |
| 27 Aug 2026, 11:55 | 16,270 | -20 |
| 26 Aug 2026, 09:07 | 16,290 | -21 |
| 25 Aug 2026, 07:04 | 16,311 | -47 |
| 24 Aug 2026, 08:53 | 16,358 | -63 |
| 22 Aug 2026, 14:16 | 16,421 | -36 |
| 21 Aug 2026, 07:09 | 16,457 | -9 |
| 20 Aug 2026, 10:12 | 16,466 | -39 |
| 19 Aug 2026, 10:12 | 16,505 | -13 |
| 18 Aug 2026, 13:17 | 16,518 | -43 |
| 17 Aug 2026, 13:43 | 16,561 | first reading |
27 posts held, back to 2 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 53 pages of 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 13 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 27 (2 July 2026 – 31 August 2026) |
| Views total | 4,783 |
| Reactions total | 31 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:03 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.
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.
42 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 39 | 92.9% | |
| ❤ | 2 | 4.76% | |
| 🔥 | 1 | 2.38% |
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 19 of the 27 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 2 July 2026 to 31 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.
手机号∶18790270162 这个人没妈妈了,有没有人去安慰他一下?
👍2
Signed 小 天
Photo, posted without a caption
👍3
Signed 小 天
云梦WebIDE 专为web网站内置APP打造 支持php8.5.1环境内置打包成APP 支持html环境内置打包成APP 支持一键网站转APP 拥有私有接口可以通过网页前端实现对接安卓原生功能 拥有php内置扩展功能 后续会更新合并arm注入的网络验证,打包的时候直接注入然后打包,敬请期待
👍2
Signed 小 天
916忆梦云商城官网 https://shop.ymy9.com/ 站长联系方式: https://a.ym0.top 商户免费成品APP卡密验证注入程序: https://arm.ymmynb.com/ (入住后有流水可以联系站长免费获取永久卡密) 🎉实力货源站或者实力项目大牛入驻可免费给广告位和置顶推荐 (入驻推荐对接商家:神西货源,晨星货源) 🔥满5即可提现 满30默认自动提现 🔥结算支持:微信/支付宝/银行卡 🔥结算时间:正常每天中午提现 🔥提现无手续费 ✨常年稳定支付三方通道 ✨支付费率可切换买家/商家承担 ✨高配服务器+cdn ✨入驻在用平台即可免费提供APP直接注入验证的程序和网络验证程序 ❇️优质高流水商户可联系站长调整费率或者开通单独费率自定义通道 ♨️减少投诉的方法:做好售后,把店铺联系方式弄成可以联系到你的,可以把你想说的话在公告里面声明 ✅拥有ICP+edi双证正规平台 ✨优质商户可提供企…
👍2
Signed 小 天
安云梯-高速代理 解决网络卡顿,推特乱码,以及IP禁 看片卡顿,解锁海外网页 欢迎使用 官网地址 https://annodeu.com 速度优化,更方便 在线客服 @xiaoanlua
👍1
Signed 小 天
平台合作易支付平台 c牛云支付 商户开户地址∶ https://cniu.cnyzf.cc/user 费率6%,无视恶意投诉 不接四大类,审核请联系公告的客服 以上是广告内容 若有其他问题可咨询我 @ymmykj
👍4
Signed 小 天
日本人手机号∶15199966765
👍5
Signed 小 天
看来重庆黑客多
👍2
Signed 小 天
梨花飘落在你窗前
👍3
Signed 小 天
我这边想写一个白嫖狗避雷站 每一个内容都包括 内容包括 白嫖狗介绍 白嫖狗联系方式 白嫖狗IP 白嫖狗账号,来源渠道(自己填) 白嫖狗账号,来源渠道(自己填) 每一个内容的白嫖狗账号可逐增 然后再底部提醒让各位老板避雷这个人建议拉黑
Signed 小 天
电话录音骂这个人一次或者把他微信下了找我拿红包 手机号∶15113263303
Signed 小 天
手机号∶13432915212 他的妈妈死了,所以他变成个孤儿了,请大家去安慰她
👍2
Signed 小 天
Showing the 12 most recent of 27 posts we hold for @XiaoYipd. 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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“小逸” (@XiaoYipd), 16,000 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/XiaoYipd.
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.