Telegram RegisterThe public register of Telegram
Telegram profile photo for 刘油&顺意のcos收藏

Channel

刘油&顺意のcos收藏

@aikan_cos

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

33,244subscribers

+11,559 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003786672554
TypeChannel
Username@aikan_cos
Description个人XP(主cos),电报/不知名小网站搜罗收集 以及群友投稿 大多是二编压缩版 投稿机器人 @shunyi_153bot
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 30 September 2026
On Telegramt.me/aikan_cos

Topic

Gaming — 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 31% 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.

Observations

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.

Views per post sit far above this size band

15,900 average views per post against 33,244 subscribers — an engagement rate of 47.9%. Across the 1,257 registered channels in the same cohort — 31,624–99,831 subscribers, posting mainly in Chinese — the middle half sit between 0.974% and 5.62%, with a median of 2.55%.

What this was computed from
Window30 days (2 September 2026 – 2 October 2026)
Posts measured37 of 37 published in the window (0 exact, 37 rounded by Telegram)
Views totalled588,940
Mature posts only63.7% over 25 posts read at least 24h after publication
Subscribers33,244 measured 30 September 2026
Cohortb31623:zho · 1,257 channels · p10 0.297% · p25 0.974% · p50 2.55% · p75 5.62% · p90 11.4%
Position in cohort99.761th percentile · 18.8× the cohort median
Uncertainty±0.024% of the figure, from Telegram’s rounding
Post languageChinese · 95.8% 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 2 October 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.

Growth

21,68533,24427,464.57 August 2026 — 21,685 subscribers7 August 2026 — 21,685 subscribers8 August 2026 — 21,755 subscribers9 August 2026 — 22,004 subscribers10 August 2026 — 22,203 subscribers11 August 2026 — 22,403 subscribers12 August 2026 — 22,739 subscribers13 August 2026 — 23,017 subscribers14 August 2026 — 23,403 subscribers16 August 2026 — 23,820 subscribers17 August 2026 — 24,151 subscribers18 August 2026 — 24,355 subscribers19 August 2026 — 24,605 subscribers20 August 2026 — 24,841 subscribers22 August 2026 — 25,172 subscribers24 August 2026 — 25,762 subscribers25 August 2026 — 25,997 subscribers26 August 2026 — 26,278 subscribers27 August 2026 — 26,535 subscribers28 August 2026 — 26,768 subscribers29 August 2026 — 26,968 subscribers30 August 2026 — 27,219 subscribers31 August 2026 — 27,455 subscribers1 September 2026 — 27,648 subscribers2 September 2026 — 27,808 subscribers3 September 2026 — 27,976 subscribers4 September 2026 — 28,221 subscribers7 September 2026 — 28,767 subscribers10 September 2026 — 29,397 subscribers12 September 2026 — 29,789 subscribers14 September 2026 — 30,073 subscribers15 September 2026 — 30,364 subscribers18 September 2026 — 30,661 subscribers30 September 2026 — 33,244 subscribers7 August 202630 September 2026
34 measurements spanning 53 days, net +11,559. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19,951–34,978 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
30 Sept 2026, 04:1833,244+2,583
18 Sept 2026, 03:3930,661+297
15 Sept 2026, 22:0230,364+291
14 Sept 2026, 03:5630,073+284
12 Sept 2026, 12:1829,789+392
10 Sept 2026, 10:1629,397+630
7 Sept 2026, 03:5928,767+546
4 Sept 2026, 14:5928,221+245
3 Sept 2026, 04:2927,976+168
2 Sept 2026, 03:0427,808+160
1 Sept 2026, 05:5527,648+193
31 Aug 2026, 07:1427,455+236
30 Aug 2026, 06:3527,219+251
29 Aug 2026, 04:2526,968+200
28 Aug 2026, 07:4726,768+233
27 Aug 2026, 05:2826,535+257
26 Aug 2026, 02:4426,278+281
25 Aug 2026, 05:4725,997+235
24 Aug 2026, 02:0325,762+590
22 Aug 2026, 10:4625,172first reading

Engagement

105 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 98 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
47.9%
avg views ÷ 33,244 subscribers
Avg views / post
15,900
37 posts measured
Reaction rate
0.122%
reactions ÷ views · ER floor
Posts in window
37
of 105 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 October 2026
Posts held105 (2 August 2026 – 1 October 2026)
Views total588,940
Reactions total719
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Oct 2026, 20:19 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.

What this channel posts

Photos
689
Videos
24
Links
163

Lifetime counters from Telegram’s own channel header, read 1 October 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.

Video runtime
28s
Average length
9s

Measured directly from 3 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.

