About Pacevine

A pacing plan computed from your route, not a flat average.

The problem

On a flat marathon, one target pace works for the whole race. On a mountain course it never does. Grade, terrain, and the fatigue that builds through the day break a flat average — the same runner can range from 6 to 20 minutes per kilometre in a single race. Predictions built on road logic fail, and runners blow up mid-race or miss cutoffs.

Most existing tools either ignore terrain and fatigue, or work as a black box: a number appears with no explanation of how it was computed and no way to check it.

How it works

Upload your route GPX, or pick a race from our catalog. We compute a pacing plan segment by segment, from the actual elevation profile, terrain, and a fatigue model — not one average pace applied to the whole route.

The plan goes with you on race day: a Garmin data field carries it on your wrist and adapts as you run (more watch platforms are coming). The plan can be recomputed and edited — you stay in control, not the algorithm.

What we hold to

Honest numbers — We never invent data. If we can't compute something reliably, we show "—" and say why, instead of making up a value.

Transparent method — Elevation gain depends on how you smooth the GPS track — there is no single true number. We explain our method openly instead of pretending there is one.

Engineering over marketing — We validate the model against real routes and reference tools. Your own pace on a route beats a population average.

Found a route that broke the plan, or have a question? Tell us through the contact form — we read every message.