Channel
@xixi09180
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 12 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003921782615 |
|---|---|
| Type | Channel |
| Username | @xixi09180 |
| Created | 10 September 2026 — measured — dated from the channel’s first post |
| First recorded | 12 November 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xixi09180 |
Adult — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 13 November 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @xixi09189/639 Nov 2026, 10:41 UTC | @xixi09180/19 · this entry10 Nov 2026, 04:16 UTC | 1.00 | 18 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @xixi09189 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 4 minutes | @xixi09189 (5–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 8 November 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @xixi09189. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 06:22 | 2 | no change |
| 12 Nov 2026, 05:47 | 2 | first reading |
13 posts held, back to 10 September 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.
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 11 November 2026 |
|---|---|
| Posts held | 13 (10 September 2026 – 11 November 2026) |
| Views total | 202 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 06:22 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 12 November 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.
Telegram’s own ‘edited’ marker: 0 of 12 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
【花名】 #兮兮 【地址】 #成华区 【标签】 #御姐 #颜值车 #代聊 #成华区 【车牌】@xixi091888 【硬件】年龄25 身高160 体重48kg 罩杯b➕ 肤色偏白 有少量纹身（肚子上） 下面户型小蝴蝶 毛量少量 湿度中 紧度中下 人照相似8 【软件】 三件套 浅吻 水中萧 【课费】6P 11PP #6/11 【特别提醒】工兵评价 优点：皮肤光滑，手感好，颜值可以，态度好，身材不错 缺点：肚子有纹身 综合性价比：8
Photo, posted without a caption
【成都琪琪修车认证】 出击报告 基础信息 【妹子花名】：兮兮 【验证留名】：… 昆哥（资料有白嫖） 【验证时间】：2026-11-10 【所在位置】：龙湖天街 【修车水费】：6p 硬件评价 【妹子年龄】：25 【身材皮肤】：身材巴适，皮肤滑嫩 【胸器信息】：B 超级好rua 【鲍鱼信息】：小蝴蝶，水是真的多啊，一摸就出水 【人照打分】：8 【颜值打分】：8.5 软件评价 【车间环境】：民宿 【服务内容】：洗，吹，做 综合评价 【推荐程度】：9 【个人发挥】：跟代哥提前联系好，地方也很好找，逛了一圈安全还不错。进去房间看到本人和照片有一点差距，但是照片很明显是本人。 推荐点一，双人洗澡的时候各种诱惑你，摸，亲，吸无所不用其极，骚得不行，迄今为止遇到最骚的一个 推荐二，上床后吸皮过水，再来一曲水中潇简直不要太爽。先来女上，一叶扁舟摇啊摇。再来后入，拼命让我用力，再深一点随后换教室，边🐍边操，…
Photo, posted without a caption
༺ཌༀ成都俱乐部·报告模板ༀད༻ 【验证留名】：#harryhui 【老师花名】：#兮兮 【老师电报】：@xixi091888 【老师年龄】：25+ 【验证时间】：11.8 【教室位置】：#杉板桥 【修车水费】：工价 【课室环境】：酒店公寓 【是否代聊】：是 【人照相似】：8分相似，照片带点美颜 【身材赘肉】：身材苗条，肚子带一点点小赘肉 【凶器罩杯】：b 【日感反馈】：老师很主动，小逼很紧，水也多，也很配合。 【服务项目】：三件套，舌，69，菜单上都有 【机车行为】：无 【优缺点锐评】：优点：老师是成熟御姐风格，刚下水，不刻意注重服务流程，一切水到渠成，很有女友感，各种要求也都很配合。缺点： 【验证群组】： @CD_julebu 【上课过程描述】： 和老师约好时间，进去房间后，和老师简单闲聊一下，然后和老师抱着调会情，然后迫不及待去洗了澡，老师现在上面开始服务，一边舔胸一边挑逗你，眼神直勾勾的看着你，然后直接主动吻上来，直接…
成都修车·男团女团验车报告 🏷️基础信息 【老师花名】:兮兮 【老师车牌】:@xixi091888 【验证留名】:(=^▽^=) 【验证时间】:11.9 【修车水费】: 6/11 【所在位置】:成华区杉板桥 【验证群聊】:@CDCnantuannvtuan 👙软硬配置 【标签类型】:#嫩妹车 #态度车 #感觉车 #成华区 #舌吻 #6P #代聊 【老师年龄】:22 【身高身材】:身高160 体重90，身材匀称 【胸器罩杯】:胸b软手很好rua 【紧度湿度】:小穴蝴蝶逼，颜色外褐紧。 【服务项目】:陪洗，舌吻，69，爱爱。 【优点缺点】:优点 颜值高 态度好 情绪价值高 💋自由发挥 【过程描述】：位置好找，直接遥控上门，妹妹直接穿的情趣内衣迎接，聊了一会天，交完水费就去洗了，没有要陪洗，因为妹妹穿的衣服懒得让她脱了，洗完后就躺在床上，妹妹骚骚的问我要我帮忙脱还是她自己来，想吃大奶就让妹妹自己脱了，就开始干活，口活很舒…
【成都91修车学院】®专属报告 🔴基础信息 【妹子花名】：兮兮 【妹子车牌】：@xixi091888 【验证留名】：bbb l 【验证时间】：11/9 【所在位置】：东郊记忆 【修车水费】：6P 11PP 【是否代聊】：是 🟡硬件评价 【身高体重】：163，一百斤左右吧，看着不胖不瘦刚刚好 【妹子年龄】：22 【湿度紧度昆感】：蝴蝶b，阴唇较小，外褐内粉，水量正常，较紧致，有包裹感 【人照评分】：8 【颜值评分】：0 【凶器罩杯】：b杯，乳头褐色，乳晕浅褐色，轻微下垂 🟢软件评价 【环境卫生】：酒店，有一次性浴巾 【服务内容】：口，做，🐍 ，69，口砂有一点儿（比较生涩，不知道哪儿学的） 【机车行为】：无 🟣综合评价 【优点缺点】：综合来说是一个颜值中上，皮肤光滑，身材中上，够骚，技术够好，态度够好的精品车 【性价比】： 8分/满分10.0分 【推荐程度】：8分/满分10.0分 评分标准 6分为…
成都修车·男团女团验车报告 🏷️基础信息 【老师花名】:兮兮 【老师车牌】: @xixi091888 【验证留名】:阿伟 【验证时间】:11.9 【修车水费】:6P 11PP 【所在位置】:成华区杉板桥 【验证群聊】:@CDCnantuannvtuan 👙软硬配置 【标签类型】:#嫩妹车 #大蟒蛇 #颜值车 【老师年龄】:22 【身高身材】:163，90 【胸器罩杯】:B 真奶 水滴型 柔软 【紧度湿度】:蝴蝶 水很多 很紧 毛量一般。 【服务项目】:陪洗 口 舌吻 菜单都有 【优点缺点】:皮肤好 很嫩 全身很柔软 💋自由发挥 【过程描述】：约好地方，交通方便，见到老师身穿女仆装，说话热情，坐沙发聊天亲吻，然后交水费，老师放水沐浴，上床开始服务，口无齿感非常舒服，不喊停不会停，服务认真，传教士很深很紧，水也很多，最后后入出货，老师皮肤非常好，以前学过舞蹈，身体非常柔软。非常推荐值得体验。 https://t.me/CDCn…
Channel photo updated
#成都嫩妹御姐高校认证报告 【妹子花名】: 兮兮 【联系方式】:@xixi091888 【验证留名】: @yinqi1999 【验证时间】: 11/8 【所在位置】: ＃成华区＃龙湖梵城 【修车水费】: 6p 11pp 【是否代聊】: 是 【身高身材】: 165/95 【妹子年龄】: 22 【湿度紧度】: 很湿很紧 【颜值相似】: 8 真人比照片好看 【凶器罩杯】: B 【环境卫生】: 干净 【服务内容】: 陪浴 大蟒蛇 69 口 深喉 舔胸舔蛋 【机车行为】: 无 【优点缺点】: 优点:服务态度超级好 主动大蟒蛇 情绪价值高 暂无发现缺点 【性价总比】: 9分/ /满分10.0分 【推荐程度】: 9分/满分10.0分； 评分标准 6分为及格，7分为良品（考虑价格可以看一看），8分（值得价格并且建议体验），9分（实为该价位中少见的精品），10分（极品） 【个人发挥】:代哥遥控进门，老师穿了一身小裙子，真人化妆后比照片好看很多，…
成都大话修车群专属报告模板 基础信息 【妹子花名】：#兮兮 【妹子车牌】：@xixi091888 【验证留名】：🈚 【验证时间】：11.8 【所在位置】：杉板桥 【修车水费】：600/P 1100/PP 【是否代聊】：代聊 硬件信息 【身高体重】：163/ 90 【妹子年龄】：22 【湿度紧度昆度】：户型蝴蝶，外微褐内粉，高等湿度、紧度适中、日感佳 【颜值相似】： 8.5 【凶器罩杯】：胸B 软件信息 【环境卫生】: 民宿环境，干净整洁 【服务内容】：帮洗、水中箫、舔咪咪、口、69、爱爱 【机车行为】：无 综合信息 【优点缺点】：优点：皮肤光滑，态度很好，配合度高，情绪价值反馈不错 缺点：肚子上有一道手术减肥痕迹 【性价比】： 8.5 【推荐程度】：8.5 评分标准 6分为及格，7分为良品（考虑价格可以看一看），8分（值得价格并且建议体验），9分（实为该价位中少见的精品），10分（极品） 【个人发挥】：顺…
Channel name was changed to «兮兮的赛后好评»
Showing the 12 most recent of 13 posts we hold for @xixi09180. 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.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“兮兮的赛后好评” (@xixi09180), 2 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/xixi09180.
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.