Channel
@kaiyun113
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001738490596 |
|---|---|
| Type | Channel |
| Username | @kaiyun113 |
| Description | 浮生乐园优质聊天群，本群畅所欲言，正常广告随便发，禁止刷屏！！！https://t.me/boyu153 世界曝光吧： @bgb886 认证招商 😄 @fushengna 菲律宾炮房🚘 @laoba256 招聘入职🫶🏻 @arcwarden111 骗子曝光👻 @heitao886 每日推单🥷🏽 @tuidanba 官方招商🔥 @heitao886 移步主群 各类项目 合作多多 |
| Created | 21 August 2023 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kaiyun113 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 05:01 | 2 | no change |
| 10 Aug 2026, 18:49 | 2 | first reading |
3 posts held, back to 21 August 2023 — 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 pageof 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 3 posts for this entry, the most recent from 21 August 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
八月活动上新 🅰️：负盈利55%（客户输100w 您拿55w 👍代理回归尽享55%） ❶ 人头费2998- 299998（❗️线红了？别担心，我们给您发工资） ❷ 体育电竞流水返现 400-77777 ❸ 真人场馆新赠500/个上不封顶！ ❹ 代理推荐代理，额外拿介绍佣金4% ❺ 数字货币存款嘉奖1200-15000 ❻ 新开代理渠道费报销、负盈利额外奖励、 发展新会员引导首存 复存奖励、新会员首存100+送100 (❗️有渠道没费用？别担心，我们给您报销） 😄 会员首存复存可申请高额首存彩金及复存彩金！ 😄 负盈利返点55%+新增奖励+大客户svip活动单日可提百万等 我这里只有真诚和不可撼动的信誉,期待您的加盟 ！ ！ 💗陈浮生💗 ⏰ 曝光频道 🏐 实时足球 电竞 篮球红单 📱 官方频道 浮生乐园优质聊天群， 本群畅所欲言，正常广告随便发，禁止刷屏！！！ 招商负责人: @fushengna …
Video, posted without a caption
Channel created
Showing the 3 most recent of 3 posts we hold for @kaiyun113. 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“平淡无奇小招商” (@kaiyun113), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/kaiyun113.
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.