Channel
@cctyss6
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002018498795 |
|---|---|
| Type | Channel |
| Username | @cctyss6 |
| Created | 20 April 2024 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cctyss6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:32 | 1 | no change |
| 7 Aug 2026, 12:50 | 1 | first reading |
4 posts held, back to 20 April 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 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 4 posts for this entry, the most recent from 20 April 2024. 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.
12个世界顶级足球俱乐部合作，实力大平台！给你一个可靠信任的保障！ 🚀全网寻找：SEO，ASO，CPA，CPS，一切网红，主播，各种社群群主，只要你有流量，就能变现，特殊扶持，福利待遇全网最高。🚀 👨💻开线/换线/团线/线下团队/包网找我 2023一起合作发大财！ 💎1️⃣：专享55%佣金（玩家亏损金额的百分之五十五分给代理） 💎2️⃣：2024新增人头好礼（高达299998） 💎3️⃣：流水反水奖励（高达77777） 🌐官方频道： @obtiyu01 🌐官方招商: @ob3456 机器人双向联系： @ob3456bot
为迎接欧洲杯，4月份注册的代理可以享受6个月的55%！ 江南体育-星空体育-天博体育-博鱼体育-九游娱乐 #代理待遇： 第一：代理前6个月拿55% 第二：新增奖励，拉5-10有效会员区间，一次性奖励2998，＞300个奖励 299998！ 第3：流水奖励，（代理线下会员投注体育电竞流水10-50万之间，奖励400，50/100万之间奖励2200，最高奖励77777 投注真人视讯流水在50-100万之间，奖励888，最高奖励88888） 第4：会员彩金，首存一千给与108+88彩金， 参与首存之后，玩家还可以参与4次复存活动 👉详谈 咨询 @ob3456 飞机双向咨询：@ob3456bot
Channel photo updated
Channel created
Showing the 4 most recent of 4 posts we hold for @cctyss6. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“招商合营” (@cctyss6), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/cctyss6.
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.