Track3D Guide

How to Translate an Elevation Profile Into Your Ultramarathon Race Plan

Trail & ultramarathon guidance

Two 100 km races can both have 4,000 meters of climbing and be completely different races.

One might spread that climbing across dozens of short rollers, another might put most of it into three long climbs. One might give you its biggest descent while your legs are still fresh, another might save it for kilometer 85.

The total elevation gain tells you how much climbing there is.

The elevation profile tells you when you will suffer.

An elevation profile shouldn't just be something you glance at before the race and decide looks “hilly”. It can help you break the course into meaningful sections, understand where hiking is likely to be part of the plan, identify where descents may become expensive, position checkpoints and cutoffs in context and build a timing plan that reflects the actual terrain and therefore effort.

The goal is not simply to read the elevation profile.

The goal is to translate it into a race plan you can actually use.

Total elevation gain is only the first number

Total elevation gain is useful. It gives you a quick indication of how much climbing is in the race and makes it possible to compare courses at a very broad level.

But it does not tell you what the race will feel like.

Imagine two 100 km courses with 4,000 metres of climbing.

Course A	Course B
Four major climbs of roughly 1,000 m each	Constant short climbs and descents across the entire race
Long periods of sustained climbing	Frequent changes in rhythm
Long descents between major summits	Very little truly flat running
Simple to divide into major terrain blocks	Potentially harder to settle into one rhythm

The total climbing is identical.

The way you train for them, pace them and plan checkpoint arrival times may not be.

That is why the first thing I want from an elevation profile is not the total number. I want to see how the climbing and descending are distributed across the course.

Read the axes before you read the shape

An elevation profile is normally a graph of distance against altitude.

The horizontal axis shows how far through the race you are and the vertical axis shows the altitude at that point.

That sounds obvious, but it matters because the line itself can be visually misleading.

If you see a big spike at 70 km, consider:

How long is the climb? A 600 m gain over 3 km is not the same climb as 600 m over 10 km.
What altitude does it start and finish at?
How much climbing has already happened before you reach it?
What comes immediately after it? A long descent, another climb or a runnable section?
Where is the next checkpoint?
What time of day are you likely to reach it?

Those questions begin turning the graph into a race rather than a picture.

The elevation profile becomes more useful when the route, checkpoints and race timing are considered together.

The steepness of the line is not the gradient of the trail

This is one of the easiest mistakes to make when looking at an elevation profile.

The horizontal and vertical axes usually use completely different scales. A graph may compress 100 kilometres of distance into the width of your screen while stretching 1,500 metres of altitude across most of the height.

That can make a perfectly normal climb look like a wall.

Another website can display exactly the same course using a different graph height and make it look much flatter.

Do not estimate trail gradient from the angle of the line on the page.

Use the actual distance and elevation change.

If a climb gains 600 metres over 6 kilometres, its simple average gradient is about 10%.

If the exact same climb is drawn on a very tall chart it may look brutally steep. On a shallow chart it may look almost gentle.

The trail did not change but the way it is displayed in the chart did.

Elevation gain per kilometre can help compare races

One useful way to add context to the total climbing is to look at how much vertical gain is packed into the race distance.

A 100 km race with 4,000 metres of gain averages:

4,000 m ÷ 100 km = 40 metres of climbing per kilometre

A 50 km race with the same 4,000 metres averages 80 metres per kilometre.

That does not automatically make the second race “twice as hard”. It tells you that the climbing is much more concentrated relative to the race distance.

This is useful for rough comparison, especially when looking at several races, but I would not turn it into a universal difficulty scale.

Forty metres per kilometre spread across long smooth climbs is different from forty metres per kilometre on a highly technical course with constant short ascents and descents.

Use vertical density to ask better questions, not to replace the profile.

One long climb and ten short climbs are different race strategies

A profile with one sustained climb allows you to settle into a rhythm for a long period. Depending on gradient and terrain, that might mean a controlled run, a power hike or a combination of both.

Repeated short climbs can be a different problem as they constantly change what your legs are doing.

Run. Climb. Descend. Run again. Climb again.

The total vertical gain may be the same, but the rhythm of the course is not.

Long sustained climb

Easier to identify as one race section. Effort can settle into a relatively consistent climbing rhythm.

Repeated rollers

Constant transitions between climbing, descending and flatter running can make average pace and simple split planning less useful.

Short steep ramps

May encourage repeated switches between running and hiking even if the overall section does not look dramatic.

Long runnable false flat

