EspañolGo to the app →
Section 2

Analysis — compare laps

This is where everything happens. This tab compares two laps meter by meter and shows you where time is gained and lost, with every channel and detail panel.

Pick reference and compared

When you load the session, the app automatically builds a list of every lap with its time. You pick two:

By default the app builds the comparison with its own criteria (not simply "best against worst"), but you can always change either one manually by tapping the corresponding selector.

Reference and compared lap selectors, with the lap-time bar chart

Look at a single lap

If you don't want to compare against anything yet, you can look at just one lap — useful for reviewing an installation lap or getting a feel for the layout before you start comparing.

Compare with another saved session

You're not limited to comparing laps from the session you just loaded. You can bring in a lap from another date, another track day, or even another driver (if you're on a track with the same layout).

  1. Tap the compare-with-another-session button
  2. Pick the driver
  3. Pick the track
  4. Pick the saved session and the specific lap
'Compare with another session' dropdown open with the driver search box and the full list, each with its session count

Once you pick the specific lap, the trace updates with the real comparison — in this case, the same driver against themselves on another lap of the session:

Compared trace after picking driver, track, session and lap from another saved session — the chart title shows the name and date of the session that was brought in
What it's for: seeing how the same driver evolves across sessions, or showing a driver a teammate's faster lap on the same track.

Compared trace

This is the main chart: it overlays the two laps meter by meter (not second by second) so they can be compared even with different lap times. The spots where one lap pulls away from the other are where time is lost or gained.

Compared trace with reference and compared overlaid, corners marked, and cumulative time lost below

Reading the trace is the foundation of the whole analysis: every time the two lines separate, there's something worth reviewing — a longer braking zone, a slower entry, a corner exit with less traction, and so on.

Zoom 1×, 2×, 4×, 8× and drag

You can zoom into a specific stretch of the track to see the fine detail of a corner or braking zone. The available zoom levels are 1×, 2×, 4× and 8×.

With zoom active, you drag the chart horizontally to move along the track without losing your zoom level. This is also reflected in the channels panel below — zoom is shared between the trace and the channels.

If you're on a trackpad, you can also zoom with a two-finger pinch (or Ctrl + mouse wheel) right on the chart, for an in-between zoom level instead of jumping between the fixed buttons.

Zoom selector with the 1×, 2×, 4× and 8× options

Yellow pin

A click on the trace (without dragging) drops a yellow pin at that exact meter of the track. Every panel (channels, map, corners) syncs to show both laps' data at exactly that point.

The pin shows up as a tag with the distance in meters and a button with an icon next to it to remove it — while it's placed, clicking another point on the trace just moves it there.

Typical use: drop the pin right on a corner's braking point to compare speed, RPM and lateral G of both laps at that exact meter.

Cumulative time lost

The delta chart shows, meter by meter, how much of a time gain or loss the compared lap has built up relative to the reference. A line going down means time is being lost in that stretch; one going up means time is being gained.

Cumulative time-lost chart between two laps
How to read it quickly: the final value (the total time gap) matters less than where the slope changes — that's exactly where something happened.

Channels

Below the trace is the channels panel, which plots any variable the logger recorded along the track: Speed, LatAcc, LonAcc, RPM, Slip, Heading, Gyro, Altitude, Radius, Nsat, PosAccuracy, SpdAccuracy and Slope, depending on what your file has.

Channels panel with the list of available variables and the Speed chart comparing two laps

Braking and throttle pickup

This panel (below channels) measures, for each corner, exactly where each lap started braking and where it got back on the throttle — using the corner's apex as the zero-point reference.

ColumnWhat it shows
BrakingMeters before the apex where braking started (always negative, or "—" if no braking was detected in that corner) — one column per lap, in its color
Δ brakeDifference between the two braking points — positive (green) means the compared lap braked later, i.e. more aggressively
ThrottleMeters after the apex where the lap got back on the throttle (usually positive; can be negative if it was already accelerating before reaching the apex) — one column per lap, in its color
Δ throttleDifference between the two throttle pickup points — negative (green) means the compared lap got on the throttle earlier, i.e. better exit traction
Braking and throttle pickup panel, with all 11 corners and their Braking, Δ brake, Throttle and Δ throttle columns for both laps
What it's for: while the compared trace shows you that there's a difference in a corner, this panel tells you exactly at which meter it started — whether it was at the braking point, the exit, or both.

Fullscreen mode

The maximize icon, next to the trace's zoom buttons, opens a fullscreen mode (it hides the browser tabs and address bar) built for looking at fine detail with more room on screen — similar to RaceStudio's views.

Fullscreen mode with the trace on top, stacked channels below, the track map and the values panel on the side

To exit, tap Close in the top right or press Escape.

Whatever zoom level and pin you have set are kept when you go fullscreen — it's a continuation of where you were looking, not a fresh start.

Track map

If your file has GPS, you'll see the track layout with the corners numbered. The reference lap is drawn as a solid line and the compared lap as a dotted gray line (red/green are reserved for the hit/miss markers), so wherever the lines visually separate is where one lap took a different line than the other.

Track map with both laps overlaid (solid and dotted line), corners numbered

The Speed button, top right of the map, switches to a view that highlights speed at every point instead of the per-lap trajectory. You scroll to zoom and drag to pan; hovering the mouse over the trace or the channels shows the map the exact matching position.

Track map in Speed view, with a gradient from slow (red) to fast (green)

Corners — apex speed

