Telegram RegisterThe public register of Telegram
Telegram profile photo for 【璀璨星空】全国高端外围

Channel

【璀璨星空】全国高端外围

@ccxkww

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2,139subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002774226075
TypeChannel
Username@ccxkww
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/ccxkww

Growth

2,1392,1432,1416 August 2026 — 2,142 subscribers7 August 2026 — 2,141 subscribers9 August 2026 — 2,142 subscribers12 August 2026 — 2,143 subscribers16 August 2026 — 2,139 subscribers6 August 202616 August 2026
5 measurements spanning 9 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,138–2,144 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 04:492,139-4
12 Aug 2026, 13:542,143+1
9 Aug 2026, 20:582,142+1
7 Aug 2026, 02:042,141-1
6 Aug 2026, 22:022,142first reading

Engagement

4 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.257%
avg views ÷ 2,139 subscribers
Avg views / post
5.5
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 4 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held4 (6 August 20266 August 2026)
Views total22
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:55 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
14s
Average length
5s

Measured directly from 3 videos 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.

Recent posts

6 Aug 2026, 06:15 UTC7 viewsread 7 August 2026

🏆全国高端外围第一品牌🏆 ☞【璀璨星空】全国外围行业领导者,竭诚为您服务!🉑预约🉑临时安排!频道中有看中的直接转发给群主 @ccxkaf 双向限制请联系 @ccxkaf11bot

6 Aug 2026, 06:14 UTC7 viewsread 7 August 2026
Photo

杭州亦辰🏠08❤️萝莉 𝐀𝐠𝐞年龄/真实08年 ·𝐇𝐞𝐢𝐠𝐡𝐭身高/164 甜妹 萝莉 •𝐁𝐮𝐬𝐭🐻 /c 🥛全身雪白 冷白皮 可素颜见人 •Weight体重/90斤 身娇体软 🥢腿 漫画腰 🉑69 🐍吻 陪浴 不吸烟 无不良嗜好 学生兼职0️⃣整 | 纯❤️新人下海 初恋女友fee 期待素质哥哥 🈶 jk 丝袜情趣✨纯天然三点粉,⛲乖巧伶俐🌸 #上城区

6 Aug 2026, 06:14 UTC6 viewsread 7 August 2026
Photo

杭州❤️人上海戏剧学院在校生真实可验证件05年极品高白纯硬5 上海东方宾利签约模特 第55届全球联合国小姐新人奖 第31届IMC上海国际模特大赛十佳 净高178cm 真实D罩杯 高长腿 A4腰 标准模特身材 极品高白纯 可欲 颜值天花板 不俗不媚 #上城区 #鹦鹉🦜

6 Aug 2026, 06:14 UTC2 viewsread 7 August 2026
Photo

杭州07雪儿 🍓166天然C杯 体重90斤 💍纯情女高 小甜妹 🍒甜度严重超标,想被哥哥抱起来doi 🍑后入超级大屁屁 细腰翘臀 绝佳视觉享受 🍑bb紧致粉嫩如chu 🍓全身无整 皮肤超白嫩 🍓💧胸型超级酥软 前凸后翘三点粉 🍒性格超温柔体贴可爱 🍒上课热情超级配合,不催不事 🉑👄🉑🐍🉑69🉑🚗🉑🛁🉑配合各种动作 🍒双商高 乖巧听话 不催不事♡ (好评选手 🈶真实好评图) #西湖区

Showing the 4 most recent of 4 posts we hold for @ccxkww. 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.

Citation-graph rank

Citation-graph rank — 1,041,827 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

Cite this entry

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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“【璀璨星空】全国高端外围” (@ccxkww), 2,139 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ccxkww.

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.