Telemetry Analysis

The Telemetry Analysis feature is the core of TrackOut. It lets you upload session files, visualize your driving data across multiple channels, and compare laps to find where you can improve.

Accessing Analysis

Open Analysis from the Track days group in the app sidebar to upload, connect a RaceBox, browse every saved analysis session, or review lap times. The saved-session library starts at All time, so an older recording does not look missing.

From Track Days, Upload telemetry parses the file in your browser and then asks where it belongs: it ranks likely Track Days from the recording date and detected venue, lets you pick another past day, and lists that day's on-track sessions. Choose an individual session, keep day-only context, or leave the recording unlinked. When exactly one of that day's sessions has a start time within 15 minutes of when the recording began, TrackOut pre-selects it and marks it Likely match — otherwise it keeps day-only selected rather than guessing. You can always change the choice before confirming.

Choose Upload telemetry in Analysis, or drop a file on the sidebar's Drop telemetry panel, and the Drop telemetry dialog reads it and says what it found ("AiM · 14 laps · 10 Hz GPS"). When the file clearly belongs to one track day, the dialog names the Car and Session it matched and why, and Open in Analysis files it there; Change picks somewhere else. See Uploading data.

A saved session

A saved session opens on its summary: the Laps list, a Speed trace for the picked lap against another (dashed), a Throttle · Brake strip when the file logged them, and Sectors, the time gained (teal) or lost (red) per sector with their sum. Click a lap to pick it, and use the Compare switcher to choose the lap it is measured against -- by default the session's best, or the next-fastest when you picked the best. The Car and Session switchers jump to another car's sessions or another saved session.

Full analysis opens the complete cockpit -- track map, channel stack, turn inspector and coaching -- and your browser's Back returns to the summary.

A Telemetry chip on a history row marks a day that already has saved telemetry. On a day with one saved file the chip opens it in the cockpit; on a day with several it opens the session browser so you can pick.

Analysis shows RaceBox, AiM, VBOX, and CSV sources together. Each saved row shows when it was recorded, its car and track/layout, whether it is timed or untimed, and whether it is linked to a TrackOut day or on-track session. Unlinked analysis has its own visible section. Use Link, Relink, or Unlink when your TrackOut records change later.

Key features

AIM XRK/XRZ file support

Upload files directly from AIM data loggers. Files are parsed in the background in your browser with no server round-trip required. Closing the upload flow cancels parsing. XRZ files are automatically decompressed before parsing, and TrackOut can read expanded channel samples from modern AIM exports when they are present.

AIM imports use the logger's GPS, lap, and channel records to place the session on the map, build the lap list, and surface available channels such as speed, RPM, G-force, and gear. A file whose only timed lap is stored as an out-lap still opens as a single-lap session, the same way GPS-only VBOX and CSV traces do. If the logger stopped recording part-way round a lap, that lap is listed with an Invalid badge and is never your best or reference lap. If a download was damaged in transfer, TrackOut skips the broken frames and keeps the rest of the session. Re-upload the original file from Uploading Data if an older import showed a distorted driving line, sparse GPS, or missing later laps.

Racelogic VBOX file support

Upload .vbo files from Racelogic VBOX units from the same telemetry upload flow. TrackOut reads session metadata, GPS samples, speed data, and lap telemetry, then normalizes supported speed units so VBOX sessions can be analyzed alongside AIM sessions. When the file includes Racelogic start/finish gates, lap times come from those gate crossings so they match the logger. GPS-only VBOX files with no lap markers still open as a single-lap session.

Camera video from VBOX Video loggers

A .vbo from a VBOX Video logger (such as the HD2) names the camera files recorded alongside it. When you open one in the cockpit, a Camera panel appears above the track map. Choose the video files saved with the session -- for example Driver1_0001.mp4, Driver1_0002.mp4 -- and the footage follows the cursor: scrub the timeline and the video seeks to that moment, press play and the video drives the cursor. You can pick the files in any order, and add more later.

The video never leaves your device. TrackOut plays the files straight from your computer, so they are not uploaded or saved with the session, and you choose them again each time you open the file.

• A missing file. If the cursor reaches a part of the lap recorded in a file you have not chosen, the panel names it. Playback stops at that boundary instead of skipping ahead.
• Several files. Playback carries on from one file into the next without a pause in the cursor.
• Out of step? Use the Sync buttons to move the footage 0.1 s earlier or later; select the value to reset it.

