Anker | Live Charged.-Anker US

Keydous NJ80-AP V3 Mechanical Keyboard

Keydous NJ80-AP V3 Mechanical Keyboard - Main image
Keydous NJ80-AP V3 Mechanical KeyboardKeydous NJ80-AP V3 Mechanical KeyboardKeydous NJ80-AP V3 Mechanical KeyboardKeydous NJ80-AP V3 Mechanical KeyboardKeydous NJ80-AP V3 Mechanical Keyboard
$4999.5 $9999 In stock

Category: NJ80-AP 75% keyboard

Fitur Baru NJ80 V3 (Versi Firmware AP800)

  • Polling Rate Ganda 8K:mendukung polling rate 8000Hz di mode kabel, 2.4GHz, dan nirkabel, mengurangi latensi respons hingga serendah 0.125ms. Anda dapat dengan bebas beralih antara polling rate 1k, 2k, 4k, dan 8k di dalam driver.
  • Pengisian Cepat:Dilengkapi baterai 4800mAh yang terisi penuh dalam sekitar 4 jam [Pengisian standar: sekitar 9+ jam.] Berdasarkan pengujian Lab Keydous dengan pengisi daya 67w; hasil aktual dapat bervariasi tergantung pada adaptor pengisian cepat spesifik Anda.

Dirancang untuk akustik murni dan kesempurnaan sentuhan, keyboard ini memberikan pengalaman mengetik yang sangat mulus dan bebas dari suara hampa. Dengan konektivitas tiga mode (Bluetooth, 2.4GHz, dan USB-C), NJ80 tersinkronisasi dengan mulus hingga 5 perangkat di Windows, Mac, Android, iOS, dan Linux, beradaptasi dengan mudah ke alur kerja harian atau pengaturan gaming Anda.

Customer Reviews (4.6 / 5 · 8 reviews)

Matthew U. ★★★★★

The 8K polling rate over 2.4GHz is honestly wild, I notice zero lag in fast games and it feels just as responsive as wired. Build quality is solid and the 75% layout fits my desk perfectly, though switching between Bluetooth and dongle took a second to get used to.

Carter Q. ★★★★★

Switched from a 1K board and the difference in wireless response is immediately noticeable, especially in fast-paced games. The 0.125ms latency claim feels real—my clicks register the instant I press them, and battery life hasn't been an issue either.

Adam D. ★★★★★

The 8K wireless polling is genuinely snappy—I notice zero lag in fast games, and the wired mode feels just as tight. Battery life seems solid so far, and the 0.125ms response time claim actually checks out in practice.