Editorial standards

How we set our benchmarks

Every number on this site should be checkable. This page explains where our calculators' maths comes from, how the benchmark ranges were chosen, and which claims are sourced versus coaching judgment.

The short version: our calculators use standard, published cycling formulas. Our benchmark bands are coaching-convention orientation ranges, not population statistics — and we do not claim otherwise, because we are not aware of a public dataset of amateur cyclist FTPs that would justify a percentile claim.

Who writes this

SmarterTraining is an independent cycling training app built around adaptive workout selection for real-world athletes. We write about training because it is the same problem the product solves: what should an amateur with a full life actually do this week?

SmarterTraining’s training guidance is educational and should not be treated as clinical or scientific advice. Where we rely on published physiology, we say so and point to the source; where we make a coaching judgment, we label it as one. Knowing which is which is the purpose of this page.

What kind of claim is what

Everything we publish falls into one of three buckets:

  • Standard formulas. Arithmetic and widely published conventions — W/kg is FTP divided by kilograms, FTP is conventionally estimated as 95% of 20-minute power, power zones follow the Coggan percentages. These are not our opinions and we present them as convention.
  • Derived models. Our benchmark and age tables. The inputs are stated on this page, the outputs are computed from them in code, and every page that shows one is reading from the same source. You can check our arithmetic.
  • Coaching judgment. Statements like “most amateurs should run two hard days a week” or “3 W/kg is solid trained fitness.” These are opinions informed by mainstream coaching practice. We label them as guidance, not findings.

What we do not do: invent statistics, quote population averages we cannot source, cite studies we have not read, or claim to have tested products we have not.

How the calculators work

FTP from a 20-minute test

The FTP calculator multiplies your 20-minute average power by 0.95. This 95% convention is standard in cycling coaching and exists because a 20-minute maximal effort draws on anaerobic capacity that you could not sustain for a full hour, so the raw figure overstates threshold.

It is a convention, not a measurement. A ramp test uses a different estimate entirely, and the two are not interchangeable — the gap between them for the same rider can exceed a year of genuine training. Compare like with like, and see ramp test vs 20-minute test.

Watts per kilogram

The W/kg calculator divides FTP in watts by body weight in kilograms. Pounds are converted at 2.2046 kg per lb. We use body weight only, not bike weight, because that is the convention riders compare against.

Power zones

The cycling power zone calculator uses the seven-zone Coggan model, expressed as percentages of FTP. Sweet Spot (roughly 88–94% of FTP) is shown alongside them as a coaching convention rather than a Coggan zone — it deliberately overlaps upper Tempo and lower Threshold.

How the W/kg benchmark bands were chosen

These are the bands behind the W/kg chart, what is a good W/kg, the calculators, and the progression guides. Four decisions produced them:

  1. They are referenced to trained male amateurs. The convention these bands sit in was built around men, and we label them that way on every page rather than presenting them as universal. See the section below on why there is no parallel female table.
  2. The boundaries sit on a 0.5 W/kg grid. That is the granularity at which a rider's practical capability visibly changes, and it maps one-to-one onto our progression guides — so a reader who lands in a band has exactly one guide to read next. Bespoke boundaries like 3.2 or 4.7 would imply a precision the evidence does not support.
  3. Two anchors set the scale. The framing follows the widely used power-profile convention in cycling coaching (Allen & Coggan, Training and Racing with a Power Meter), in which roughly 4 W/kg at threshold is the commonly cited gateway to competitive amateur racing and about 5 W/kg the entry to elite power-to-weight. We step evenly from those two anchors.
  4. Absolute FTP bands are computed, not written. The FTP table is the W/kg table projected onto a 75 kg reference rider and rounded to the nearest 5 W. This is why the FTP and W/kg tables on this site cannot contradict each other: there is one set of numbers, viewed two ways.

The resulting bands

Canonical W/kg bands and their equivalent FTP at the 75 kg reference weight
LevelW/kgFTP at 75 kg
NoviceUnder 2.0Under 150 W
Recreational2.0–2.5150–190 W
Intermediate2.5–3.0190–225 W
Experienced3.0–3.5225–265 W
Advanced3.5–4.0265–300 W
Competitive4.0–4.5300–340 W
Elite amateur4.5–5.0340–375 W
Elite5.0+375 W+

What these bands are not

They are not percentiles. You will find sites quoting things like “the average cyclist has an FTP of X” with apparent precision; treat those with suspicion. Cyclists who record an FTP are a self-selected, already-training group, so any average drawn from training-app data is biased upward by an unknown amount. We do not publish a population average because we have not found a source we would be willing to stand behind.

