Telegram RegisterThe public register of Telegram

Channel

开云体育官方频道 kaiyun

@kaiyun

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,160subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001691124367
TypeChannel
Username@kaiyun
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/kaiyun

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 65% 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.

Content that also appears on other registered channels

Posts published here appear word for word on 3 other registered channels. They sit inside a group of 5 channels that share the same post bodies with each other. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@J9yaya/46229 Jul 2026, 06:14 UTC@kaiyun/2301 · this entry29 Jul 2026, 10:41 UTC1.004.4 hours
@kaiyun/2302 · this entry2 Aug 2026, 08:19 UTC@J9yaya/4652 Aug 2026, 08:54 UTC1.0035 minutes
@J9yaya/4663 Aug 2026, 05:43 UTC@kaiyun/2303 · this entry3 Aug 2026, 06:47 UTC1.0064 minutes
@J9yaya/4674 Aug 2026, 07:49 UTC@kaiyun/2304 · this entry4 Aug 2026, 09:41 UTC1.001.9 hours
@J9yaya/4685 Aug 2026, 06:30 UTC@kaiyun/2305 · this entry5 Aug 2026, 06:38 UTC1.009 minutes
@J9yaya/4697 Aug 2026, 06:59 UTC@kaiyun/2306 · this entry7 Aug 2026, 09:07 UTC1.002.1 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@J9yaya6 (6/6 hand-verifiable sample passed)1.0088 minutes@J9yaya (51)
@titankuaibao6 (6/6 hand-verifiable sample passed)1.002.7 hours@titankuaibao (60)
@ybergou5 (5/5 hand-verifiable sample passed)1.002.1 hours@ybergou (50)

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. 2 of the 16 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 14 comparable posts for this entry, running 14 July 2026 to 7 August 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 5, the earliest publisher we hold is @J9yaya. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

1,1601,1641,1627 August 2026 — 1,164 subscribers7 August 2026 — 1,164 subscribers7 August 2026 — 1,162 subscribers11 August 2026 — 1,160 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -4. 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 1,159–1,165 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:311,160-2
7 Aug 2026, 17:081,162-2
7 Aug 2026, 10:021,164no change
7 Aug 2026, 09:491,164first reading

Engagement

20 posts held, back to 14 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.3%
avg views ÷ 1,160 subscribers
Avg views / post
189
18 posts measured
Reaction rate
0.207%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 4 of 18 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (14 July 20267 August 2026)
Views total3,408
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 10:02 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.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

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 4 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 2reactions 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 14 July 2026 to 7 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.

Recent posts

7 Aug 2026, 09:07 UTC22 viewsread 7 August 2026

⚽️8月8日足球赛事精选⚽️ 【挪威超 01:00】桑讷菲尤尔 vs KFUM奥斯陆🔥🔥 桑讷菲尤尔主场阵形严密中前场衔接流畅逼抢积极! 👉盘口推荐:桑讷菲尤尔-0/0.5@1.82 【荷甲 02:00】坎布尔 vs SBV精英🔥🔥 SBV精英中前场推进有序硬实力占优! 👉盘口推荐:SBV精英0@2.00 【葡超 03:15】埃斯托里尔 vs 法马利康🔥🔥 埃斯托里尔坐镇主场防守端稳扎稳打力求首胜! 👉盘口推荐:埃斯托里尔+0/0.5@1.83 【日职J1联 18:00】名古屋鲸鱼 vs 清水心跳🔥🔥 清水心跳防线收缩迅捷战术韧性十足! 👉盘口推荐:清水心跳+0/0.5@2.06 【韩K1联 19:00】金泉尚武 vs 首尔FC🔥🔥 首尔FC高居榜首实力雄厚配合默契! 👉盘口推荐:首尔FC-0.5@1.97 【中超 20:00】云南玉昆 vs 成都蓉城🔥🔥 云南玉昆主场气势如虹防守体系严密! 👉盘口推荐:云南玉昆+

