New in 1.29 A tyre icon for every compound

Read the field without looking.

Timing and telemetry overlays for iRacing. Multi-class standings, an on-track relative, fuel strategy, a corner-by-corner coach and a driving cluster — each in its own window, over the game.

Free and open source · Windows · no administrator rights needed

v1.29
TelemetryLab Timing & telemetry for iRacing
Overlays
5
Widgets
7
Themes
4
Feed
~60Hz
Price
0€
Licence
MIT
The standings overlay: a session header, then GT3 and GT4 class groups with gaps, lap times and race control's flags. The relative overlay: the cars ahead and behind on track, with the player's row highlighted. The coach overlay: the corners that cost the most time on the last lap, and why. The fuel overlay: fuel laps left, the pit window and a recommended stop. The radar: two LED boxes, with the R lit for a car alongside on the right.
Five of the overlays, placed the way they sit over the game. A composite of real captures, taken on the built-in mock feed.

Overlays

Everything you would turn your head for.

Five overlays and seven widgets. Each one opens as its own frameless, always-on-top window — place it, size it, lock it, and it comes back where you left it.

Standings COLUMNS15 ROW32px

The running order, grouped by class.

Each class opens with its own header — car count, strength of field and the lap that leads it — then every car on its own row. There is no scroll bar: the table scales to fit the window, keeping every column you picked.

  • Gap to the class leader and the interval to the car ahead
  • Sectors graded against your best and the field's
  • iRating with a projected change, licence and safety rating
  • A green ▲ or red ▼ beside the new position on every pass
  • Every car's tyre compound, coloured as on TV — white H for hards, blue W for wets, red, yellow and green for softs, mediums and inters
  • Race control's flags after the driver's name — black flag, meatball, slow down, DQ
The standings overlay showing two class groups: all six GT3 cars
                       and the top three GT4 cars, under a session header naming the
                       session, the track and its layout, with the lap, time left,
                       incidents, temperatures, strength of field and clock. Each group opens with a header strip
                       carrying strength of field, car count and fastest lap, followed by
                       rows — each opening on a thin bar in its class colour, teal for
                       GT3 and orange for GT4, with a hairline between rows — carrying
                       position, position change, car number, car brand, flag, driver, a
                       combined licence and iRating pill — each licence marked by a short
                       bar in its own colour, blue A, red R, green B, gold C, orange D,
                       and a dark one for P — gap,
                       interval, last lap, best lap, tyre and three sector columns — two of the GT4 cars are on
                       wets, shown by a blue W on a dark tyre, the rest on hards, a white H. The car brands are drawn as their own
                       marks in light grey, McLaren's and Aston Martin's lettering included. Each class leader's row reads GAP and INT
                       where it has no gap to show. Three rows carry race control's marks
                       straight after the driver's name, each a small filled chip: a red
                       chip with a flag in it — a black flag — on the third GT3 car, a
                       yellow chip with a gauge reading low — told to slow down — on the
                       fourth, and a red chip with a disc in it — the meatball — on the
                       second GT4 car.
Relative SORTtrack order GAPsigned

Who is actually coming.

Sorted by time on track, not by position, so it shows the cars you are about to meet whatever lap they are on. Lapped cars turn blue, and a closing indicator fires when a faster car is catching you — red when it is from another class.

The relative overlay in a two-class race, under the same session
                       header as the standings: cars ahead and behind
                       the player sorted by on-track time, each row opening on a thin
                       bar of its class colour, with a small GT3 or GT4 tag beside the
                       car number. GT3 cars on the
                       player's lap are written in light grey; GT4 cars a lap down on the
                       player, both ahead and behind, are written in blue with a
                       minus-one-lap tag. Every row carries the driver's licence,
                       safety rating and iRating as one pill — the licence marked by a
                       short bar in its own colour — and its tyres, drawn like a TV compound
                       graphic: a white H for hards or a blue W for wets, then the laps on the set — three of
                       the GT4 cars are on wets. The player's own row is the only
                       highlighted one, outlined and set apart by a gap above and below.
Fuel BURNmeasured

The stop, before you need it.

Strategy from your own measured burn, not a number typed in before the race: the pit window, the lap it recommends, and how many laps short you are at the pace you are driving.

