Import your RaceBox sessions (.vbo)

Prerequisites

• Device: RaceBox Mini, Mini S or Micro
• App: RaceBox (Android or iOS)
• A recorded track session, with the start/finish line set in the app
• Generated format: .vbo

What is RaceBox?

RaceBox is a standalone GNSS logger, compact and subscription-free, widely used at motorcycle, car and karting track days. It records position, speed and acceleration at high frequency (25 Hz on the sessions we validated), and the mobile app exports each session as a .vbo file.

The .vbo is a text format created by RaceLogic and adopted by several manufacturers. Brake Point reads it whatever the column order in the file: RaceBox does not write its columns in RaceLogic’s order, and the import adapts automatically.

Step 1 - Export the session to VBO

1. Open the RaceBox app and select the track session you want to analyse
2. Start the session export and choose the VBO format (.vbo)
3. Transfer the file to your computer (share, email, cable)

The exported file is named something like RaceBox Track Session on 25-07-2026 14-55 Karting.vbo. You can rename it safely, Brake Point reads the date from inside the file.

Step 2 - Import into Brake Point

1. Log in to app.brakepoint.io
2. Click Import a session
3. Select your .vbo file
4. Brake Point splits the laps and starts the analysis

Data extracted

Data	Source
Laps	Start/finish line written into the file by RaceBox
Speed	GNSS
GPS position	Latitude, Longitude (track map)
Distance	Distance travelled per lap
Session date	Read from the file, not from its modification date

How laps are split

RaceBox writes the start/finish line you set in the app into the file itself. Brake Point uses it directly: a lap is cut at the moment your path crosses that line, not when you pass near a point.

That is what makes the import reliable on short circuits. On the karting session we used as a reference, the finish line sits 25 m from a stretch of track driven in the opposite direction: proximity-based detection counts phantom laps there, a line crossing does not.

In practice: set your start/finish line in RaceBox before going out. Without it, Brake Point has to fall back on the circuit coordinates in our database, and lap splitting becomes approximate, or impossible if the circuit is not referenced yet.

Limitations (experimental support)

• GNSS only: RaceBox is not wired to any engine unit. The export therefore has no RPM, gear, throttle or brake data.
• No G-forces or lean angle yet: the file does carry accelerometer and gyroscope channels, but their values are expressed in the device’s own frame and include gravity. Until they are corrected for how the unit was mounted, showing them would mean showing wrong numbers. We would rather show nothing than a bad G reading. This is in progress.
• One session per file: export each session separately.

RaceBox support is being improved. If you hit an issue, contact us with your file.