If you have ever looked at a climb on a Garmin Edge, Wahoo ELEMNT, Strava, or training platform and wondered what is VAM in cycling, the short answer is simple: VAM measures how quickly you gain elevation. It is usually shown in vertical metres per hour, or m/h.
That makes VAM useful for analysing climbs, but it is not a universal fitness score. A short, steep effort can produce a bigger number than a steady mountain climb, even when the longer effort demands more from you overall. Use VAM to compare similar efforts, not to turn every ride into a leaderboard.
This is an explainer for riders who already record rides or use a cycling computer. VAM can support your training analysis, but it does not replace power, heart rate, perceived exertion, or a broader view of your performance.
What does VAM mean in cycling?
VAM comes from the Italian phrase velocita ascensionale media, meaning average ascent speed. In practical terms, it is the rate at which you climb vertically. A VAM of 800 m/h means you are gaining 800 metres of elevation per hour at that rate.
It describes vertical movement, not forward speed. You might be travelling at 12 km/h on a steep climb and 25 km/h on a shallow one, but VAM focuses on how much elevation you gain over time.
- VAM: vertical ascent rate, normally shown in m/h.
- Average speed: how quickly you travel along the road.
- Gradient: how steep the road is, usually expressed as a percentage.
- Elevation gain: the total vertical metres climbed.
- Power: the mechanical effort applied to the pedals, measured in watts.
You will usually encounter VAM in climb analysis on a cycling computer, a Strava segment, or a dedicated training platform. Some systems calculate it from GPS elevation data, while others may use a barometric altimeter or corrected mapping data.
The useful judgment is this: VAM works best when you compare your own efforts on the same or very similar climbs. Comparing a 10-minute ramp with somebody else’s two-hour mountain ascent is mostly comparing apples with a derailleur.
How to calculate VAM
The basic formula is:
VAM = elevation gained in metres / climbing time in hours
For example, if you climb 600 metres in 45 minutes, first convert 45 minutes into hours:
45 minutes = 0.75 hours
Then:
600 / 0.75 = 800 m/h
Your VAM for that effort is 800 m/h.
A second example is 300 metres of climbing in 30 minutes:
30 minutes = 0.5 hours
300 / 0.5 = 600 m/h
For a quick calculation, you can also multiply elevation gain by 60 and divide by time in minutes:
VAM = elevation gain in metres x 60 / time in minutes
If you prefer imperial units, the same method gives vertical feet per hour. Climb 2,000 vertical feet in 30 minutes and you are climbing at 4,000 ft/h. The unit changes, but the calculation does not.
Use the elapsed time for the defined climbing effort. If you stop at a junction, pause your computer, or include a long traffic interruption, decide whether that is part of the effort before comparing it with another ride. Different platforms handle stopped time differently, so consistency matters more than pretending the number is laboratory-grade.
Do not normally divide the total elevation gain of an entire ride by the ride time and call it a climb benchmark. Descents, flat roads, junctions, cafe stops, and traffic make that an overall ride-climbing rate, not a useful measure of how you climbed one hill.
VAM examples: what the number is actually telling you
The same rider can produce very different VAM figures in a single week. Duration, gradient, pacing, fatigue, and the type of climb all matter.
| Climbing effort | VAM |
|---|---|
| 300 metres in 30 minutes | 600 m/h |
| 600 metres in 45 minutes | 800 m/h |
| 500 metres in 20 minutes | 1,500 m/h |
The 1,500 m/h result looks spectacular, but it is not automatically the strongest performance. That effort lasts only 20 minutes and may be a short, steep climb ridden close to maximum sustainable intensity. The 800 m/h effort lasts 45 minutes and may demand much more disciplined pacing.
A short ramp can also make VAM unusually sensitive to timing and elevation errors. Starting the timer a few seconds late, finishing it a few seconds early, or gaining a handful of incorrectly recorded metres can move the result substantially.
Gradient changes the interpretation too. On a very steep climb, aerodynamic drag and rolling resistance matter less, so power-to-weight ratio becomes especially important. On a shallow climb, wind and drafting can have a larger effect. Two riders producing similar power may therefore record different VAM figures because of body mass, conditions, or pacing.
VAM is related to climbing performance, but it does not tell you your FTP, threshold fitness, or overall cycling ability. A rider can be strong on long climbs without producing an impressive short-climb VAM, and a punchy climber can post a huge number that fades quickly.
VAM benchmarks: useful ranges without false precision
Broad benchmarks can provide context, but they should not become a ranking system. The following ranges are illustrative for recreational cycling and are heavily dependent on climb duration, gradient, rider mass, weather, altitude, pacing, and data quality.
| Illustrative VAM | How to interpret it |
|---|---|
| 400-600 m/h | A common range for newer or less-trained riders, particularly on sustained climbs. |
| 600-800 m/h | A solid recreational climbing effort on a suitable climb. |
| 800-1,000 m/h | Useful context for a strong amateur effort, depending heavily on duration and gradient. |
| 1,000+ m/h | Often associated with highly trained riders or short, hard climbs; duration is essential context. |
These are not universal ability categories. A 700 m/h result over an hour may be more meaningful than 1,100 m/h over eight minutes. Altitude, heat, road surface, headwind, and accumulated fatigue can also make a normally familiar climb produce a lower number.
Your own repeatable climb is the best reference point. If you ride the same 20-minute climb with the same device and similar conditions, a personal best or a consistent improvement is more useful than comparing your result with an unrelated number from another rider.
Professional-rider VAM figures are particularly poor targets for ordinary training decisions. Race pacing, exceptional power-to-weight ratios, drafting, altitude, and short-duration efforts can all make those figures look like normal goals when they are not. Use professional data as sport context, not as a reason to redesign your life around one hill.
Why VAM can be misleading
VAM depends on two measurements: elevation and time. Errors in either one affect the result.
GPS elevation can be noisy, especially on short climbs. Smoothing, map corrections, tree cover, and poor satellite data can add or remove apparent elevation. A barometric altimeter can be more responsive, but pressure changes and calibration errors can still create drift.
Start and finish points matter. If one ride begins at the bottom of the climb and another begins 100 metres up the road, the numbers are not directly comparable. A few seconds of transition at either end can also make a noticeable difference on a short effort.
VAM is also affected by factors that have little to do with a simple improvement in fitness:
- Gradient and changes in gradient.
- Headwind, tailwind, and drafting.
- Heat, altitude, and road surface.
- Traffic, junctions, and interruptions.
- Cadence, pacing, and fatigue.
- GPS smoothing, barometric drift, and device differences.
That is why VAM is not a pure fitness score. Treating a single GPS-derived number as definitive is especially risky on short climbs, where small errors can create large percentage changes.
How to use VAM in training and ride analysis
Choose a repeatable climb and track efforts over a consistent duration, such as 10, 20, or 30 minutes. Record the elevation gain, elapsed climbing time, device used, and general conditions. A spreadsheet or calculator is enough; you do not need another subscription simply to divide metres by hours.
Use VAM alongside other information when it is available. Power, particularly watts per kilogram, helps explain the effort more directly. Heart rate and perceived exertion show how hard the climb felt. Time, cadence, temperature, wind, and fatigue help explain why the number changed.
VAM can also expose pacing problems. If the first few minutes produce a very high figure and the final section collapses, you may have started too aggressively. A slightly lower opening pace with a steadier finish can produce a better overall climb and a more useful training result.
Look for trends across several similar efforts rather than reacting to one ride. The safest practical default is to treat VAM as a climbing-specific dashboard metric: useful for tracking repeatable efforts, but not the final verdict on whether you are getting fitter.
Common VAM questions
Is a higher VAM always better?
No. A higher VAM means faster vertical gain for that particular effort, but it does not make unlike efforts directly comparable. A short, steep climb can produce a high number that fades quickly, while a lower VAM sustained for an hour may represent stronger pacing and greater endurance.
Is VAM the same as watts per kilogram?
No. VAM measures the rate of vertical ascent; watts per kilogram measures power relative to body mass. They can correlate on a steady climb, particularly when gradient is high, but wind, road surface, pacing, gradient changes, and elevation-data errors can separate them. If you have power data, use it to add context rather than treating VAM as a substitute.
I’ve spent way more time in the bike trade than anyone should reasonably want to. In that time I’ve wanted to make cycling jargon and marketing easier to cut through to help people get the bike of their dreams.
When I’m not writing about bikes, I can be seen out bikepacking on single speed bikes or teaching kids how to ride.
