Methodology

Purpose

LMU BoP Tourism is an independent comparison site for Le Mans Ultimate. It turns public lap time, balance, race pace, and schedule signals into pages that help players compare cars, tracks, setup shops, and game versions.

The site is not an official BoP source. It is a data aid for sim racers, not a rulebook or guarantee of what will be fastest for every driver.

Lap Time Sources

Setup-shop benchmark laps are collected from GoSetups, BeAlien, and Hymo. Each source is handled separately, then converted into the same internal shape: source, car, class, track, game version, and lap time in milliseconds.

The website displays benchmark lap times only. It does not sell, host, or distribute setup files.

Normalization

Car, class, and track names are matched to canonical site records before data is stored. Game versions are normalized so different source formats can be compared consistently. Lap times are stored as integer milliseconds so sorting and gaps are deterministic.

If a source publishes a car, class, or track name that cannot be resolved with confidence, that row is held out of the public comparison tables until it can be mapped safely.

Fastest Lap Selection

For each source, the site keeps one current row per car, track, and version. If the same version appears again, the row is updated only when the newly seen lap is faster. Slower repeats are ignored for ranking purposes.

This keeps comparison pages focused on each source's best known benchmark for the selected car, track, and version.

BoP And Version Context

BoP pages compare lap times against the game version attached to each benchmark. Where version and balance context matters, the interface labels older data so users can judge whether a time is still useful after later game updates.

Patch and BoP history pages are derived from public update information and internal canonical car records. They are intended to explain context, not to replace official patch notes.

Car Strength Rankings

Car strength pages aggregate benchmark pace across selected tracks. The ranking favors cars that are consistently close to the fastest benchmark rather than cars that are strong at only one circuit.

These rankings are best read as pace indicators. Driver comfort, stint length, setup style, tyre behavior, traffic, and race format can all change the practical answer.

Race Pace And Schedule Data

Race pace, statistics, leaderboards, and weekly schedule pages use game-service and public-facing race data processed on a schedule. The site groups and summarizes this data into track, class, car, setup type, and race context views.

The collection details for those feeds are intentionally summarized here. The important user-facing rule is simple: these pages are generated from stored data, refreshed by background jobs, and not by live provider calls during page rendering.

Update Cadence

Source refreshes run automatically. Different data families update on different schedules depending on how often the underlying source changes and how expensive the refresh is. Public pages show the latest stored data available to the application.

Limitations

• - Benchmark laps reflect the source's driver, conditions, setup, and publication timing.
• - Not every source publishes every car and track at the same time.
• - A newer patch can change the relevance of older laps even when those laps remain visible for comparison.
• - Race pace targets are guidance, not a promise that a specific time is achievable for every driver.

Corrections

If a car, track, version, source, or lap time appears wrong, send details through the Contact page. Corrections are handled manually when source evidence is clear.