5 Aug 2026, 06:38 UTC95 viewsread 7 August 2026

中北美杯 10:30 温哥华白浪 球半 亚特兰特 推荐:温哥华白浪 -1.5 俄杯 23:30 莫斯科斯巴达 球半 奥伦堡加索维克 推荐:莫斯科斯巴达 -1.5 俄杯 23:30 沃罗涅日火炬 受半球 莫斯科迪纳摩 推荐:莫斯科迪纳摩 -0.5 欧冠杯 00:30 奥胡斯 半/一 萨巴赫 推荐:奥胡斯 -0.5/1 欧协联 01:00 布兰 半/一 阿波罗利马索尔 推荐:布兰 -0.5/1 俄杯 01:45 克拉斯诺达尔 一球 格罗兹尼特里克 推荐:克拉斯诺达尔 -1 俄杯 01:45 圣彼得堡泽尼特 一/球半 巴蒂卡 推荐:圣彼得堡泽尼特 -1/1.5 欧冠杯 02:00 费内巴切 球半 格拉茨风暴 推荐:费内巴切 -1.5 冰岛超 02:00 凯夫拉维克 半球 阿古雷利 推荐:凯夫拉维克 -0.5 欧罗巴杯 02:15 费伦茨瓦罗斯 半/一 扎布热矿工 推荐:费伦茨瓦罗斯 -0.5/1 欧协联 02:30

4 Aug 2026, 09:41 UTC96 viewsread 7 August 2026

⚽️8月5日足球赛事精选⚽️ 【欧冠资 00:00】米亚尔比 vs 布拉迪斯拉发🔥🔥 米亚尔比主场阵形严密中前场衔接流畅! 👉盘口推荐:米亚尔比-0.5@2.03 【欧冠资 01:30】索菲亚列夫斯基 vs 海拉提🔥🔥 海拉提后防收缩果断防守反击犀利韧性十足! 👉盘口推荐:海拉提+0.5/1@1.99 【欧冠资 02:00】圣吉罗斯 vs 博多格林特🔥🔥 博多格林特客场高位压制掌控比赛节奏! 👉盘口推荐:博多格林特+0/0.5@1.98 【欧联资 03:00】拉恩 vs 伊比利亚1999🔥🔥 拉恩坐镇主场战意高涨中后场防守稳扎稳打! 👉盘口推荐:拉恩+0/0.5@1.83 【哥伦甲 09:20】百万富翁 vs 帕斯托体育🔥🔥 百万富翁主场气势如虹火力全开攻势犀利! 👉盘口推荐:百万富翁-1@2.00 【俄罗斯杯 23:30】莫斯科斯巴达 vs 奥伦堡🔥🔥 莫斯科斯巴达主场统治力强锋线多点开花! 👉盘口推荐:莫斯科斯巴

3 Aug 2026, 06:47 UTC113 viewsread 7 August 2026

俄甲 22:00 乌法 平/半 卡马斯 推荐:乌法 -0/0.5 罗甲 23:30 克卢日大学 半球 博托沙尼 推荐:克卢日大学 -0.5 芬超 00:00 塞伊奈约基 受平/半 赫尔辛基 推荐:赫尔辛基﹣0/0.5 匈甲 00:30 萨拉格斯基 受平/半 保克什 推荐:保克什 -0/0.5 瑞典超 01:00 尤尔加登 一/球半 瓦斯特拉斯 推荐:尤尔加登 -1/1.5 瑞典超 01:00 哈尔姆斯塔德 受一/球半 天狼星 推荐:天狼星 -1/1.5 挪甲 01:00 兰黑姆 受平/半 海于格松 推荐:海于格松 -0/0.5 丹麦超 01:00 欧登塞 半球 桑德捷斯基 推荐:欧登塞 -0.5 波兰超 01:00 克拉科维亚 平/半 什切青 推荐:克拉科维亚 -0/0.5 瑞典甲 01:05 奥雷布洛 平/半 韦纳穆 推荐:奥雷布洛 -0/0.5 苏超 02:30 凯尔特人 两球 邓迪FC 推荐:凯尔特人

