Supported devices

Works with the gear you already own.

Vetkuro records a full session from phone sensors alone. Add a Bluetooth GPS receiver, an OBD-II adapter, an action camera or a heart rate strap and the same session picks up more channels — nothing is rewired, nothing is re-bought. Everything on this page is tested and shipping today, not a roadmap.

Every supported device

Four answers per class, in the order you need them: does it work, what data do I get, how do I connect it, and where does it stop. Anything on this list is tested and shipping.

Phone sensors

Nothing to buy

Does it work?

Yes, out of the box. A phone alone produces a complete session — laps, sectors, live delta and a line on the map.

What data do I get?

Position and speed from the phone's own GNSS, plus motion from the accelerometer and gyroscope.

  • Speed
  • Position
  • LateralG
  • LongitudinalG

How do I connect it?

Nothing to pair. Mount the phone where it can see sky, wait for the fix, hit record.

Where it stops

Typically 10 Hz — 5.0 m between samples at 180 km/h. Throttle and brake are estimated from motion and labelled as estimates.

Tested
  • Internal GPS
  • Accelerometer
  • Gyroscope
  • Device motion

External GPS

Biggest single upgrade

Does it work?

Yes, over Bluetooth. This is the upgrade that changes the analysis rather than the lap time.

What data do I get?

The same position and speed channels, sampled far more often — plus the receiver's own quality channels.

  • Speed
  • Position
  • SatelliteHDOP
  • FixStatus

How do I connect it?

Power the receiver, pair it in session setup, and Vetkuro shows its measured rate and accuracy before you roll.

Where it stops

Published rates vary by device and firmware. Bluetooth range is short — keep the receiver and the phone in the same part of the cabin.

Tested
  • RaceBox Mini / Mini S / Micro
  • QSTARZ BL-1000GT
  • VetkuroGPS
  • Generic BLE NMEA 0183

OBD-II

Car dependent

Does it work?

Yes on most cars built from 2008, with any adapter speaking the ELM327 command set.

What data do I get?

What the car reports about itself, instead of what motion implies. RPM and throttle position are near-universal.

  • RPM
  • Throttle
  • EngineLoad
  • CoolantTemp

How do I connect it?

Plug the adapter into the OBD port and pair it. Vetkuro runs the ELM327 initialisation and detects which PIDs your car answers.

Where it stops

Which channels appear is decided by the car, not by us. Brake pressure and gear are often unavailable; a 2010 hatchback exposes far fewer than a 2022 sports car.

Tested

Cameras

Synced to the lap

Does it work?

Yes — the phone camera, a paired GoPro Hero 9 or newer, or both at once.

What data do I get?

Onboard video tied to the session, so moving the cursor on the delta curve moves the footage with it.

  • Video
  • Multi-source

How do I connect it?

Start and stop a paired GoPro from the app, or record with the phone while it logs. Clips attach to the session automatically.

Where it stops

GoPro support starts at Hero 9. Long sessions in the sun are a heat and storage question before they are a software one.

Tested
  • Internal camera
  • GoPro Hero 9 and newer
  • Two or more sources

Health / heart rate

Any standard strap

Does it work?

Yes, with any monitor speaking the standard BLE Heart Rate profile — including the strap you already run with.

What data do I get?

Beats per minute stored on the session and readable against lap times.

  • HeartRate

How do I connect it?

Pair the strap in session setup, or let Vetkuro read from Apple HealthKit or Google Health Connect.

Where it stops

Heart rate explains fatigue, not technique. Useful when the last laps of a stint lose tenths for no visible reason.

Tested
  • Any standard BLE HRM
  • Apple HealthKit
  • Google Health Connect

Found your gear on the list?

Pair it in session setup and record — free on iOS and Android, no lap limit.

How much precision do you actually need?

Sample rate decides how far the car travels between two recorded points. That distance is the resolution of your braking point, your apex and your delta. Set a speed and see what each rate gives you.

180 km/h
60 km/hhairpin to back straight280 km/h
1 Hz Basic logger

50.0 m

between samples

Half a straight between points. Enough for a lap time, useless for a braking point.

10 Hz Typical phone GNSS

5.0 m

between samples

Solid lap and sector timing. A corner entry is a handful of points, so fine detail is interpolated.

25 Hz External receiver

2.0 m

between samples

Turn-in, apex and exit are each several samples. This is where overlaying two laps starts to pay.

At 180 km/h: 1 Hz 50.0 m, 10 Hz 5.0 m, 25 Hz 2.0 m between samples.

Distance between samples is speed divided by rate — at 180 km/h, 10 Hz puts 5.0 m between points and 25 Hz puts 2.0 m. Published rates vary by device and firmware; check the receiver’s own specification for the exact figure.

What each device class adds to the session.

Everything in the first column is already there with just a phone. The rest is additive — you can bring one device or all four.

In the session Phone only + External GPS + OBD-II + Camera + HRM
Lap times and automatic sector splits Yes Sharper — — —
Live delta to your reference lap Yes Sharper — — —
Driven line on the track map Yes Higher resolution — — —
GPS speed and position Yes Yes — — —
Engine RPM, throttle, vehicle speed — — Yes — —
Engine load and temperatures — — Car dependent — —
Onboard video tied to the session Phone camera — — GoPro, multi-cam —
Heart rate through the session — — — — Yes
Weather logged with the session Yes — — — —

Which OBD-II channels appear depends on the car’s own PID support. Vetkuro lists what it detected on your vehicle rather than promising a fixed set.

Getting a session worth analysing.

Four things that decide whether your data is good enough to compare laps with. All of them happen before the green flag.

Give the receiver sky

Dashboard or roll hoop, not the passenger footwell or a pocket. Heated windscreens and metallic tints both cost you satellites, and a weak fix shows up as a line that wanders through the apex.

Wait for the fix before you roll

The session setup screen shows GPS status and the connection state of every paired device. Leaving the pit lane on a partial fix usually costs you the out-lap and the first flying lap.

Keep Bluetooth short

BLE is happier over a metre than over three, through a body. If the link drops mid-session Vetkuro reconnects and marks the gap — the session survives, but the affected laps are flagged rather than quietly patched.

Watch heat and storage

A phone recording video in direct August sun will throttle. Shade the mount, keep it charging, and clear space before the day — video plus telemetry is the largest thing you will record.

In the product

You can see the quality before you drive.

Everything paired is on one screen with what it is actually delivering — the receiver’s update rate, satellite count and accuracy, whether the OBD adapter answered, whether the strap is talking. Pair once and the app reconnects on its own next time.

This is the screen worth ten seconds on your out-lap. A session recorded with a poor fix cannot be repaired afterwards, and no amount of analysis will tell you what you did in the corner where the fix was gone.

  • Update rate shown as measured, not as advertised
  • Several devices at once — receiver, OBD adapter, camera, strap
  • If one drops mid-session, the rest keep recording

Not sure which of these you actually need?

The device questions people ask most — phone GPS versus a receiver, whether OBD-II is worth it, which GoPro models work — are answered in one place.

Device questions in the FAQ

Record your next session for free.

Bring the phone you already own to the next track day. Everything on this page applies from the first session.

Point your camera here
Scan to install the Vetkuro mobile app

Point your camera here

iOS · Android