Running league appendix

The Competitive Rulebook is shared across URX leagues. Pages written in discipline-neutral language apply to every competitive event unless they explicitly point here.

This appendix holds Running league specifics: how pace and distance are expressed, what outdoor GPS evidence should look like, and integrity expectations that differ from Swimming. For pool laps, open-water formats, and min/100 m pacing, read the Swimming league appendix.

Units and display

When a shared Rulebook page gives a numeric example without naming a league, check this table—or the Swimming appendix—before comparing your effort to a threshold.

When shared pages defer here

Shared articles describe activities, publication, verification, and mechanics for all leagues. Consult this appendix when you need:

• Pace or distance numbers in min/km / km / mi
• Outdoor GPS route evidence and track-quality norms
• Running mechanic floors (minimum pace, walking vs running range)
• Accuracy and progression signals that read GPS and pace stability on outdoor sessions

Core policy remains in Submission requirements, Accepted evidence, and Race mechanics.

Outdoor GPS and route evidence

Running activities in URX are normally outdoor efforts recorded with a tracking application that captures GPS (or equivalent location) along the route.

A strong screenshot or tracker link typically shows:

• Total distance and elapsed time (or moving time, if your app distinguishes it—match what you publish)
• Average pace in min/km (or min/mi)
• A visible session date within the three-calendar-day freshness rule
• A route map or clear indication the session was recorded outdoors, when the app provides one

Reviewers and automation treat implausible GPS (teleporting, collapsed distance, obvious indoor-treadmill patterns presented as outdoor road/trail) as integrity risk. Honest tracker glitches may still enter manual review; systematic misrepresentation is a Rule violation, not a mere publication block.

When you are near the top of a leaderboard, include a tracker link whenever the publication form offers it—see Provisional leader.

Running mechanics and pace floors

RUN races are scored on running, not on walking. Most formats apply a minimum pace floor: the slowest pace still eligible per unit distance, as stated in the race brief. Activities slower than that threshold cannot be published to that race—the system blocks the post; that is not Disqualification (DQ) unless integrity abuse is involved.

Mechanic names (Classic, Open, Pace Lock, Multirun, …) are shared product terms; numeric bands in the brief are always league-scoped. Full type definitions: Race mechanics.

Integrity notes (running)

• One activity, one publication — the same outdoor run must not be bound to multiple race publications (see Submission requirements).
• Fresh activity — session date must fall inside the three-calendar-day window ending on the publication day; backdating or recycled captures are rejected or escalated.
• Mechanic fit vs DQ — wrong pace or distance for a given race blocks publication to that event; it is not DQ unless paired with fraud or Abuse & manipulation policy behaviour.
• Accuracy — Accuracy metric reads pace stability on verified outdoor sessions; erratic or inconsistent reporting can increase review scrutiny.

Related shared topics

See also: Verified performance; Swimming league appendix; Discipline metric.