The fuel and strategy overlay, under a strip naming the track and a
                       1.0-lap margin: a 'Pit stop needed' block reading 1.6 fuel laps
                       against 8 laps to the flag, 7.3 litres in tank at 2.86 litres per
                       lap, a pit window of laps 18 to 19, a recommended pit on lap 19, a
                       note reading 'short by 7 laps at the current burn', and two
                       candidate plans — a one-stop on lap 19 and a two-stop. Below them,
                       a fuel-per-lap table lists laps 17 back to 14 with the litres each
                       burned — 2.93, 2.91, 2.76 and an estimated 2.82 — each against the
                       2.86 average in red when over and green when under, beside its
                       lap time and the litres left in the tank at the line.
Coach RUNSlocally

Where the lap went, corner by corner.

Every lap is lined up against your quickest clean lap, metre by metre. The coach names the one or two corners that cost you most, and why — braked early, coasted, over-slowed the apex, late on the throttle.

The coach overlay, under a strip naming the track with the
                       reference lap at 2:18.607, the last lap at 2:20.128 and a
                       delta of plus 1.521. The headline tip, marked by a red bar on its
                       left edge, reads
                       T4, 'Coasted 153 m off both pedals', plus 0.52 seconds, with
                       the apex and exit 2 km/h slower and '3 of the last 6 laps'. A
                       second tip reads T3, 'Braked 25 m early', plus 0.41 seconds,
                       entry 30 km/h slower, '5 of the last 6 laps'. Below, a strip
                       of the lap coloured yellow and red by where time went, and a
                       list of all six corners as bars from a centre line — T2 too
                       hot, T3 early brake and T4 coasting in red — ending in a lap
                       row of plus 1.52 seconds against the reference.
Dashboard WIDGETS7 GRID12 col

A driving cluster you lay out yourself.

Speed, gear and shift lights, a pedal trace, fuel, lap timing, tyre temperatures, position and the radar — arrange them on one grid, or pop any widget out into a window of its own.

The dashboard overlay's seven widgets on one grid: a speed gauge
                       reading 224 km/h in fifth gear under a shift-light bar at 6871
                       rpm; an inputs panel with the throttle trace in cyan and the
                       brake in grey beside throttle, brake and clutch bars and a
                       steering wheel; fuel — 15.1 litres in tank, 5.4 laps left at
                       2.82 litres a lap; lap timing — last 2:20.128, best 2:18.917 in
                       green, current lap running and a delta of plus 1.211 in red;
                       temperatures and pressures for all four tyres; position P6 on
                       lap 15; and the radar's two LED boxes with the L lit red.
Radar SOURCEiRacing spotter

A spotter for single-screen drivers.

On one monitor the car in your blind spot is a voice, not a picture. The radar is two LED boxes and nothing else: when iRacing's own spotter calls a car alongside, that side's letter lights up red. Size the window to sit either side of your car.

The radar widget: two square LED boxes in carbon frames, an L on
                       the left and an R on the right. The R is lit red — a car
                       alongside on the right — and the L sits dark.
What every column on the timing screen means
Standings row
ColumnReadsColour
POS Position in class, or overall when the field is ungrouped ↑ gained · ↓ lost for three seconds after a pass
GAP Seconds behind the class leader, or laps down — the leader's own row reads GAP —
INT Seconds to the car directly ahead of you in class —
LAST Your last completed lap, ruled when it grades green rule personal best · purple leads the session
BEST Fastest lap of the session for that car filled when it leads the class
iR iRating, with a projected change for this race ▲ gain · ▼ loss — an estimate
LIC Licence class and safety rating, joined to the iRating as one pill iRacing's own licence colour, as a short bar opening the pill
S1–S3 Sector time when it is a best, the delta when it is a loss purple · green · yellow · red
Session header
FieldReadsColour
RACE Session type, filled with the flag currently flying green · yellow · red
CIRCUIT The circuit and its layout — the first field to go when the overlay narrows —
LAP Laps done over the race distance — projected in a timed race —
LEFT Time, or laps, left in the session —
INC Your incident points this session yellow then red as a limit comes into sight
TRACK · AIR Track and air temperature —
SOF Strength of field —
TIME Local time, for when the stint has stopped meaning anything —

Features

Built to stay out of your way.

