Channel
@xndsisi
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
254subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002868289820 |
|---|---|
| Type | Channel |
| Username | @xndsisi |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/xndsisi |
Politics & activism — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 9 Oct 2026, 23:40 | 254 | -2 |
| 29 Sept 2026, 08:22 | 256 | +1 |
| 12 Sept 2026, 19:20 | 255 | +6 |
| 4 Sept 2026, 18:39 | 249 | +1 |
| 28 Aug 2026, 23:05 | 248 | +3 |
| 21 Aug 2026, 11:04 | 245 | +1 |
| 8 Aug 2026, 09:46 | 244 | no change |
| 7 Aug 2026, 21:31 | 244 | first reading |
5 posts held, back to 1 November 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 18 March 2026. An engagement rate over an empty window would be a number about nothing.
10 reactions across 2 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 3 of the 5 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 1 November 2025 to 18 March 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.
补充几个特别有意思的小细节，让你们看看这帮警察有多有好玩： 2025.10.31，当时不是给我断水断电嘛，断电他们承认，断水死活不承认，最后我找物业，物业也说没断水，然后让物业派人去总水阀，就是总水阀被关了，我倾向于认为他们的人可能刚好遇到了物业的水电工，让他给我断水，既没上报物业，也没跟领导说，讲真管理挺失败的 2025.11.06，拿着违法的搜查令到处搜也就算了，连垃圾桶都不放过，被带走的时候看见他们在楼下翻我的大号垃圾袋，因为垃圾袋很大，所以我很久才会倒一次垃圾，里面还有我的排泄物😥（给我断水了，没法冲马桶，我在垃圾袋里解决一下很正常吧）在垃圾袋里面发酵好多天了哥们，都是他们刚来那两天的，这帮人是想在我家搜到毒品还是想搜到啥😓 2025.11.06，我当时不是六天六夜没吃饭吗？那天中午在徐圩分局吃的，给我打的菜是辣椒炒鸡蛋，而且还挺辣的，我本来就饿得胃疼，不吃又饿的难受，我敢说绝对是故意的，我就不信徐圩分局食堂只有辣…
我一个违反治安管理处罚法的，往我手机电脑里装监控软件实时监控我？ 后续：2025，11.06日带着违法的搜查令破门，公安机关搜查令必须是刑事案件，我是行政，法律规定无搜查令不允许破门，不允许查看手机电脑内容，这是法律有明文规定的 当天至少八个警察起步，防爆叉防爆盾，外面还有无人机，带头市局的人身穿防弹衣，身上配枪，一大早六点多吧，开始破门，听到声音我马上开门，所以锁没被完全砸坏，不得不说我这个电子锁质量是真牛逼，被砸了两次，锁芯都坏了，屏幕裂了都还能正常使用 他们自己也跟我说这是抓杀人犯的待遇，我说实话，一般杀人犯没这待遇😁没把我送派出所，给我送徐圩分局去，他们聊天的时候说是某局长亲自交代的😁行政拘留十日，加手机电脑没收三十天 哦对了，传唤不是只能24小时吗？超出24小时之后，他们给我带到警车上在外面呆了从早上五六点吧，到晚上六七点，这个违不违规啊，没搜索过，就这还四个警察两辆警车看着我呢😁 先是做出下面的1234578…
❤5
往上滑😁 连云港公安对我的违法违规行为： 1.搜查令违法+非法侵入住宅（无搜查令不得破门，且公安机关的搜查令必须是刑事案件） 2.搜查过程违规（搜查无见证人，搜查主卧时我不在，被偷的钥匙就在主卧的电脑桌上，我被带走后还在我家长时间逗留） 3.搜查时偷走我家的钥匙，并拒不承认（拿着违法的搜查令到你家违法破门，强行控制住你，然后拿走你家的钥匙，这算入室盗窃还是入室抢劫呀🥰） 4.对我和我的父母进行恐吓骚扰，严重影响工作生活 5.东辛农场派出所民警于文晗记笔录时全程恐吓我，对笔录进行断章取义，无中生有，笔录都记好了，签字确认好了，突然修改然后跟我说就只有那几个地方改了，其他没有修改的地方你不用看，但我还是一个字一个字的看，果然发现他直接给我加了从来没说过的话🤣我让他改，他就说这个不影响的，最后非常嚣张的说 ——我就不改，你能把我怎么样？我看个笔录还找各种理由催促我，一直凶狠的瞪着我🤣（中国属于重笔录，轻证据，一份笔录就能给你定罪，为…
❤5
刘永红152201196902241057： 13894684097 13321578756 13384360520（刘永红之母程淑珍使用） 13321578770（舔狗王伟杰使用） 孙丽云152201196407214027： 空 刘思慧152201199407301087： 17843360699（注销） 18844127353 18389597306（注销） QQ号： 924299495 1558512838 微信号： xndsisi0703 学校宿舍： 海口海南大学8号学生宿舍楼404室 吉林省长春市高新技术开发区吉林大学前进南区南苑五舍C区405 家庭地址： 白城市火车站心悦城公寓 吉林省长春市宽城区华源公园一号二期 吉林省长春市朝阳区前进街道阳光城日丽园11栋5单元716 刘思慧已关闭账号搜索功能并禁止添加好友，连QQ邮箱都注销了，所以胁迫请打电话，发短信
庆祝100人简单发点什么吧 刘思慧全家户籍剩余的人 姓名:刘丽影（刘思慧爸爸的妹妹） QQ号: 3099778677 手机号运营商: 中国移动 手机号归属地: 吉林省白城市 手机号: 15834626868 地址: 吉林省白城市镇赉县镇赉镇吉林省白城市镇赉县苇海综合门诊 姓名:孟南（刘丽影的儿子） 地址: 高校 长治医学院 医学检验学系 手机号运营商: 中国电信 手机号归属地: 吉林省白城市 手机号: 18043668617 姓名:冯洁（刘思慧妈妈的妹妹） 身份证:152221197110011229 手机号:13894684197 号码归属地:吉林白城(中国移动)
Showing the 5 most recent of 5 posts we hold for @xndsisi. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“曝光母狗 刘思慧” (@xndsisi), 254 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/xndsisi.
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.