Thousands of laps analysed across 212 tracks in 44 countries
How it works
Film your session
GoPro with GPS enabled or DJI Osmo Action with the GPS remote. The telemetry records itself.
Upload the footage
The GPS stream is inside the video file. We extract it, clean it and split the session into laps. Optional logger file sits on the same timeline.
Read the data like a driver
Sectors, lines, corner speeds and coaching notes, each tied to the footage that produced them.
Camera telemetry that complements the dash
Video path needs no extra fitment
Nothing extra to wire for the analysis pack. The camera on your helmet or pod is enough to start the debrief.
Data with the video built in
Traditional telemetry makes you match a chart against your memory of the lap. Here every data point links to the footage, so you see what the numbers meant.
Interpreted for you
Sector deltas and coaching notes in plain language. The analysis a team data engineer would do, done before you open the page.
Dash import enriches the pack
Run MyChron or Alfano? Bring RPM and temperature channels in alongside GPS and video. The dash stays for live work. The analysis pack gets better.
What your camera records, and what it doesn't
Everything in this table is already in the FAQ further down. It's here so you can see it in one place.
| Channel | From the camera? | How often (GoPro) | Notes |
|---|---|---|---|
| GPS position | Yes | About 10 times a second | Roughly 2.5 m between fixes at 90 km/h. A phone's built-in GPS manages about one fix a second, about 25 m apart |
| Speed | Yes, from GPS | About 10 times a second | Enough for corner speeds and braking points |
| Acceleration | Yes, from GPS | About 10 times a second | |
| G-force | Yes, from the motion sensors | About 200 Hz | |
| RPM | No | From the logger. Import an Alfano or AiM file alongside the video | |
| Temperatures | No | From the logger, same as RPM |
One corner, two laps: a speed trace from Whilton Mill
This is a public session: B. Philpot at Whilton Mill on 19 April 2026, 15 laps timed from onboard GPS video. The fastest the kart went all session was 49.3 mph.
Pick Turn 2, a right-hander, in the Corner Analysis tab and the page draws one speed line per lap through it. Laps 9 and 10 are worth putting side by side.
| Turn 2 | Speed in | Slowest | Speed out |
|---|---|---|---|
| Lap 9 | 49 mph | 27 mph | 32 mph |
| Lap 10 (best lap) | 49 mph | 33 mph | 35 mph |
Same speed on the way in. Then lap 9 scrubs off six more mph before the apex and comes out three slower.
That's the shape to look for on a speed trace. A dip that goes deeper than your best lap's, from the same entry speed, usually means you braked harder or longer than the corner needed. The corner box timed both laps at 11.9 s, so the cost doesn't show up there. It shows up afterwards, because a kart that leaves a turn 3 mph down carries that deficit down the next straight. Lap 9 finished 0:55.709, 0.238 s behind lap 10's 0:55.471.
You only see a dip like that with a dense GPS track. At 49 mph a kart covers about 22 metres every second. A GoPro logs its position about ten times in that second. A phone's built-in GPS logs it about once, and one point every 22 metres won't draw that shape.
Open the session and pick Turn 2 to see the traces and watch both laps through it.
Telemetry is one kind of karting data. Here's how it compares with a logger file and the timing sheet.
Common questions about kart telemetry
How do I get telemetry on a kart?
Two strong routes, and they stack. A dedicated dash like a MyChron or Alfano for live RPM, temps and an in-kart sense of timing. And the GPS already inside your camera for post-session laps, sectors, lines and coaching. If you film on a GoPro or a DJI with its GPS remote, you're recording that second layer every lap without knowing it.
What telemetry can you actually get from camera footage?
Position, speed and acceleration ten times a second from a GoPro, which is enough for lap times, sector splits, racing lines, braking points and corner speeds. What you don't get from GPS alone is engine data like RPM or temperatures. That's still the dash's job. If you run an Alfano or AiM, import those channels alongside the video.
Is camera GPS good enough for real telemetry?
For driver improvement and video-backed analysis packs, yes, and a GoPro is a different league to a phone. It logs its position ten times a second. An iPhone manages about one fix in that same second, and a kart covers 25 metres while it waits, so the phone is guessing where you were across most of a corner. The GoPro narrows that to roughly 2.5 metres. That resolution is what makes braking points, apex speed and line differences show up cleanly.
How accurate is a GoPro fix, and did it get worse at 10Hz?
It got better, even though the newer cameras log slower. The Hero 11 and 13 run a u-blox MAX-M10S receiver that reads several satellite systems at once, GPS, Galileo, GLONASS and BeiDou, where older Heros leaned on GPS alone. Seeing more satellites gives better geometry and a tighter fix, around a metre and a half under open sky. The old Heros could sample faster at 18Hz off a single system, but sample rate was never what set the accuracy. The number of satellites in view is. More systems at 10Hz beats one system at 18Hz.
What does kart telemetry cost this way?
If you already own the camera, nothing to start on the video path. Race Ninja is free to try. Keep your MyChron or Alfano if you already have one. You're not forced to choose a single spend to get useful data.
How do I read kart telemetry if I'm not a data engineer?
That's the part we care most about. Instead of handing you raw traces, Race Ninja turns the data into sector times, a racing line on the map and written coaching notes tied to your video. You can dig into the traces if you want. You don't have to.