Half Marathon Splits Calculator: Exact Mile and Kilometer Paces

A half marathon splits calculator converts a finish-time goal into average pace and cumulative checkpoint times across 21.0975 km (13.1094 miles). For a 2:00:00 goal, exact even pace is 5:41.27 per km or 9:09.23 per mile; the cumulative targets are 28:26 at 5 km, 56:53 at 10 km, 1:00:00 at true halfway, and 1:53:45 at 20 km.

The reliable calculation method keeps fractional seconds internally, derives every checkpoint from the original finish time, and rounds only the displayed result. That prevents a pace band from drifting away from the goal as rounded segments accumulate.

A split calculator answers the arithmetic question: given this finish time, when should I reach each marker? It does not establish whether the target matches your current fitness. If that is still undecided, work through the separate half marathon goal-time calculation before building the race card.

Lock five decisions before calculating your splits

A useful result depends on more than typing two hours into a time field. Set these inputs first:

Course conditions are a second layer. Generate the neutral split table first, then redistribute the same total time across slower and faster segments if the route warrants it.

Tool labels can obscure the job being performed. The Calculator.net pace calculator solves pace, time, or distance from two known variables. The RunHive half marathon chart translates a finish goal into per-mile pace, per-kilometer pace, and a halfway split. The Strava running pace calculator presents expected pace and estimated finish time for selected race distances. For race-day execution, request cumulative marker times in addition to the average pace.

The exact half marathon split formula

Let `T` be the goal time in seconds and use these distance constants:

```text T = hours × 3600 + minutes × 60 + seconds Dkm = 21.0975 Dmi = 21.0975 / 1.609344 = approximately 13.1094

pace per km = T / Dkm pace per mile = T / Dmi cumulative time at x km = T × x / Dkm cumulative time at y miles = T × y / Dmi ```

For a checkpoint interval rather than a cumulative time, subtract the preceding exact cumulative result. Do that subtraction before rounding.

Worked calculation for a 2:00 half marathon

A two-hour goal contains 7,200 seconds:

• Per-kilometer pace: `7200 / 21.0975 = 341.2727 seconds`, or 5:41.27.
• Per-mile pace: `7200 / 13.1094 = 549.2251 seconds`, or 9:09.23.
• The 10 km checkpoint: `7200 × 10 / 21.0975 = 3412.73 seconds`, or 56:52.73.
• The midpoint: `7200 × 0.5 = 3600 seconds`, or 1:00:00.

The hundredths describe the calculation, not a demand to control each stride to one-hundredth of a second. A watch or printed band can show whole seconds while the calculator retains the decimals underneath.

Why rounded pace creates finish-time drift

This does not make a display of 5:41/km incorrect. It means the displayed label should not become the input for every subsequent row. When I design calculator output, the entered finish time remains the source of truth.

Round the display, not the race.

Using 21.1 km instead of 21.0975 km creates another, smaller discrepancy: at a two-hour pace, the extra 2.5 meters represent about 0.85 seconds. The full distance is easy to store, so there is little reason to discard it.

Half marathon pace chart by goal time

The table uses full-precision distance and then rounds pace to hundredths of a second. Halfway equals half the finish time only for an even-split plan.

For a whole-second watch display, round 9:54.99 to 9:55 rather than reading the decimal as a separate split. Keep the unrounded value for cumulative checkpoints.

Cumulative checkpoints for common finish goals

These are even-split targets calculated directly from the finish time. Each cell is independently rounded to the nearest second, so adding rounded table cells is not the intended calculation method.

The midpoint is 10.54875 km, which is 548.75 meters beyond the 10 km marker. At a two-hour goal, the 10 km target is 56:52.73 and the midpoint is 1:00:00—a gap of 3:07.27. A runner who mistakes 10 km for halfway could think they are more than three minutes ahead while following the plan exactly.

Why a 1:45 goal is not simply 4:59 every kilometer

The exact pace for 1:45:00 is 4:58.61/km. Multiplying the displayed 4:59 by 21.0975 produces 1:45:08.15, an 8.15-second overrun.

One integer-second representation derived from rounded cumulative targets looks like this:

That is a rounding solution for a printable band, not an instruction to surge whenever a 4:58 follows a 4:59. The smoother race-day reference is the cumulative column: 24:53 at 5 km, 49:46 at 10 km, 52:30 at halfway, and 1:39:32 at 20 km.

Even, negative, and positive splits use different halfway targets

An even split assigns equal time to equal distances. A negative split assigns less time to the second half, while a positive split assigns more. The Year Round Running calculator is an example of a tool that generates negative-split schedules by mile or kilometer.

The following two-hour scenarios illustrate the arithmetic. The later-half examples allocate 50.5% and 49.5% of total time across equal 10.54875 km halves; they are scenarios, not performance prescriptions.

A good split is therefore goal-relative. For an even two-hour plan, 1:00:00 is the correct midpoint. For the later-half-faster example, 1:00:36 is correct. Comparing either runner with the other plan would produce the wrong diagnosis.

Use an even table when equal time per unit distance is the intended model. Choose a later-half-faster allocation only if the slower opening is explicit in the plan. A later-half-slower model is useful as a contingency calculation because it shows how much time must be banked—or how the finish changes—when the second half receives more time.

Convert half marathon pace to km/h or mph

Pace reports time per unit distance; speed reports distance per unit time. The conversions are:

```text km/h = 3600 / pace in seconds per km mph = 3600 / pace in seconds per mile ```

For a two-hour goal, the unrounded values are 10.54875 km/h and approximately 6.5547 mph. A calculator can therefore show 5:41/km, 9:09/mile, 10.55 km/h, and 6.55 mph without contradiction; each is a rounded view of the same target.

Choose the unit used by the course markers for the main race card. A secondary conversion can help with training or comparison, but alternating between rounded kilometer and mile targets during the race introduces avoidable noise.

Make course adjustments without changing the finish by accident

An even split table assigns the same time budget to every unit of distance. It does not inspect climbs, descents, exposed sections, turns, or planned stops. A course-adjusted plan changes segment targets while holding the total constant.

The audit equation is simple:

```text sum of all segment adjustments = 0 seconds ```

Consider an illustrative two-hour plan with a 3 km sector assigned 10 extra seconds per kilometer. That sector consumes 30 additional seconds. To preserve 2:00:00, the other 18.0975 km must return the same 30 seconds:

• Neutral pace: 5:41.27/km.
• Assigned 3 km sector: 5:51.27/km, adding 30 seconds in total.
• Remaining distance: subtract `30 / 18.0975 = 1.6577 seconds per km`.
• Required average across the remainder: approximately 5:39.61/km.

Those numbers demonstrate time-budget conservation; they do not establish how a particular hill should be paced. Course-specific inputs must determine the adjustment. The same accounting applies to a planned stop: adding 20 seconds without rebalancing produces a finish target of 2:00:20 rather than 2:00:00.

A reproducible course-aware workflow is:

1. Generate neutral cumulative splits from the original goal.
2. Define segment boundaries using identifiable course points.
3. Enter each slower or faster adjustment separately.
4. Rebalance the net adjustment to zero if the finish goal remains fixed.
5. Recalculate cumulative checkpoints from the adjusted segments.
6. Confirm that the last row still equals the entered goal.

For a deeper implementation of that layer, see the race pacing calculator workflow for course elevation. If wind or climate values are included, record the source and timestamp with the plan and update the inputs when newer race-week information becomes available.

Turn the calculation into a printable race card

A race card needs fewer columns than the underlying calculator. Keep the goal, strategy, clock basis, target, actual time, and delta. A compact two-hour version could read:

```text HALF MARATHON — GOAL 2:00:00 — EVEN Clock basis: ______________________

MARKER TARGET ACTUAL DELTA 5 km 0:28:26 ______ ______ 10 km 0:56:53 ______ ______ Halfway 1:00:00 ______ ______ 15 km 1:25:19 ______ ______ 20 km 1:53:45 ______ ______ Finish 2:00:00 ______ ______ ```

At each chosen marker, calculate `delta = actual cumulative time − target cumulative time`. A positive value means the selected clock is later than the target; a negative value means it is earlier. This is clearer than trying to reconstruct the race from a single rounded lap pace.

