> For the complete documentation index, see [llms.txt](https://docs.av-scripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.av-scripts.com/laptop-pack/racing/telemetry.md).

# Telemetry

Telemetry quietly records what happens on every finished race and gives each of your drivers a private breakdown of how they drove: their racing line on the map, how long each sector took, where they crashed, and how it all stacks up against their fastest lap.

<figure><img src="/files/kzeygFcCjzzeoFYRxSHV" alt=""><figcaption></figcaption></figure>

### What it does

Every time a driver **finishes** a race, Telemetry saves a compact snapshot of that run:

* the **line they drove**
* their **speed** along that line
* the **time at each checkpoint** (their sector splits)
* where they **crashed**, if they did

Runs that end in a DNF, a cancel, or a disconnect are simply discarded — only clean, completed races are kept.

Everything is stored **per driver, per track**. Each driver only ever sees their own data.

### What your players get

#### The "My Runs" panel

Players open a track from the racing app and find a **My Runs** tab right next to the track's Leaderboard. It shows the breakdown of their most recent run on that track, plus an interactive map.

If a driver has never finished that track, they simply see a friendly note letting them know there's nothing to show yet.

<figure><img src="/files/Ch63P0iXX1z6P17r8oBy" alt=""><figcaption></figcaption></figure>

#### Sector breakdown

The run is split into sectors (one per checkpoint). For each sector the panel shows three columns:

| Column      | Meaning                                                                                                                                    |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Sector**  | Which sector it is (1, 2, 3 …).                                                                                                            |
| **Time**    | How long that sector took.                                                                                                                 |
| **vs Best** | The difference against their best lap — **green means faster, red means slower**. A dash means there's no best lap to compare against yet. |

### Best lap — the reference that matters

The number every driver is chasing is their **best lap**, not their best total race time.

This is an important distinction. If comparisons were based on total race time, a driver's one-lap race could never be beaten by a two-lap race, no matter how fast they drove — the totals simply aren't comparable. By using the **fastest single lap** as the benchmark instead, a driver can improve their reference in **any** event, whether it's a sprint, a one-lap dash or a multi-lap circuit.

In short: drive a quicker lap in any race and the bar moves up. That best lap is also what powers the sector comparisons and the optional Ghost Replay.

### Multi-lap races

On circuits with more than one lap, Telemetry keeps each lap separate:

* the sector breakdown is shown **per lap**
* the map gets a **lap selector**, letting the driver pick which lap to view so the lines from different laps don't stack on top of each other

{% hint style="info" %}
Telemetry data is personal. Drivers see their own runs; it is not a public leaderboard. Class records are handled separately by the track Leaderboard.&#x20;
{% endhint %}