TELOS TELOS F1
AUS GP | 00D : 00H : 00M : 00S
 Quick-Start Guides

TUTORIALS

Learn TELOS in Minutes

In-depth, example-driven lessons covering every feature — from your first lap comparison to pitwall-grade gap-delta and degradation analysis. Tap any lesson to expand it.

Getting Started
Your First Lap Comparison
Put two drivers head-to-head and read who is faster, and exactly where.
Beginner4 min read
Select a sessionOverlay two driversRead speed & throttle
  1. From the top bar, pick a Grand Prix and a session. For a clean first comparison, choose Qualifying — every driver pushes a single flying lap, so the data is easy to read.
  2. In the left panel set your target driver, then add a reference driver. Example: target NOR, reference VER.
  3. Open Lap History and click each driver's fastest lap (the purple-flagged one). ★ it to bookmark.
  4. The two telemetry traces now share a single x-axis. Read the speed line first, then throttle to see who commits earlier out of a corner.
  5. Hit Swap Drivers (or press R) to flip target/reference without losing your lap selection.
Worked example — NOR vs VER, Qualifying

Say NOR's lap is 1:21.340 and VER's is 1:21.512 — a 0.172s gap. The lap-time number alone tells you NOR was quicker, but not where. Open the traces and you might see NOR carrying +4 km/h minimum speed through the fast Turn 9, while VER claws back a tenth under braking into the final chicane. That is the story the timing screen can't show you.

Pro tip

Always compare like-for-like laps: two flying laps on the same tyre compound. Comparing a fresh-soft lap to a used-medium lap will make one driver look faster when it's really just the rubber.

Navigating the Dashboard
A guided tour of every control, panel and chart.
Beginner5 min read
Top-bar selectorsDriver panelLap historyTelemetry charts
  1. Top bar — the GP selector, a year toggle (jump to 2024/2025 historical data) and the session selector (FP1 / FP2 / FP3 / Q / Sprint / Race).
  2. Left panel — target driver, reference driver, a one-click Swap, and the full Lap History list with Sort Mode (by lap number, time, or sector).
  3. Centre stage — the synchronized telemetry charts: speed, throttle, brake, gear and the gap-delta strip, all locked to one x-axis.
  4. Top right — the ENG button (Engineer View) and the Share button for screenshots.
What each channel means at a glance
ChannelColourUnitRead it for
SpeedCyankm/hWhere time is won/lost
ThrottleGreen%Corner-exit commitment
BrakeRed%Braking points & trail-braking
GearYellow1–8Shift timing & corner gear
Pro tip

Set Sort Mode to sector to instantly surface a driver's best individual sectors — useful for spotting a "theoretical best lap" hiding across several real laps.

Using Keyboard Shortcuts
Drive the whole dashboard without ever touching the mouse.
Beginner2 min read
Toggle viewsSwap driversNavigate laps
  1. E — toggle Engineer View (compact, dense layout).
  2. R — swap / set the reference driver.
  3. Esc — close any open modal or overlay.
  4. ↑ / ↓ — step through Lap History when the panel is focused.
A real workflow, keyboard-only

During a live qualifying session: press E for Engineer View, use ↑/↓ to jump onto the latest hot lap as it lands, then R to slam it against the session-leader's benchmark — all in about three seconds, without breaking eye contact with the screen.

Telemetry Analysis
Reading the Gap Delta Chart
The pitwall's favourite tool — find exactly where time is won and lost.
Intermediate6 min read
Sign conventionSlope = whereDistance interpolation
  1. Overlay two drivers on a comparable lap first (see "Your First Lap Comparison").
  2. Read the sign: negative = target ahead (faster), positive = behind.
  3. Read the slope, not just the value. A falling curve means the target is actively gaining time right there; flat means they're matched.
  4. A sharp step down at a braking marker is a braking-point advantage. A gradual gain through a corner sequence is superior exit speed and traction.
  5. The final value of the curve equals the total lap-time difference.
Worked example — reading a delta trace by distance

Target LEC vs reference HAM. Here's the gap (negative = LEC ahead) sampled at key points around the lap:

DistanceSectionGap (s)What happened
0 mS/F line0.000Even start
620 mT1 exit−0.090LEC better traction
1480 mBack straight+0.040HAM higher top speed
2300 mFinal sector−0.210LEC stronger in slow corners
3340 mLap end−0.165Final gap = lap-time diff

Reading this: LEC is the quicker lap overall (−0.165s), but HAM is genuinely faster on the straight (the curve ticks positive). If LEC could find HAM's top speed, the gap would be over three tenths — that's an actionable engineering insight, not just a stopwatch number.

Common mistake

Don't read the gap as "how far apart they are on track." It's a time difference computed by resampling both laps onto a common distance axis — the same method F1 engineers use, and far more accurate than subtracting lap times.