Can look almost flat on a compressed profile while quietly accumulating climbing and time.

This is why I split the race by meaningful terrain changes rather than by arbitrary 10 km blocks.

Average gradient can hide the real climb

A climb that gains 800 metres over 8 kilometres averages roughly 10%.

That number is useful, but it can hide a lot.

The first four kilometres might sit at 5%. The next two could be much steeper. The final two might flatten again.

A runner may be comfortable running one part and choose to hike another even though the entire climb has one average gradient.

The same problem appears when a short steep section is averaged together with a long gentle approach.

So when a major climb matters to the race plan, look beyond the average:

How long is it?
How much does it gain?
Does the gradient stay consistent?
Are there short steep sections inside it?
Is there somewhere to recover before the next major feature?

Where the climbing occurs matters

A major climb at 15 km and the same climb at 85 km are not the same planning problem.

Early in a race you are fresh, fuelled and probably moving more efficiently. Late in a race you may be dealing with accumulated fatigue, darkness, food fatigue, sore feet and many hours of descending already in your legs.

The profile gives you the order in which those problems arrive.

Profile feature	Race planning question
Large climb in the first quarter	How do I avoid turning the first climb into a race?
Long climb immediately after a major aid station	What food, fluid and equipment need to leave that checkpoint with me?
Major climb late in the race	How much time and energy do I realistically expect to have when I reach it?
Long descent before the final climb	How much damage might that descent do before I need the legs again?
Runnable final section	Is the planned schedule actually leaving enough time to use it?

The profile is not just showing you terrain.

It is showing you the sequence in which the race will ask you to deal with that terrain.

Do not ignore the descents

The climbs normally get the attention because they create the positive elevation number.

The descents can be just as important to the race plan.

Downhill running is usually cheaper from a cardiovascular point of view than climbing, but it creates substantial eccentric loading in the legs. Recent research in experienced trail runners continues to show measurable muscle damage and strength loss after sustained downhill running.

That means a long descent should not automatically be treated as free time.

There are several different descent problems:

Descent type	What it may mean for the race
Long smooth descent	Potentially fast, but sustained eccentric loading can become expensive later
Steep technical descent	Pace may be limited by footing, confidence and concentration rather than fitness
Repeated short descents	Constant braking and reacceleration can interrupt rhythm
Late race descent	Fresh-leg expectations from training may not reflect what is possible after many hours

This is one reason average pace becomes such a poor description of a mountain ultra.

A kilometre downhill is not automatically the opposite of a kilometre uphill.

The profile tells you where you lose altitude.

It does not tell you how much your legs will enjoy doing it.

Where are you likely to run and where are you likely to hike?

A race plan does not need to pretend every kilometre will be run.

On steeper climbs, hiking can be an efficient and completely normal part of ultramarathon pacing. The exact point where walking becomes more economical than running is not one universal gradient for every runner.

Controlled research continues to show that the preferred walk to run transition on climbs relates closely to energetic cost, but it varies with speed and conditions.

For race planning, the practical question is simpler:

Which parts of this profile are realistically going to be hiking terrain for me?

Mark those areas before assigning section times.

If you know a long climb is likely to be mostly hiking, do not build its split from your normal running pace and hope the gradient somehow disappears on race day.

Likewise, do not assume every moderate climb will be walked simply because it points upward on the graph.

Your own training and race experience matter here.

Put the checkpoints and cutoffs onto the elevation profile

The profile becomes far more useful when you stop looking at it as terrain alone.

Add the checkpoints.

Now the questions change.

Is the checkpoint at the top of the climb or two kilometres after it? Is there a major descent before the next aid station? Is the tight cutoff immediately after the hardest climbing section? Is the crew checkpoint before or after the point where you expect to change into night gear?

A checkpoint at 60 km tells you distance.

A checkpoint at 60 km sitting at the end of a 1,100 metre climb tells you much more.

Distance tells you where the checkpoint is.

The elevation profile tells you what you have to do to get there.

This is also where cutoff planning becomes more useful. A cutoff that looks generous on a spreadsheet may be much less comfortable once you can see the terrain that sits immediately before it.

Turn the profile into race sections

Once the main terrain features and checkpoints are visible, divide the race into sections that actually mean something.

Do not worry about making every section the same distance.

A useful section might be:

Start to the base of the first major climb
The full climb to the ridge
The ridge and technical descent to CP2
The long runnable valley section
CP4 through the final major climb
The final descent and run to Finish

