Channel
@kaiyunDLZX
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,688subscribers
-88 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001701701689 |
|---|---|
| Type | Channel |
| Username | @kaiyunDLZX |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/kaiyunDLZX |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 06:38 | 1,688 | -4 |
| 1 Sept 2026, 21:05 | 1,692 | -11 |
| 30 Aug 2026, 02:56 | 1,703 | -2 |
| 27 Aug 2026, 07:38 | 1,705 | -2 |
| 23 Aug 2026, 20:58 | 1,707 | -4 |
| 20 Aug 2026, 15:33 | 1,711 | -17 |
| 17 Aug 2026, 11:24 | 1,728 | -13 |
| 14 Aug 2026, 01:58 | 1,741 | -13 |
| 10 Aug 2026, 17:15 | 1,754 | -22 |
| 7 Aug 2026, 16:08 | 1,776 | no change |
| 7 Aug 2026, 05:45 | 1,776 | first reading |
5 posts held, back to 1 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 2 pages 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 5 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
⚡️诚邀SEO⚡️个人代理⚡️推广团队⚡️劫持⚡️站长⚡️飞机群主⚡️电销⚡️主播⚡️短视频自媒体⚡️博主流量变现-加盟入驻💰 🌸体育 🌸真人 🌸电子 🌸电竞 🌸彩票 🌸 棋牌 🌸 捕鱼🌸 💸代理合营计划： 1️⃣代理负盈利佣金提成比例55% 2️⃣月人头叠加周人头双重享受 3️⃣日活奖励最高38888元 4️⃣首存体验金100元-300元与首存彩金共享 5️⃣投注冠军盘口最高奖励188888元 6️⃣渠道推广全力扶持 费用报销简单快捷 👌首存彩金+每天复存彩金会员活动助推 🌡晋升礼金，红包🧧/豪礼大放送 8️⃣月 代理活动图 🌸 开云 🌸 乐鱼 🌸 mk 🌸华体会 🌸 米兰 🌸 od 🌸爱游戏 🌸 九游 🌸 星空 🇪🇸西甲揭幕战 8月16日 🇫🇷法甲揭幕战 8月22日 🏴英超揭幕战 8月22日 🇮🇹意甲揭幕战 8月23日
od8月代理活动图
星空8月代理活动图
米兰8月代理活动图
mk8月代理活动图
Showing the 5 most recent of 5 posts we hold for @kaiyunDLZX. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“开云代理中心” (@kaiyunDLZX), 1,688 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/kaiyunDLZX.
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.