{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Splits{{ resultsReady ? computation.values.analysis.split_count : '—' }} Pace basis{{ paceBasisLabel }} Clock delta{{ resultsReady ? finishDeltaLabel : '—' }}
{{ liveMarkerText }}
Up to 80 characters.
Changing the unit preserves the physical distance.
Use the normal lap, kilometre, mile, or checkpoint interval.
Examples: 24:30, 1:38:12, or 1470.
Example: 1 km - 4:52. Up to 200 non-empty lines.
The neutral default is blank.
Leave both blank when a clock anchor is not needed.
Pace review
{{ row.label }}{{ row.display }}
What the splits say
  • {{ note }}

The chart renderer is unavailable. The same pace values remain in the review and ledger.

SplitMarkerSegmentTimeCumulativePaceVs overallCopy
{{ row.index }}{{ row.marker }}{{ row.segment }}{{ row.split }}{{ row.cumulative }}{{ row.pace }}{{ row.delta }}
Race Pace and Finish Time Suite Build race pace and finish-time plans from a goal, recent result, or training block with stop-aware splits and scenario comparisons.
Pace & Speed Converter Convert running pace and speed between metric and imperial units, with constant-speed times for common distances and optional custom splits.
Race Finish Time Calculator Estimate race finish time from distance and pace or speed, then compare splits, planned stops, pacing profiles, and cutoff margin.
Race Finish Time Predictor Predict a race finish from a recent result using the Riegel formula, then compare condition scenarios with target paces and even splits.

A finish time says how long the whole race took. Splits explain how that time was built, one lap, kilometre, mile, or checkpoint at a time. Two runners can finish together yet arrive there very differently: one may hold an even pace, while the other starts quickly and gives time back late.

Useful split review depends on three quantities that are easy to confuse. A marker is the cumulative distance reached, a segment is the distance since the previous marker, and pace is the time needed to cover a standard distance. Pace is normally shown per kilometre or mile; short track work is often easier to read per 100 metres.

Record Best use Common mistake
Finish time only Overall result and average pace Assuming the pace stayed even
Equal-distance splits Pacing changes across comparable segments Mixing kilometre, mile, and metre markers
Checkpoint splits Reviewing an irregular course or manual timing points Treating cumulative markers as segment lengths

A small difference between splits may be normal on hills, turns, crowded starts, or aid-station sections. The same difference on a flat track can be a more direct pacing signal. Comparison is strongest when the timing method, marker placement, and distance units stay consistent.

Hand-timed splits are an analysis aid, not an official placing record. A late lap press moves time from one segment into the next, and a missed press can make two neighboring segments look misleading even when the finish time is correct.

How to Use This Tool:

Choose live capture when you are timing the race now, or enter a completed finish and split notes for later review.

  1. Enter the Race distance and its unit, then set the usual Default split distance. Changing a distance unit preserves the physical distance.
  2. For live timing, start the clock and press Lap at each marker. Pause only when timing should stop, then press Finish to place the captured elapsed time and laps into the review inputs.
  3. For an existing record, enter the Recorded finish time and add one split per line. A line may contain an increasing distance marker such as 3 km; a line without one advances by the default split distance.
  4. Add Target pace only when you want signed comparisons against a planned pace. The pace basis follows the race unit: per kilometre, per mile, or per 100 metres.
  5. Check Race review first. Resolve an invalid time, a marker that does not increase, or a marker beyond the finish before comparing Split pace and the Split ledger.

Interpreting Results:

The overall pace is finish time divided by race distance. Fastest and slowest split pace identify the ends of the recorded range, while Pace spread shows the difference between them. A small spread suggests even recorded segments, but terrain and marker quality still matter.

  • Vs overall is negative for a faster-than-average segment and positive for a slower one.
  • Split clock total should be compared with the recorded finish. A non-zero finish delta means the listed split durations do not add to the finish time.
  • A striking fast/slow pair is often worth checking against the original stopwatch notes before treating it as a pacing change.

Technical Details:

All distances are converted to kilometres for calculation, and all durations are parsed into seconds. Results are then scaled to the selected display basis. The arithmetic uses full parsed values; duration labels are rounded to the nearest whole second only when displayed.

Formula Core

Overall and segment pace use the same rate equation. The segment distance is the current cumulative marker minus the preceding marker.

poverall = tfinishdrace di = mi−mi−1 pi = tidi Δtfinish = ∑i=1nti−tfinish

Here, t is seconds, d is kilometres, and m is a cumulative distance marker. Seconds per kilometre are multiplied by 1.609344 for seconds per mile and divided by 10 for seconds per 100 metres.

Input Accepted rule Effect
Finish or target duration HH:MM:SS, MM:SS, or plain seconds; minute and second fields after a colon must be below 60 Converted to seconds before pace arithmetic
Split line duration First recognizable clock token or seconds token, greater than 0 and no more than 24 hours Becomes that segment's duration
Explicit marker First distance in km, miles, or metres; strictly greater than the preceding marker and not beyond the race distance Defines the current cumulative marker
No marker Previous marker plus the configured default split distance Builds the next equal-length segment
Split list 1 to 200 non-empty lines All valid rows contribute to cumulative time and pace

For a 5 km finish of 24:30, 1470 seconds divided by 5 km gives 294 seconds per kilometre, displayed as 4:54/km. Five listed splits totaling 24:30 produce a finish delta of zero.

Accuracy Notes:

Manual lap presses carry reaction-time and marker-placement error. Use them to understand pacing, not to settle placing, qualification, or record claims.

  • A late press makes the current segment long and the following segment short.
  • A missed press can cause the next generated marker to exceed the race distance.
  • Mixed or incorrect units change the denominator and therefore the reported pace.
  • For an official result, use the event's certified timing and published finish record.

Worked Examples:

Even five-kilometre review

Five one-kilometre splits between 4:50 and 4:58 produce a narrow pace spread. If their durations add to 24:30, the zero finish delta supports using the split chart as a clean pacing review.

One missing marker

With a default split distance of 400 m, a line that contains only 1:32 advances 400 m from the previous marker. If that inferred marker passes the race distance, correct the missing or wrong marker before reading the pace.

References: