Sighting Frequency Calculator
The formula
What the sight cost tells you
The navigation arithmetic: how often you lift your eyes, what each lift costs in rhythm and drag, and the percentage of the race it takes.
Calculation: Loss = sightings × cost; sighting count = distance/stroke length ÷ strokes-per-sight. Enter your inputs and every substitution is shown below the result.
Reading the result
In clear water sighting is insurance; the plan is to buy as much of it as the conditions demand and no more.
Rules of thumb: 8–15 strokes between sights; 0.2–0.5 s each
Limitations and best practice
The cost is not just seconds — each sighting collapses two kicks of rhythm; the real tax is the broken roll.
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
Should you sight in the pack?
How high should you sight?
Source & methodology
OWS coaching norms.
How Sighting Frequency works — and what your result really means
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Sighting Frequency 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 Sighting tax in real time, and see every substitution printed below.
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.
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.
Nothing below is stock text pasted around a number: the worked example computes sighting tax = 128.2 s from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Strokes per sighting first, at ≈11.1 % 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 Sighting Frequency formula, explained
One formula, published in full: Loss = sightings × cost; sighting count = distance/stroke length ÷ strokes-per-sight. 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.
Strokes per sighting (example value 9) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Stroke rate (/min) (example value 45) is a quantity rather than a category — precision here is cheap and worth having. Check the convention first: if the source says “6.5 % per year”, type 6.5 and let the formula do the rest.
Seconds lost per sight (example value 0) 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.
Race distance (m) (example value 5,275) 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.
The default Sighting Frequency calculation, written out in full
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Strokes per sighting, Stroke rate (/min), Seconds lost per sight, Race distance (m). Run to the end, the sighting tax resolves to 128.2 s — At 9-stroke spacing you sight 366 times over 5,275 m — 128 s of tax (2.8% of a 75:24 swim). Sighting every 6 strokes doubles it on the bands this tool uses.
- Strokes = 5,275 ÷ 1.6 m DPS = 3,297
- ÷ 9 per sight = 366.3 sightings
- × 0.35 s = 128.2 s tax
Sightings made — 366.3. Compare it against the main result of 128.2 s before drawing conclusions.
Baseline swim time — 73:16. This is the number experienced users quote when the headline alone would mislead.
% cost — 2.83. This is the number experienced users quote when the headline alone would mislead.
Technique fix — crocodile eyes: sight at the recovery, not a lift. 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.
How far Sighting Frequency can reasonably move
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of Sighting Frequency, not an interpolation.
| Strokes per sighting setting | Sighting tax |
|---|---|
| 80 % of the example value | 160.3 s |
| 90 % of the example value | 142.5 s |
| example inputs | 128.2 s |
| 110 % of the example value | 116.6 s |
| 120 % of the example value | 106.8 s |
That spread — 106.8 s at the low end, 160.3 s at the high — is what a careful read of Sighting Frequency looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Strokes per sighting alone; the substitution steps will follow your figures exactly.
Where Sighting Frequency is fragile — and where it is not
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 sighting tax. It is the fastest honest answer to “what matters most in Sighting Frequency?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Strokes per sighting +10 % → Sighting Frequency = 116.6 s · −10 % → 142.5 s (the sighting tax shifts ≈11.1 %)
- Seconds lost per sight +10 % → Sighting Frequency = 141.0 s · −10 % → 115.4 s (the sighting tax shifts ≈10.0 %)
- Nudge Race distance by ±10 % and Sighting Frequency lands between 115.4 s and 141.0 s (sensitivity ≈10.0 %)
Strokes per sighting is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 116.6 s to 142.5 s. That is where a careless figure does the most damage, so check it against a source, and treat Seconds lost per sight as the second priority (≈10.0 % 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 Sighting Frequency verdict
A number on its own is trivia; a number against a range is intelligence. The default case lands in the “At 9-stroke spacing you sight 366 times over 5,275 m — 128 s of tax (2.8% of a 75:24 swim). Sighting every 6 strokes doubles it” 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 Strokes per sighting, ±10 % covers 116.6 s to 142.5 s. 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.
The comparison worth making is not with somebody else’s Sighting Frequency but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
Why Sighting Frequency results go wrong — and how to prevent it
The cost is not just seconds — each sighting collapses two kicks of rhythm; the real tax is the broken roll. 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.
Reporting the headline and quietly discarding Sightings made. The companions are where the shape of the trade-off survives the rounding.
This model has its own particular trap: Strokes per sighting carries ≈11.1 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
The subtlest error is answering the wrong question precisely. Confirm that sighting tax is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Six things to confirm before acting on Sighting Frequency
- Confirm the example values are plausible for your own situation before replacing them.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Re-verify Strokes per sighting against a source document — ten percent of error there moves the headline by ≈11.1 %.
- Note the date and the inputs beside the number so the figure can be audited later.
- Verify each input against its original source document, not memory.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
A routine for decision-grade Sighting Frequency
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 Sighting Frequency takes a minute to learn and applies to every input above.
Step 1 — gather before you type. Sighting Frequency depends on strokes per sighting, stroke rate (/min), seconds lost per sight, race distance (m). Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. Compare the calculation to the rough guess you arrived with, and ask why they differ.
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. If a result feels obviously right, that is the moment to check the inputs hardest.
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. If a result feels obviously right, that is the moment to check the inputs hardest.
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. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 128.2 s, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. A result worth acting on survives having its two shakiest inputs halved.
Where Sighting Frequency matters in practice
Most Swimming disagreements are arithmetic disagreements in disguise. When Sighting tax of 128.2 s 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. Compare the calculation to the rough guess you arrived with, and ask why they differ.
The audience for this page is people who need one trustworthy number before their next decision. In professional Swimming practice the pattern is always the same — screen with Sighting Frequency, then invest slow analysis only in whatever survives the screen. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
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 Strokes per sighting that nobody recalculated for a year. Write the figure down before moving on; memory flatters whichever number you saw last.
Quick answers: what searchers ask about Sighting Frequency
What affects Sighting Frequency the most?
The short answer: Strokes per sighting. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the sighting tax recalculated — Strokes per sighting moved it furthest, by roughly 11.1 % (116.6 s to 142.5 s).
Which matters more: seconds lost per sight or strokes per sighting?
Strokes per sighting, by a factor of about 1.1. Concretely: ten percent on Strokes per sighting is worth ≈11.1 % of Sighting Frequency, the same nudge on Seconds lost per sight only ≈10.0 %. That ranking is re-computed for each page from that page’s own defaults.
What is a typical Sighting Frequency?
With the example inputs on this page the result is 128.2 s, labelled “At 9-stroke spacing you sight 366 times over 5,275 m — 128 s of tax (2.8% of a 75:24 swim). Sighting every 6 strokes doubles it”. “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 Sighting Frequency by hand?
Loss = sightings × cost; sighting count = distance/stroke length ÷ strokes-per-sight is the entire method. Work the inputs in that order — Strokes = 5,275 ÷ 1.6 m DPS = 3,297 — and you will reach 128.2 s on the default figures, the same number this tool prints.
What happens to Sighting Frequency if strokes per sighting changes by 10 %?
On these inputs a ±10 % change in strokes per sighting takes Sighting Frequency to 116.6 s against the 128.2 s example — around 11.1 % of the headline. The same test on every other field is in the sensitivity section.
Is the Sighting Frequency result of 128.2 s good or bad?
The tool answers “what”, not “whether”: 128.2 s carries the verdict “At 9-stroke spacing you sight 366 times over 5,275 m — 128 s of tax (2.8% of a 75:24 swim). Sighting every 6 strokes doubles it” 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.
How often should I check Sighting Frequency?
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. Sighting Frequency is a snapshot, not a subscription; stale snapshots are the most common silent error in Fitness & Sports planning.
How often do I recheck Sighting Frequency?
Whenever Strokes per sighting changes materially, or on a deliberate block cycle (4–8 weeks is standard practice). A stale Sighting Frequency under-programs strong athletes and over-programs tired ones.
Should you sight in the pack?
Sparingly: follow feet, sight only when the feet leave.
How high should you sight?
Eyes just clear the surface looking through the arms; a full head-lift costs body line.
Does this Sighting Frequency 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.
Glossary for Sighting Frequency
- Sightings made
- 366.3 for the Sighting Frequency worked case; it sits next to the main result because it carries context the headline leaves out.
- Baseline swim time
- 73:16 on the example inputs — a companion figure printed beside the headline of Sighting Frequency so that no result is read in isolation.
- % cost
- 2.83 for the Sighting Frequency worked case; it sits next to the main result because it carries context the headline leaves out.
- Sighting tax
- The primary output of this tool: 128.2 s for the default inputs, computed exactly from Loss = sightings × cost; sighting count = distance/stroke length ÷ strokes-per-sight.
- Worked example
- Every substitution in order, from the example inputs to 128.2 s — the audit trail for the headline figure.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “At 9-stroke spacing you sight 366 times over 5,275 m — 128 s of tax (2.8% of a 75:24 swim). Sighting every 6 strokes doubles it”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Sighting Frequency 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: Loss = sightings × cost; sighting count = distance/stroke length ÷ strokes-per-sight. Source of record: OWS coaching norms. 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.
After the number: what to do with it
Save the number together with its inputs and today’s date; a Sighting Frequency figure without context is unusable the moment an input changes.
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.