RE: typical throughput in BLE 2M phy

Priyanka — Mon, 15 Jun 2026 21:12:24 GMT

Hi,
Your observed ~820 kbps on Windows is actually a reasonable result when connecting to a laptop (non-Nordic central).
It is below the best-case Nordic-to-Nordic numbers, but laptop Bluetooth stacks often cap throughput because you do not control the central’s controller scheduling, connection-event length, number of packets per event, buffering, driver behavior, or OS GATT API overhead.

Please refer the following:

https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/building-a-bluetooth-application-on-nrf-connect-sdk-part-3-optimizing-the-connection#mcetoc_1ftnicups1

The ~2 ms idle period at the end of each connection event (reserved by the central) doesn't scale with connection interval, so shorter intervals have lower radio duty cycle efficiency. A laptop's BLE host stack also introduces additional overhead compared to a Nordic dongle.

I would suggest you to try a longer connection interval, such as 15 ms, 30 ms, or 45 ms, not only 7.5 ms. Use one packed binary notification stream, as you are doing. Avoid multiple characteristics for parallel data unless you have a strong reason.

-Priyanka