That gives you terrain blocks that can be understood individually.

Here is a simple hypothetical example:

Section	Distance	Gain	Loss	Profile interpretation
Start → CP1	18 km	400 m	250 m	Rolling opening section
CP1 → CP2	13 km	1,000 m	100 m	First major sustained climb
CP2 → CP3	15 km	100 m	900 m	Long descent
CP3 → CP4	24 km	800 m	700 m	Constant rolling terrain
CP4 → CP5	14 km	900 m	100 m	Late major climb
CP5 → Finish	16 km	250 m	1,000 m	Long descent with a runnable finish

Now you have something you can plan.

Turn the sections into time, not one average pace

This is the point where the elevation profile becomes a race plan.

If your target finish is 16 hours, it is tempting to divide 100 km into 16 equal hours and start with an average pace.

That is easy.

It is also weak planning for a hilly course.

The 13 km section with 1,000 metres of climbing should not receive the same pace assumption as a runnable 13 km valley section. The long technical descent may also take very different time from what the distance suggests.

Instead, assign time to each section based on what that terrain is likely to cost.

Then add the checkpoint stops.

Then check the cutoffs.

Then check whether the result still reaches the target finish.

Distance is part of section time.

Terrain explains why equal distances do not necessarily deserve equal time.

If you want the broader framework around target finish, stops and race execution, the related Guide How to Plan Your Race Day for a 100K or 100 Mile Ultramarathon covers that in more detail.

Use the profile to identify the expensive kilometres

Some kilometres cost much more time than others.

A steep climb can be expensive because forward speed is low. A technical descent can be expensive because you cannot safely use the downhill speed the profile seems to offer. A rolling section can be expensive because it never lets you settle.

The profile helps you find those sections before race day.

That is useful for pacing, but it is also useful for expectations.

If a 12 km leg is expected to take three hours, knowing that before the race feels very different from reaching 90 minutes and wondering why you have only covered half of it.

A good race plan removes some of those surprises.

What an elevation profile cannot tell you

An elevation profile is useful, but it is not the course.

Two sections with the same gradient can have completely different real-world difficulty.

Missing from a simple profile	Why it matters
Technical surface	Rocks, roots, stairs and loose ground can change both climbing and descending speed
Mud or snow	The same gradient can become a completely different movement problem
Altitude	Absolute altitude is a different stress from total elevation gain
Weather exposure	Heat, cold, wind and rain can change effort and equipment requirements
Trail width and congestion	Early bottlenecks can affect movement even on easy terrain
Night	Technical terrain may take longer when visibility and concentration are reduced

This is why I would never take a profile, run a formula across it and treat the result as a prediction of what will definitely happen.

The profile gives structure to the plan.

Your knowledge of the course, conditions and yourself still matters.

Why Garmin, Strava and the race may show different elevation gain

If you have ever loaded the same route into several platforms, you may have noticed that the elevation totals do not always agree.

That does not necessarily mean one of them is broken.

Elevation can come from different sources:

Barometric altimeter data from a device
GPS derived altitude
Digital elevation models or elevation databases
A corrected elevation basemap

Platforms can also apply different smoothing and filtering rules before adding every little rise and fall into the total.

Strava, for example, explains that it may use barometric data, GPS plus its elevation basemap or public elevation data depending on the source. It also smooths elevation to reduce GPS noise.

So if the official race page says 4,800 metres, your GPX parser says 5,050 and another platform says 4,650, the useful response is not automatically to choose the biggest number.

Understand which course file you are using and use one consistent source for your planning.

Treat elevation gain as measured data, not absolute truth

Small differences between platforms are normal because the source elevation data and the way it is processed can differ. Large differences are worth investigating before you build the race plan.

Where Track3D Race Planner fits

Track3D Race Planner starts with the actual race course rather than an average pace.

Load the GPX or supported FIT course and the planner builds the distance and elevation profile from that route. You can then place checkpoints into the course, add official cutoffs, plan checkpoint stop time and set the target finish.

The useful part is that those things remain connected.

A major climb is not just a spike on a chart. It sits inside a specific checkpoint to checkpoint section with distance, gain, loss, planned time, arrival, stop and departure.

Course-Aware Pacing can then distribute the available moving time across the course rather than pretending every kilometre deserves the same pace.

That does not mean the model knows whether the trail will be muddy or whether your quads will be destroyed after the previous descent. Those are still real-world variables.

What it does is give the plan a better starting structure than distance divided by target finish time.

The elevation profile is the terrain story.

