Skip to main content

Leaderboard

LMP3 COTA Leaderboard

The ten fastest LMP3 drivers at COTA, 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 COTA, qualifying, ten fastest drivers
# Driver Car Setup Qualifying lap Gap Valid since
1 Driver 54a8 Duqueine D09 Open setup 2:00.301 V1.4
2 Driver 6a69 Duqueine D09 Open setup 2:01.293 +0.992 V1.4
3 Driver aac6 Duqueine D09 Open setup 2:01.355 +1.054 V1.4
4 Driver 4f32 Duqueine D09 Open setup 2:01.398 +1.097 V1.4
5 Driver 1218 Duqueine D09 Open setup 2:01.412 +1.111 V1.4
6 Driver 9ddf Duqueine D09 Open setup 2:01.466 +1.165 V1.4
7 Driver e455 Ginetta G61-LT-P325 EVO Open setup 2:01.474 +1.173 V1.4
8 Driver d49e Duqueine D09 Open setup 2:01.562 +1.261 V1.4
9 Driver 1cb1 Ligier JS P325 Open setup 2:01.615 +1.314 V1.4
10 Driver b0bb Duqueine D09 Open setup 2:01.616 +1.315 V1.4

Best qualifying lap per driver, counting every LMP3 car and every race length, out of 296 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.