Video follows the lap you are using as the reference. It needs the original .vbo, so it is not available on a session reopened from your saved sessions.

CSV telemetry support

Upload .csv exports from RaceChrono, Harry's LapTimer, TrackAddict, and similar GPS loggers. The file needs a header row with time, latitude, longitude, and speed; column names can vary, and a unit written into the header -- Speed (km/h), SPEED[km/h] -- is read and converted rather than ignored. See Uploading data for the exact header names TrackOut accepts. If the CSV has no lap column, TrackOut treats the whole trace as one lap when it has at least two GPS samples spanning a second or more.

RaceBox support in Chrome

Choose Connect RaceBox in Analysis while using Chrome on macOS, localhost, or a secure HTTPS TrackOut page. Close the RaceBox app first so the browser can connect. RaceBox Mini supports live capture; Mini S and Micro also support stored-memory download.

TrackOut labels readings as Ground speed, 3D speed, or Speed mode unknown. 3D speed includes vertical movement; choose ground speed in the RaceBox app for driving if you need to change that setting. TrackOut only reads the setting. If the device cannot report its speed mode, recording remains available with the unknown label.

Live recordings retain the speed mode and firmware known when recording starts, so saved analysis shows the recording's speed source. Stored-device recordings and older imports show Speed mode unknown because today's settings cannot establish how an earlier recording measured speed. A standalone .racebox backup contains raw data only; importing that backup separately also leaves the mode unknown. Saving the session in TrackOut preserves its captured details.

Expand Connection details to see the model, firmware, hardware revision, serial number, rejected frames, storage retries, and the last valid GPS sample time. Optional device details may be unavailable. These counters cover the current connection and reset when you disconnect.

A Mini or Mini S with an empty, non-charging battery disconnects while idle. If the battery empties during recording or download, TrackOut keeps the connection until you stop or the download finishes, then disconnects. Stop when safe and charge the device before reconnecting; captured data remains available to save.

For a supported storage model, TrackOut checks memory automatically. Locked memory can be unlocked with the security code shown in the RaceBox app. A completed download saves one .racebox backup to your browser before you analyze it, and it does not erase anything from the device. Keep the backup to import again later through Upload telemetry.

Choose Cancel download to stop a transfer cleanly on the RaceBox. Any data already received remains available as a .racebox.partial recovery file and cannot be analyzed as a complete recording.

If the connection breaks mid-download, save the .racebox.partial recovery file before clearing or closing. A partial file cannot be analyzed.

RaceBox does not transmit circuit timing gates or lap results. TrackOut derives laps locally when the recording's GPS route clearly matches a nearby catalog layout with surveyed start/finish data. It picks a high-confidence match automatically, asks you to choose when layouts are ambiguous, and keeps the recording untimed when none fits. Saved rows identify these as TrackOut-calculated laps.

For live use, choose Open Track Mode after connecting. Select an exact nearby timing layout or Readings only, then start the dashboard for speed, G, current/last/best lap, and delta. A stale GPS signal invalidates the current lap. Stop and analyze keeps the raw RaceBox backup and opens the normal import flow.

Multi-lap comparison

Compare up to 10 laps side-by-side with distinct color-coded traces. See exactly how your driving differs between laps at every point on track. Learn more in Lap Comparison.

GPS track mapping

Visualize your driving line on an interactive satellite map. Each selected lap draws its real GPS path in that lap's color -- the line the logger recorded, not a projection snapped to the track centerline. Braking zone markers show where you begin and end braking. When a known track is detected, the official centerline is overlaid for reference so you can compare your line against the layout.

TrackOut still uses the centerline under the hood for cursor sync, delta heatmaps, and turn markers, but the colored lap lines you see on the map are the device's raw GPS samples. Gaps in GPS (for example before the first fix or through a dropout) break the line instead of drawing a chord across the infield. This is especially helpful for AIM files, where accurate GPS decoding keeps each lap's driving line correctly placed on the map.

On a curated layout, the cursor, car markers, turn labels, and start/finish move along that centerline instead of jumping from vertex to vertex, so nearby turns stay separately labeled.

Map overlays