2 Aug 2026, 08:19 UTC115 viewsread 7 August 2026

美职业 10:30 洛杉矶银河 平/半 达拉斯FC 推荐:洛杉矶银河 -0/0.5 美职业 10:30 波特兰伐木者 平手 西雅图海湾人 推荐:波特兰伐木者 +0 墨西联秋 11:00 蓝十字 球半 亚特兰特 推荐:蓝十字 ﹣1.5 中超 18:00 青岛西海岸 半/一 青岛海牛 推荐:青岛西海岸 -0.5/1 韩K联 18:30 大田市民 一球 光州FC 推荐:大田市民 -1 韩K联 18:30 济州SK 受平/半 仁川联队 推荐:仁川联队 -0/0.5 韩K联 18:30 蔚山HD 半球 FC安养 推荐:蔚山HD -0.5 韩K2联 18:30 安山小绿人 受平/半 金海 推荐:金海 -0/0.5 韩K2联 18:30 釜山偶像 受平/半 首尔衣恋 推荐:首尔衣恋 -0/0.5 韩K2联 18:30 金浦市民 半球 庆南FC 推荐:金浦市民 -0.5 中超 19:35 辽宁铁人 受平/半 上海申花 推荐:

29 Jul 2026, 10:41 UTC200 viewsread 7 August 2026

欧协联 22:30 杜卡吉尼 受一球 卢加诺 推荐:卢加诺 -1 欧冠杯 23:00 阿拉木图凯拉特 平/半 奥莫尼亚 推荐:阿拉木图凯拉特 -0/0.5 芬甲 23:30 MP米克力 平/半 卡亚尼卡帕 推荐:MP米克力 -0/0.5 欧冠杯 00:00 考诺萨基列斯 半/一 克拉克斯维克 推荐:考诺萨基列斯 -0.5/1 欧冠杯 01:00 波兹南莱赫 半/一 奥胡斯 推荐:波兹南莱赫 -0.5/1 欧协联 01:00 哥本哈根 半/一 普莱西亚 推荐:哥本哈根 -0.5/1 欧冠杯 01:30 贝尔谢巴夏普尔 半/一 维京古尔 推荐:贝尔谢巴夏普尔 -0.5/1 欧冠杯 01:30 克拉约瓦大学 半球 索非亚列夫斯基 推荐:克拉约瓦大学 -0.5 阿甲 01:30 巴拉卡斯中央队 平/半 阿尔多斯维 推荐:巴拉卡斯中央队 -0/0.5 欧冠杯 02:00 扎布热矿工 受一球 费内巴切 推荐:费内巴切 -1

25 Jul 2026, 05:41 UTC268 views0 reactionsread 7 August 2026
Photo

🅥开云体育作为亚洲最大持有合法牌照的投注平台 🅥 致力于为玩家提供专业,安全,丰富的游戏服务 🅥 体育,真人,电竞,棋牌,电子等上千款服务应有尽有。 🅥 开云体育邀请你共创财富。 🅥 开云官方频道: @kaiyun 🅥 开云官网链接: http://43kyty.com 🅥 优惠福利: 首存+官网+复存 彩金 等级平移 空降嫩模 🅥 温馨提示: 国外IP限制 点击 下载VPN​

25 Jul 2026, 05:41 UTC192 viewsread 7 August 2026

