Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7417259306
Signed 🤖群管机器人

Channel
@fy999999999
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
7,819subscribers
-5,835 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002885216320 |
|---|---|
| Type | Channel |
| Username | @fy999999999 |
| Description | < 免责声明 > 开发者不会主动联系你 狙击鸭不会诋毁任何人及项目 网络上任何流言也要注意甄别 本项目仅供逆向学习研究 体验者的任何行为与作者无关 若有侵权违法行为,请联系我删除内容 请在24小时内删除本应用[下载代表同意本协议] 开发者: @jjy0731 合作 批卡 开版本联系 别的信息不回 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 55 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/fy999999999 |
Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 12:47 | 7,819 | -61 |
| 9 Nov 2026, 23:17 | 7,880 | -43 |
| 6 Nov 2026, 23:05 | 7,923 | -20 |
| 4 Nov 2026, 02:49 | 7,943 | -28 |
| 1 Nov 2026, 08:54 | 7,971 | -733 |
| 29 Oct 2026, 18:39 | 8,704 | -2,548 |
| 28 Oct 2026, 15:50 | 11,252 | -216 |
| 27 Oct 2026, 14:10 | 11,468 | -8 |
| 26 Oct 2026, 13:31 | 11,476 | -21 |
| 25 Oct 2026, 10:58 | 11,497 | -412 |
| 24 Oct 2026, 07:36 | 11,909 | -9 |
| 23 Oct 2026, 04:36 | 11,918 | -5 |
| 22 Oct 2026, 06:35 | 11,923 | -23 |
| 20 Oct 2026, 23:19 | 11,946 | -17 |
| 20 Oct 2026, 00:41 | 11,963 | -8 |
| 19 Oct 2026, 01:27 | 11,971 | -36 |
| 17 Oct 2026, 21:59 | 12,007 | -18 |
| 16 Oct 2026, 19:58 | 12,025 | -43 |
| 15 Oct 2026, 23:00 | 12,068 | -23 |
| 15 Oct 2026, 00:28 | 12,091 | first reading |
83 posts held, back to 21 June 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 72 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 2 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 83 (21 June 2026 – 5 November 2026) |
| Views total | 2,705 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 06:19 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.
Lifetime counters from Telegram’s own channel header, read 17 November 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 5 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.
379 reactions across 29 posts, in 8 distinct kinds. The most used accounts for 90.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 343 | 90.5% | |
| 👏 | 14 | 3.69% | |
| 🤩 | 11 | 2.90% | |
| 🥰 | 4 | 1.06% | |
| ❤🔥 | 2 | 0.528% | |
| 👌 | 2 | 0.528% | |
| 🔥 | 2 | 0.528% | |
| 🎉 | 1 | 0.264% |
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 31 of the 83 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 379 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 83 most recent posts we hold, published 21 June 2026 to 5 November 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.
Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7417259306
Signed 🤖群管机器人
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7417259306
Signed 🤖群管机器人
@全体成员 有玩内部的现在可以来找我了 我拉个群 共同商议 定制绘图UI什么的 定价350一个月 一对一定制驱动 只有单透 没有自瞄 走极致稳定路线 工作室什么的也可对接 @C11nb666
Signed 🤖群管机器人
好久没来反馈了 来波反馈吧 热乎图 公益卡密获取:https://t.me/C11nb000
客户反馈走一波 还是很有实力的这位客户 不管外面怎么和谐,C11依旧站在凛冽之颠 我们的口号是? 卡密获取地址:https://t.me/C11nb000 点击链接加入群聊【C11独家驱动解密】: https://qm.qq.com/q/oNAK074jf4
10.27 公益卡密已放网盘 卡密获取地址:https://t.me/C11nb000 【频道置顶网盘里面】
对大家比较疑惑的问题回答一下 1. 会不会拉闸外挂180啊? 答:独家驱动方案不会 2.为什么会拉闸客户端一天 答:可能是吃举报或者环境不行喔,现在王者吃举报就会客户端 推荐做个好的环境 环境好能抗更多举报 3. 为什么局内发不了文字 点不了投降 而且显示警告挂机啊等 答:独家离线方案 打字会在王者服务器留下记录 所以打不了字 但是可以开麦 弹挂机提示 滑动屏幕即可 总结:独家驱动方案+独家离线方案 我只保证大家不会拉外挂180 至于客户端跟行为异常 那就是你们自己的事了 公益多久我也不知道,反正肯定尽可能公益时间长一点 说白了我也是为了圈为了挣钱 但是我不会拿垃圾东西给你们用,反正仁者见仁吧这个东西 别回头开启收费了 又骂我忘本什么的 公益期间每天被同行打服务器五六百万次 uc网盘虽然有收益但是一天五六十块,根本连服务器运营成本都不够 团队的人本来说10月底就开始收费 但是我跟他们沟通了 反正尽可能公益时间长一点 …
❤1
C11公益解密 10月26日巅峰赛反馈 持续稳定中 下载链接 https://drive.uc.cn/s/87f480966e6d4
Signed 鸭 霸王
10.26日 公益卡密已放网盘 获取卡密:https://t.me/C11nb000
【玩王者的都加一下这个频道】 好朋友项目 公益的很好用 还在玩泛滥驱动的解密项目? 兄弟吃点好的吧,对自己好点 独家驱动 稳定性拉满 不磨叽 直接公益 独家驱动+自瞄+bp查询 该有的都有 点我加入频道领卡密 点我加入QQ群 https://t.me/HeXian886 https://t.me/HeXian886 https://t.me/HeXian886
❤1
C11公益解密 客户2100巅峰赛被对面加好友问候 依旧稳如老狗
Signed 鸭 霸王
Photo, posted without a caption
Signed 鸭 霸王
Showing the 12 most recent of 83 posts we hold for @fy999999999. 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.
We recorded 1 post on @fy999999999 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 registered channels — 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.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“王者狙击鸭解密” (@fy999999999), 7,819 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/fy999999999.
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.