Interval Pace Calculator
The formula
What the interval pace tells you
The honest door-to-door arithmetic for interval pace: moving time plus the stops that every timetable quietly forgets.
Calculation: time = distance ÷ speed; total = time + buffer. Enter your inputs and every substitution is shown below the result.
Reading the result
Compare the pure-driving and buffered lines; the gap is your real scheduling slack.
Limitations and best practice
Average speed ≠ posted speed — urban reality is 60–70 % of the limit; set the speed input to lived experience.
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
Why add buffer at all?
Does it handle multiple legs?
Source & methodology
Uniform-motion arithmetic.
Interval Pace explained: formula, worked example and honest limits
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Interval Pace is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Travel time in real time, and see every substitution printed below.
People rarely disagree about arithmetic; they disagree about assumptions that were never written down. Printing the substitution and the sensitivity ranking removes that category of disagreement for Interval Pace.
In Fitness & Sports the same quantity is often quoted under two or three different conventions. The formula printed above fixes one convention and applies it consistently, which is what makes results from this page comparable with each other.
Nothing below is stock text pasted around a number: the worked example computes travel time = 563 min from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Average speed first, at ≈10.7 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Inside the Interval Pace calculation: formula and every input
One formula, published in full: time = distance ÷ speed; total = time + buffer. 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.
Distance (km) (example value 765) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Small measurement errors grow here: a length that is squared or cubed in the model magnifies a one-percent slip into a three-percent answer.
Average speed (km/h) (example value 85) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Stops & buffer (minutes) (example value 23) is a measured number in the unit named by the label; the formula does not convert for you. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Interval Pace with real numbers, step by step
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Distance (km), Average speed (km/h), Stops & buffer (minutes). The endpoint of that chain is 563 min of travel time, sitting in the “Long haul — split it or rotate drivers” band.
- Hours = 765 ÷ 85 = 9.00
- Total = 540 + 23 min buffer = 563 min
Pure driving — 540 min. This is the number experienced users quote when the headline alone would mislead.
Buffer share — 4.1%. If your inputs change, this is usually the first companion figure to move.
At 20 % slower pace — 698 min. If your inputs change, this is usually the first companion figure to move.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
Scenario table: Interval Pace at ±10 % and ±20 % of the key input
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Average speed setting | Travel time |
|---|---|
| 80 % of the example value | 698 min |
| 90 % of the example value | 623 min |
| example inputs | 563 min |
| 110 % of the example value | 514 min |
| 120 % of the example value | 473 min |
The corridor runs from 473 min to 698 min across that band — which is the range worth planning inside rather than the single 563 min point estimate. Reproduce it in the form above by editing Average speed alone; the substitution steps will follow your figures exactly.
Where Interval Pace is fragile — and where it is not
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the travel time recomputed, so the ranking below is measured rather than asserted. It is the fastest honest answer to “what matters most in Interval Pace?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Average speed +10 % → Interval Pace = 514 min · −10 % → 623 min (the travel time shifts ≈10.7 %)
- Nudge Distance by ±10 % and Interval Pace lands between 509 min and 617 min (sensitivity ≈9.6 %)
- Nudge Stops & buffer by ±10 % and Interval Pace lands between 561 min and 565 min (sensitivity ≈0.4 %)
Average speed is the dominant lever here: ten percent either way moves the result by about 10.7 %, from 514 min to 623 min. Measure that input from a document rather than from memory, and treat Distance as the second priority (≈9.6 % per ten percent). Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
Interpreting the Interval Pace verdict
Nobody acts on a bare figure — they act on a figure with a comparison attached. On the example inputs the band reads “Long haul — split it or rotate drivers”; 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 Average speed, ±10 % covers 514 min to 623 min. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Related measures answer related questions, and the distinctions matter: Interval Pace is the quantity, Travel time is this tool’s reading of it, and the decision that follows belongs to neither of them separately.
How people get Interval Pace wrong
Average speed ≠ posted speed — urban reality is 60–70 % of the limit; set the speed input to lived experience. 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.
Using stale inputs. Interval Pace is only as current as the numbers behind it — an estimate carried over from a previous season, rate table or report quietly biases every output. Re-measure the inputs first; that single habit fixes more bad Interval Pace figures than any formula change.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Average speed dominating — a careful figure there beats false precision everywhere else.
The subtlest error is answering the wrong question precisely. Confirm that travel time 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 Interval Pace figure
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Check Average speed before anything else: it is the measured dominant input, ≈10.7 % of Interval Pace per ten percent.
- Confirm the example values are plausible for your own situation before replacing them.
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
How to use the Interval Pace tool properly
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 Interval Pace takes a minute to learn and applies to every input above.
Step 1 — start from evidence. The inputs behind Interval Pace are distance (km), average speed (km/h), stops & buffer (minutes). Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. Rounding early is the quietest way to introduce a permanent error.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the Travel time (563 min for the example values), and note the verdict band. The test of a good estimate is not that it feels right but that it changes what you do.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. The input you reach for first is usually the one you measured longest ago.
Step 4 — compute a corridor, not a point. Three runs — worst, likely, best — turn Interval Pace from a snapshot into a range. Plan against the pessimistic end and treat the optimistic end as the upside story. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 563 min, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. Re-running a number costs seconds; retracting a decision costs considerably more.
From calculation to decision: where Interval Pace earns its keep
In Running the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. The inputs are the part of the work that nobody else can do for you.
Used properly this is a five-minute filter that saves weeks. Compute Interval Pace, reject what fails, and only then bring in the expensive analysis for the survivors. If a result feels obviously right, that is the moment to check the inputs hardest.
Treat Interval Pace like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Quick answers: what searchers ask about Interval Pace
What affects Interval Pace the most?
The short answer: Average speed. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the travel time recalculated — Average speed moved it furthest, by roughly 10.7 % (514 min to 623 min).
Which matters more: distance or average speed?
For Interval Pace, Average speed wins the head-to-head (≈10.7 % against ≈9.6 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Interval Pace?
With the example inputs on this page the result is 563 min, labelled “Long haul — split it or rotate drivers”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Interval Pace by hand?
time = distance ÷ speed; total = time + buffer is the entire method. Work the inputs in that order — Hours = 765 ÷ 85 = 9.00 — and you will reach 563 min on the default figures, the same number this tool prints.
What happens to Interval Pace if average speed changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the travel time goes across 514 min to 623 min, a swing of roughly 10.7 % around the 563 min baseline. That ratio is the practical definition of how much this input matters.
Is the Interval Pace result of 563 min good or bad?
Neither, on its own — the label “Long haul — split it or rotate drivers” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Average speed alone moves it by ≈10.7 %.
Is Interval Pace individualized?
Partly — the tool is mechanical on the inputs you provide (Distance (km), Average speed (km/h)); what varies person-to-person is the response. Start at the computed 563 min, adjust by results within a few sessions.
How often should I check Interval Pace?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. Interval Pace is a snapshot, not a subscription; stale snapshots are the most common silent error in Fitness & Sports planning.
Why add buffer at all?
Fuel, rest and traffic are non-zero; a plan without them is late by construction.
Does it handle multiple legs?
Run each leg and sum; one blended average speed overstates optimism.
Does this Interval Pace 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 Fitness & Sports figures and the reason you can re-run this page as often as you like.
The vocabulary of Interval Pace
- Pure driving
- 540 min in the default Interval Pace calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Buffer share
- 4.1% for the Interval Pace worked case; it sits next to the main result because it carries context the headline leaves out.
- At 20 % slower pace
- 698 min on the example inputs — a companion figure printed beside the headline of Interval Pace so that no result is read in isolation.
- Travel time
- The primary output of this tool: 563 min for the default inputs, computed exactly from time = distance ÷ speed; total = time + buffer.
- Worked example
- Every substitution in order, from the example inputs to 563 min — the audit trail for the headline figure.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “Long haul — split it or rotate drivers”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Interval Pace moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Interval Pace model comes from
There is no black box on this page — the engine evaluates time = distance ÷ speed; total = time + buffer. Source of record: Uniform-motion arithmetic. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
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. Nothing is smoothed, weighted or adjusted behind the scenes; where judgement enters, this page says so and names the input responsible.
After the number: what to do with it
Save the number together with its inputs and today’s date; an Interval Pace figure without context is unusable the moment an input changes.
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.