Channel
@xixiit
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,312subscribers
+115 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003300543826 |
|---|---|
| Type | Channel |
| Username | @xixiit |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/xixiit |
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 19 Sept 2026, 17:18 | 2,312 | -18 |
| 14 Sept 2026, 22:37 | 2,330 | -3 |
| 11 Sept 2026, 00:57 | 2,333 | +5 |
| 5 Sept 2026, 19:00 | 2,328 | +32 |
| 2 Sept 2026, 03:52 | 2,296 | +26 |
| 30 Aug 2026, 05:18 | 2,270 | +9 |
| 27 Aug 2026, 15:24 | 2,261 | +12 |
| 24 Aug 2026, 23:18 | 2,249 | +34 |
| 21 Aug 2026, 00:54 | 2,215 | +18 |
| 20 Aug 2026, 15:00 | 2,197 | no change |
| 20 Aug 2026, 14:45 | 2,197 | first reading |
17 posts held, back to 4 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 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 17 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
18 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 83.3% | |
| 💊 | 2 | 11.1% | |
| 👍 | 1 | 5.56% |
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 12 of the 17 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 4 July 2026 to 15 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.
🐴杭州无内鬼报告模板2.0 【位置艺名】：拱墅区妮妮酱 【联系方式】：@niniya00 【喝茶留名】：哈士奇 【喝茶时间】：8月14日 【喝茶价格】：1000p 【芳龄身高】：25/163 【罩杯手感】：D 很软 【服务内容】： 课表上的都有 【优点缺点】： 很优秀的老师，身材超好，情绪价值也很到位，满满都女友感，配合度也很高 【体验细节】： 小区环境不错，进门老师会贴心的帮忙洗澡，洗澡过程中还会帮忙口，老师的嘴巴超软。洗完澡后还能自己挑选喜欢的战袍，老师的战袍琳琅满目。躺床上后又那体验老师的舌头了，技术真的超好，差点没忍住。正戏开始老师也是配合度拉满，会主动骑上来动，总之体验拉满，是会二刷三刷的宝藏老师 温馨提醒】：报告仅供参考，请理性选择，切勿对号入座。 👑👑👑无内鬼报告回收计划已启动 ，提交报告得积分1积分等于1软妹币各种白嫖半价好礼等你兑换。提交报告可助力老师入驻免费无内鬼精选榜单~更有机会入围杭州极品必刷榜 无内鬼管…
🤩🤩
👍1
是拥有“维纳斯的酒窝”的妮妮酱🎀
❤1
杭州学生会：https://t.me/students_union 【出击老师】：妮妮酱 【出击留名】：404 【出击时间】：2026-08-11 【大概位置】：西文街地铁站附近 【修车水费】：竞拍P 【高端服务】：六九、舌吻 【人照相似】：人照十分，颜值满分 【身高身材】：身高163，纹身无，腰臀比很棒，还有腰窝 【胸器罩杯】：罩杯32D很软，乳头小粉，皮肤光滑 【湿度紧度】：户型没看毛发正常，湿度不错，做爱反馈完美 【课室环境】：小区，停车还好方便（最近在修路，需要停旁边），出入无门禁 【个人卫生】：无抽烟，房间很干净，有陪浴，有浴巾/漱口水 【时间管理】：排课合理，无催客赶客，有情绪价值 【服务点评】：女友式服务，可选战袍，典型E人，笑起来很甜，水中萧，AB面，价格是合理，值得二刷 【推荐程度】：9.9 【流程细节】： 前言:赛季末的竞拍是异常激烈的，因为预告提前知晓了妮妮酱是最后一天的竞拍: 弱水三千，只取一瓢。 万…
❤1
周末愉快🤩🤩
我在杭州学生会免费上榜了https://t.me/students_union
繁花报告模板：https://t.me/HZFHLYQ 【优势】 皮肤白 服务好 性格好 【劣势】 暂时没有 🐻有一点点科技吧 【妹子花名】：妮妮酱呀 【联系方式】：@niniya00 【妹子年龄】：看着很年轻 【验证留名】：LLL 【验证时间】：7月25日 【上课费用】：1000p 【颜值】：人照9分 【身材】：165身高白皮，胸软 【服务态度】：配合度拉满 【时间管理】：课时合理 【卫生环境】：房间干净整洁 【额外加分项】：服务态度还是不错 【综合评价】：好评 【流程小文】: 这次竞拍到700券以后，纠结了好久还是选择了妮妮酱，上次结束以后就跟老师讲的下次有空再去，这次必须补上，准点到达以后先来个抱抱，嘘寒问暖了一会去洗澡，有水中萧，很舒服，服务的话也不是简单三件套，口活也是很赞，口的很有感觉，带上tt必须先后入一手，搞了几分钟快有感觉了赶紧换个姿势，几分钟以后也就没了，最近真的特优质，不到10分钟就没了，结束聊聊…
❤4
🤩🤩在线中🤩
再也不说期待夏天了🤩🤩 热死啦🤩🤩
❤2
🔣更新一下装备🔣🥵🥵
我在杭州学生会免费上榜了https://t.me/students_union
杭州基金会：https://telegram.me/Foundation_Of_HangZhou 【出击时间】：2026-07-15 【老师花名】：妮妮酱 【出击留名】：真不会搞笑（三代目） 【开课位置】：西文街地铁站附近 【修车水费】：竞拍p 【人照评分】：9 【颜值评分】：9 【身材评分】：9.5 【服务评分】：9 【态度评分】：9.5 【环境评分】：9.5 【综合评分】：9.25 【过程描述】： 老师住在一个新小区，好多都还在装修，进出方便，比较安全，房间环境也比较整洁。初见妮妮酱，还是比较惊艳，妆容精致，特别是笑容很好看。皮肤白皙，胸大，屁股也比较饱满，腹部也基本没赘肉，身材很棒。当然，感觉有点科技成分，但视觉上真的享受。然后一起洗澡，前后都帮洗，然后突然就蹲下口，很舒服。服务也还不错，特别口的技术很好，会不断用舌尖挑逗，双眼魅惑的看着你，时间也很久，直接就是梆硬。戴套后，直接女上起手，内部温热，也比较紧致，而且老师比…
❤1
Showing the 12 most recent of 17 posts we hold for @xixiit. 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“妮妮酱🥰（拱墅定金预约）” (@xixiit), 2,312 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/xixiit.
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.