Use the overlay controls on the track map to change what is drawn on top of your driving line:

• Phases -- Shows brake, apex, and throttle markers for each turn on the curated layout
• Δ (delta heatmap) -- Colors the driving line by time gained or lost vs the reference lap
• Off -- Hides overlays so you can focus on the raw driving line and centerline

Switch between SAT, STR, and HYB to change the basemap style.

Track layout picker

When TrackOut recognizes a venue with more than one configuration -- for example a full course and a short course -- a layout picker appears under the session title. AiM loggers record which configuration a session was driven on, so an AiM session opens on the layout you last used for that configuration. Otherwise TrackOut picks the layout your GPS trace actually follows; if it cannot tell, it uses the venue's default. Choose a different layout if it guessed wrong so turn numbers, coaching windows, and corner focus all match that configuration. Your choice is saved with the session, so it reopens on the same layout.

Turn windows are placed from the layout's own start/finish line, found on your GPS trace, rather than from wherever your logger started counting the lap. Along the lap, TrackOut lines your trace up with the layout every few hundred metres, so a wide line early in the lap does not shift later corners. Small chips on the map say how the placement was made. Estimated turns means the start/finish could not be found on the trace (or the layout only pins turn apexes). Reversed layout means you drove the circuit against the stored direction and the turns were mirrored to match. GPS shifted N m means your logger's GPS sat a few metres off the surveyed layout, so TrackOut moved the whole session onto it before drawing your lines and placing turns.

Compare turns and straights

Open Segments on a saved session, choose a turn from the map, or select a corner in the summary's delta table. Load the available lap traces when prompted. A corner delta opens with the same two laps you were comparing. Cross-session corner deltas stay in the summary because turn detail compares laps from the current recording. Previous segment and Next segment move turn → straight → turn in driven order, including reversed layouts. A complete circuit wraps through its final straight; incomplete reference recordings keep navigation bounded. Your A/B selections and view stay selected, and each segment starts replay at zero; Back to analysis returns to the session. On a wide screen the segment table on the left lists every turn and straight with A, B and A − B times and both whole-lap times; on a narrower screen it becomes a strip of segments (T1, 1–2, T2 …) above the map. Click a row, a strip chip, or a segment on the Full lap · A − B by segment map to open it, or press the left and right arrow keys to step through segments.

Choose two sources independently: an individual lap, Optimal (the fastest eligible traversal of this segment), or Average (a synthetic mean of eligible traversals). Optimal keeps the time, speed and driving line from that same lap. Average shows the contributor count for each metric and has no measured driving line. Its chart readout also shows how many laps supplied the current speed or G value, such as 1/2 laps when one lap is missing that reading. If your selected lap cannot cover the segment, including a timed lap without telemetry, it stays selected with an explanation and unavailable readings. Choose another source to compare.

The source badges and map pointers identify A and B and the lap each represents. Both measured driving lines are solid over the map. Segment replay always moves each source to its recorded position at the same elapsed time from segment entry, with both clocks starting at zero, making their relative progress visible. A source that finishes first stays at its exit with an exited indication. The detail opens with the cursor partway into the segment so the readouts show live values; moving to another segment or changing a source starts again at entry. Press play to replay the segment in real time, or scrub the slider, map or channel trace; the map, every channel and the readouts follow the same elapsed clock. The channel trace stacks the A − B delta with speed, throttle, brake and steering by default (lateral G when the recording has no steering). Use + Channel to add steering, longitudinal G, RPM or gear, the × on a chip to remove one, and Reset for the default set. Channels the recording did not log are listed as Not recorded. Each lane is scaled to the traces it shows, and its title names their range, for example SPEED · MPH · 83–106. When the file has no throttle or brake sensor, those lanes show acceleration and deceleration in G and are labelled inferred; they are not pedal positions. Coaching uses recorded brake and steering when present and says when it falls back to deceleration and lateral G. The segment map draws over the TrackOut map of the circuit. On a phone, the A/B selectors sit together with Swap so you can quickly reverse the comparison. The segment-time delta and live gap appear above the segment map, and the full-track map sits below the charts and metrics. GPS gaps remain unavailable, and Average has no position pointer or invented driving line. The detail follows your speed-unit preference. Deltas are source A minus source B, with both original values beside them.

