Terrain-first running analytics

Know
your hills.

Find your most similar past efforts — climb for climb, gradient for gradient.

Segments
Finish a run; see your most similar past efforts, climb for climb.
Custom segment
Draw any stretch and find its closest matches across your history.
Race Preview
Predict a course’s splits — with honest flags where you have no comparable terrain.
Insights
Standing readouts of your training, learned patterns, and projected race times — each with its confidence.
How it works
Elevation profile — click a segment to compare
Segments in this run
Most similar efforts in your history
Segment overlay — this effort vs the selected match
Route
Running stats
Time in HR zone
Draw a segment — box-select a distance window on the profile
Route
Segment overlay — custom effort vs matches
Matches
Course profile — click a segment or box-select · colour = terrain, fade = confidence
Course route
Selection overlay — vs your history
Most similar efforts in your history
Insights

What your history says about you.

Standing readouts of the same engine that powers Race Preview — each shown with how sure we are and the data behind it. Where your history is too thin to be honest, the card says so.

How sure are we? — every insight carries one of these
Your runs

A plain summary of your history.

Confirmed

Holds up on runs we didn't train on.

Early signal

A real pattern, but not certain yet.

Rough estimate

A ballpark — treat it loosely.

Limited data

Not enough varied runs yet.

1
Your runs

Your training at a glance

A plain summary of what you've actually been doing — distance, effort and terrain. No models, no predictions, just your history.

2
What we've learned

What your running says about you

Patterns we've picked up from your runs — how hills, effort and fatigue change your pace. Each one shows how sure we are it's real.

3
Looking ahead

Where your fitness could take you

An estimate of your current race times, worked out from your recent training — no race required. These look forward, so they carry more uncertainty than the patterns above.

How it works

Two runs are comparable when they share a shape.

A 5-minute climb in the Alps and one in the Peak District can be the same effort. Altim ignores where you ran and compares the terrain you ran over — so every match is apples to apples.

The matching, in three steps

From a raw GPS track to a ranked list of efforts

Every run you sync goes through the same pipeline. Nothing here depends on the route’s location — only on its shape.

1

Split by terrain

Each track is cut into segments and labelled by gradient — climb, descent or flat — so a run becomes a sequence of shapes rather than a single line on a map.

2

Score the shape

Each segment is compared against every effort in your history on gradient, length and elevation change. The closer the profiles, the higher the similarity score.

3

Rank the matches

Efforts are sorted by quality and surfaced as your closest comparisons — so you see how today measures up against the times you ran something genuinely alike.

The building blocks

Four terrain classes, used everywhere

The same colours mean the same thing on every chart and table in the app — once you learn them here, you can read any profile at a glance.

Climb
Sustained uphill gradient — where pace drops and effort spikes.
Descent
Downhill running, where the shape of the drop sets your speed.
Flat
Level ground — the baseline your climbs and descents are measured against.
No match
Terrain you’ve never run before — shown greyed, never guessed.
Reading a result

How match quality is graded

Not every comparison is equally trustworthy. Each match carries a quality grade so you know how much weight to give it.

Very similar

Near-identical shape. Same gradient and length — the most direct comparison you can make against your past self.

Similar

Comparable effort. Minor differences in length or steepness, but the same kind of terrain.

Loose

Roughly alike. Useful for a ballpark sense, but read the overlay before drawing conclusions.

Weak

Distant match. Shown for completeness — the shapes diverge enough that the comparison is only indicative.

When there’s no honest comparison, we say so

In Race Preview, a course can include terrain you’ve simply never run. Rather than invent a prediction, those sections are faded out and flagged low-confidence — an honest gap beats a confident guess.

Standing readouts

What the Insights tab tells you

Race Preview compares a single run. Insights points the same engine at your whole history and reports what it sees — no race or course required. It refreshes after every sync, and comes in three layers:

1

Your training at a glance

A plain summary of what you’ve actually been doing — how much you run, how hard, and over what terrain. Facts about your history, no models involved.

2

What your running says about you

Patterns learned from your runs — how hills slow you down, how pushing harder speeds you up, and whether your fitness is trending up over time.

3

Where your fitness could take you

A forward-looking estimate of the race times your recent training points to — no race needed. Looking ahead is harder, so these carry more uncertainty.

Every insight wears its confidence on its sleeve

Rather than state everything with the same authority, each card carries a small label telling you how much to trust it — from a plain summary of your runs, through patterns we’ve verified, down to early hunches. When your history is too thin to be honest, the card says so instead of guessing.

Your runs

A summary of your history. A direct readout of what you did — not a prediction.

Confirmed

Trust it. The pattern still holds on runs the model was never shown, so it’s a real signal, not a fluke.

Early signal

Promising, not certain. The shape is there in your data, but not yet strong enough to be sure it’s real.

Rough estimate

A ballpark. Built from limited data — useful for a sense of scale, but treat it loosely.

Limited data

Not enough yet. Too few varied runs to show this reliably — it’ll sharpen as you log more.

See it on your own runs

Sync a run and watch the matching surface your closest past efforts.

What’s next

Where Altim is headed.

The engine that matches your terrain is just the start. Here’s what we’re building next — to make every prediction sharper and bring the same honesty to more of your training.

On the roadmap

Coming in future releases

A look at the features in progress and exploration. Priorities may shift, but this is the direction — each one earns its place by making the analysis more accurate or more useful.

Automatic activity sync

In progress

Connect your Garmin account once and new runs flow in the moment you finish — no manual upload, no export archives. Support for Coros, Polar and other brands follows.

For Everyone

Cycling support

Up next

The same terrain-first engine, tuned for the bike. Compare climbs and descents ride-to-ride, preview a course, and bring cyclists into Altim alongside runners.

For Cyclists

Terrain surface awareness

Exploring

Today every surface is treated alike. By tagging each segment as trail, asphalt, gravel or grass , matches get more honest and predictions more accurate — a road tempo won’t be compared to a muddy trail of the same gradient.

Improves Accuracy

Find a segment near you

Exploring

Pick a segment from a race course and Altim finds real-world segments near you — or in any area you choose — that match its shape. Train on terrain that mirrors the race, before race day.

For Race prep

Something you’d like to see?

Altim is built around how runners actually train. If a feature would change how you prepare, tell us — it helps set what comes next. Share an idea →