Swim Tracking
Understanding swim pace, splits and stroke metrics
Learn what swim pace, splits, stroke count and SWOLF can tell you, how to compare like-for-like sessions and why one number cannot describe your technique.
3 min read
A swim record is most useful when it answers a question. Did you hold the intended pace? Did the final repeats slow down? Did the session feel easier under comparable conditions? Understanding a few measurements will help you ask better questions without chasing every number on the screen.
Separate pace from the session clock
Pace expresses time over a standard distance, commonly 100 metres or 100 yards. In an illustrative example, 200 metres completed in four minutes is 2:00 per 100 metres. To calculate it, divide swim time in seconds by distance and multiply by 100. Keep metres and yards separate when comparing records.
Check which time your app is using. Time spent swimming, the duration of an interval and total elapsed session time may include different amounts of rest. A session with longer rests can look different even if the swimming pace is unchanged. Compare the actual repetitions before drawing a conclusion from a session average.
Use splits to see how the effort was distributed
A split is the time for part of a swim, such as each 50 metres within a 200. Consider two illustrative 200-metre swims that both take four minutes. Four 60-second splits show an even distribution; 54, 58, 63 and 65 seconds show a fast start followed by slowing. The average is identical, but the pacing story is different.
For a repeat set, compare repetitions as well as splits within them. Keep the rest interval visible. Holding the same time with twice the recovery is not a like-for-like test. A traffic interruption or an unusually long turn can also explain a single slow split.
Check how your device defines a stroke
Stroke count needs a counting convention. Some swimmers manually count each hand entry; Garmin Swim 2 counts a cycle of the arm wearing the watch. Check your device’s definition before comparing its number with a coach’s count or another device.
Stroke rate adds a time dimension, but its displayed units also matter. Record the units rather than assuming every system uses the same convention. Fewer strokes are not automatically better: a longer glide may reduce the count while slowing the swim. Read count or rate alongside pace and how the movement felt.
Further reference: Garmin Swim 2: swim terminology and counting conventions.
Treat SWOLF as context, not a technique grade
For a pool length, SWOLF combines the time in seconds with the recorded stroke count. For example, 30 seconds plus 18 counted strokes produces 48. Its meaning depends on the length, stroke, counting method and how the swim was performed.
Compare your own similar efforts under the same conditions. A push-off, deliberate glide or change of stroke can alter the score without answering whether your whole stroke has improved. Do not use it as a ranking between swimmers or as a diagnosis of a technical fault.
Further reference: Garmin’s definition of SWOLF.
Choose a small review set
For your next comparable session, record the distance and rest, each repeat time, and a brief note on effort. Add stroke count only if you can measure it consistently. Check an implausible distance or split against what you remember swimming before using it to change a training target.
Look for a pattern across several sessions: steadier splits, similar pace with a more controlled effort, or the same stroke count at a different pace. The purpose is to support a decision about training, not to make every metric improve at once.
Explore the thinking behind DuoSwim Sense.