Understanding X-Mode Zones
Decode the purple overlays and what high X-Mode % really tells you.
Intermediate5 min read
Read the overlayLap Insights %Correlate to sector time
  1. On the speed trace, purple segments mark where X-Mode (max power / aero efficiency mode) is active.
  2. Open the Lap Insights panel to see the lap's total X-Mode usage %.
  3. Cross-reference each purple zone against the sector times — high deployment usually correlates with lower times in those zones.
  4. Compare the same zone between two drivers to see who deploys it earlier and holds it longer.
Worked example — same zone, two drivers
DriverX-Mode in Zone 2Sector 2 time
PIA78%27.602
RUS61%27.880

PIA holds X-Mode 17 percentage points longer through Zone 2 and is 0.278s up in that sector. The overlay shows why the timing sheet looks the way it does.

Pro tip

High X-Mode % isn't automatically "better" — it can cost battery/energy later in the lap. Watch for a driver who deploys less but still matches the sector time: that's efficiency, and it pays off on the next straight.

Sector Analysis & Stints
Break a session down by sector and read tyre degradation across a stint.
Intermediate6 min read
Sort by sectorSpot out/in-lapsRead degradation
  1. Set Sort Mode to sector to rank laps by individual sector performance and surface a driver's true peak pace.
  2. Compare sector splits between target and reference to localise a gap — a deficit is rarely spread evenly across all three sectors.
  3. Out-laps and in-laps are flagged so warm-up and cool-down laps don't pollute your read of pure pace.
  4. Walk down a stint lap-by-lap and watch the lap time climb — that slope is tyre degradation.
Worked example — reading degradation on a medium stint
LapTimeΔ vs firstNote
L12——Out-lap (flagged, ignore)
L131:23.100.00First green lap
L161:23.34+0.24Holding well
L201:23.95+0.85Deg kicking in
L231:24.60+1.50Cliff approaching → box

About 0.15s/lap of degradation that accelerates past L20. A strategist reads this and calls the stop before the cliff at ~L24.

Advanced Features
Engineer View Deep Dive
The compact, information-dense layout built for live sessions.
Advanced4 min read
Toggle & persistenceDensity trade-offsLive-session use
  1. Toggle via the ENG button (top right) or press E.
  2. Padding collapses and panels compress so you can see the maximum number of channels and laps at once.
  3. Your choice persists across reloads via LocalStorage — set it once and it sticks.
  4. It shines during live qualifying, when you're scanning many laps in quick succession.
Pro tip

On a laptop, Engineer View + the keyboard shortcuts turn TELOS into a near-broadcast pitwall: E to densify, ↑/↓ to walk laps, R to benchmark. Full reference in the docs.

Exporting & Sharing Data
Get lap telemetry out of TELOS and into your own tools.
Advanced5 min read
CSV for spreadsheetsJSON for codeShare image
  1. CSV — a flat, per-sample table. Drop it straight into Excel, pandas or R.
  2. JSON — a structured object with full metadata (session, driver, lap time, sector splits) plus the raw channel arrays.
  3. Share Image — a session-summary screenshot via the Web Share API or clipboard.
  4. All three live on the telemetry panel of any selected lap.
Worked example — load an exported lap in Python
# exported from TELOS → lap JSON
import json, pandas as pd

lap = json.load(open("VER_monaco_q3_lap.json"))
df  = pd.DataFrame(lap["channels"])

# top speed and where it happened
print(df["speed"].max(), "km/h")
print(lap["meta"]["lap_time"], lap["meta"]["sectors"])
Pro tip

Building a product on this data instead of one-off exports? The public REST API serves predictions, standings and the grid as clean JSON — no manual download step.

Multi-Year Historical Comparison
Put the same circuit side by side across different seasons.
Advanced5 min read
Year selectorMatch the lap typeTrack evolution
  1. Use the Year selector to switch between historical seasons at the same Grand Prix.
  2. Pick the equivalent session and a comparable lap — pole lap vs pole lap is the cleanest read.
  3. Overlay the speed traces to see how car and driver pace has evolved season over season.
  4. Historical telemetry comes from FastF1 — check Data Sources for exact coverage.
Worked example — pole pace, year over year
YearPole lapΔ vs prevDriver
20231:29.708—VER
20241:28.864−0.844NOR
20251:28.107−0.757LEC

Roughly 1.6s of lap-time gained in two seasons. Overlay the traces and you'll usually find most of it in higher minimum corner speeds — that's aero and tyre development made visible.

Need More Help?

Other Resources

Full Documentation
Complete technical reference for all platform features.
Read Docs →
Support Center
FAQ, bug reporting, and direct contact with the team.
Get Help →
Discord Community
Live help, analysis sharing, and feature discussions.
Join Server →