Expected lap times in iRacing
"What lap time should I be doing here?" has no single answer, and any site that gives you one number is guessing. What does exist is a distribution — a band of lap times for every iRating level, on this week's combo, from drivers who actually ran it. That is a target you can use.
Pace is a cloud, not a number
Plot every driver in a session with iRating on one axis and their lap time on the other and you get a downward-sloping cloud: faster drivers cluster at higher ratings, but the spread at any given rating is wide. A 2.0k driver and a 3.0k driver are frequently within a couple of tenths. The gap between them is mostly what happens between the fast laps.
This is why the chart is more useful than a leaderboard for answering the pace question. A leaderboard tells you what the quickest driver did. The cloud tells you what someone like you did, which is the number you can actually act on.
Reading your own position in the cloud
Find your rating on the horizontal axis and look at the vertical spread above and below the trend at that point. Where you sit is a diagnosis:
- Below the trend — you are quicker than your rating implies. Pace is not your limiter. Losses are coming from starts, incidents, traffic, tyre management or strategy, and your iRating graph is being held down by something other than speed.
- On the trend — pace and result are consistent. Improvement here comes from raw speed: setup work, reference points, and laps on the combo.
- Above the trend — you are finishing better than your pace suggests, usually through consistency and clean racing. Worth knowing, because it means the ceiling is speed and practice will move it.
One caveat worth taking seriously: a scatter of average lap time and a scatter of best lap time say different things. Best lap rewards one good lap; average lap rewards forty. Over a race distance, the average is the number that decides where you finish.
Getting a target for this week's combo
/fastest qualifying and /fastest race post the top ten laps for the
current week's track. Both take an iRating band filter, which is the part that
matters here — filtering the board to your own band turns a list of alien laps into a realistic
target. You can also filter by car class and division, hide team-mates, or highlight specific
drivers, and each command can drop a scatter or boxplot chart into a follow-up thread.
/fastest qualifying board — the same
read, applied to the whole week rather than a single race.Qualifying pace is not race pace
A qualifying lap is the best possible lap: minimum fuel, fresh tyres, clear track. A race lap
carries fuel, degrading tyres, dirty air and traffic. Chasing your qualifying time on lap 30 is
how a good race becomes a wall. Expect a meaningful gap between the two boards, and benchmark
race laps against /fastest race rather than against the qualifying board.
Track state moves both. A surface that has rubbered in over a race week is faster than the same
surface on Tuesday, so a time that was competitive early in the week can be mid-pack by Sunday. /fastest history pulls the leaderboard from the last time the series visited the track,
which is the honest way to check whether you have improved or the field simply has.
Common questions
What lap time should I be running at my iRating?
There is no single number, but there is a reliable range. Lap time plotted against iRating for a real field gives you a band for every rating level, and where that band sits for the current week's combo is what you should be measuring yourself against. /fastest qualifying and /fastest race post the top ten laps for the week's track with an iRating band filter, so you can narrow the board to drivers at your level rather than to aliens.
Why am I as fast as drivers 1000 iRating above me but not gaining?
Because iRating scores finishing position against expectation, not lap time. Sitting below the pace trend for your rating means speed is not your limiter — starts, racecraft, incidents, consistency over a stint or strategy are. That is a much better problem to have than the reverse, and it is the one that responds fastest to practice.
Is a qualifying time a fair target for race pace?
No, and treating it as one is the most common way to burn a race. A qualifying lap is one lap, low fuel, clear track and fresh tyres. Race pace is set by fuel load, tyre wear over a stint, traffic and a rubbered-in track surface. Expect race laps to be slower than the qualifying board, and compare race laps to race laps — /fastest race exists for exactly that.
How do I benchmark against the last time this track came around?
/fastest history posts the fastest qualifying or race lap leaderboard from the previous time a series visited a given track. It is the cleanest way to tell whether you have actually improved on a combo or whether the field has simply got quicker.
Do I need an iRacing API key to pull lap times?
No. myRaceStats runs against its own iRacing connection. You invite the bot, run /connect once, and the leaderboard and pace commands work from Discord slash commands.