Create the event
Set the route, checkpoints, controls, event places, timing, participant invites, and public link.
Live tracking + participant app + dynamic event control
MapCatch lets outdoor event organisers start with the phones participants already carry, without waiting for tracker rental, shipping, handover, or returns. The phone becomes the participant's event map: own position, route context, official messages, progress, and other competitors when allowed. Organisers can update routes, checkpoints, visibility, tracking sources, messages, and results also during the event.
No mandatory tracker rental for phone-based setups. Add prepared Android phones, GSM trackers, or satellite trackers only where the event needs dedicated hardware, stronger coverage, or stricter evidence.


Use participant phones or prepared Android phones when app interaction and low logistics matter.
Add GSM, SPOT, Garmin, ZOLEO, uploads, timing data, or corrections where phones are not enough.
Update routes, checkpoints, controls, places, messages, tracking sources, and result context during the event.
Keep live positions, participant context, public following, replay, and corrections aligned.
How MapCatch works
Build the event once, then keep it accurate as the route, checkpoints, controls, field, weather, devices, and organiser decisions change.
Set the route, checkpoints, controls, event places, timing, participant invites, and public link.
Use participant phones, rented Android phones, GSM trackers, satellite trackers, uploaded activities, timing data, or organiser corrections.
Send official messages, update routes or controls, switch tracking sources, handle incidents, and keep the event view aligned with reality.
Spectators follow the live event record. Organisers can replay, correct, and show what changed.
Event types
Use MapCatch for fixed courses, checkpoint logic, reveal rules, optional variants, and event structures that change in the field.

Long routes, sparse fields, route progress, replay, and corrections.

Checkpoints, crews, route or control changes, safety context, and changing conditions.

Separate stages, timing context, participant state, and public story.

Locations, clues, missions, proof points, teams, and custom scoring.

Different start times with shared rankings, progress, and public following.

Mandatory or optional controls, route choices, map context, and reveal rules.

Sparse updates, satellite devices, narrative context, and long-duration awareness.
Why it is different
MapCatch keeps route, checkpoints, controls, event places, tracking sources, official messages, public following, replay, and corrections aligned while the event unfolds.
Participants and spectators see route progress, standings, messages, source context, replay, and visible corrections.
Use routes, checkpoints, controls, event places, optional variants, progressive reveal, and event-specific rules.
Update routes, controls, messages, tracking sources, and result context while the event is live.
Use phones where they fit, trackers where they matter, and uploads or corrections where evidence is needed.
Manage the event from the start area, checkpoint, car, forest, or finish without returning to a laptop.
Phone-first event control
Yes. Mobile-first organiser controls keep decisions close to the field.
Change the event structure. Publish route, checkpoint, control, or place changes for closures, permit changes, unsafe sections, or optional variants.
Send official event context. Participants can receive messages, control updates, and route context in the app instead of relying on scattered chats.
Switch tracking sources. Move a participant from phone to tracker, tracker to upload, or correction to official result when reality changes.
Keep corrections transparent. Tracking source changes and result corrections can stay visible in the live event record.
Devices
Yes. MapCatch can combine several sources for one participant and keep the event story coherent when coverage, batteries, hardware, or organiser decisions change.

Best for low logistics, rich interaction, official messages, route or control updates, and high-detail tracks.

Best when you want phone-app benefits but need prepared, predictable hardware.

Best for simple dedicated equipment where cellular coverage is usable.

Best for remote terrain, oceans, long signal gaps, and sparse satellite updates.
Best for official evidence, post-event completion, checkpoint confirmation, and clear results.
What changes for organisers
Usually built around one route and participant dots.
Supports routes, checkpoints, controls, event places, reveal rules, tracking sources, and corrections.
Every participant usually needs assigned hardware.
Start with phones where suitable; add devices only where needed.
A tracker reports position but tells the participant little.
The app can show route context, official messages, standings, updates, and event state.
Course or rule changes often sit outside the tracking map.
Update routes, controls, messages, and tracking sources during the event.
A failed tracker creates a gap or manual cleanup later.
Combine or switch phone, tracker, upload, timing, and correction sources.
Followers see dots, leaderboard, and maybe replay.
Followers and organisers can understand what changed, why it changed, and how the final result was corrected.
Pricing
Start with app access for participants. Add rented phones, GSM trackers, satellite trackers, delivery, setup, or race-day support only when your event needs them.
The estimator shows an example setup first. Your quote depends on duration, rented hardware, integrations, and support.
Public following
Spectators, crews, families, and fans can follow on the web or in the MapCatch app.
They open the public event view to follow positions, progress, standings, ETA, messages, replay, and visible corrections.
Public following shows the live event record, but it is not the centre of the product.
Trust and safety
MapCatch improves event awareness, but it is not an emergency dispatch service and does not guarantee remote-area coverage.
Plan remote or high-risk events with suitable trackers, communications, local procedures, and support.
Safety awareness and incident context. Stale positions, low battery, off-route context, and organiser messages can support human decisions without replacing emergency procedures.
Changing conditions. Route, checkpoint, control, or place changes can be published with official messages when weather, access, or field decisions require it.
Plan your event
Tell us the format, terrain, participant count, event structure, and where conditions may change.