What is the polling rate of a Bluetooth mouse?

About 125 to 133 Hz. A mouse on Bluetooth sends its position 125 to 133 times a second, against 1000 Hz or more on its own 2.4 GHz dongle. Bluetooth 6.2 can raise that past 1000 Hz, but only when both the mouse and the PC support it, and nothing says a Windows PC does yet. So on a PC today, Bluetooth is for office work and travel, and the dongle is for play.

Polling rate and connection interval

Polling rate is how many times a second the mouse reports to the computer, so at 125 Hz that is one report every 8 ms. Our polling rate page has the full arithmetic.

Mice on Bluetooth connect over Bluetooth Low Energy (LE). ASUS, for one, lists "Bluetooth LE" for its ROG Keris Wireless. An LE link does not run all the time: the two ends wake up at a fixed beat, swap data, then go quiet again to save power. The gap between those wake-ups is the connection interval. A mouse can only send at those moments, so the interval sets the top polling rate it can reach.

Why Bluetooth stops at about 133 Hz

Before Core 6.2, the Bluetooth SIG says, "the minimum interval was 7.5 ms with a 1.25 ms resolution". That is the floor, and one report per 7.5 ms works out to 133 Hz (derived).

Windows documents the same old range. Microsoft's API reference for Bluetooth LE defines the interval in "1.25ms increments, ranging from 0x0006 to 0x0C80". That is 7.5 ms to 4 seconds (derived: 6 × 1.25 ms and 3200 × 1.25 ms).

So why do makers print 125 Hz and not 133? Both appear, and both describe the same ceiling. 133 Hz is what the shortest legal interval allows, while 125 Hz is the figure makers print. Nordic's blog says LE gaming accessories have "typically been limited to roughly 125 Hz". Note that 8 ms is not even a step on the 1.25 ms grid: the steps on either side of it are 7.5 ms (133 Hz) and 8.75 ms (114 Hz).

What makers and reviewers state

The Aerox 3 Wireless appears twice on purpose. SteelSeries says 125 Hz and TechPowerUp says 133 Hz for the same mouse, which is the 125 or 133 split from the section above, shown on one product.

One mouse, worked through

Take a Logitech G603 and suppose you pair it to a laptop over Bluetooth. Logitech fixes it at 8 ms, and on average a movement waits half an interval before it is sent, so the wait is 4 ms (derived). Plug in the LIGHTSPEED receiver and set 1000 Hz, and the wait falls to 0.5 ms. The receiver saves 3.5 ms on this one step alone.

Now suppose the same link could run at the old floor of 7.5 ms. The wait drops to 3.75 ms, a saving of a quarter of a millisecond, which is why 125 and 133 Hz are the same answer in practice.

Last, suppose a Core 6.2 mouse and a Core 6.2 receiver agreed on 750 µs. That is 1333 Hz, and the wait is 0.375 ms (derived), a little shorter than the 0.5 ms of a 1000 Hz dongle.

What Bluetooth does buy you is battery. ASUS rates the ROG Harpe Ace Extreme at 98 hours on Bluetooth and 70 on 2.4 GHz, lights off, as our RGB battery page records. Polling rate moves the hours on a dongle too, and our polling rate battery life page gives them from 1000 to 8000 Hz.

What Bluetooth 6.2 changed

Core 6.2 added Shorter Connection Intervals (SCI). The SIG says it "reduces the minimum interval to 375 µs, with 125 µs resolution". It names "high-performance HID devices" and gaming, where HID means human interface devices such as mice and keyboards. Nordic's blog puts it plainly and lists "gaming mice and keyboards". It says SCI allows report rates over 2 kHz, though Nordic expects real rates of 1 to 2 kHz.

Real chips do not reach 375 µs yet. Novel Bits' hands-on guide gives 750 µs on Nordic's nRF54L and 875 µs on the nRF52, nRF53 and nRF54H, which is about 1333 Hz and 1143 Hz (derived).

The catch is that "SCI requires support on both ends of the connection". The guide says phone support "is still emerging", so SCI is best suited to "dedicated central hardware", such as a gaming dongle. A Nordic engineer made the same point on Nordic's DevZone: a USB dongle can run the fast Bluetooth link itself. To the PC it is just a USB device, so "there will be no dependency of the OS".

And Windows? We searched for a Microsoft statement on Shorter Connection Intervals and found none, and its API reference still lists the 7.5 ms floor. We will not guess past that.

Interval is not latency

Our wireless versus wired table puts Bluetooth at 10 to 30 ms. That does not clash with a 7.5 ms interval, because the interval is only how often the mouse may send. Latency is the whole trip, from your hand moving to the PC acting on it, and the wait for the next send slot is one part of that trip. SCI shrinks that part. It says nothing about the rest, so a fast interval alone does not prove Bluetooth latency matches a dongle.

What this page does not cover

This is about Bluetooth LE mice on a PC. Game controllers can differ: our DualSense polling rate page found 542 to 799 Hz over Bluetooth, so 133 Hz is not a rule for every Bluetooth device. The 125 Hz figures are what makers state, not our tests, and the rate a PC actually grants can be lower; a polling test tool will show it. We found no mouse that lists SCI in its specs, so every SCI figure here is a chip or spec figure, not a product you can buy. What still applies either way: a 2.4 GHz dongle at 1000 Hz is the setting for play.

Sources

• Bluetooth SIG, Bluetooth Core 6.2 feature overview.
• Mohammad Afaneh, Novel Bits, "Bluetooth LE Shorter Connection Intervals: Hands-On Guide with nRF54L15" (16 December 2025).
• Joel Kauppo, Nordic Semiconductor, "What's new in Bluetooth Core 6.2: An overview" (5 November 2025).
• Nordic DevZone, "Bluetooth Core 6.2 Shorter Connection Intervals availability in consumer hardware", answer by Nordic staff.
• Microsoft Learn, BluetoothLEPreferredConnectionParameters.MinConnectionInterval.
• Logitech support, G603 performance and endurance modes when using Bluetooth.
• SteelSeries support, Can I use Aerox 3 Wireless with Bluetooth?
• Keychron, spec sheets for the M2 mini and BM24.
• TechPowerUp, battery sections of the Aerox 3 Wireless and Cobra Pro reviews.