Channel
@kaiyuntuidan0
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
22subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003710114692 |
|---|---|
| Type | Channel |
| Username | @kaiyuntuidan0 |
| Created | Between 1 February 2026 and 1 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/kaiyuntuidan0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 01:57 | 22 | +1 |
| 11 Aug 2026, 14:16 | 21 | no change |
| 9 Aug 2026, 08:01 | 21 | first reading |
20 posts held, back to 1 July 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.
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 11 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 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 1 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 1 July 2026 to 11 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.
欧冠杯 23:00 阿拉木图凯拉特 VS 索菲亚列夫斯基 平手 推荐：阿拉木图凯拉特 +0 欧冠杯 0:00 博德闪耀 VS 圣吉罗斯 半/一 推荐：博德闪耀 -0.5/1 欧冠杯 1:30 奈梅亨 VS 奥林匹亚科斯 平手 推荐：奈梅亨 +0 欧冠杯 3:00 里昂 VS 布拉格斯巴达 一球 推荐：里昂 -1 ============================== 对错勿怪 福利领取：@YH10001
中超 19:35 重庆铜梁龙VS 上海海港 一球 推荐：上海海港 -0/0.5 中超 20:00 山东泰山 VS 天津津虎门 半/一 推荐：山东泰山 -0.5/1 ============================== 对错勿怪 福利领取：@YH10001
韩K联 18:30 富川FC VS 光州FC 半球 推荐：富川FC -0.5 韩K联 18:30 全北现代 VS 济州SK 半球 推荐：全北现代 -0.5 中超 19:35 大连英博 VS 辽宁铁人 一球 推荐：大连英博 -1 中超 19:35 云南玉昆 VS 成都蓉城 平/半 推荐：成都蓉城 -0.5 ============================== 对错勿怪 福利领取：@YH10001
韩K联 18:30 大田市民 VS 光州FC 一球 推荐：大田市民 -1 韩K联 18:30 蔚山HD VS FC安养 半球 推荐：蔚山HD -0.5 中超 19:35 辽宁铁人VS 上海申花 受平/半 推荐：上海申花 -0/0.5 中超 20：00 深圳新鹏城 VS 重庆铜梁龙 平/半 推荐：深圳新鹏城 -0/0.5 ============================== 对错勿怪 福利领取：@YH10001
❤1
中超 19:35 河南队 VS 大连英博 半球 推荐：大连英博 +0.5 芬甲 23:30 科特卡 VS SJK学院 球半 推荐：科特卡 -1.5 挪超 01:00 瓦勒伦加 VS 汉坎 半/一 推荐：瓦勒伦加-0.5/1 挪超 03:00 博德闪耀 VS 利勒斯特罗姆 球半 推荐：博德闪耀 -1.5 ============================== 对错勿怪 福利领取：@YH10001
韩K联 18:30 光州FC VS 济州SK 受半球 推荐：济州SK -0.5 韩K联 18:30 FC首尔 VS 蔚山HD 半球 推荐：FC首尔 -0.5 中超 19:35 成都蓉城 VS 北京国安 平/半 推荐：成都蓉城 -0/0.5 中超 19:35 成都蓉城 VS 北京国安 平/半 推荐：成都蓉城 -0/0.5 ============================== 对错勿怪 福利领取：@YH10001
世界杯 03:00 西班牙（中） VS 阿根廷 平/半 推荐：西班牙 -0/0.5 ============================== 世界杯推荐 （对错勿怪） 福利领取：@YH10001
世界杯 05:00 法国（中） VS 英格兰 平/半 推荐：法国 -0/0.5 ============================== 世界杯推荐 （对错勿怪） 福利领取：@YH10001
世界杯 03:00 英格兰 VS 阿根廷 平手 推荐：阿根廷 +0 英格兰胜率约35.1%，阿根廷胜率约31.8%，平手概率约33.1%，有可能拖入点球 ============================== 世界杯推荐 （对错勿怪） 福利领取：@YH10001
世界杯 03:00 法国（中） VS 西班牙 平/半 推荐：法国 -0/0.5 ============================== 世界杯推荐 （对错勿怪） 福利领取：@YH10001
世界杯 05:00 挪威（中）VS 英格兰 受半球 推荐：挪威 +0.5 世界杯 09:00 阿根廷（中） VS 瑞士 半/一 推荐：瑞士 +0.5/1 ============================== 世界杯推荐 （对错勿怪） 福利领取：@YH10001
世界杯 03:00 西班牙（中） VS 比利时 半/一 推荐：西班牙 -0.5/1 ============================== 世界杯推荐 （对错勿怪） 福利领取：@YH10001
Showing the 12 most recent of 20 posts we hold for @kaiyuntuidan0. 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.
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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“开云体育赛事推单” (@kaiyuntuidan0), 22 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/kaiyuntuidan0.
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.