Use checkpoints that you expect to identify on the course. If the plan is keyed to physical markers, compare the clock at those markers even when the watch reaches its own kilometer or mile alert at a different point. Verify the available markers and timing basis in the organizer's current race information.

For a PDF or pace-band workflow:

1. Generate cumulative times from the exact total.
2. Limit the card to identifiable checkpoints.
3. Add blank actual and delta fields if you want to record them.
4. Export or print at a size you can read while moving.
5. Recheck the finish row after any formatting or manual edits.

The free running split calculator guide explains the broader split-generation workflow. A spreadsheet, calculator, or printable PDF can all be valid outputs if they preserve the same arithmetic.

Separate race prediction from split calculation

A mathematically perfect table can be built for a finish time that has weak support from recent running data. Precision in the rows does not make the target itself precise.

Race-equivalency tools address that earlier decision. The McMillan calculator presents race predictions and training paces, while the Luke Humphrey Running equivalency calculator converts an existing race result into estimated equivalents. Those estimates can supply a candidate finish time; the split calculator then performs deterministic arithmetic on the selected target.

Keep the distinction visible in your plan:

Record the race or workout used for the prediction, the model selected, and any material difference between that input and the target event. If two methods disagree, inspect their inputs and assumptions rather than hiding the disagreement inside an average.

Split-table failure modes and their fixes

The final-row test catches several of these errors at once: the last cumulative checkpoint must equal the entered finish time, down to the stored precision.

Frequently asked questions

What is a good split for a half marathon?

A good split is one that matches the declared finish goal, strategy, timing basis, and course model. On a flat even-split plan, halfway should equal exactly half the goal time: 45:00 for 1:30, 52:30 for 1:45, 1:00:00 for 2:00, and 1:15:00 for 2:30. A planned negative split has a later halfway target because the second half receives less time.

What pace is needed for a two-hour half marathon?

The exact average is 5:41.27/km, 9:09.23/mile, 10.54875 km/h, or approximately 6.5547 mph. Whole-second displays round those values to about 5:41/km and 9:09/mile, but cumulative checkpoints should still be calculated from 7,200 total seconds.

What is the pace for a 1 hour 45 minute half marathon?

A 1:45:00 target requires 4:58.61/km or 8:00.57/mile. Even cumulative checkpoints are 24:53 at 5 km, 49:46 at 10 km, 52:30 at halfway, 1:14:39 at 15 km, and 1:39:32 at 20 km.

Is 2.5 hours slow for a half marathon?

The label is not useful for calculating or selecting a personal plan. A 2:30:00 finish translates to 7:06.59/km or 11:26.53/mile, with an even halfway target of 1:15:00. Assess whether that target fits your evidence, course, and race objective rather than assigning it a universal category.

Is the 10 km split the halfway split?

No. Within a 21.0975 km calculation, halfway is 10.54875 km. The two markers are 548.75 meters apart, so they require separate cumulative targets.

What is the 10-10-10 rule for marathons?

A common version divides a marathon into the first 10 miles, the second 10 miles, and the remaining 10K; how each block is paced varies by the plan defining the phrase. It does not map cleanly to a half marathon. Use explicit distances and time allocations in a half marathon calculator so there is no ambiguity.

Is it true that only 1% of people run a half marathon?

A bare percentage cannot be evaluated without a defined population, time period, event type, and primary data source. Treat the claim as unverified unless its source supplies those details. It has no effect on the pace or split calculation.

Can a half marathon splits calculator produce a PDF?

A calculator can format its cumulative output for printing or PDF export. Check that the PDF states the goal, distance, units, split strategy, and clock basis, and that its finish row exactly matches the entered total.

Run this audit before printing

• Confirm that the distance is 21.0975 km and the chosen mile conversion is consistent.
• Confirm that 10 km and 10.54875 km are separate rows when both are shown.
• Confirm that course adjustments sum to zero if the original finish goal is fixed.
• Confirm that every cumulative row comes from unrounded internal values.
• Confirm that the card names its timing basis and uses markers available on the course.
• Confirm that the last row equals the entered finish time.

If the final row differs by even one displayed second, regenerate the cumulative rows from the original total instead of patching an individual split.