星辞无畏契约主频道 pinned «🎮瓦手【盖亚】公益直装1.0重磅来袭!✅ 📣国外程序员在内侧服时已沉淀数月 通宵达旦 只为发布拯救拉闸市场 拷打全网所有野鸡直装! 🤔您还在因为被人乱穿 被颗秒 难上分 难带妹 而苦恼? 【盖亚】直装潜心研发只为给各位爹妈解决烦恼!!上分/带妹/接单/护航必备! 🐔全网更新最效率 功能最齐全 稳定最顶尖!内透➕-丝滑蓝光绘制 -人物方框 -人物射线- 人物血量人物信息-预警背敌-漏打自瞄-主播顶尖同款自喵-支持观战透视-人物范围-人物午后! 👍不说太多花言巧语 一次体验即让您终身难忘体验什么叫做拷打全网什么赋能哥…»

Channel
星辞无畏契约主频道
@WWQY9963
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,285subscribers
+41 since we began measuring on 10 October 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003563792333 |
|---|---|
| Type | Channel |
| Username | @WWQY9963 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 October 2026 |
| Last confirmed live | 16 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 October 2026 |
| On Telegram | t.me/WWQY9963 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Oct 2026, 13:26 | 5,285 | -6 |
| 13 Oct 2026, 16:21 | 5,291 | +47 |
| 10 Oct 2026, 01:22 | 5,244 | first reading |
Engagement
9 posts held, back to 9 October 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.26%
- avg views ÷ 5,285 subscribers
- Avg views / post
- 172
- 8 posts measured
- Reaction rate
- 3.12%
- reactions ÷ views · ER floor
- Posts in window
- 9
- of 9 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.
| Window | Rolling 30 days · latest post in window 9 October 2026 |
|---|---|
| Posts held | 9 (9 October 2026 – 9 October 2026) |
| Views total | 1,379 |
| Reactions total | 43 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Oct 2026, 01:22 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.
Reaction mix
43 reactions across 8 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 43 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 8 of the 9 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 9 October 2026 to 9 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
给我打爽了
👍6
但是该说不说是真的稳定
👍6
Photo, posted without a caption
👍7
反馈
👍6
打的是真爽,但不过也不敢杀过头
👍6
⚠️失控进化【星辞 Ai自瞄】10月9号反馈 安心使用大号 稳定连打 无需一把一退 无需root 2026年全网最稳黑科技😀 🔘支持多款游戏穿越火线 三角洲行动 无畏契约 失控进化 使命召唤一卡通用⚠️ 购买链接: https://mall.682fk.cn/shop/R2XX832T
👍7
反馈盖亚
👍3
⚠️目前瓦手全网拉闸 盖亚直装一直在连打 一直在奔放 啊!目前公益中!公益中!公益中! 😙反馈的人少就关闭公益了 发反馈的联系 @JHsae8
👍2
Showing the 9 most recent of 9 posts we hold for @WWQY9963. 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.
Forward network
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“星辞无畏契约主频道” (@WWQY9963), 5,285 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/WWQY9963.
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.