Turn timing runs from the turn's entry to its exit. A straight runs from the preceding turn's exit to the next turn's entry, with its own Straight time and Maximum speed. Straight means the interval between turns; it does not claim the road is geometrically straight. Overlapping or touching turns leave no straight, and unresolved boundaries remain unavailable. Straights have no apex marker. The following-straight maximum is separate context and does not change that time. Explicit layout annotations define these windows; estimated annotation windows and turns detected from the recording are labeled inferred. Marker-only annotations infer entry and exit from a complete reference lap, preserving the annotation’s label. If its boundaries cannot be inferred, that turn and its neighboring straight context stay unavailable while other turns remain usable. Detected turns use the fastest complete lap with enough sensor or GPS data to identify corners, keep the same boundaries across the session and do not claim official turn numbers. If the selected layout cannot load, try again; TrackOut keeps your chosen turn map.

Missing measurements appear as — (unavailable), rather than zero. A lap with usable timing can still contribute its turn time when speed is missing. Incomplete laps, invalid laps, timing gaps and unusable alignment are excluded from aggregates. A lap must cover the recorded start-to-finish clock as well as the lap distance. Gaps in GPS break the line while keeping measured sections visible. Gaps in recorded G leave only the affected readings unavailable and preserve measurements before and after the gap. Position marks the fixed turn apex with a diamond on the reference line; it does not move to either lap’s speed minimum. The diamond remains visible when the selected sources have no GPS line, including two Average sources, if the reference lap has a GPS fix there. Longitudinal G is derived from usable speed readings when the logger did not record it, and the view labels that source. Lateral offset, track usage, geometric radius, apex classification, track-out turn rate and segment video are not available in this view.

Channel analysis

Use Add trace to choose any recorded numeric channel, plus Elapsed time, Distance, and Reference gap. Channels with the same logger label remain separate choices. Hover a chart for each lap's value; missing coverage says No data and breaks the line.

Choose Stacked plots for a separate pane per channel group or Shared plot to draw the groups together. Each attribute has a labeled scale and unit; channels use different line patterns while lap colors stay consistent. Expand Channels and scales to add an overlay, show its Difference from reference, choose a supported display unit, or set a Manual scale. Unknown units stay labeled unknown unit. If an older saved channel name matches multiple source channels, choose the specific recorded channel again; the plot stays unavailable until its source can be identified.

When you change a display unit, any manual scale converts with it so the same readings stay visible. Saved overlays also follow compatible channel spelling changes when you reopen a view.

The horizontal axis changes the comparison:

Reference gap always measures time difference at matched track positions, even when displayed against the reference lap's elapsed time. It requires a computed comparison; a recorded predictive-time channel remains a separate source channel.

The lap scrubber, start/end buttons and playback follow your chosen axis. In elapsed-time mode they preserve the time comparison even when that moment has no GPS position.

The cockpit keeps the lap selector, reference comparison, and live readouts visible while you scroll, so you can keep context as you move between the map, channels, and turn analysis.

Use Add Channels when a file includes useful raw AIM channels that are not already displayed. TrackOut prioritizes the channels drivers usually care about first -- throttle, brake, steering angle, speed, RPM, gear, and brake pressure -- and lets you explicitly map the logger source to the analysis role.

If TrackOut does not recognize a device channel automatically, click Map channels -- it appears in the transport bar under the session header whenever a priority channel is still unmapped, and the same picker is available from the channel stack -- and choose the matching source channel from your file. This helps speed, brake, throttle, G-force, gear, and RPM traces line up with the labels you expect.

A speed mapping needs a recognized speed unit. If a source has an unknown or incompatible unit, it remains available as a trace and does not replace the existing GPS speed reading.

Chart navigation

Use the cockpit charts like a data logger review tool:

• Scroll over a chart to zoom around the cursor position
• Shift-drag to pan the current window along the lap
• Double-click a chart or click the reset chip to return to the full lap

The same zoom window applies to shared and stacked plots, the reference-gap pane, and the track map. Panning an elapsed-time plot preserves its time span. If a sensor event has no GPS position, you can still read it on the time plot; the map shows the position as unavailable.

Segment comparisons

Choose a corner or straight in Segments, click its position on the track map, or pick a row under Interval timing. The selected range appears on your plots and map. Zooming changes the view without changing the timed segment. The ribbon identifies detected regions, layout regions, timing sectors or derived sectors so you can see where its boundaries came from.

