Threshold Swim Calculator

ByDr. Liam Gallagher, DPT, CSCS ✓ Verified 📚 248 Calculators Authored

Doctor of Physical Therapy & Sports Performance Scientist · Doctor of Physical Therapy (DPT), Certified Strength and Conditioning Specialist (CSCS)

📅 Published: Sep 28, 2026

The formula

Aerobic threshold ≈ CSS + 3 s/100; interval = reps × set + rest

What the threshold clock tells you

The swim-lane version of lactate-threshold training: a pace a few seconds per hundred off CSS, held for 20–40 minutes of net work.

Calculation: Aerobic threshold ≈ CSS + 3 s/100; interval = reps × set + rest. Enter your inputs and every substitution is shown below the result.

Reading the result

If the last rep is comfortably on pace, the set was too slow — threshold work should end at the edge of holding.

Rules of thumb: 3 × 400, 4 × 300, 1500 continuous are the canonical sets

Limitations and best practice

CSS itself drifts; retest every 4–6 weeks or the threshold clock quietly becomes a tempo clock.

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 threshold the same as T-pace?

In Swim-Australia usage T-pace ≈ this clock; naming differs between coaching schools, so define by feel and HR together.

Why +3 s/100?

Empirically, CSS is a ~30-min hold; one extra second buys the 40-min sustainable band most threshold sets target.

Source & methodology

McLean/Pro Swim coach practice; CSS literature.

Threshold Swim: the number, the method and the caveats

This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Searchers land on a Threshold Swim 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.

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 Threshold Swim.

Individual variation is large here: limb proportions, fibre mix and history all shift how a population-average Threshold Swim maps to you. Use it as a starting prescription, then let performance feedback over weeks tune it.

What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here threshold pace /100 = 79.0 s, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — CSS pace /100 first, at ≈9.6 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.

The Threshold Swim formula, explained

The engine implements a single stated model: Aerobic threshold ≈ CSS + 3 s/100; interval = reps × set + rest. 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.

CSS pace /100 (s) (example value 76) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.

Set distance (m) (example value 300) is a quantity rather than a category — precision here is cheap and worth having. Keep every length field in the same unit; the formula assumes a consistency it cannot check for you.

Pool length (m) (example value 45) 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.

Reps (example value 3) 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.

Threshold Swim with real numbers, step by step

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: CSS pace /100 (s), Set distance (m), Pool length (m), Reps. The endpoint of that chain is 79.0 s of threshold pace /100, sitting in the “Threshold clock = CSS + 3 = 79.0 s/100; 3 × 300 swims in 3:57 with ~33 s rest per 45 m — 13:30 total, landing exactly in the 20–36 min work window” band.

Threshold = CSS + 3 s = 79.0 /100
300 m = 3:57 plus 33 s rest
3 reps → 13:30 elapsed

Per 100 m — 79.0 s. If your inputs change, this is usually the first companion figure to move.

Send-off interval — 270.0 s. This is the number experienced users quote when the headline alone would mislead.

Work time — 711.0 s. Compare it against the main result of 79.0 s before drawing conclusions.

Breath cue — able to speak a sentence, not a paragraph. This is the number experienced users quote when the headline alone would mislead.

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 Threshold Swim corridor: your result across a realistic band

The honest version of any estimate is a corridor, and this one is cheap to produce: Threshold Swim was recomputed at 5 points along the dominant input, with every other field left untouched.

CSS pace /100 setting	Threshold pace /100
80 % of the example value	63.8 s
90 % of the example value	71.4 s
example inputs	79.0 s
110 % of the example value	86.6 s
120 % of the example value	94.2 s

Across 5 settings of CSS pace /100, the result spans 63.8 s to 94.2 s. 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 CSS pace /100 alone; the substitution steps will follow your figures exactly.

Where Threshold Swim 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 threshold pace /100 recomputed, so the ranking below is measured rather than asserted. For Threshold Swim the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.

CSS pace /100 +10 % → Threshold Swim = 86.6 s · −10 % → 71.4 s (the threshold pace /100 shifts ≈9.6 %)

CSS pace /100 is the dominant lever here: ten percent either way moves the result by about 9.6 %, from 71.4 s to 86.6 s. Measure that input from a document rather than from memory. 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.

Interpreting the Threshold Swim verdict

A number on its own is trivia; a number against a range is intelligence. The default case lands in the “Threshold clock = CSS + 3 = 79.0 s/100; 3 × 300 swims in 3:57 with ~33 s rest per 45 m — 13:30 total, landing exactly in the 20–36 min work window” 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 CSS pace /100, ±10 % covers 71.4 s to 86.6 s. 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.

Set Threshold Swim 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.

Why Threshold Swim results go wrong — and how to prevent it

CSS itself drifts; retest every 4–6 weeks or the threshold clock quietly becomes a tempo clock. 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.

Reading Threshold Swim as a promise rather than a conditional. Every number here is of the form “if these inputs, then this result”; when an input moves, the honest response is to recompute rather than to defend the old figure.

Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: CSS pace /100 first, everything else second.

A final trap is presentation: reporting Threshold Swim 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 Threshold Swim

Record the date and the inputs alongside the number so future-you knows what was assumed.
Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
Re-verify CSS pace /100 against a source document — ten percent of error there moves the headline by ≈9.6 %.
Verify each input against its original source document, not memory.
State, in one sentence, which convention each rate, unit or period in the form is using.
Confirm the answer against one independent method or published benchmark for Threshold Swim.

A routine for decision-grade Threshold Swim

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 Threshold Swim takes a minute to learn and applies to every input above.

Step 1 — collect, then type. Everything this tool asks for is listed above (css pace /100 (s), set distance (m), pool length (m), reps). 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. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.

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 Threshold pace /100 (79.0 s for the example values), and note the verdict band. Rounding early is the quietest way to introduce a permanent error.

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. If the answer changes your behaviour, it deserves a second run with different assumptions.

Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. Rounding early is the quietest way to introduce a permanent error.

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. Most surprises in numbers are surprises about inputs, not about formulas.

Where Threshold Swim matters in practice

In Swimming 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. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.

Used properly this is a five-minute filter that saves weeks. Compute Threshold Swim, 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.

Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. Suspiciously tidy answers deserve the same scrutiny as untidy ones.

What the labels on this page mean

Per 100 m: 79.0 s on the example inputs — a companion figure printed beside the headline of Threshold Swim so that no result is read in isolation.
Send-off interval: 270.0 s in the default Threshold Swim calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
Work time: 711.0 s in the default Threshold Swim calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
Threshold pace /100: The primary output of this tool: 79.0 s for the default inputs, computed exactly from Aerobic threshold ≈ CSS + 3 s/100; interval = reps × set + rest.
Worked example: The step-by-step substitution printed above, so the arithmetic can be re-derived by hand or in a spreadsheet.
Verdict band: A named zone on the range of plausible results; the example inputs land in “Threshold clock = CSS + 3 = 79.0 s/100; 3 × 300 swims in 3:57 with ~33 s rest per 45 m — 13:30 total, landing exactly in the 20–36 min work window”, and your inputs may not.
Sensitivity (±10 %): How far the Threshold Swim 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: Aerobic threshold ≈ CSS + 3 s/100; interval = reps × set + rest. Source of record: McLean/Pro Swim coach practice; CSS literature. 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. Nothing is smoothed, weighted or adjusted behind the scenes; where judgement enters, this page says so and names the input responsible.

Turning this Threshold Swim 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.

Whoever you are (people who need one trustworthy number before their next decision), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Fitness & Sports, a dated figure is a trend, and an undated one is a rumour.