澳维超 13:00 墨尔本城青年队 受一球 艾云达尔 推荐:艾云达尔 -1 澳维超 15:00 丹德农迅雷 受半/一 阿东那 推荐:阿东那 -0.5/1 中超 17:30 青岛海牛 平手 天津津门虎 推荐:青岛海牛 +0 韩K联 18:30 金泉尚武 受平/半 大田市民 推荐:大田市民﹣0/0.5 韩K联 18:30 浦项制铁 受平/半 全北现代 推荐:全北现代 -0/0.5 韩K2联 18:30 釜山偶像 受平/半 水原三星 推荐:水原三星 -0/0.5 韩K2联 18:30 大邱FC 半球 水原FC 推荐:大邱FC -0.5 韩K2联 18:30 华城FC 平/半 忠南牙山 推荐:华城FC -0/0.5 韩K2联 18:30 全南天龙 平手 庆南FC 推荐:庆南FC +0 俄超 19:00 莫斯科迪纳摩 一/球半 苏苏维埃之翼 推荐:莫斯科迪纳摩 -1/1.5 中超 19:35 辽宁铁人 半球 青岛西海岸

24 Jul 2026, 05:48 UTC201 views1 reactionsread 7 August 2026

澳维超 17:30 格林古利 受半球 丹德农市 推荐:丹德农市 -0.5 澳维超 17:30 黑德堡 一球 乔治十字 推荐:黑德堡 -1 澳维超 17:30 圣奥尔本斯圣特斯 受半/一 休城 推荐:休城 -0.5/1 澳维超 18:15 欧克莱卡诺 一球 南墨尔本 推荐:欧克莱卡诺 -1 澳维超 18:30 普雷斯顿莱恩 球半 班特列 推荐:普雷顿莱恩 -1.5 东南锦 21:30 东帝汶 受三球半/四 越南 推荐:越南 -3.5/4 罗甲 23:30 阿拉德联队 平/半 加拉茨钢铁 推荐:阿拉德联队 -0/0.5 芬超 00:00 雅罗 受平/半 塞伊奈约基 推荐:塞伊奈约基 -0/0.5 丹麦甲 00:00 瓦埃勒 半/一 AB格莱萨克瑟 推荐:瓦埃勒 -0.5/1 俄超 01:00 莫斯科中央陆军 半球 巴蒂卡 推荐:莫斯科中央陆军 -0.5 瑞典超 01:00 瓦斯特拉斯 一/球半 奥尔格里特 推荐:

1

19 Jul 2026, 08:15 UTC275 views1 reactionsread 7 August 2026
Photo

【7月20日 3点整 世界杯 西班牙 vs 阿根廷】 全场让球:阿根廷+0/0.5@1.96 全场大小:大2/2.5@2.03 推荐比分:2-2

1

19 Jul 2026, 08:15 UTC248 viewsread 7 August 2026

⚽️7月20日足球赛事精选⚽️ 【冰岛超 00:00】雷克雅未克 vs 斯塔尔南🔥🔥 斯塔尔南力保不失加强整体防守! 👉全场让球:斯塔尔南+1@2.01 【罗马甲 00:30】佩特罗鲁 vs 布加勒斯特迪纳摩🔥🔥 佩特罗鲁主场优势进攻火力全开! 👉盘口推荐:佩特罗鲁+0/0.5@2.06 【塞尔超 01:00】苏杜利察 vs 鲁卡尼马拉多特🔥🔥 鲁卡尼马拉多特已斩获八连胜气势如虹! 👉盘口推荐:鲁卡尼马拉多特+0.5@1.90 【世界杯 03:00】西班牙 vs 阿根廷🔥🔥 西班牙防守稳固传控能力强表现稳定! 👉盘口推荐:西班牙-0/0.5@1.94 【秘鲁甲 08:00】利马联盟 vs 万卡约体育🔥🔥 利马联盟进攻思路明确空间利用能力突出! 👉盘口推荐:利马联盟-1/1.5@1.95 【芬兰超 23:00】TPS杜古 vs 埃尔维斯🔥🔥 埃尔维斯防守稳固配合默契韧性十足! 👉盘口推荐:埃尔维斯0@1.91

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

Citation-graph rank

Citation-graph rank — 139,289 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 5 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.

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

“开云体育官方频道 kaiyun” (@kaiyun), 1,160 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/kaiyun.

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.