Detects corners by GPS radius of curvature if your logger has that channel (more accurate on fast or very open corners), or by lateral load over 0.7g if it doesn't — over the reference lap, the apex is the point of minimum speed within each one. This panel (further down the Analysis tab, near the traction/slip panels) shows you, corner by corner:

ColumnWhat it shows
CornerCorner name (C1, C2, C3…)
ApexTrack meter where the point of maximum curvature is
Speed [lap]That lap's apex speed — one column per lap picked, in its color (blue reference, red compared)
Diff.Difference between the two — highlighted in red or green if it's over 1.5 km/h
Peak lat.Peak lateral acceleration recorded in the corner (how close to the limit it was taken)
Corners — apex speed panel, with all 11 corners detected and their Apex, Speed V6, Speed V4, Diff. and Peak lat. columns
It's read-only: this table only compares the two laps you picked above (reference and compared) — it's not where corners get corrected. That's the "Corner calibration" panel further down.

Corner calibration

This is a separate panel (collapsible, below the map) where you manage how the corners were detected for this track — unlike the table above, this doesn't compare two specific laps, it votes across every lap in the session to define a single, persistent corner profile for that track.

Corner calibration panel collapsed, showing the corner count, the track, and the last calibration date, with the Recalibrate and Edit corners buttons

Tapping "Edit corners" opens the map in edit mode:

Corner calibration panel in edit mode, with the track map and corner C1 selected showing the Cancel and Delete buttons

Changes stay in a draft — nothing is saved until you tap Save changes. If you want to back out of everything, Cancel discards the whole draft and goes back to the previous profile.

Notices you might see here: "Low-confidence profile" if it was calculated with fewer than 3 laps, or a notice that without GPS data corners are estimated from lateral acceleration alone (with no real geometry or map to verify them against).
Corners you edit by hand stay protected: a manually marked corner won't get overwritten if you recalibrate afterward, and if you delete one, that area stays suppressed and won't reappear on its own.

Friction circle

Plots lateral acceleration (the "corner →" axis) against braking/acceleration at every point of the lap, forming a cloud of points colored by speed. The 1g and 2g rings are the theoretical grip reference — the closer the cloud gets to the edge, the closer to the tire's limit the lap was driven.

Friction circle with a lap's point cloud, colored by speed, against the 1g and 2g reference rings

The "combined peak" figure is the maximum total acceleration recorded in the lap (lateral + longitudinal combined), the most extreme point in the whole cloud.

RPM vs longitudinal acceleration

This panel crosses engine RPM with longitudinal acceleration (brake/throttle) at every point of the lap. It's useful for seeing whether the driver is in the right rev range coming out of corners, and whether braking is progressive or abrupt.

RPM vs longitudinal acceleration chart, comparing two laps

Sectorization and ideal lap

Splits the track into sectors so you can compare partial times, not just the total lap — that way you see where along the layout the difference between two laps is concentrated, without having to read the whole trace at once. There are two modes, with a selector above the panel: Automatic and Manual.

Automatic mode

The track splits itself into sectors, anchored to the exit of each corner — the same cut points apply to every lap in the session, since the corners are stable session to session. You can't edit these by hand in this mode.

Sectorization panel in Automatic mode, with 3 sectors and the best-time-per-sector table

Manual mode

You decide where to cut each sector yourself, dragging directly on the speed trace — just like in RaceStudio. This manual sectorization only applies to this session, it isn't saved like the corner calibration is.

On the right, the "Where the cuts fall" mini map shows a colored dot for each cut, placed at the physical spot on the track it corresponds to — so you can visually confirm the cut landed where you wanted (right at the exit of a specific corner, for example) instead of having to guess just from the speed trace.

Sectorization panel in Manual mode, with the speed trace and draggable cuts, the mini map of where the cuts fall, and the 4-sector table

How to read the numbers

FigureWhat it is
Actual best lapThe best full lap time you actually drove in the session
Ideal lapThe sum of the best time achieved in each sector, regardless of which lap each one came from
Consistency marginThe gap between those two — how much is left on the table if you managed to string your best sectors together into one lap

The table below breaks it down sector by sector: the best time achieved there, which lap it was achieved on ("Achieved on"), that same section's time on the lap you picked above as reference, and the difference between the two.

The ideal lap is a theoretical reference, not necessarily a lap that could be driven start to finish in one go: it stitches together each lap's best sector, and sometimes a heroic sector comes with a mistake in the next one. It's useful for seeing the ceiling, not as a literal single-lap target.

Braking consistency

Analyzes how repeatable a driver's braking point and intensity are across several laps of the session (not just the two you're comparing). The result is classified into ranges:

RangeWhat it means
Very consistentThe driver brakes at practically the same point and with the same intensity lap after lap
ConsistentThere's minor variation, within what's expected
VariableThe braking point shifts noticeably between laps
ErraticThere's no clear pattern — a sign it's worth working on the braking reference
Why it matters: a driver who's erratic under braking can post a fast lap "by chance" that they can't repeat. This panel catches that even when the lap time looks good.

Slip channel calibration

Slip is the difference between the speed the engine would imply from its RPM and gear ratio, and the actual speed measured by GPS — 0% means there's no slippage. To calculate it correctly, the app needs the real drivetrain data for that session:

Slip channel calibration panel with the Front sprocket, Rear sprocket and Wheel diameter fields
Important: if you changed the gear ratio between sessions (a rear sprocket swap for a different track, for example), recalibrate this channel before comparing — otherwise the slip calculation will come out wrong even if the rest of the analysis is fine.

You can save a default calibration under Account → Default Slip calibration so you don't have to load it on every new session.