TL;DR
If you want to use Drivurs today, choose a RaceBox device (Mini, Mini S, or Micro). If you already own Dragy or Solo II hardware, you can still use their ecosystems - but Drivurs currently focuses on RaceBox for in-app sessions.
This is a buyer decision, not an accuracy shootout. Manufacturers describe accuracy using different conditions and methods, so a marketing number is not a controlled head-to-head test.
If you’re undecided, pick the option you’ll actually use weekly: consistent mounting, consistent runs, and a workflow that keeps your history organized long-term for your goals.
Start with the real question: what are you trying to do?
Pick the primary goal:
- Drag-style runs (0-60, 1/8, 1/4, trap speed)
- Track sessions (repeatable laps, logs, and comparisons)
- Build tracking (connect performance notes to your current mod list)
Different devices and apps optimize for different workflows.
What Drivurs supports (today)
Drivurs currently supports RaceBox devices for performance sessions:
- RaceBox Mini
- RaceBox Mini S
- RaceBox Micro
If you want a single workflow that includes garage build logs + community + events + RaceBox sessions, RaceBox is the right choice for Drivurs.
Current buyer matrix
| Decision | RaceBox Mini / Mini S / Micro | Dragy DRG70C / Dragy Pro | AiM Solo 2 |
|---|---|---|---|
| Primary workflow | Phone-connected drag or lap sessions; Mini S/Micro also have device-side storage | Dragy phone apps for acceleration and lap workflows; Pro adds storage and IMU | Dedicated in-car lap timer with track database and display |
| Receiver/update detail | Mini family and Micro use a listed 25 Hz GNSS receiver | Current DRG70C and Pro product pages list a 10th-generation u-blox receiver | AiM documents GPS-based lap timing and track recognition in the Solo 2 guide |
| Screen on the hardware | No; use the connected app | No; use the connected app | Yes, with lap information on the device |
| Internal recording | Mini: no. Mini S and Micro: yes | DRG70C: no listed internal run storage. Pro: 128 MB, up to 30 hours claimed | Solo 2 stores sessions for later review/download |
| Power approach | Mini/Mini S: internal battery. Micro: external 3.5-16 V | Internal rechargeable battery | Internal battery with external power supported by the product workflow |
| Live Drivurs Race Session | Mini, Mini S, and Micro: supported | Not supported | Not supported |
| Best fit | Drivers who want live RaceBox data inside Drivurs | Drivers committed to Dragy’s own app and leaderboard workflow | Track drivers who want a dedicated display and track-centric hardware |
Read each manufacturer’s current manual before buying. Dragy Pro and DRG70C are not interchangeable feature sets; RaceBox Mini and Mini S differ on storage; Micro is an externally powered installation; and Solo 2 is a different display-led track tool.
RaceBox: the Drivurs-integrated choice
Choose RaceBox when the requirement is a live session inside Drivurs. Mini is the enclosed battery-powered live-phone option, Mini S adds device-side storage, and Micro trades the enclosure and battery for a compact externally powered board. Drivurs scans and connects to those three models from the Race Session flow, subscribes to live telemetry, and waits for GPS readiness.
Do not extend that statement to standalone import. Mini S and Micro can record without a constant phone connection, but this comparison does not promise that Drivurs imports those device recordings.
Dragy: phone-app performance timing
The current Dragy product family centers on Dragy’s iOS/Android apps. DRG70C is the simpler current box. Dragy Pro adds a six-axis IMU, internal storage, file management, and RaceChrono compatibility according to Dragy’s product page. Those are reasons to choose Pro within the Dragy ecosystem; they do not make it a Drivurs-supported receiver.
Dragy is a sensible choice when its acceleration reports, community/leaderboard, and existing app workflow are the product you want. If Drivurs integration is non-negotiable, choose a supported RaceBox instead.
AiM Solo 2: dedicated track display
Solo 2 is oriented around circuit use: an on-device display, automatic track recognition, lap timing, stored test data, and later analysis through AiM’s tooling. That makes it materially different from a small receiver that expects the phone to be the main interface.
Choose it when immediate lap information on dedicated hardware and the AiM track workflow outweigh the convenience of using the same mobile product for garage, events, and Race Sessions. Solo 2 is not a live Drivurs device.
Questions to ask before you buy any timing device
Instead of asking “which is best,” ask questions that match your workflow:
- Do you want drag-style runs, track sessions, or both?
- Can you mount the device with a clear sky view every time?
- Does the ecosystem help you understand when data is usable (readiness/quality signals)?
- Do you want your performance tracking tied to a build log and a community, or do you want a standalone timing app?
- Are you willing to run multiple attempts and compare trends, not one hero run?
Even the “best” device won’t fix inconsistent setup.
What matters more than brand: consistency
No matter which device you use, your results depend on:
- Mounting and sky view
- Fix quality and sample rate (when applicable)
- Road grade and wind
- Repeatable start procedure
If you change three variables every run, you won’t be able to trust comparisons.
If you switch ecosystems, reset your baseline
If you move from one device to another:
- Treat your first few sessions as a new baseline.
- Don’t compare a new device’s numbers directly to old screenshots from a different setup.
- Re-run the same road/direction and build a consistent dataset again.
This isn’t about “which is more accurate.” It’s about keeping comparisons honest.
Common mistakes (how people pick the wrong device)
- Buying based on one “hero screenshot” instead of workflow + repeatability
- Ignoring mounting and sky view (then blaming the brand)
- Comparing runs from different roads/directions and calling it “gains”
- Assuming Drivurs supports Dragy/Solo II sessions today (Drivurs focuses on RaceBox)
- Switching ecosystems and not resetting your baseline
Decision checklist (pick one path)
Path A: You require Drivurs + RaceBox sessions
Choose RaceBox if you want:
- A current RaceBox setup guide in the Academy
- Readiness checks (“GPS Ready”) before you run
- Run labeling (valid / warnings / invalid / incomplete)
- Performance context that can live next to your garage setup
Start with RaceBox in Drivurs, then use the Mini, Mini S, and Micro setup guide.
Path B: You already own Dragy hardware
If you already own Dragy:
- Use the Dragy ecosystem for sessions today.
- If you move to RaceBox later, you can bring performance habits (repeatable setup, consistency) with you.
This isn’t a “wrong” choice - just a different ecosystem.
Path C: You already own Solo II hardware
If you already own Solo II:
- Use the Solo II ecosystem for your workflow.
- Evaluate whether you want an additional system for build logs, community, and events.
Where Drivurs fits in the decision
If your goal is to keep everything connected - garage setup, club membership, events, and performance sessions - Drivurs is designed for that unified workflow. RaceBox is the hardware that plugs into Drivurs sessions today.
If you only want timing and nothing else, any ecosystem can work. If you want coordination and context, Drivurs is built to keep the proof.
Next steps (Drivurs)
- Feature page: RaceBox in Drivurs
- Use case: For Track Drivers
Related guides
- Pillar: Racing sessions, validation, and leaderboards
- Same cluster: How accurate is GPS for racing apps?
- Same cluster: How do you set up a RaceBox Mini S with Drivurs?
- Different cluster: Should you use a build log or spreadsheet to track car mods?