stints.gg Get notified

Endurance race management for sim racing teams

Your endurance race, run from one plan.

Stints planned around when your drivers can actually drive, re-timed from every pit-in. A live pit wall on every screen in the team, fed straight from Le Mans Ultimate. And every lap your drivers do, kept to compare corner by corner.

See the features

One email when testing opens, nothing else. What happens to your email

Windows 10 and 11 · Planning works for any sim · Live data, Driving and Spotter for Le Mans Ultimate

NEXT STOP · STINT 2
14:47to pit-in · lap 11
VIRTUAL ENERGY
33%7.5Laps left
Damage on the car, but the menu says Do Not Repair
The pit wall at Sebring: the driver's PC reads LMU, every screen in the team shows it.
Plan

A stint plan that keeps up with the race

Out and in times, laps, in-game time of day and each driver's local time, all from the race setup. Record a pit-in, or let LMU record it, and every stint after it moves.

Pit now

Recorded pit-ins re-time the rest

Enter the actual pit-in and in-lap, or hit Pit now. Grey predictions turn into what really happened, and every later stint shifts.

0.998×

Pace that isn't one number

A pace factor per driver, time-of-day periods, fuel-saving stints, and a damage modifier that carries forward.

+1 lap 15.5

What's left at the flag

Final stint energy, race laps against the ideal, time lost, tires against the allowance, surplus stints in case it runs long.

Built around when people can drive

Drivers mark the hours they can drive, not stints, so their marks stay right when stints move. Auto-fill builds the rotation from those marks and each driver's limits; click and drag to adjust.

Never a blocked driver, open before tentative, each driver's stints in a row respected
Real timezones with daylight saving for the race date: 03:00 in Sydney is 03:00 in Sydney
Fair share per driver, and confirmations when drivers agree to the stints they're given
Timeline: the rotation against each driver's night at home and night in the sim.
Availability in half-hour slots, in your time, GMT, in-game or theirs.
Plan drivers: click to put a driver in the car, drag down for a double stint.

Compare strategies before you commit

From the stint you're on: the current plan beside flat out, fuel saving, no tire changes, tires every other stop or fitted to the allowance. Apply one in a click; Ctrl+Z takes it back.

Plan on Virtual Energy or the tank, with a reserve at the end of each stint
The fuel ratio where fuel and Virtual Energy run out together
Stop cost from pit lane loss plus the car's own pit rules
Lap times, energy and pit values filled from your drivers' calibration runs, races or practice
Pit wall

Who's in, who's next, when to box

Plan mode is the countdown to the box, the next driver in their own time, and one-tap incidents. Live car is everything LMU knows about the car and the field, from any teammate's PC that's in the session.

Every panel on the live pit wall

Move and resize them, take off what you don't need. These are from a recorded GT3 race at Sebring, 37 laps in.

The race at a glancePlaces gained since the grid and this stint, the gap ahead and behind and which way it's going, the last lap against your typical one, energy and the last lap you can pit on.
Our carTires, brakes and suspension per corner, body damage by zone, and every hit with where and how hard.
Track map with flagsEvery car on the line with its place in class, our sectors in timing colours, the pit entry, and yellow and blue flags where they are. Zoom in, follow a car, or turn it heading-up.
Next stopWhat the stop will cost, what a repair would add, and every place LMU's pit menu disagrees with the plan.
Our classThe timing board with make logos, sectors in timing colours, energy, stops, stint length, track-limit points and penalties to serve. Laps and Strategy views too.
RelativeThe cars around ours on track, five times a second, with penalties to serve, blue flags and lapped cars marked.
Pace comparison, in wordsOur driver against any car over the last 5, 10 or 20 clean laps: who's quicker, in which sector, and who's steadier.
Rivals' stopsWho pitted early and how short they filled, and how long each car stands in the box.
Telemetry logEverything LMU reported and what the app did with it: pit-ins written, penalties, contacts and hits. Accept, dismiss or undo.
Track limitsPoints against the limit, and how far to a penalty.
Last stopHow long the car stood against LMU's estimate, and what it cost.
Our lapsEvery lap against the typical one, with sectors, driver and off tracks.
Weather forecastTrack and air now, rain and sky from start to finish.
Layouts