Turn on Extend selection, or Shift-click a neighboring region, to combine sections such as a corner and its exit. You can combine the last and first regions across start/finish. Split at cursor, Merge selection, and Rename division edit your saved analysis divisions; they do not change the track's official turns or sectors. Those divisions and the selected range return with your workspace when its recorded coordinates are compatible.

Each selected lap shows its measured interval time, its Entry gap against the reference, and the Local time gained or lost inside the range. For example, entering 0.600 seconds behind and leaving 0.400 seconds behind means a local gain of 0.200 seconds. Negative local values mean a gain. Choose Since segment entry for the reference pane's local gap trace, or Accumulated to see the existing lap gap.

Use best segment pass makes the fastest valid pass through this range the reference, even when another lap was fastest overall. TrackOut searches all valid, compatible laps in the session and adds the winner to your comparison if it was hidden. Only laps with complete measured coverage qualify. Missing crossings, GPS dropouts, incomplete laps and incompatible coordinates show Unavailable.

Braking zone detection

TrackOut automatically detects braking zones and provides statistics for each one, including entry speed, exit speed, peak braking G, and duration. Compare braking zones across laps to find where you can brake later or carry more speed.

Delta time trace

The delta trace shows cumulative time gained or lost compared to a reference lap. When both laps have usable GPS, TrackOut matches them at the same place on track -- not the same distance along each lap's own path -- so a wider or tighter line through a corner costs only the time it actually took. Without GPS, the comparison still uses each lap's own distance, which can invent time from the extra metres. Steep slopes highlight sections where the most time is being gained or lost, helping you prioritize which corners to work on. Open an older session again to see the position-matched trace; you do not need to re-upload.

Consistency and smoothness readouts

TrackOut now summarizes each session with coaching-style readouts:

• Consistency -- A 0-100 score that rewards tight lap-time spread across your best valid laps. Higher scores mean you are repeating the same pace more reliably.
• Smoothness (proxy) -- A 0-100 score based on how steady your peak G loads are from lap to lap. Higher scores suggest more repeatable inputs.
• Off optimal -- The gap between your best lap and the session's optimal lap when that information is available.

These readouts appear in the telemetry analysis cockpit and wherever you open a saved session. Any session with at least 3 valid laps gets them, including one you typed lap times into by hand -- open the session from the day plan and the readouts sit under the lap list. A session with fewer than 3 valid laps shows no consistency score.

On a paid plan the score TrackOut stored for the session is the one you see, so the cockpit and the session form agree. The cockpit's per-corner Consistency column needs at least 3 selected laps before it can score a turn; until then each cell says Needs 3 laps. That column is not a paid feature -- it is only waiting on laps.

Corner coaching

On tracks with a curated track map, corner analysis follows the track's official turn layout: corners are labeled with their real turn numbers and names (for example T10A -- The Esses) instead of generic detected corners, and the same turn keeps the same identity on every lap you compare.

Complex turns that are split into multiple segments on the official map -- such as T2A and T2B for a multi-part hairpin -- each get their own coaching card and metrics. Corners that cross the start/finish line are included in the same layout, so coaching stays aligned with how the track is actually driven.

For each corner, TrackOut compares your selected laps against the reference lap and reports where the time comes from:

• Braking point -- how much earlier or later you started braking, in feet/meters of track distance
• Turn-in -- where you began steering into the corner relative to the reference
• Entry, apex, and exit speed -- speed deltas at each phase of the corner, in mph
• Time to throttle -- how much longer you waited before returning to power

When the track map can be aligned reliably to your lap, coaching also identifies where the centerline tightens or opens, and where an official turn contains opposing bends. Your official turn numbers and hand-drawn boundaries stay the same. Track shape, the annotated apex, and the point where you reach minimum speed are separate measurements -- a minimum-speed shift does not prove you clipped the corner earlier or later.

A technique difference becomes an opportunity when the reference is measurably faster through the same corner and following straight, without a lower exit speed. Otherwise it remains an observation. Time to throttle describes your input timing; it is not an equivalent amount of lap time lost. Comparisons against a theoretical best corner remain observations because that corner alone does not prove a better following straight.

