Create the event
Set the course, controls, event locations, timing, participant invites, and public link.
Live GPS tracking + participant app + event control
MapCatch helps outdoor event organisers run many events with the phones participants already carry, without renting, shipping, handing out, or collecting GPS trackers. The phone becomes the participant’s event map: it shares live position and shows own location, route context, official messages, progress, and other competitors when allowed. Organisers can update routes, checkpoints, visibility, tracking sources, messages, and results while the event is running.
For phone-based events, organisers do not have to rent and distribute GPS trackers. Add prepared Android phones, GSM trackers, or satellite trackers only when the event needs managed hardware, stronger coverage, longer battery life, or stricter proof.


Let participants use their own phones, or rent prepared Android phones when you want the app workflow with predictable hardware.
Use GSM, SPOT, Garmin, ZOLEO, uploads, timing data, or corrections when coverage, battery life, rules, or proof require more than a phone.
Update routes, checkpoints, event locations, messages, tracking sources, and result notes during the event.
Positions, route progress, participant messages, public following, replay, and result corrections stay connected.
How MapCatch works
Set up the event once, then adjust routes, checkpoints, participant devices, messages, and results as real-world conditions change.
Set the course, controls, event locations, timing, participant invites, and public link.
Use participants’ own phones, rented Android phones, GSM trackers, satellite trackers, uploaded activities, timing data, or organiser corrections.
Send official messages, update routes or checkpoints, switch tracking sources, handle incidents, and keep the event map aligned with reality.
Spectators follow the event on a live map. Organisers can replay, correct, and explain what changed.
Event types
Use MapCatch for fixed routes, checkpoint logic, hidden or gradually revealed sections, optional route choices, and formats that change during the event.

Long courses, spread-out fields, course progress, replay, and corrections.

Controls, crews, course 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 a public live view.

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

Sparse updates, satellite devices, narrative context, and long-duration awareness.
Why it is different
MapCatch keeps routes, checkpoints, event locations, tracking sources, official messages, public following, replay, and result corrections together as the event unfolds.
Participants and spectators see route progress, live results, organiser messages, tracking-source information, replay, and visible corrections.
Use routes, checkpoints, event locations, optional variants, progressive reveal, and event-specific rules.
Update routes, checkpoints, messages, tracking sources, and result notes while the event is live.
Use phones where they are enough, trackers where conditions require them, and uploads or corrections where proof is needed.
Manage the event from the start area, a control, the car, the forest, or the finish without returning to a laptop.
Control from a phone
Yes. Organisers can make field decisions from a phone instead of returning to a laptop.
Change the route or checkpoint structure. Publish route, checkpoint, or location changes for closures, permit changes, unsafe sections, or optional variants.
Send official event context. Participants can receive messages, checkpoint 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 remain visible in the live event record.
Devices
Yes. MapCatch can combine several sources for one participant and keep the history understandable when coverage, batteries, hardware, or organiser decisions change.

Best for simple logistics, rich interaction, official messages, course 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, control confirmation, and clear results.
What changes for organisers
Usually built around one route and participant dots.
Supports routes, checkpoints, event locations, reveal rules, tracking sources, and result corrections.
Every participant usually needs assigned hardware.
Use participant phones where possible; add rented phones or trackers only where needed.
A tracker reports position but tells the participant little.
The app can show route context, official messages, live results, updates, and event state.
Course or rule changes often sit outside the tracking map.
Update routes, checkpoints, 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 and maybe a leaderboard or 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 live view
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, live results, estimated arrivals, messages, replay, and visible corrections.
The public view is what followers see; organiser tools behind it keep the map, messages, and results accurate.
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-course context, and organiser messages can support human decisions without replacing emergency procedures.
Changing conditions. Course, control, or location 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, route or checkpoint structure, and where conditions may change.