METRIC EXAMPLE
Aerobic efficiency in meters per heartbeat
Meters per heartbeat gives a physical unit to one running-efficiency ratio. Keep that unit attached to the number when comparing results.
Convert the clock to minutes
Divide distance in meters by average heart rate multiplied by duration in minutes. Equivalently, multiply speed in meters per second by 60 and divide by heart rate in beats per minute. Runome's summary aerobic-efficiency calculation uses this meters-per-beat convention.
The result is a ratio formed from recorded summary values. It does not count the oxygen used to cover a meter, and it does not measure laboratory running economy. A useful label keeps both the calculation and that limitation visible.
A 10K example with a reciprocal check
Using an illustrative 10,000-meter run completed in 50 minutes at an average 150 bpm, the denominator is 150 × 50 = 7,500. Dividing 10,000 by 7,500 gives approximately 1.333 meters per beat.
| Measure | Calculation | Value |
|---|---|---|
| Aerobic efficiency | 10,000 ÷ (150 × 50) | 1.333 m/beat |
| Heart-rate cost | 150 ÷ (10,000 ÷ 3,000) | 45.0 bpm/(m/s) |
| Reciprocal check | 60 ÷ 45.0 | 1.333 m/beat |
The factor of 60 matters because one formula uses minutes and the other uses seconds. Multiplying the unrounded values yields 60. If your two answers do not agree, inspect the unit conversions and time basis before interpreting either value.
The name is not a universal scale
Another app can use a differently scaled ratio with a similar label. For example, RUNALYZE documents a pace-based efficiency formula with a scaling factor of 47. Its displayed value therefore should not be compared numerically with an unconverted meters-per-beat result.
This is a units issue, not evidence that one app observed a different heart rate. First identify the formula, speed unit, time unit and averaging method. Only then decide whether a conversion is meaningful.
Compare conditions as well as numbers
A higher value can result from higher speed, lower recorded heart rate or both. Inspect which input changed. Keep the route, workout purpose and sensor coverage comparable; do not infer a training adaptation from one favorable ratio.
Use Runome's activity comparison to examine the underlying runs, and read the heart-rate cost example for the inverse view. If the run includes substantial changes in pace, start with selecting a steady segment rather than assuming the whole-run ratio describes every portion.