Running Power Calculator
The formula
What the running watts tells you
The mechanical power a runner produces, built from the di Prampero model: metabolic cost, vertical work on grades, and air drag.
Calculation: di Prampero: P = (155.7·v⁻¹ − 31)·mg + g·sinθ·mv + 0.5·ρ·CdA·v³. Enter your inputs and every substitution is shown below the result.
Reading the result
Power strips out HR lag — the number responds the instant you surge, which is why it works for intervals.
Rules of thumb: Recreational 250–350 W; elites 400 W+ at marathon pace
Limitations and best practice
The metabolic cost term (≈3.6–5.5 J/kg/m) varies by runner; an assumed 4.4 mislabels everyone’s absolute watts, though trends stay valid.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Is running power like cycling power?
Does wind really matter?
Source & methodology
di Prampero 1985; Minetti 2002.
How Running Power works — and what your result really means
You are here because you need a specific number, and you want to see how it was produced before you rely on it. Searchers land on a Running Power page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
A calculation like this one is worth roughly as much as a careful sentence: it forces several vague considerations into one comparable quantity. Once Running Power is on the table, the argument can stop being about impressions.
In plain terms, Running Power answers the question "Running power?". The measurement matters because it converts a situation that feels complicated — several inputs pulling in different directions — into a single number you can act on. Within Health & Medical, Fitness Performance is the context where this figure is quoted most often, and professionals treat it as a first-pass screen rather than a verdict.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to running power = 2,549 W on the default inputs, and the sensitivity section ranks the inputs that move the result — Pace first, at ≈11.3 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
How Running Power is computed, line by line
One formula, published in full: di Prampero: P = (155.7·v⁻¹ − 31)·mg + g·sinθ·mv + 0.5·ρ·CdA·v³. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.
Weight (kg) (example value 76) is a quantity rather than a category — precision here is cheap and worth having. Weigh rather than estimate where you can — this field usually enters the formula multiplicatively.
Pace (min/km) (example value 5) is a quantity rather than a category — precision here is cheap and worth having. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Grade (%) (example value 0) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Enter it exactly as your document states it — quoted annual, monthly and effective rates are three different numbers.
Metabolic cost (J/kg/m) (example value 9) is a quantity rather than a category — precision here is cheap and worth having. Keep every money input in the same currency; mixing systems quietly corrupts the comparison.
Air drag coefficient (Ns²/m²) (example value 1) is a quantity rather than a category — precision here is cheap and worth having. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
A fully worked Running Power example
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Weight (kg), Pace (min/km), Grade (%), Metabolic cost (J/kg/m). The endpoint of that chain is 2,549 W of running power, sitting in the “2,549 W to hold 4.50/km — 2,533 W metabolic, 0 W climbing, 15 W air” band.
- v = 1000 ÷ (4.50 × 60) = 3.70 m/s
- P = cost·m·g·v + m·g·sinθ·v + ½ρCdA·v³
- = 2,533 + 0 + 15 = 2,549 W
Speed — 3.70 m/s. If your inputs change, this is usually the first companion figure to move.
Metabolic term — 2,533. If your inputs change, this is usually the first companion figure to move.
Grade term — 0. This is the number experienced users quote when the headline alone would mislead.
Power per kg — 33.53 W/kg. Compare it against the main result of 2,549 W before drawing conclusions.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
The Running Power corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: Running Power was recomputed at 5 points along the dominant input, with every other field left untouched.
| Pace setting | Running power |
|---|---|
| 80 % of the example value | 3,196 W |
| 90 % of the example value | 2,836 W |
| example inputs | 2,549 W |
| 110 % of the example value | 2,314 W |
| 120 % of the example value | 2,120 W |
Across 5 settings of Pace, the result spans 2,120 W to 3,196 W. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Pace alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change Running Power the most
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the running power. It is the fastest honest answer to “what matters most in Running Power?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Pace +10 % → Running Power = 2,314 W · −10 % → 2,836 W (the running power shifts ≈11.3 %)
- Weight: ten percent up gives 2,802 W, ten percent down gives 2,295 W — ≈9.9 % of the running power either way
- Metabolic cost: ten percent up gives 2,802 W, ten percent down gives 2,295 W — ≈9.9 % of the running power either way
- Air drag coefficient +10 % → Running Power = 2,550 W · −10 % → 2,547 W (the running power shifts ≈0.1 %)
Pace is the dominant lever here: ten percent either way moves the result by about 11.3 %, from 2,314 W to 2,836 W. Spend your verification effort there first, and treat Weight as the second priority (≈9.9 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Reading the result: bands, zones and thresholds
Nobody acts on a bare figure — they act on a figure with a comparison attached. On the example inputs the band reads “2,549 W to hold 4.50/km — 2,533 W metabolic, 0 W climbing, 15 W air”; your own figures place you on a different rung of the same ladder. The sensitivity list shows how far a modest input error moves you along that ladder: for Pace, ±10 % covers 2,314 W to 2,836 W. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.
Set Running Power beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
The errors that quietly break a Running Power figure
The metabolic cost term (≈3.6–5.5 J/kg/m) varies by runner; an assumed 4.4 mislabels everyone’s absolute watts, though trends stay valid. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Acting on one reading. Day-to-day variation is real; confirm any surprising Running Power on two separate occasions before changing behaviour.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Pace dominating — a careful figure there beats false precision everywhere else.
The subtlest error is answering the wrong question precisely. Confirm that running power is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
A quick check for any Running Power figure
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Put Pace under a magnifier; the sensitivity table above is the reason why.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Compare the result with one independent method or published benchmark.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
Step by step: getting a trustworthy Running Power out of this tool
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Running Power takes a minute to learn and applies to every input above.
Step 1 — collect, then type. Everything this tool asks for is listed above (weight (kg), pace (min/km), grade (%), metabolic cost (j/kg/m), air drag coefficient (ns²/m²)). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. The point of transparency is that a reader can disagree with a specific line rather than with you.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 4 — ask what would have to be true. Take the result you want and work backwards through the inputs until you find the assumption that produces it; then decide honestly whether that assumption is defensible. Write the figure down before moving on; memory flatters whichever number you saw last.
Step 5 — write the one-line memo. “Running power = 2,549 W on this date, from these inputs.” That line is the entire deliverable; everything else on this page is how you earned the right to write it. Re-running a number costs seconds; retracting a decision costs considerably more.
Who actually uses Running Power — and when
Numbers earn their keep in conversations, and Running Power is no exception. In Health & Medical discussions around Fitness Performance, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. Rounding early is the quietest way to introduce a permanent error.
Used properly this is a five-minute filter that saves weeks. Compute Running Power, reject what fails, and only then bring in the expensive analysis for the survivors. Re-running a number costs seconds; retracting a decision costs considerably more.
There is a personal-administration use people overlook: periodic self-checking. Running Power quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. Rounding early is the quietest way to introduce a permanent error.
Quick answers: what searchers ask about Running Power
What affects Running Power the most?
Measured on this engine, Pace is the dominant lever: moving it ±10 % shifts the running power across 2,314 W to 2,836 W — about 11.3 % of the headline, with Weight next at ≈9.9 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Which matters more: weight or pace?
By the numbers, Pace: a ten-percent change in it moves the result ≈11.3 %, versus ≈9.9 % for Weight. Spend your measuring effort in that order — precision on the weaker lever buys almost nothing.
What is a typical Running Power?
On the worked example above Running Power comes out at 2,549 W. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Running Power by hand?
Three steps: write the formula (di Prampero: P = (155.7·v⁻¹ − 31)·mg + g·sinθ·mv + 0.5·ρ·CdA·v³), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Running Power than any number of calculator runs.
What happens to Running Power if pace changes by 10 %?
On these inputs a ±10 % change in pace takes Running Power to 2,314 W against the 2,549 W example — around 11.3 % of the headline. The same test on every other field is in the sensitivity section.
Is the Running Power result of 2,549 W good or bad?
The tool answers “what”, not “whether”: 2,549 W carries the verdict “2,549 W to hold 4.50/km — 2,533 W metabolic, 0 W climbing, 15 W air” for the default case, which is a starting interpretation rather than a verdict on your situation. Re-run with your own figures and compare the bands.
Does Running Power change with age?
Yes — reference bands shift deliberately across the lifespan, which is why this tool prints an interpretation rather than a bare number. Re-read the bands each time inputs like Weight (kg) change materially.
Is Running Power accurate?
The arithmetic is exact: di Prampero: P = (155.7·v⁻¹ − 31)·mg + g·sinθ·mv + 0.5·ρ·CdA·v³ is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 2,549 W result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Is running power like cycling power?
Same unit, different reliability — the treadmill and shoe sensors estimate the model, not measure force.
Does wind really matter?
Above ~15 km/h the cubic air term grows fast; a headwind can add 40+ W.
Does this Running Power tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Health & Medical figures and the reason you can re-run this page as often as you like.
The vocabulary of Running Power
- Speed
- 3.70 m/s for the Running Power worked case; it sits next to the main result because it carries context the headline leaves out.
- Metabolic term
- 2,533 in the default Running Power calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Grade term
- 0 in the default Running Power calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Running power
- The primary output of this tool: 2,549 W for the default inputs, computed exactly from di Prampero: P = (155.7·v⁻¹ − 31)·mg + g·sinθ·mv + 0.5·ρ·CdA·v³.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “2,549 W to hold 4.50/km — 2,533 W metabolic, 0 W climbing, 15 W air”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Running Power moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
The model is published arithmetic implemented exactly as written: di Prampero: P = (155.7·v⁻¹ − 31)·mg + g·sinθ·mv + 0.5·ρ·CdA·v³. Source of record: di Prampero 1985; Minetti 2002. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. What that buys you is reproducibility — two people, two browsers, the same arithmetic, and a printed trail from inputs to result that either of them can audit.
Turning this Running Power into a decision
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.