Named layouts

One for the race engineer, one for the spotter, one for the driver between stints. Switch from the pit wall's header.

Screens

Every monitor its own wall

Put the pit wall on other monitors, each with its own layout, and save the whole setup to switch between.

Account

Follows you to every PC

Layouts are kept on your account, so the wall looks the same on the sim rig and the laptop.

Before the race

Arrange it on a recorded race

Until your event has data, the panels can show a recorded race so you can build the wall before the green flag.

LMU · live

The schedule fills itself in

Link the event to the race, or let it link itself, and pit-ins, penalties and incidents are written as they happen. Automatic writes them straight away, each one undoable from the telemetry log; Suggest waits for someone with schedule rights.

Safeguards drop to Suggest when the data looks wrong, like two PCs disagreeing on the lap count
Ignore a teammate's PC, or take data from the driving PC only
Practice and qualifying on the pit wall, never in the race plan
An unplanned stop records the tires it fitted and offers whoever drove out for the next stint

Read-only, always. It reads the shared memory LMU provides for plugins and asks the game's local API for information only. It never writes to the game, never touches another process and never changes the pit menu. Turn on Enable Plugins in LMU and the app starts reading.

Driving

Where the time goes, corner by corner

Every session you drive in LMU is kept with its laps, their traces and the setup. Pick any two laps, yours or a teammate's, and see where one gains: braking point, minimum speed, throttle on exit, the line.

T8 +0.15

Corners, found for you

Corners come from LMU's track map, numbered as LMU counts them, each from where braking starts to the next one's braking. The lap's gap splits across them.

4 m earlier

Braking, apex, exit

Where each driver brakes, the minimum speed, when they're back to full throttle and the exit speed. Speed, inputs, gear, RPM and the line, with both cars replayed on the map.

Explain

Ask where the 0.42 s went

Claude reads the figures for the two laps and answers corner by corner, weighing what isn't driving: fuel, tires, setup and conditions.

Every track and class you or a teammate drove, with your best against theirs.
A track and class: your best against the fastest teammate, your calibration, and every session by driver or day.

Your laps, your call

Laps are sent only with LMU data switched on. Per team, share all your sessions, the ones you pick, or none. Teammates who share with you show up beside your laps.

Every online race, and where you finished

Your profile keeps your online qualifying and races from LMU, on whichever PC you drove: the finish in class and overall, places made from the grid, the gap to class pole, and the standings of each session.

Any car's laps beside yours, sector by sector and lap by lap
The last 30 or 90 days in figures: wins, podiums, average finish
Your team's races too: the car's result at the flag and every stint

Calibration: measure the car before you plan the race

A guided offline run of about 45 minutes measures one driver in one car at one track. An overlay in the game says what to do next and when a lap didn't count. Results stay with the driver, and Race setup fills lap times, energy, fuel and pit values from the roster's calibrations in one click. A driver without one is filled from their races, or else their offline practice.

The runThe app follows it from LMU and says what to do next; a lap off track or over the limits doesn't count, and the run adds one.
✓Warm up

Tires and brakes up to temperature. The out-lap never counts.

2Race pace

Laps at the pace you’d race. A lap off track or over the limits doesn’t count, and the run adds one.

6 of 10 laps counted
3Energy stop

A refuel-only stop, timed against LMU’s own rules, and the pit lane loss.

4Tire stop

Four new tires: the change time, and what cold tires cost on the out-lap.

5Fuel save

Laps on a lower energy target, set by the team, to measure the saving’s pace.

6Long run · optional

A longer stint for tire wear and how much pace the tires lose with age.

An overlay in the gameThe step, its progress and the last lap over LMU, so the driver never leaves the car. Borderless or windowed; in VR, keep the app on a second screen.
Straight into the planRace pace and its spread, energy and fuel per lap, the best fuel ratio, pit lane loss, stop times against LMU's rules, cold tire cost and tire wear. Race setup flags it when a driver has a newer run.
Spotter