Reaction mix

1,615 reactions across 95 posts, in 22 distinct kinds. The most used accounts for 66.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,06666.0%
👍24815.4%
🗿654.02%
❤‍🔥533.28%
🫡432.66%
🔥251.55%
🥰251.55%
🤩191.18%
💩181.11%
😁80.495%
🥴80.495%
🍌60.372%
👏60.372%
🤮60.372%
🐳50.31%
🌭40.248%
🕊30.186%
👎20.124%
🙈20.124%
⚡10.062%
2 further kinds20.124%

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 99 of the 105 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 1,615 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 105 most recent posts we hold, published 2 August 2026 to 1 October 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.

Recent posts

1 Oct 2026, 08:16 UTC≈6,370 views17 reactionsread 1 October 2026
Photo

#糯米奶麻薯 #索拉里斯最强妈妈 3荤2素 评论区查看详细

👍10❤7

1 Oct 2026, 05:23 UTC≈7,350 views9 reactionsread 1 October 2026

我靠 小号登录凭证掉了😭 之前买完之后没改自动终止会话。 刚刚重登要邮箱验证。那邮箱我哪有啊。注销邮箱还得等一周

👍5🕊3❤1

28 Sept 2026, 17:46 UTC≈14,900 views99 reactionsread 1 October 2026

一v一

❤‍🔥53💩15❤7🗿7👍5🌭4🐳4🥴3

27 Sept 2026, 03:28 UTC≈20,800 views44 reactionsread 1 October 2026
Photo

#小甜菜 #jiujiuo0 #菜菜 正片流出 27V+23sV+57P 重制版 原主X https://x.com/jiujiuo0 宝藏博主 非常值得投喂 #cos #妮露 #绮良良 #瑶 #时之愿境 #守岸人 #菲比 #流萤 #春日来信 #申鹤 #冷花幽露 #云璃 #符玄 #四系乃 #四季夏目 #克鲁鲁 #cos #原神 #王者荣耀 #鸣潮 #崩坏星穹铁道 #崩铁 #约会大作战 #星光咖啡馆与死神之蝶 #终结的炽天使 评论区查看详细

❤44

27 Sept 2026, 03:00 UTC≈17,000 views15 reactionsread 1 October 2026
Photo

#小甜菜 #jiujiuo0 #菜菜 X作品 26年 荤 xp #原味 评论区查看详细

❤15

27 Sept 2026, 02:53 UTC≈16,300 views9 reactionsread 1 October 2026
Photo

#小甜菜 #jiujiuo0 #菜菜 X作品 25年 荤 xp #原味 尿湿内裤 #お漏らし #露出 #放尿 评论区查看详细

❤9

27 Sept 2026, 02:31 UTC≈19,100 views8 reactionsread 1 October 2026
Photo

#小甜菜 #jiujiuo0 #菜菜 X作品 21年~24年 半绿 原主X https://x.com/jiujiuo0 宝藏博主 非常值得投喂 xp #原味 #生理期 #露出 尿湿内裤 #お漏らし 评论区查看详细

❤6👍2

26 Sept 2026, 17:08 UTC≈17,100 views28 reactionsread 1 October 2026
Photo

#玥下 #反差玥玥 粗稿 XP #淫妻 #绿帽 #多人 #换妻 评论区查看详细

❤22👍3💩3

26 Sept 2026, 16:55 UTC≈16,100 views12 reactionsread 1 October 2026

副频改更少萝了(不常更) 感兴趣也可以看看↓ https://t.me/aikan_z7z8/198 对了 关注大本营喵↓ https://t.me/shunyi_plus

👍7😁2❤1🤯1🥰1

24 Sept 2026, 16:29 UTC≈21,100 views35 reactionsread 30 September 2026
Photo

#桃谷若姬子 旧作重制版 - 补全了遗漏的视频 - 增加了明确的分类 - 部分视频替换了更清晰版本 视频资源直达↓ https://t.me/+BuJJ7w23VqoyZWVk 图948P 放评论

❤28👍7

Showing the 12 most recent of 105 posts we hold for @aikan_cos. 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.

Posts edited after publishing

@aikan_cos edited 10 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
27 September 2026

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

12 Aug 2026, 09:19 UTCAnonymous Poll989 voters

话说群友们知道往期内容更新吗

  1. 知道25%
  2. 不知道75%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 105 most recent posts we hold, published 2 August 2026 to 1 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

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.

Cite this entry

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 30 September 2026 — this entry's latest reading, not the date you are reading this.

“刘油&顺意のcos收藏” (@aikan_cos), 33,244 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/aikan_cos.

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.