Racing

GPS timing and verified runs with graphs, device checks, and leaderboards.

Log 0–60, 60–130, 0–130, 1/8 mile, 1/4 mile, and 1/2 mile sessions, then review the data with graphs, grade validation, and device readiness.

0–60, 60–130, 0–130
1/8, 1/4, and 1/2 mile
Device and GPS readiness
Leaderboards with publish control

Get early access GPS timing guide

1/4 mile

13.571 s

Uploaded 3w ago

Trap

125.2 km/h

VerifiedvalidGrade -0.08%

Lux

2022 Genesis G70

›

Run viewer

Peak 140.6 km/h · 13.2s

speedaccelgrade

27.0 1.0s

Samples 135 grade -0.08%

0–100

4.080 s

1/4

13.571 s

GPS timing

Run viewer

Use graphs and run validation before you trust the number.

The run viewer keeps the headline metric tied to graph detail and validation checks.

Device readiness

3 devices

Supported hardware stays clear before you start a pull.

Device and GPS readiness show up early so setup mistakes are easier to catch.

Privacy

Opt-in

Private testing stays private until you publish.

Leaderboards work better when publishing remains explicit instead of automatic.

Safety

Supported devices and safe testing come before the leaderboard

Safety, legality, and device setup stay up front because credible performance testing starts there, not as an afterthought.

Safety first

Use a closed course when possible and confirm the hardware before the run starts.

RaceBox setup guide Run validity guide Legal + safety overview Track vs street mindset

Validation sequence

GPS ready

Vehicle selected

Metric armed

Grade acceptable

Metrics

Supported timing views stay close to your runs

Pick the metric you care about, keep the session history nearby, and compare changes with the right context.

Street / drag staples

0–60, 60–130, and 0–130

The metrics enthusiasts actually use when comparing meaningful changes instead of random bragging rights.

Distance timing

1/8, 1/4, and 1/2 mile

Distance timing belongs next to the run viewer and session history, not as detached numbers.

Validation layer

Grade validation and device readiness

Focus on quality, repeatability, and setup checks before you focus on any one run time.

Sessions

Racing gets more useful when it stays attached to your vehicle

Your session flow works best when your runs stay tied to the exact build you tested.

1/4 mile

13.571 s

Uploaded 3w ago

Trap

125.2 km/h

VerifiedvalidGrade -0.08%

Lux

2022 Genesis G70

›

Run viewer

Peak 140.6 km/h · 13.2s

speedaccelgrade

27.0 1.0s

Samples 135 grade -0.08%

0–100

4.080 s

1/4

13.571 s

Trap

125.2 km/h quarter-mile terminal

Step 01

Select your vehicle

Testing works best when your runs stay tied to the build you actually drove.

Step 02

Run the session with a supported device

Keep device and GPS readiness easy to follow before you start a pull.

Step 03

Review graphs and quality

Look at the graphs, grade, and consistency before you trust the headline number.

Step 04

Publish only what you want public

Leaderboards stay opt-in so private testing and public competition can coexist cleanly.

Run viewer

Use the run viewer to understand what the number means

Speed, acceleration, and grade graphs help you spot traction issues, heat soak, or inconsistent conditions.

Speed graph

See where your car actually picked up

Spot traction issues, shift behavior, and consistency run to run.

Acceleration graph

Find dips, heat soak, or intervention

The curve matters because the cause of the number matters.

Grade graph

Keep comparisons honest

Grade awareness helps you avoid the “one downhill pull” problem.

Leaderboards

Publishing is explicit, not assumed

The public competitive layer works better when the private testing layer still feels complete.

Private by default

Unpublished runs stay with you

Not every test pass needs to become content. Drivurs keeps that choice explicit.

Public when ready

Leaderboards with actual context

Publishing becomes more credible when the leaderboard still points back to graph detail and quality signals.

RaceBox devices

Device support matters because it affects how you capture and trust the data

Supported-device details stay clear here, and the hardware remains third-party.

Supported devices

RaceBox Mini

Compact GPS timing hardware for portable performance logging.

Supported devices

RaceBox Mini S

A higher-spec option if you want another supported RaceBox device.

Supported devices

RaceBox Micro

Another supported option when you want a compact GPS timing setup.

Important note

RaceBox is a third-party product.

Drivurs is not affiliated with, sponsored by, or endorsed by RaceBox. This page only explains which devices are supported in Drivurs Racing.

Get early access

Use graphs, validation, and session history before you trust the number

Racing is built for repeatable testing, cleaner comparisons, and leaderboards you can publish when you are ready.

Get early access GPS timing guide