The Race Plan turns that story into sections, times, checkpoints and decisions.

Once the Race Plan is built, the same checkpoint structure can also be carried into Garmin Course Points so useful race information stays close at hand on a compatible watch.

A practical elevation profile checklist

Look at	Ask yourself	Put into the Race Plan
Total elevation gain	How much climbing is there overall?	Whole-course terrain context
Distribution of climbs	Long climbs, rollers or short ramps?	Meaningful terrain sections
Gradient changes	Where am I likely to run or hike?	Realistic section timing
Major descents	Are they runnable, technical or likely to damage the legs?	Do not assume downhill equals free time
Location in race	What will this terrain feel like after the hours before it?	Late-race timing expectations
Checkpoints	Where do aid stations sit relative to the major terrain?	Arrival, stop and departure plan
Cutoffs	Does the hardest terrain sit before a tight deadline?	Cutoff buffer by checkpoint
Surface and conditions	What can the graph not show me?	Keep the plan flexible

Common elevation profile questions

How do I read an ultramarathon elevation profile?

Start with the horizontal distance axis and vertical altitude axis, then identify the major climbs, descents and flatter sections. Look at how much elevation each climb gains, how long it lasts and where it occurs in the race. Then place checkpoints and cutoffs into that terrain rather than treating the profile as a standalone graph.

How much elevation gain is a lot in a trail race?

There is no universal number because distance and terrain distribution matter. Four thousand metres across 50 km is a very different concentration of climbing from four thousand metres across 160 km. Elevation gain per kilometre can help compare courses, but it should not be treated as a complete difficulty score.

Can I calculate trail race pace from elevation gain?

Elevation is one important input, but a simple gain-to-time formula cannot see technical surface, weather, altitude, mud, fatigue or how the climbing is distributed. For an ultra, section timing is generally more useful than applying one adjustment to the whole race.

Should I run or hike steep climbs in an ultra?

Both can be appropriate. The energetically efficient transition between walking and running varies with gradient, speed and the runner. Use your training experience to identify where hiking is likely to be part of your race rather than relying on one universal gradient threshold.

Why does the profile make a climb look almost vertical?

The horizontal and vertical axes use different scales. The visual angle of the line is not the trail gradient. Use the actual elevation change and horizontal distance when assessing a climb.

Why do Strava, Garmin and my GPX show different elevation gain?

Platforms can use different elevation sources and smoothing methods. Barometric altitude, GPS, digital elevation models and corrected elevation databases can all produce slightly different totals. Use a consistent course source for race planning and investigate differences that are large enough to materially change the plan.

Are descents important when planning an ultra?

Yes. A downhill section may allow faster movement, but sustained descending creates significant muscular loading and technical descents can be slow. A long descent can also affect what your legs are capable of on a later climb.

Does Track3D use the elevation profile when building the Race Plan?

Yes. Track3D uses the course distance and terrain to support Course-Aware Pacing, while checkpoints, planned stops, target finish and cutoffs remain part of the same schedule. It is a planning model, not a guarantee of race performance.

Turn the profile into something you can race

An elevation profile is one of the most useful pieces of information you get before a trail ultra.

But the line by itself is not the plan.

Look at where the climbing occurs. Look at the descents. Find the places where the gradient changes enough to change how you expect to move. Put the checkpoints and cutoffs into that terrain. Divide the race into sections that mean something.

Then assign the time.

That is the point where the elevation profile stops being a picture of the course and starts becoming part of your race plan.

Start with the course, then build the race around it.

Load your GPX or supported FIT course into Track3D Race Planner, add the checkpoints and cutoffs, and turn the terrain into a practical race schedule.

Open Track3D Race Planner

This Guide uses current trail-running guidance and research to explain the concepts behind elevation-profile interpretation. Trail Running Movement’s 2026 profile guide discusses axis scaling, climb distribution, average-gradient limitations and the need to consider descents: How to read an elevation profile and prepare for trail races. Strava explains that elevation can be calculated from barometric data, GPS and elevation databases and that smoothing affects total elevation gain: Strava Elevation. A 2026 study of experienced trail runners found muscle-damage and strength-loss responses after a controlled downhill run: Downhill running-induced muscle damage in trail runners. A 2026 study of endurance-trained runners found the preferred uphill walk-run transition closely aligned with energetic crossover under controlled conditions: Uphill walk-run transition study. These findings provide context, not universal race prescriptions; terrain, conditions and individual ability still matter.

Back to Guides