The overlays carry no controls at all — while you are reading them your hands are busy. Everything you can change lives in the manager instead.

  • One window per overlay

    Frameless and always on top. Each window remembers its own position and size, and reopens exactly where you left it.

  • Lock it, drive through it

    A locked window is click-through: the mouse goes straight to iRacing. Ctrl+Shift+L toggles the focused one.

  • Live preview, no apply button

    Every setting lands the moment you change it — on the preview and on the overlay already open over the game.

  • Straight from the sim

    A small bridge reads iRacing's shared memory and streams it to the overlays over a local WebSocket at about 60 Hz.

  • Try it without a sim

    Turn on mock data and the whole interface runs on a synthetic multi-class field. Every capture on this page was taken that way.

  • Yours, on your PC

    No account to make and nothing that phones home. It installs in your own user profile — no administrator rights.

Manager THEMES4

Configured once, then left alone.

Pick an overlay and its whole configuration is on one page — appearance, visibility, window — next to a live preview of the overlay it is changing.

  • Choose your timing columns; the table scales to keep every one
  • Four themes: Carbon, Midnight, Graphite and Endurance
  • Mock data in the global settings, for when there is no sim to hand
The Overlay Manager: a left rail listing Dashboard, Standings,
                     Relative, Fuel Calc and Coach, a column of widget and
                     appearance settings in the middle, and a live scaled preview
                     of the dashboard overlay on the right — its speed gauge
                     reading 206 km/h in fifth, and a throttle and brake trace
                     below it, throttle in cyan and brake in grey.

Install

From download to the grid in three steps.

  1. Download

    TelemetryLab-setup.exe — the link always points at the newest release.

  2. Run the installer

    It installs for your user only, with no administrator prompt. Windows will call the publisher unknown, because the installer is not code-signed: choose More info, then Run anyway.

  3. Place your overlays

    Open the ones you want from the manager and put them where you want them. Start a session in iRacing and they fill with live data.

Want proof of what you downloaded? Every release publishes the installer's SHA-256 on the release page, with the command that checks it.

Price

Free. All of it.

There is no paid tier and nothing held back for one. Every overlay, every widget and every update is in the download.

TelemetryLab

0 €no account, no trial

  • Standings, Relative, Fuel, Coach and Dashboard
  • All seven widgets, the radar included
  • Four themes and a live-preview manager
  • Every release, as it ships
  • The source code, MIT licensed
Download for Windows

Buy me a coffee

Optionalwhatever you like

  • The same software — nothing unlocks
  • A way to say it helped your racing
  • Time for the next overlay
Buy me a coffee
Open source LICENCEMIT STACKTauri · React · Python

All of it is on GitHub.

Read it, fork it, change it, ship your own build — commercially if you like. A mock feed drives every overlay from synthetic telemetry, so you need Windows and iRacing to use it, and neither to improve it.

No account, no telemetry of its own
Nothing here phones home. The only data it handles is the sim's, and it stays on your machine.
The arguments are written down
design.md records why each screen looks the way it does — including the decisions that were later reversed.
Bug reports that get somewhere
Two questions up front: does it still happen with mock data on, and what kind of session were you in.

FAQ

Questions, answered.

Do I need iRacing running to try it?

No. Turn on Mock data in the manager's global settings and the whole interface runs on built-in synthetic telemetry — a full multi-class field, with no bridge and no sim.

Is it really free?

Yes. There is no paid tier, no trial and no account. The code is MIT licensed, so you can read, change and redistribute it. If you want to support it, there is a coffee link — it unlocks nothing.

Why does Windows say the publisher is unknown?

The installer is not code-signed, so SmartScreen has no publisher to name and blocks it by default. Choose More info, then Run anyway. To check what you downloaded, compare its SHA-256 with the one published on the release page.

Does it need administrator rights?

No. The setup .exe installs into your own user profile — nothing is written to Program Files, and it opens the app when it finishes. A .msi for per-machine installs sits beside it on the release page.

Does it work on macOS or Linux?

Not for racing: iRacing's shared memory exists only on Windows. For development, yes — the mock feed and the interface run anywhere, which is how most of it is built.

Can I move the overlays while I drive?

Unlock a window and drag it; lock it again and it is click-through, so the mouse goes to the sim. Ctrl+Shift+L toggles the lock on the focused window. Positions and sizes are remembered between sessions.

Is it affiliated with iRacing?

No. TelemetryLab is an independent project and is not affiliated with or endorsed by iRacing.com Motorsport Simulations.

Your next stint, with the field in view.

Free for Windows. Installs in your user profile, opens when it is done.