Channel
@kaiyun778899
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,410subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002000161872 |
|---|---|
| Type | Channel |
| Username | @kaiyun778899 |
| Created | Between 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 3 September 2026 |
| On Telegram | t.me/kaiyun778899 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 07:17 | 1,410 | -1 |
| 27 Aug 2026, 23:38 | 1,411 | -2 |
| 17 Aug 2026, 17:08 | 1,413 | -4 |
| 10 Aug 2026, 21:35 | 1,417 | -1 |
| 7 Aug 2026, 22:03 | 1,418 | no change |
| 7 Aug 2026, 13:30 | 1,418 | first reading |
8 posts held, back to 1 July 2024 — 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 8 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
五大联赛 战火即将点燃， 开线致富联系 ： @siri9977
五大联赛点燃~
羡慕代理的一天~
体育丨六合丨电竞丨棋牌丨百家乐丨彩票丨电子 ✅代理专享 🥓 免费做代理拿分红🥰🥰🥰 🚩个月 🥓 客户输100W佣金🥰🥰万 🥓 新增人头费最高29998元 🥓 所有场馆皆有流水奖励 🥓 代理介绍代理4%客损提成 🥓虚拟币回馈最高15000元 🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀 ✅会员专享 💛会员存款迎新大礼包 💛 会员首存体验金 💛 首存礼金 最高可送5288+6888 💛 复存礼金 最高可送4888 💛 高额反水活动 ✅可U存U取，业界龙头平台，大额无忧！ ✅充值渠道齐全，24小时在线客服为会员提供安全充值通道！ ✅充值提款到账速度快，秒杀其他平台！ ✅首存+复存返利活动，详细介绍请看平台优惠活动界面！ ✅实时高清体育赛事性感美女在线直播互动！ 1 月份活动政策： 查看活动：开云 爱游戏 乐鱼 华体会 OD 星空 九游 米兰 📱
星空7月合营活动
OD7月合营活动
Showing the 8 most recent of 8 posts we hold for @kaiyun778899. 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“🏆开云体育官网招商频道🏆” (@kaiyun778899), 1,410 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/kaiyun778899.
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.