Endurance events

Bikepacking and endurance races

Track long routes, sparse fields, route progress, standings, ETA, replay, and result corrections.

MapCatch is built for formats where participants spread out over hours or days and the public story depends on route progress, fresh positions, and a clear official timeline.

Cyclist riding an endurance route through open terrain

What matters

Designed around this event shape

Route progress and ETA

Show where each participant sits on the route, not only where the last GPS update was received.

Long-field visibility

Combine phone, tracker, upload, and correction data when update frequency or signal changes over the course.

Replay and result fixes

Keep the public story and the official event result aligned after the field finishes.

Why MapCatch

Why MapCatch is different here

The participant phone is not just a beacon. It can carry official route changes, warnings, chat, and progress context back to the rider while the public map updates from the same event state.

Long routes can evolve during the race. Organisers can adjust closures, neutral sections, checkpoint rules, or fallback tracking sources without rebuilding the event around a separate tracker-only system.

Public dotwatching can show more than dots: route progress, ETA, replay, source history, and corrections all stay connected to the official event story.

Organizer sales

Planning endurance races?

Share the route format, participant count, dates, terrain, and tracking mix you are considering.