Demonstrated opportunities are ranked by their measured interval difference, evidence strength, and corner priority. The leading opportunity is labelled as one next-session experiment. Evidence scores reflect sample quality, measured versus estimated channels, and support across compared laps; they are not probabilities or guarantees of improvement.

Focus a corner for your next stint

After reviewing where you gained or lost time, use Focus T4 next stint (or the label for your top-ranked corner) to carry one goal to your next session at that layout. TrackOut saves the corner identity, your baseline best segment time, and which session set the focus on this device.

• On the session where you set the focus, the panel shows Focused on T4 for your next stint with a Clear action if you change your mind.
• On your next session at the same layout, a Focus debrief row compares your new best segment time to the baseline from when you set the focus -- for example T4: −0.280 vs when you set it. It worked. Gains and matches use accent styling; slower results are framed as worth another stint.
• After the debrief, a fresh focus CTA appears so you can set the next corner goal and keep the loop going.

Unlock braking and throttle coaching

Braking and throttle insights need live pedal data on at least one lap. When your file has brake or throttle channels that are not mapped -- or mapped to a source with no pedal values -- the insights panel shows a prompt such as Map Brake + Throttle to unlock braking and throttle coaching for every corner.

Click Map channels to open the same channel picker the scrubber uses. Map the raw logger channels to the brake and throttle roles, then return to the insights panel for full corner-by-corner coaching.

Turn consistency coaching

When you select at least three laps, TrackOut scores how consistent you are through each turn. Use the Consistency column, turn inspector chip, and Most inconsistent turns callout to find corners where your segment times vary the most.

Paid plans also show brake-point spread when the data is available, helping you see whether inconsistent lap time comes from braking at different distances.

Analysis workspaces

Named workspaces let you keep different chart layouts for the same car and logger profile -- for example Race day, Qualifying, or Wet setup. Switch workspaces from the cockpit header, rename them, mark a default, or delete layouts you no longer use. On this browser, reopening the same source profile restores the last workspace you used, including its plot layout, horizontal axis, channel groups, relative settings, scales, and display units. A profile with no saved view starts with stacked plots.

Workspace changes sync to your account when you are online. If you rename a workspace or change the default while offline, TrackOut keeps that pending change locally and replays it when you reconnect. Deleting a workspace requires an active connection.

Session saving

Save parsed sessions to your account so you can revisit them later without needing the original file. The original file and parsed analysis data are stored securely. See Saving Sessions for details.

On the web, saved sessions load lap summaries and a few comparison traces first. Use Load lap to fetch another trace, or Load all laps for session-wide analysis. Comparisons use the laps that have loaded; theoretical lap results and saved whole-session corner results wait until all traces are available.

New web imports retain the full parsed GPS trace and, when supplied by the parser, native channel samples with their original sensor rates and units. Fast sensor events are preserved independently of the GPS sample rate. Older sessions keep the detail they were originally saved with; re-upload the original file to analyze detail that an older import left out.

Typical workflow

1. Open Analysis and upload XRK, XRZ, VBO, CSV, or RaceBox telemetry, or connect RaceBox in Chrome
2. Choose a Track Day and optionally its individual on-track session, or leave the recording unlinked. You can Link, Relink, or Unlink from the saved-session library later
3. Review the lap list and identify your fastest and average laps
4. Confirm or add any important raw channels, especially throttle, brake, steering angle, RPM, gear, or brake pressure
5. Select 2-10 laps to compare and choose the reference lap. Invalid laps stay in the list with an Invalid badge and cannot be the reference.
6. Use chart zoom and pan to focus on the most important track sections
7. Use the synchronized map, channel stack, G-force panel, stint evolution, and delta waterfall to find time-gain opportunities
8. Check the consistency, smoothness, and off-optimal readouts to understand repeatability
9. Check braking zones and turn consistency for corner-specific insights
10. Save the session if you want to revisit it later

Related pages

• Uploading Data -- Supported file formats and data channels
• Lap Comparison -- Color coding, delta analysis, and best practices
• Available Charts -- Detailed guide to every chart type
• Session Cockpit -- Everything on the cockpit screen, panel by panel
• Saving Sessions -- How to save and reload sessions
• Coaching lines -- Draw braking and racing lines that persist on saved sessions
• Tips for Better Analysis -- Practical advice for faster lap times