Spot a teammate in any session

Daily races, league nights, offline practice: see who's on track now and open their car on the same live screen as the pit wall, with your own layouts. No event to set up.

Who's on track now, in which session and car, and who's in the menus.

Same wall, any race

Position, gaps, energy, the car's state, the map, relative and timing. The next stop without the plan's checks, since there's no plan behind it.

They choose who spots them

Per team: everyone, the teammates they pick, or nobody. They can see who's spotting them right now.

Knows where they are

On track, setting up a session, or in LMU's main menu, so you know whether to wait. In one of your team's events, they open on that event's pit wall.

Teams

One event, the whole team, live

Events belong to your team. Share each one with the members who need it, choose what they may change, and everyone with it open sees every edit as it happens.

Roles and permissions

Owners, admins and members. Start from View only, Driver, Race engineer or Full edit, then fine-tune each area, down to whose availability someone may edit.

Invite links

Send a link in any chat. It names your team, opens the app, and lets new members download it. Sign in with email or Discord.

Public view-only link

The plan and pit wall for reserves or your stream, in any browser or on a phone, without signing in. Availability, notes and the briefing stay private.

Briefing: goals, retirement conditions, backup comms, and checklists for every driver swap.
Race report: the plan against what happened, by stint and by driver.
AI assistants

Ask your assistant about the race

Connect Claude, ChatGPT, Cursor or VS Code to your account. Ask who's next and when, what the fuel window looks like, how the rivals are stopping, or where you lost time to a teammate's lap. Mark availability, log an incident or build a pit wall layout from a chat.

It sees what you see and asks before it changes anything
Team admins can limit it to the public view, or turn it off
Disconnect from the account menu and it stops straight away
Undo and redo for every edit Import and export events as files Duplicate an event onto a new date Read-only when the connection drops Updates in the background Dark and light themes, team accent colour English and Polish

Questions teams ask

When can we try it?+

We’re testing with a few teams first. Leave your email at the top or the bottom of this page and we’ll write once, when testing opens to more teams.

I have an access code. How do I get in?+

Install stints.gg from the link we sent you, choose Create an account and enter the code, with Discord or with email. A team invite link from someone already in lets you in too, no code needed.

Which sims does it work with?+

Planning, availability, the schedule, the pit wall's Plan mode and the report work for any endurance race in any sim; you enter pit-ins yourself. Live car data, automatic pit-ins, Driving, Spotter and calibration are for Le Mans Ultimate.

What does it run on?+

Windows 10 and 11. New versions download in the background and install when you close the app.

Does every driver need to install it?+

Everyone who marks availability, follows the plan or works the pit wall installs it and joins the team. For live data, one PC running LMU in the session is enough. People without an account can follow a public view-only link.

Is reading LMU's telemetry safe?+

It only reads: the plugin shared memory, mapped read-only, and the game's local API for information, never for changes. Nothing is injected, the game's process is never touched, and the pit menu is never changed.

Who sees my laps?+

Your laps are sent only with LMU data switched on. For each team you choose: all your sessions, the ones you pick, or none.

Can we use it with an AI assistant?+

Yes: Claude, ChatGPT, Cursor and VS Code can connect to your account. In stints.gg, open the account menu, then AI assistants, copy the address and add it to your assistant as a custom connector, then sign in. (Custom connectors in ChatGPT depend on its plan.)

Do we have to plan with Virtual Energy?+

No. Each event plans with Virtual Energy (100% per stint) or the fuel tank, with an optional energy reserve at the end of each stint.

What if we lose connection mid-race?+

The event stays open, read-only, until the connection is back. Then edits resume and everyone catches up.

What happens to my email?+

It’s kept on our server only to write to you once, when testing opens. It isn’t shared or used for anything else, and we’ll take it off the list if you ask.

Plan your next endurance race

stints.gg opens for testing soon. Leave your email and we’ll write once, when it does.

Already have a code from us? How to get in