Skip to content

Ultra cutoff planner

Compute the minimum average pace to beat an ultra cutoff and sanity-check your buffer with a planned pace.

Last updated/Feb 03, 2026, 02:17 PM

Tool

Inputs → outputs

This page is intentionally practical: get numbers first, then read the how-to.

Inputs

  • Distance (km/mi)
  • Cutoff time (hh:mm)
  • Planned pace (sec per unit) (optional)

Outputs

  • Required average pace
  • Planned finish time
  • Buffer vs cutoff

Examples

50K in 8:00 cutoff
Compute required average pace; then add margin for aid-station time and terrain.
50 miles in 12:00 cutoff
Use as baseline, then adjust for vert, trail surface, and stoppage.

Calculator

Ultra cutoff planner

Compute the minimum average pace to beat a cutoff, and sanity-check your buffer with a planned pace.

Example: 420 sec per km = 7:00/km.

Required pace (km)

9:36

Planned finish

Buffer vs cutoff

Limitation: this ignores elevation, trail surface, aid-station stoppage, and mandatory gear transitions. Use it as a baseline, then add margin.

Assumptions

What this tool assumes

  • You can translate average pace into on-course execution (terrain can break this).
  • Aid-station time is not included — add margin.

Limitations

What can break it

  • Does not account for elevation gain/loss, technical trails, heat, or mandatory gear transitions.
  • Cutoffs are often per-segment; you should verify segment rules and plan accordingly.

Related

Use this with a plan

Coaching beta

Get a plan that adapts to your life.

Join the 26weeks.ai TestFlight beta for adaptive coaching, recovery-aware adjustments, and race-week reminders.

FAQs

Why do I need extra margin?

Ultras include aid-station time, terrain slowdowns, and fatigue drift. A cutoff is a hard line; planning margin is the safe move.

Should I pace by mile/km splits?

Usually not. Pace by effort and terrain, then use cutoffs as checkpoints rather than rigid split targets.

What’s the best way to avoid missing cutoffs?

Start conservatively, keep moving through stations, and avoid big spikes in effort early that cause late crashes.

Keep going