@Charles Lopez you're exactly right that the connection count ceiling is a stack/firmware thing, not an RF thing — the 2Mbps throughput is more than enough headroom for 8-10 nodes sending telemetry.
The honest answer on simultaneous central connections is that the STM32WB07 at the core of the MultiNav Pro+ supports multiple concurrent BLE connections, but the practical ceiling depends heavily on how you configure your connection intervals and what you're actually sending per node. Running 8 persistent connections simultaneously is achievable but you'll want to tune your connection intervals carefully — tight intervals across 8 connections starts eating into the radio's scheduling budget fast. A lot of people in similar setups land on slightly relaxed connection intervals (say 100-200ms range) per peripheral, which keeps the central from thrashing while still giving you near-realtime updates across the fleet.
The other approach worth considering for a fleet tracking use case specifically is whether you actually need persistent connections to all 8 at once, or whether a scan/advertise pattern where the remotes broadcast their GNSS position periodically and the base just listens would serve you better — it's simpler to scale, more resilient to individual node dropouts, and for position reporting you often don't need the bidirectional overhead of a full connection. The tradeoff is you lose the ability to push commands back to individual nodes unless you handle that separately.
What's the update rate you're targeting per node, and is this purely inbound telemetry to the base or do you need to send commands back out to the remotes? That'll narrow down which architecture actually makes sense here.