How the by-age tables were built

FTP by age and W/kg by age are two views of one model, which is how we fixed a real contradiction: the two tables previously implied different peak fitness for the same rider while linking to each other.

The model has three parts:

  1. A single reference band. A male amateur in his 20s who trains consistently, taken as 3.24.4 W/kg — equivalently 240330 W at 75 kg. On our scale that spans Experienced through Competitive: a rider who is comfortably strong on fast group rides, up to one who is competitive in regional amateur racing. It is the range for a rider who trains — not an average across all cyclists, which would sit well below it, and not a ceiling. Plenty of trained riders in their 20s fall outside it in both directions.
  2. A published age-adjustment curve. The share of that reference band a rider who keeps training is assumed to hold in each later decade. This is the “share of reference” column shown on both pages — the model is on the page, not hidden behind it.
  3. Projection. Every range in both tables is the reference band multiplied by that decade's adjustment.

The adjustment curve is anchored on a well-established observation in exercise physiology: maximal aerobic capacity (VO₂ max) declines roughly 0.5–1% per year from the late 30s, with the rate steepening after about 60. Compounded over a decade that is around 5–10%, which is what the curve reflects.

The approximation we are making, stated plainly

We then apply that curve to threshold power. This is the weakest link in the model, and it deserves to be said outright rather than buried: FTP is not the same measurement as VO₂ max. Threshold sits at some fraction of aerobic capacity, and that fraction is itself trainable. Threshold fraction, training history, muscle fibre characteristics, body composition, and current training status all move an individual's FTP independently of their VO₂ max trajectory — which is why a masters rider who starts training seriously can raise threshold power while aerobic capacity is nominally declining.

So the curve gives us a defensible shape for scaling a reference across the decades. It is not evidence that FTP or W/kg declines at exactly that rate, and we do not present it as such. The outputs are illustrative age-adjusted training references — orientation for a rider comparing themselves against peers, not a standard anyone should be meeting at a given age.

One curve drives both tables. An earlier version of this model scaled W/kg slightly harder than FTP in each later decade, on the reasoning that body weight tends to drift upward and W/kg is power divided by weight. That was our own coefficient with nothing behind it, so we removed it. Body weight is a real factor in how power-to-weight ages — it is just not one we can quantify, and a made-up number is worse than none.

And the caveat that matters most in practice: these are ranges for riders who keep training, and the difference between training consistently and not dwarfs the age effect entirely. A fit rider in their 50s routinely out-powers a sedentary 30-year-old.

Who the numbers apply to — and why there is no female table

Every numeric range on this site — the W/kg bands, the FTP bands, and both age tables — is referenced to trained male recreational and amateur cyclists. That is the population the underlying coaching convention was built around, so it is the population the numbers describe.

We do not publish a parallel numeric table for women. Sex-based physiological differences — haemoglobin mass, lean mass distribution, absolute aerobic capacity — mean these values do not transfer directly, so presenting them as universal would be wrong. But we also do not have a source or model for female threshold power-to-weight that we consider robust enough to publish as numbers, and inventing an offset would be worse than saying nothing.

So the honest position is: female cyclists should not read our tables as a percentile or reference table for themselves. Comparing against riders of the same sex, similar age, and similar training history is far more informative than any generic chart — and your own trend over time is better still. If we find a dataset solid enough to change this, we will publish it here and say where it came from.

How we write about other products

We make a cycling app, so our comparison pages are not neutral and we do not claim to be a review site. What we can commit to:

  • Facts come from the vendor. Prices, platforms, and trial terms are read from each company's own pages, kept in one file in our codebase, and shown with the source link and the date we last checked. Comparison pages were last reviewed in August 2026.
  • We say what we have and have not tested. We use our own product daily, so that assessment is first-hand. We have not run controlled head-to-head tests against other platforms, and we say so on the page rather than implying testing we did not do.
  • We publish our own weaknesses. Being iOS-only, having no virtual worlds, and not offering a dated periodized build are real limitations, and they appear in the same tables as everything else.
  • We do not invent competitor flaws. If we cannot verify something, it does not go on the page.

Corrections

If a number here looks wrong, or a competitor fact has gone stale, tell us at [email protected] and we will check it. Because the benchmark model lives in one place in the code, a correction propagates to every page that shows it.

Finally, the obvious but necessary note: this site is training guidance, not medical advice. If you have a health condition, are returning from illness or injury, or plan a significant change in training or body weight, talk to a qualified professional.