Swimming Pace Calculator
The formula
What the swim pace tells you
Pace normalised per 100 m for any pool length — the swimmer’s version of min/km.
Calculation: CSS-style pace per 100 m with drag-cubed power implication. Enter your inputs and every substitution is shown below the result.
Reading the result
Water punishes drag cubically, so the fastest way to a new pace is usually better body position, not more power.
Rules of thumb: Beginner 2:00–2:30/100; club 1:15–1:35; sub-1:00 competitive
Limitations and best practice
Comparing a tapered 25 m yard pace to a 50 m metres pace ignores turns; use the same pool for trend lines.
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
Pace or stroke count to get faster?
Why do my 200s feel harder than 100s?
Source & methodology
CSS (Maglischo); swim drag model.
Swimming Pace: the number, the method and the caveats
You are here because you need a specific number, and you want to see how it was produced before you rely on it. Swimming 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 Pace /100 m 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 Swimming Pace.
It helps to separate the mechanics from the interpretation. The mechanics are fixed: CSS-style pace per 100 m with drag-cubed power implication. Anyone, anywhere, entering the same inputs will get the same 1:47. The interpretation is where experience counts: whether 1:47 is good, normal or alarming depends on comparisons covered below, and that is the part most articles about Swimming Pace never explain.
Nothing below is stock text pasted around a number: the worked example computes pace /100 m = 1:47 from this tool’s own defaults — which is the thread the rest of this guide pulls on.
How Swimming Pace is computed, line by line
One formula, published in full: CSS-style pace per 100 m with drag-cubed power implication. 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 (m) (example value 1,675) is a measured number in the unit named by the label; the formula does not convert for you. 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.
Total time (min) (example value 30) is a measured number in the unit named by the label; the formula does not convert for you. Use the value as of today, not as of the last time you looked — time fields drift silently.
Pool length (m) (example value 19) 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.
Drag factor (tapered) (example value 2) is a quantity rather than a category — precision here is cheap and worth having. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Swimming Pace with real numbers, step by step
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Distance (m), Total time (min), Pool length (m), Drag factor (tapered). Run to the end, the pace /100 m resolves to 1:47 — 107 s per 100 m (1:47) — at drag-cubed physics, holding 2% faster costs ~6% more power on the bands this tool uses.
- Total 30.0 min ÷ (1,675/100) = 107.5 s/100 m
- Per 50 m split: 0:54
- Drag power ∝ v³ — small pace cuts cost disproportionate watts
Laps to swim — 88.2. Compare it against the main result of 1:47 before drawing conclusions.
Splits pace per 50 — 0:54. Read next to the headline, this is the figure that shows the shape of the trade-off.
Speed — 0.93 m/s. Compare it against the main result of 1:47 before drawing conclusions.
Mins at this pace for 800 — 14.3. If your inputs change, this is usually the first companion figure to move.
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.
Interpreting the Swimming Pace verdict
Nobody acts on a bare figure — they act on a figure with a comparison attached. The verdict attached to the default calculation — “107 s per 100 m (1:47) — at drag-cubed physics, holding 2% faster costs ~6% more power” — is one band on a ladder your own figure may sit somewhere else on. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Placing this figure in context: calculators of this kind differ less in arithmetic than in what they choose to ignore. This one keeps Distance (m) explicit so that the omissions are visible rather than hidden in a preset.
Common mistakes with Swimming Pace (and the fix)
Comparing a tapered 25 m yard pace to a 50 m metres pace ignores turns; use the same pool for trend lines. 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.
Chasing precision in Total time (min) while Distance (m) is still a guess. The sensitivity ranking above shows exactly where the accuracy budget should go.
A final trap is presentation: reporting Swimming Pace 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 Swimming Pace
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Verify each input against its original source document, not memory.
- Confirm the inputs are dated — a Swimming Pace figure should carry the date it was computed.
- 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.
- Confirm the answer against one independent method or published benchmark for Swimming Pace.
A routine for decision-grade Swimming Pace
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 (m), total time (min), pool length (m), drag factor (tapered)). 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. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 2 — baseline before exploration. Get one defensible Pace /100 m on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Half of a good calculation is knowing which input you would hate to be wrong about.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Step 5 — schedule the next run. In Health & Medical 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.
The real-world conversations Swimming Pace settles
Most Fitness Performance disagreements are arithmetic disagreements in disguise. When Pace /100 m of 1:47 sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. Estimates improve most when the worst case is written down in ink.
The audience for this page is people who need one trustworthy number before their next decision. In professional Fitness Performance practice the pattern is always the same — screen with Swimming Pace, then invest slow analysis only in whatever survives the screen. A figure nobody can reproduce is a figure nobody will act on twice.
There is a personal-administration use people overlook: periodic self-checking. Swimming Pace quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. Most surprises in numbers are surprises about inputs, not about formulas.
People also ask about Swimming Pace
What is a typical Swimming Pace?
There is no honest universal average for Swimming Pace, but there is a reference point: the defaults on this page produce 1:47 (107 s per 100 m (1:47) — at drag-cubed physics, holding 2% faster costs ~6% more power). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Swimming Pace by hand?
Use the stated model — CSS-style pace per 100 m with drag-cubed power implication — and substitute in the order the tool prints (it starts from Total 30.0 min ÷ (1,675/100) = 107.5 s/100 m). On the example inputs the hand route lands on 1:47, exactly what the calculator shows. A spreadsheet reproduces it in two or three cells; doing it once by hand is what makes the automated answer trustworthy.
Is the Swimming Pace result of 1:47 good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Swimming Pace sit against the 1:47 reference above, how far would a plausible input error move it, and what does the alternative option compute to?
Can Swimming Pace be negative or empty?
Yes, and that is informative rather than broken: a negative Swimming Pace usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
How accurate is Swimming Pace for me personally?
The formula encodes averages; body-composition and measurement error typically shifts results by a few percent in either direction. Use ranges and trends, and treat any single 1:47 as approximate.
Pace or stroke count to get faster?
Stroke count first — long strokes at the same rate are free speed.
Why do my 200s feel harder than 100s?
Because you start the second length from a glide; swim-specific pacing drills fix the pattern.
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.
The vocabulary of Swimming Pace
- Laps to swim
- 88.2 on the example inputs — a companion figure printed beside the headline of Swimming Pace so that no result is read in isolation.
- Splits pace per 50
- 0:54 on the example inputs — a companion figure printed beside the headline of Swimming Pace so that no result is read in isolation.
- Speed
- 0.93 m/s on the example inputs — a companion figure printed beside the headline of Swimming Pace so that no result is read in isolation.
- Pace /100 m
- The primary output of this tool: 1:47 for the default inputs, computed exactly from CSS-style pace per 100 m with drag-cubed power implication.
- Worked example
- Every substitution in order, from the example inputs to 1:47 — the audit trail for the headline figure.
- Verdict band
- The plain-language label — here “107 s per 100 m (1:47) — at drag-cubed physics, holding 2% faster costs ~6% more power” — mapping the computed figure onto experience-based ranges for Health & Medical.
The provenance of this Swimming Pace calculation
The model is published arithmetic implemented exactly as written: CSS-style pace per 100 m with drag-cubed power implication. Source of record: CSS (Maglischo); swim drag model. 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.
Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. The promise to the reader is narrow and testable: same inputs, same output, no silent rounding, and no figure presented without the formula that produced it.
Turning this Swimming Pace into a decision
Save the number together with its inputs and today’s date; a Swimming 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.