What you can do with Lapfly

Fly: replay your laps in 3D

Compare recorded laps with synchronized telemetry alongside the bikes. Pause, scrub, and inspect the channels behind what you see.

Fly rebuilds the lap in 3D from its actual GPS path and drives the bike along it with your real channels. Run two laps together and the reference rides as a time-aligned ghost, so you can see where the selected laps gain or lose time. The reference can be another lap in the same session or a lap from a different session on the same circuit.

The telemetry panel can follow the corner you are watching or show the whole lap, with per-bike lean, speed, throttle, brake and gear readouts beside it. Colour the racing line by speed, throttle, brake, lean or sector, switch between a follow-chase and a free orbit camera, and jump from any corner straight back to the dashboard.

Data required: usable GPS. Available analysis depends on the recorded channels.

Data requirements and limitations

Fly needs usable GPS position to build the track and the racing line. Channel colouring and the dials appear only for the channels your recording contains.

The track width and edges are illustrative, not surveyed limits, and the on-screen bike is a generic model rather than your machine.

Check logger compatibility

Understand your riding and bike with AI

Telemetry comparison and setup history

Overlay channels across laps, compare laps and sessions, and read delta time against a reference by sector and by corner.

Compare laps and sessions in detail, including across different sessions on the same circuit, and point at the corners costing you the most. Review suspension travel from logged fork and shock channels, record each bike and its suspension setup against a session, and see that setup beside your lap time across every session you have run at a circuit, with the last known setup carried forward.

Data required: the channels you want to compare must be in the file. Suspension needs fork and shock travel; delta and corner analysis need GPS speed and position.

Data requirements and limitations

Suspension travel is a reading, not a limit: Lapfly reports the travel used and will not claim a component bottomed without a recorded stroke length. Setup history reflects what you enter.

Check which channels your logger provides →

Braking and trail braking

For each corner, Lapfly finds the point where you last get on the brake before the apex, and how far that is from the apex.

Trail-braking analysis goes further: where you release the brake, how far before the apex you release it, how much brake pressure you still carry at the apex, and your lean at brake onset and at the apex. It is corner-relative, and comparable lap to lap and corner to corner.

Data required: a front-brake channel. Trail-braking metrics also need GPS speed and lean angle.

Data requirements and limitations

This needs a brake-pressure sensor, so GPS-only sources such as a phone or GoPro do not unlock it. Lapfly reports your brake-application point, read against corner radius and entry speed, rather than a blanket braking zone.

Check logger compatibility

Engine and shifting

Review the engine channels your ECU records, starting with RPM, and see how your upshifts line up.

Shift analysis detects your upshifts from a gear or shift-drum channel, reads the RPM at each shift, and flags upshifts that happen well below your peak logged RPM, with a per-shift list and your average upshift RPM.

Data required: an RPM channel, plus a gear or shift-drum channel for shift detection.

Data requirements and limitations

The shift reference is a share of your own peak logged RPM, not a dyno-derived power point, so treat it as a consistency guide rather than a power-shift recommendation. It needs an ECU or gear source, so GPS-only files do not provide it.

Track maps, turns and sectors

A GPS track map shows your line, braking points and lean angle across the whole circuit.

Turns are detected and matched to a circuit database with real corner names, and sector and corner splits drive the delta comparisons you use to find time.

Data required: GPS position, and speed for the splits.

Data requirements and limitations

Everything is computed from an uploaded file after the session; there is no live timing or live map. Sector boundaries come from the resolved circuit, never invented from the data.

Sharing and leaderboards

Your laps are private by default. Choose individual laps to make public and they join the circuit leaderboard.

Riders compare their best public lap on the same track, with an optional engine-size filter, and circuit pages are public and indexable. Nothing is shared unless you turn it on.

Browse circuits →