Skip to main content

Leaderboard

LMP3 Monza Leaderboard

The ten fastest LMP3 drivers at Monza, from laps set in official Le Mans Ultimate races under the BoP the game is running now.

Data on this page is cached and may be up to 24h old. For live figures, use the Discord bot.

LMP3 at Monza, qualifying, ten fastest drivers
# Driver Car Setup Qualifying lap Gap Valid since
1 Driver f560 Duqueine D09 Fixed setup 1:43.069 V1.4
2 Driver 39f4 Duqueine D09 Open setup 1:43.117 +0.048 V1.4
3 Driver 3877 Duqueine D09 Fixed setup 1:43.180 +0.111 V1.4
4 Driver d7bf Duqueine D09 Fixed setup 1:43.209 +0.140 V1.4
5 Driver 3ed8 Duqueine D09 Fixed setup 1:43.219 +0.150 V1.4
6 Driver 6ec6 Duqueine D09 Open setup 1:43.341 +0.272 V1.4
7 Driver 4d88 Duqueine D09 Fixed setup 1:43.348 +0.279 V1.4
8 Driver 5d01 Duqueine D09 Fixed setup 1:43.350 +0.281 V1.4
9 Driver b89c Duqueine D09 Open setup 1:43.370 +0.301 V1.4
10 Driver cc9d Duqueine D09 Fixed setup 1:43.372 +0.303 V1.4

Best qualifying lap per driver, counting every LMP3 car and every race length, out of 19,617 drivers with a qualifying lap here under the current BoP. Valid since is the patch that set the BoP this lap was driven under, and it can differ per car: a BoP change applies to the cars it names, so one car's record can reach back further than another's on the same board.

How these boards are built

Every lap comes from an official multiplayer race. A driver appears once, at their best lap in any car of the class, and the board names the car that set it. Only laps set under the current BoP count: a lap from before a BoP change was set under different rules, so it is not a record under these ones, and a change empties a board until the next race runs. Fastest race laps are split by race length, because fuel load makes a sprint lap and an enduro lap different things.

Drivers with an account here are shown by their Discord username, and can switch that off on their profile. Everyone else gets a stable label like "Driver 4f2a", which is the same driver every time and leads nowhere. The privacy policy covers both.