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/Mar 20, 2026, 02:10 PM
Jump to

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

Export

Print or share the tool

Useful outputs beat generic SEO copy. Print a PDF or share this page before race week.

Tip: print or save as PDF for race week.

Example presets

Prefill with a realistic scenario

Pick an example to prefill the calculator, then tweak inputs for your own training week.

Loading cutoff planner…

Quick answers

The 60-second version

Snippet-ready answers to common questions. Use the calculator above for the numbers.

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.

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