Gear Ratio Calculator
The formula
What the gear ratio tells you
The honest door-to-door arithmetic for gear ratio: 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.
Gear Ratio 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. Searchers land on a Gear Ratio 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.
What makes Gear Ratio worth calculating is not precision but position: it tells you which side of a threshold you are on, and by how much. A rough figure that settles the direction beats an elaborate one that never commits.
There is a habit that separates people who get useful answers from Cycling numbers: they decide what question the figure answers before they compute it. Gear Ratio answers “Travel time?” — and nothing else, which is precisely why the result is trustworthy.
Nothing below is stock text pasted around a number: the worked example computes travel time = 622 min from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Average speed first, at ≈10.8 % 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.
Every input in Gear Ratio, and what it does to the answer
The engine implements a single stated model: time = distance ÷ speed; total = time + buffer. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Distance (km) (example value 855) is a measured number in the unit named by the label; the formula does not convert for you. Keep every length field in the same unit; the formula assumes a consistency it cannot check for you.
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. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Stops & buffer (minutes) (example value 18) is a quantity rather than a category — precision here is cheap and worth having. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Gear Ratio 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 622 min of travel time, sitting in the “Long haul — split it or rotate drivers” band.
- Hours = 855 ÷ 85 = 10.06
- Total = 604 + 18 min buffer = 622 min
Pure driving — 604 min. Read next to the headline, this is the figure that shows the shape of the trade-off.
Buffer share — 2.9%. Compare it against the main result of 622 min before drawing conclusions.
At 20 % slower pace — 772 min. Read next to the headline, this is the figure that shows the shape of the trade-off.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
The Gear Ratio corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: Gear Ratio was recomputed at 5 points along the dominant input, with every other field left untouched.
| Average speed setting | Travel time |
|---|---|
| 80 % of the example value | 772 min |
| 90 % of the example value | 689 min |
| example inputs | 622 min |
| 110 % of the example value | 567 min |
| 120 % of the example value | 521 min |
That spread — 521 min at the low end, 772 min at the high — is what a careful read of Gear Ratio looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Average speed alone; the substitution steps will follow your figures exactly.
Where Gear Ratio 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. Read it as a map of where Gear Ratio is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Average speed +10 % → Gear Ratio = 567 min · −10 % → 689 min (the travel time shifts ≈10.8 %)
- Distance: ten percent up gives 682 min, ten percent down gives 561 min — ≈9.7 % of the travel time either way
- Nudge Stops & buffer by ±10 % and Gear Ratio lands between 620 min and 623 min (sensitivity ≈0.3 %)
Average speed is the dominant lever here: ten percent either way moves the result by about 10.8 %, from 567 min to 689 min. That is where a careless figure does the most damage, so check it against a source, and treat Distance as the second priority (≈9.7 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
What a Gear Ratio of 622 min means in practice
The value above only becomes useful the moment you know what it is being measured against. The verdict attached to the default calculation — “Long haul — split it or rotate drivers” — is one band on a ladder your own figure may sit somewhere else on. The sensitivity list shows how far a modest input error moves you along that ladder: for Average speed, ±10 % covers 567 min to 689 min. 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.
Where Gear Ratio sits next to similar measures: this tool answers “how much is the Gear Ratio”, while the related calculators answer “what do I do about it”. Reading the result alone tends to over-weight a single snapshot; pairing it with the companion tools above turns the number into a decision.
How people get Gear Ratio 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.
Treating the example inputs as a recommendation. They are a demonstration of the mechanism — a decision-grade Gear Ratio begins the moment your own figures replace them.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Average speed first, everything else second.
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.
Before you trust your Gear Ratio: a short checklist
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Verify each input against its original source document, not memory.
- Check Average speed before anything else: it is the measured dominant input, ≈10.8 % of Gear Ratio per ten percent.
- Note the date and the inputs beside the number so the figure can be audited later.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Confirm the answer against one independent method or published benchmark for Gear Ratio.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — collect, then type. Everything this tool asks for is listed above (distance (km), average speed (km/h), stops & buffer (minutes)). 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. When two sources disagree, it is almost never the arithmetic that differs.
Step 2 — baseline before exploration. Get one defensible Travel time on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. Precision is a promise you make about your data; make sure your inputs can keep it.
Step 4 — compute a corridor, not a point. Three runs — worst, likely, best — turn Gear Ratio from a snapshot into a range. Plan against the pessimistic end and treat the optimistic end as the upside story. One decimal place more than your data supports is one decimal place of fiction.
Step 5 — schedule the next run. In Fitness & Sports the inputs drift quietly. Put a reminder a quarter out, re-enter the same fields, and read the change rather than the level. One decimal place more than your data supports is one decimal place of fiction.
The real-world conversations Gear Ratio settles
Numbers earn their keep in conversations, and Gear Ratio is no exception. In Fitness & Sports discussions around Cycling, 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. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Professionals in Cycling use this style of calculation as a screening filter before spending real money or effort: a quick Gear Ratio check eliminates weak options in minutes, and the survivors earn the deeper, slower analysis. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
Treat Gear Ratio like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. One decimal place more than your data supports is one decimal place of fiction.
Quick answers: what searchers ask about Gear Ratio
What affects Gear Ratio the most?
Gear Ratio is driven above all by Average speed. Perturbing only that field by ten percent either way produced 567 min against the 622 min baseline — a ≈10.8 % response, while Distance manages ≈9.7 %.
Which matters more: distance or average speed?
For Gear Ratio, Average speed wins the head-to-head (≈10.8 % against ≈9.7 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Gear Ratio?
With the example inputs on this page the result is 622 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 Gear Ratio by hand?
time = distance ÷ speed; total = time + buffer is the entire method. Work the inputs in that order — Hours = 855 ÷ 85 = 10.06 — and you will reach 622 min on the default figures, the same number this tool prints.
What happens to Gear Ratio 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 567 min to 689 min, a swing of roughly 10.8 % around the 622 min baseline. That ratio is the practical definition of how much this input matters.
Is the Gear Ratio result of 622 min good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Gear Ratio sit against the 622 min reference above, how far would a plausible input error move it (≈10.8 % per ten percent on Average speed), and what does the alternative option compute to?
Is Gear Ratio 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 622 min, adjust by results within a few sessions.
How often do I recheck Gear Ratio?
Whenever Distance (km) changes materially, or on a deliberate block cycle (4–8 weeks is standard practice). A stale Gear Ratio under-programs strong athletes and over-programs tired ones.
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.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
Key terms on this page
- Pure driving
- 604 min on the example inputs — a companion figure printed beside the headline of Gear Ratio so that no result is read in isolation.
- Buffer share
- 2.9% for the Gear Ratio worked case; it sits next to the main result because it carries context the headline leaves out.
- At 20 % slower pace
- 772 min on the example inputs — a companion figure printed beside the headline of Gear Ratio so that no result is read in isolation.
- Travel time
- The primary output of this tool: 622 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 622 min — the audit trail for the headline figure.
- Verdict band
- The plain-language label — here “Long haul — split it or rotate drivers” — mapping the computed figure onto experience-based ranges for Fitness & Sports.
- Sensitivity (±10 %)
- How far the Gear Ratio 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 Gear Ratio model comes from
The model is published arithmetic implemented exactly as written: time = distance ÷ speed; total = time + buffer. Source of record: Uniform-motion arithmetic. Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
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.
Next steps after the calculation
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.