ATL (Fatigue) Calculator
The formula
What the atl (fatigue) tells you
The honest door-to-door arithmetic for atl (fatigue): 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.
How ATL (Fatigue) works — and what your result really means
Health numbers only mean something against a reference — this page gives you both the number and the band it sits in. Searchers land on an ATL (Fatigue) 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.
Most confusion about ATL (Fatigue) comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
The number itself is the easy part. What takes judgement is knowing which inputs are facts in your situation and which are guesses wearing a decimal point — a distinction this page makes explicit for every field above.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here travel time = 586 min, recomputed every time a field changes, 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.
How ATL (Fatigue) is computed, line by line
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 800) is a plain measured quantity — the unit shown in the label is the unit the formula expects. 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 plain measured quantity — the unit shown in the label is the unit the formula expects. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Stops & buffer (minutes) (example value 21) is a measured number in the unit named by the label; the formula does not convert for you. 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 ATL (Fatigue) example
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Distance (km), Average speed (km/h), Stops & buffer (minutes). The endpoint of that chain is 586 min of travel time, sitting in the “Long haul — split it or rotate drivers” band.
- Hours = 800 ÷ 85 = 9.41
- Total = 565 + 21 min buffer = 586 min
Pure driving — 565 min. This is the number experienced users quote when the headline alone would mislead.
Buffer share — 3.6%. This is the number experienced users quote when the headline alone would mislead.
At 20 % slower pace — 727 min. Compare it against the main result of 586 min before drawing conclusions.
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.
How far ATL (Fatigue) can reasonably move
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 | 727 min |
| 90 % of the example value | 648 min |
| example inputs | 586 min |
| 110 % of the example value | 534 min |
| 120 % of the example value | 492 min |
The corridor runs from 492 min to 727 min across that band — which is the range worth planning inside rather than the single 586 min point estimate. Reproduce it in the form above by editing Average speed alone; the substitution steps will follow your figures exactly.
What actually moves your ATL (Fatigue)
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 travel time. For ATL (Fatigue) the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Average speed: ten percent up gives 534 min, ten percent down gives 648 min — ≈10.7 % of the travel time either way
- Nudge Distance by ±10 % and ATL (Fatigue) lands between 529 min and 642 min (sensitivity ≈9.6 %)
- Stops & buffer +10 % → ATL (Fatigue) = 588 min · −10 % → 584 min (the travel time shifts ≈0.4 %)
Average speed is the dominant lever here: ten percent either way moves the result by about 10.7 %, from 534 min to 648 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.6 % 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 an ATL (Fatigue) of 586 min means in practice
A number on its own is trivia; a number against a range is intelligence. The default case lands in the “Long haul — split it or rotate drivers” band, and bands are deliberately wide because real situations overlap. The sensitivity list shows how far a modest input error moves you along that ladder: for Average speed, ±10 % covers 534 min to 648 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.
In Fitness & Sports, ATL (Fatigue) is one instrument in an orchestra: on its own it is a number, next to Pure driving and Buffer share it becomes a diagnosis. The tools linked above exist so the headline never has to carry that weight alone.
Why ATL (Fatigue) results go wrong — and how to prevent it
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 ATL (Fatigue) begins the moment your own figures replace them.
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.
A final trap is presentation: reporting ATL (Fatigue) to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Six things to confirm before acting on ATL (Fatigue)
- Compare the result with one independent method or published benchmark.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Put Average speed under a magnifier; the sensitivity table above is the reason why.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Confirm the example values are plausible for your own situation before replacing them.
- Confirm the answer against one independent method or published benchmark for ATL (Fatigue).
How to use the ATL (Fatigue) 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 ATL (Fatigue) takes a minute to learn and applies to every input above.
Step 1 — start from evidence. The inputs behind ATL (Fatigue) 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. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Step 2 — start from the case you can defend. Enter pessimistic-but-honest figures first; the optimistic run is a ceiling, not a plan. A conclusion that holds on conservative inputs holds everywhere. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
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. Write the figure down before moving on; memory flatters whichever number you saw last.
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. The inputs are the part of the work that nobody else can do for you.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 586 min, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. A figure nobody can reproduce is a figure nobody will act on twice.
Who actually uses ATL (Fatigue) — and when
In Cycling 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 point of transparency is that a reader can disagree with a specific line rather than with you.
Professionals in Cycling use this style of calculation as a screening filter before spending real money or effort: a quick ATL (Fatigue) check eliminates weak options in minutes, and the survivors earn the deeper, slower analysis. The point of transparency is that a reader can disagree with a specific line rather than with you.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Fitness & Sports the expensive mistakes are rarely sudden; they are small changes in Distance (km) that nobody recalculated for a year. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
ATL (Fatigue) — frequently asked questions
What affects ATL (Fatigue) 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 % (534 min to 648 min).
Which matters more: distance or average speed?
For ATL (Fatigue), 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 ATL (Fatigue)?
With the example inputs on this page the result is 586 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 ATL (Fatigue) by hand?
time = distance ÷ speed; total = time + buffer is the entire method. Work the inputs in that order — Hours = 800 ÷ 85 = 9.41 — and you will reach 586 min on the default figures, the same number this tool prints.
What happens to ATL (Fatigue) 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 534 min to 648 min, a swing of roughly 10.7 % around the 586 min baseline. That ratio is the practical definition of how much this input matters.
Is the ATL (Fatigue) result of 586 min good or bad?
The tool answers “what”, not “whether”: 586 min carries the verdict “Long haul — split it or rotate drivers” 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.
Can ATL (Fatigue) be negative or empty?
Yes, and that is informative rather than broken: a negative ATL (Fatigue) usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
How do I calculate ATL (Fatigue) manually?
Write down the inputs, then follow the printed steps in order — time = distance ÷ speed; total = time + buffer. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
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 ATL (Fatigue) 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.
What the labels on this page mean
- Pure driving
- 565 min in the default ATL (Fatigue) calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Buffer share
- 3.6% for the ATL (Fatigue) worked case; it sits next to the main result because it carries context the headline leaves out.
- At 20 % slower pace
- 727 min on the example inputs — a companion figure printed beside the headline of ATL (Fatigue) so that no result is read in isolation.
- Travel time
- The primary output of this tool: 586 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 586 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 ATL (Fatigue) moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
The provenance of this ATL (Fatigue) calculation
Everything above runs on one stated formula, applied without hidden coefficients: time = distance ÷ speed; total = time + buffer. Source of record: Uniform-motion arithmetic. 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.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. 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.
What to do with your ATL (Fatigue) next
Re-measure on a second occasion before changing behaviour; single readings carry natural day-to-day variation.
The audience here is people checking a personal health figure before acting on it. 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.