Telegram RegisterThe public register of Telegram
Telegram profile photo for 酷可云

Channel

酷可云

@kukeyun

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

924subscribers

+33 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003695363137
TypeChannel
Username@kukeyun
CreatedBetween 1 December 2025 and 11 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/kukeyun

Topic

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

889924906.57 August 2026 — 891 subscribers8 August 2026 — 891 subscribers22 August 2026 — 889 subscribers30 August 2026 — 912 subscribers7 September 2026 — 922 subscribers15 September 2026 — 924 subscribers7 August 202615 September 2026
6 measurements spanning 39 days, net +33. 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 884–929 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 11:58924+2
7 Sept 2026, 21:20922+10
30 Aug 2026, 04:25912+23
22 Aug 2026, 09:52889-2
8 Aug 2026, 01:05891no change
7 Aug 2026, 18:48891first reading

Engagement

20 posts held, back to 11 May 2026the 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 20 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

18 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 38.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍738.9%
633.3%
💩211.1%
😁211.1%
🥰15.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 9 of the 20 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 20 most recent posts we hold, published 11 May 2026 to 10 July 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

10 Jul 2026, 13:25 UTC846 viewsread 8 August 2026
File

⏱️测试耗时= 109s ⏱️总体耗时= 194s #uid_8441508441 #timestamp_1783689704

10 Jul 2026, 13:21 UTC800 viewsread 8 August 2026
File

⏱️测试耗时= 114s ⏱️总体耗时= 138s #uid_8441508441 #timestamp_1783689498

10 Jul 2026, 13:17 UTC771 viewsread 8 August 2026
File

⏱️测试耗时= 163s ⏱️总体耗时= 201s #uid_8441508441 #timestamp_1783689217

6 Jul 2026, 14:53 UTC825 viewsread 8 August 2026
File

⏱️测试耗时= 107s ⏱️总体耗时= 131s #uid_8441508441 #timestamp_1783349447

6 Jul 2026, 14:45 UTC747 viewsread 8 August 2026
File

⏱️测试耗时= 116s ⏱️总体耗时= 145s #uid_8441508441 #timestamp_1783348962

3 Jul 2026, 17:54 UTC915 views4 reactionsread 8 August 2026

📢 套餐调整公告 各位用户好: 非常抱歉,近期由于运营策略调整不够准确,导致平台套餐定价不够合理。 为了更符合市场需求,也让平台能够长期稳定运营,我们已对套餐进行重新调整。 🎁 套餐升级说明 以下套餐均支持 月付 / 季付 / 年付: - 2 元 / 128G:已开放月付、季付、年付 - 3 元 / 196G → 升级为 3 元 / 256G - 4 元 / 256G → 升级为 4 元 / 386G - 6 元 / 386G → 升级为 6 元 / 512G - 8 元 / 640G → 升级为 8 元 / 768G ✅ 价格不变,流量升级 🔁 已购用户说明 已购买且仍在有效期内的用户,系统将自动升级对应套餐。 无需额外付费,也无需手动操作。 🎉 邀请返利 如果你觉得平台好用,欢迎分享给朋友一起使用。 好友消费后,你可获得其消费金额 10% 循环返利。 感谢大家一直以来的支持与理解 ❤️ 我们

👍3🥰1

2 Jul 2026, 16:46 UTC835 viewsread 8 August 2026
File

⏱️测试耗时= 75s ⏱️总体耗时= 113s #uid_8441508441 #timestamp_1783010335

22 Jun 2026, 13:00 UTC≈1,150 views2 reactionsread 8 August 2026

📢 节点优化公告 各位用户好: 我们已完成新一轮节点优化,本次优化后,整体节点稳定性将有明显提升 ✅ --- 🚀 电信用户专项优化 针对电信用户,我们新增了 **微软云马来西亚中转入口**,可进一步提升电信线路的连接速度与使用体验。 目前使用马来西亚中转入口的节点为: - 🇸🇬 新加坡|02 - 🇯🇵 日本|02 相比原有线路,电信用户访问以上节点时,网速预计会有较大提升。 --- ⚠️ 使用提示 由于该入口为共享入口,可能会出现 IP 被封禁或缓存未及时刷新的情况。 如遇到 新加坡|02 / 日本|02 无法连接,建议先尝试: 1. 更新订阅 2. 刷新客户端缓存 3. 重新连接节点 --- 感谢大家的支持与理解 ❤️ 祝大家使用顺畅,连接稳定 🚀

1💩1

20 Jun 2026, 07:08 UTC≈1,040 views2 reactionsread 8 August 2026

📢 订阅地址更新通知 各位用户好: 由于服务升级,我们已弃用部分旧订阅服务域名。 为避免影响正常使用,6 月 1 日前注册的用户,请前往 kukeyun.cc 重新获取最新订阅地址。 ✅ 操作方式: 登录站内 → 复制新的订阅地址 → 更新到客户端 感谢大家的理解与支持 🙏

😁2

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

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.

17 Jun 2026, 17:40 UTCAnonymous Poll112 voters

请问您是否需要三网优化线路

  1. 不需要10%
  2. 需要93%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 20 most recent posts we hold, published 11 May 2026 to 10 July 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

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.

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

“酷可云” (@kukeyun), 924 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/kukeyun.

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.