#千鹤躺采 #6号技师 衣服有点丑,尺度一般,对话挺有意思 完整版见评论区
👍4

Channel
@Kiiii2025
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
33,516subscribers
+5,489 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002317684120 |
|---|---|
| Type | Channel |
| Username | @Kiiii2025 |
| Description | 分享好看的资源,欢迎关注! |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/Kiiii2025 |
Adult — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
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.
12,100 average views per post against 33,516 subscribers — an engagement rate of 36.2%. Across the 1,270 registered channels in the same cohort — 31,624–99,923 subscribers, posting mainly in Chinese — the middle half sit between 0.984% and 5.55%, with a median of 2.56%.
| Window | 30 days (30 August 2026 – 29 September 2026) |
|---|---|
| Posts measured | 16 of 16 published in the window (0 exact, 16 rounded by Telegram) |
| Views totalled | 194,010 |
| Mature posts only | 40.6% over 14 posts read at least 24h after publication |
| Subscribers | 33,516 measured 26 September 2026 |
| Cohort | b31623:zho · 1,270 channels · p10 0.292% · p25 0.984% · p50 2.56% · p75 5.55% · p90 10.9% |
| Position in cohort | 99.370th percentile · 14.1× the cohort median |
| Uncertainty | ±0.04% of the figure, from Telegram’s rounding |
| Post language | Chinese · 100.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 29 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 04:21 | 33,516 | +315 |
| 19 Sept 2026, 05:00 | 33,201 | +91 |
| 16 Sept 2026, 20:40 | 33,110 | +144 |
| 14 Sept 2026, 20:20 | 32,966 | +148 |
| 13 Sept 2026, 07:22 | 32,818 | +208 |
| 11 Sept 2026, 12:16 | 32,610 | +279 |
| 8 Sept 2026, 15:59 | 32,331 | +371 |
| 5 Sept 2026, 11:18 | 31,960 | +182 |
| 3 Sept 2026, 16:19 | 31,778 | +146 |
| 2 Sept 2026, 06:53 | 31,632 | +75 |
| 1 Sept 2026, 08:27 | 31,557 | +124 |
| 31 Aug 2026, 05:25 | 31,433 | +51 |
| 30 Aug 2026, 07:12 | 31,382 | +87 |
| 29 Aug 2026, 09:18 | 31,295 | +90 |
| 28 Aug 2026, 12:42 | 31,205 | +112 |
| 27 Aug 2026, 12:45 | 31,093 | +136 |
| 26 Aug 2026, 12:08 | 30,957 | +116 |
| 25 Aug 2026, 12:23 | 30,841 | +148 |
| 24 Aug 2026, 11:44 | 30,693 | +207 |
| 22 Aug 2026, 15:54 | 30,486 | first reading |
36 posts held, back to 2 August 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 85 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.
| Window | Rolling 30 days · latest post in window 28 September 2026 |
|---|---|
| Posts held | 36 (2 August 2026 – 28 September 2026) |
| Views total | 194,010 |
| Reactions total | 117 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 07:30 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 29 September 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.
Measured directly from 23 videos 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.
256 reactions across 35 posts, in 4 distinct kinds. The most used accounts for 91.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 235 | 91.8% | |
| 👍 | 11 | 4.30% | |
| 👏 | 8 | 3.13% | |
| 👎 | 2 | 0.781% |
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 36 of the 36 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 256 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 2 August 2026 to 28 September 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.
#千鹤躺采 #6号技师 衣服有点丑,尺度一般,对话挺有意思 完整版见评论区
👍4
#千鹤躺采 #6号技师 6号技师小姐姐的写真视频,颜值不错,熊有点小 完整版见评论区
#千鹤躺采 #28号技师 青花瓷风格旗袍配上28号小姐姐的大胸,声音放大,全程娇喘声不断 完整版见评论区
❤3
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou?start=a_6226495520
❤3
#千鹤躺采 #99号技师 99号小姐姐真的是目前最顶的一个,超高颜值加一对大胸,给大哥蹭的梆硬,后面是不是射了?内裤都湿了 完整版见评论区
❤11
#千鹤躺采 #19号技师 最新超绝视频,各种蹭🐮子,顾客直接猛猛抓住19号小姐姐的胸,对话有点太假了 完整版见评论区
❤18
#千鹤躺采 #2号技师 最新视频,尺度不错,各种蹭客户的🐮子,但2号技师的颜值一言难尽 完整版见评论区
❤6
#纯种阿江 身材不错,耐看型的美女 视频合集见评论区
❤10👍3
#野心坏蛋 身材算小巧类型,颜值ok 视频合集见评论区
❤7
#玫桃泡芙 身材不错,可惜不露脸 视频合集见评论区
❤7
#米晨姐姐 抖音性感女主播 视频合集|见评论区
❤2
擦边短剧《误入爱河》 无水印完整版 #短剧 #擦边短剧 #于添 |见评论区
❤10
Showing the 12 most recent of 36 posts we hold for @Kiiii2025. 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 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Kiiii资源分享” (@Kiiii2025), 33,516 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/Kiiii2025.
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.