# Multiple Laps Races

**RUFUS Race Manager** (RRM) supports events where participants must complete multiple laps around a circuit or defined course. These formats are common in running tracks, criterium cycling, trail loops, obstacle racing, mountain biking, endurance challenges, motor races, and many other timed or lap-based competitions.

Lap-based races work differently from classical point-to-point races. Instead of progressing through a series of linear checkpoints, participants repeatedly cross the same timing point(s), and each detection contributes to their lap count, lap times, and overall ranking. RRM includes specific tools, configurations, and dashboards to ensure accurate management of these formats.

RRM supports two main types of lap-based races, each designed for a distinct competition structure.

## Types of Lap-Based Races in RRM

### Fixed Laps Races

In Fixed Laps races, each participant must complete a **predefined number of laps**. Rankings are based on the fastest total race time required to reach the target lap count.

Fixed laps are ideal when:

* The course is a loop of known distance
* The organizer wants a precise finish distance for all athletes
* Every participant should complete the same amount of work
* Results depend on speed rather than endurance duration

Examples include track races (e.g., 12 laps on a 400m track), criteriums with a fixed number of circuits, short-course trail loops, and multi-lap running challenges.

RRM automatically tracks:

* Lap count
* Lap times
* Accumulated race time
* Position changes
* Lap ranking and pace

When the final lap is completed, the participant is marked as **FINISH**, and rankings are calculated based on total completion time.

### Time-Trial (Timed) Races

In Time-Trial races, participants race for a **set duration**, and the goal is to complete **as many laps as possible** before time expires. This format prioritizes endurance and consistency rather than a predetermined distance.

Time-trial races are ideal when:

* The event follows a strict time duration (e.g., 2h MTB race, 6h run, 24h challenge)
* Athletes of different abilities should all keep racing until time is up
* The loop distance may vary or the organizer prioritizes duration over fixed distance

RRM automatically evaluates:

* Total laps completed within the time limit
* Total race time
* Lap pace and interval performance
* Final classification based on laps first, then time

Once the time limit is reached, participants complete their current lap and are then marked as **FINISH**. Rankings prioritize **laps completed**, with **finish time** used to break ties.

## Understanding Lap Logic in RRM

Regardless of the lap format:

* Each passing at the checkpoint associated with the lap line increments the participant’s lap count.
* The **Race Dashboard View** displays the race progress.
* The **Edit Participant View** displays detailed lap or time-trial performance.
* The **Event Control View/Checkpoints View** centralizes all passings.
* Classification is automatically updated as laps are validated.

Both race types leverage the same robust lap engine but apply different criteria for determining when a participant is considered finished and how results are ranked.

## Conclusion

Multiple Laps races in RRM provide a flexible and accurate framework for loop-based competitions. Whether the event is structured around reaching a fixed number of laps or maximizing laps within a time limit, RRM offers precise lap tracking, performance insights, and reliable classification tools.

Next, you can explore how to configure each type of laps race:

* [**Fixed Laps Races**](/rufus-race-manager/races/creating-a-fixed-laps-race.md)
* [**Time-Trial Races**](/rufus-race-manager/races/creating-a-time-trial-race.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.runonrufus.com/rufus-race-manager/races/multiple-laps-races.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.