Half Marathon Pace Calculator

Half Marathon Pace Calculator

Convert a target finish time and race distance into average pace, speed, and practical checkpoint splits.

Pace 4:59 min/km Speed 12.06 km/h Finish 1:45:00 Distance 21.0975 km
Example workbook validated and ready.

Race inputs

Choose a standard race or switch to a custom distance.

Use a decimal point, not a comma. Maximum supported distance is 1,000 km.

Finish time

Hours: 0-99. Minutes and seconds: whole numbers from 0 to 59.

Changes the emphasized pace; both units remain available.

Changes the emphasized speed; the alternate unit is retained.

Live results

Average pace
4:59 min/km
Equivalent: 8:01 min/mile
Average speed
12.06 km/h
Alternate speed
7.49 mph
Finish time
1:45:00
Race distance
21.0975 km
A 1:45:00 half marathon requires an average pace of 4:59 min/km.

Estimated checkpoint splits

Checkpoint Distance (km) Distance (mi) Elapsed time
5 km 5.000 3.107 0:24:53
10 km 10.000 6.214 0:49:46
15 km 15.000 9.321 1:14:39
20 km 20.000 12.427 1:39:32
Finish 21.098 13.109 1:45:00

Splits assume an even average pace from start to finish. Real courses, turns, elevation, weather, aid stations, and GPS measurement can create variation.

How to use the half marathon pace calculator

What this calculator does

This calculator turns a race distance and finish time into an average running pace, an equivalent pace in the other common distance unit, average speed, and estimated checkpoint times. It is useful for setting a race target, preparing a pacing card, comparing a completed result with a goal, or converting between min/km, min/mile, km/h, and mph. A half marathon is officially 21.0975 km, or about 13.1094 miles, as described by World Athletics' half marathon overview. The result is an arithmetic average; it does not predict fitness, account for hills or weather, or guarantee that a target is physiologically appropriate.

When to use it

Use it before a race to translate a goal time into a pace you can recognize on a watch, during training to plan goal-pace repetitions, after a race to understand your average performance, or when a plan uses a different unit system from your usual one. It can also create an Excel workbook for a coach, training log, or personal race plan.

How to calculate

  1. The calculator opens with a complete demonstration: Half marathon, 21.0975 km, and 1:45:00. The example results and a validated Excel workbook are available immediately.
  2. Choose Event. Standard selections fill the official or conventional race distance; choose Custom distance to type another value.
  3. Enter Distance with a decimal point and choose km or mi. Then enter Hours, Minutes, and Seconds for the target or recorded finish time.
  4. Select the Primary pace unit and Primary speed unit. These controls change which equivalent is emphasized without changing the underlying performance.
  5. Read the live pace, speed, finish-time, distance, and checkpoint results. Select Download Excel to export the current validated state. Reset clears the demonstration and all semantic data; Excel export then remains unavailable until a complete valid state is entered again.

Input guide

Event is required and accepts Half marathon, Marathon, 10K, 5K, or Custom distance. Selecting Half marathon supplies 21.0975 km. Changing the distance manually changes the event to Custom distance so the label never implies a standard course length that is no longer present.

Distance is a required positive decimal measured in the adjacent km or mi selection. For example, enter 21.0975 km or 13.1094 mi. A decimal point is accepted; a decimal comma, scientific notation, mixed units, zero, negatives, and values above the 1,000 km safety limit are rejected instead of being silently reinterpreted. Increasing distance while holding time constant produces a faster pace and higher speed.

Hours, Minutes, and Seconds are required whole-number time components. Hours may be 0-99; minutes and seconds must each be 0-59. The combined time must be greater than zero. For a 1 hour 45 minute finish, use 1, 45, and 0. A common mistake is entering 105 in Minutes; enter 1 hour and 45 minutes instead.

Primary pace unit accepts min/km or min/mile. Primary speed unit accepts km/h or mph. These required display controls do not alter the calculation; they choose the emphasized equivalent. NIST explains why length and time units combine into derived quantities such as velocity in its guide to SI units.

Output guide

The header pills summarize Pace, Speed, Finish, and Distance. Average pace is finish time divided by distance and is rounded to the nearest displayed second. Equivalent pace is the same performance converted to the alternate distance unit. Average speed and Alternate speed express distance per hour; higher speed corresponds to lower time-per-distance pace. Finish time and Race distance restate the validated inputs so the result remains auditable.

The Estimated checkpoint splits table lists checkpoint name, distance in kilometers, distance in miles, and elapsed time. Each row assumes exactly even pacing. A high split time means slower average progress; a low split time means faster progress. The final row must equal the entered finish time. These are planning estimates rather than recommended race tactics.

Worked example

With the startup values, total time is 1:45:00, or 6,300 seconds. Dividing 6,300 by 21.0975 km gives 298.6136 seconds per kilometer, which displays as 4:59 min/km. Converting the distance to miles gives about 13.1094 miles; 6,300 divided by that distance gives 480.5720 seconds per mile, displayed as 8:01 min/mile. Dividing 21.0975 km by 1.75 hours gives 12.06 km/h, equivalent to 7.49 mph. The final checkpoint is exactly 1:45:00.

How the pace model works

Average pace = total finish time ÷ race distance
Average speed = race distance ÷ total finish time

Pace and speed describe the same average performance from opposite directions. Pace answers “how much time is required for one kilometer or mile?” Speed answers “how much distance is covered in one hour?” Because pace is time divided by distance, a smaller pace number is faster. Because speed is distance divided by time, a larger speed number is faster.

The checkpoint table applies the same constant pace to each listed distance. That is mathematically consistent, but runners rarely move at perfectly constant speed. Congestion, turns, hills, wind, heat, hydration stops, fatigue, and intentional pacing strategy all affect actual split times. The U.S. Physical Activity Guidelines provide broad context for building activity gradually, while individual race preparation should reflect health, experience, and professional guidance where appropriate.

Practical interpretation and common mistakes

  • Do not confuse 4:59 min/km with 4.59 decimal minutes. The displayed colon separates minutes and seconds.
  • Do not compare min/km directly with min/mile; the same running speed produces a larger minutes-per-mile number because a mile is longer.
  • GPS devices can report a race distance slightly longer than the certified course because of path choice and measurement error. A watch-based pace may therefore differ from official finish-time pace.
  • A target average pace is not automatically the best opening pace. Many runners benefit from controlled early effort rather than trying to “bank” time.
  • The exported workbook stores typed numbers and current selections, including the complete split table, so it is suitable for review and further planning rather than only a screenshot of rounded values.