Minutes to Seconds

The Pace Band Says 4:15, the Watch Beeps in Seconds

A goal time is decided in minutes: sub-20 for the 5K, under three hours for the marathon, a half in one fifty-nine. The moment that goal has to be executed it stops being minutes. A watch alerts on a lap in seconds, a coach on the infield calls a 400 in seconds, a pace band is printed in seconds of drift per kilometre, and every argument about whether the first 10 km went out too hard is settled in single seconds. Pacing is the discipline of holding a number you decided in minutes while the feedback arrives in seconds, and the conversion between the two runs constantly in a runner's head.

Conversion factor: 1 min = 60 s, so multiply minutes by 60. A 4:15 per-kilometre target is 4 × 60 + 15 = 255 s per km, which over the 42.195 km of a marathon comes to 10 759.7 s, or 2:59:20 — the reason 4:15 is the pace everyone chasing a sub-three memorises.

Where the Two Units Sit in a Race Plan

The goal is stated in minutes

Entry forms, qualifying standards and club targets are all whole minutes, or minutes and seconds. Nobody enters a race hoping for 10 760 seconds.

The correction is made in seconds

You never adjust by a minute mid-race. You take three seconds off a kilometre, or give four back on a climb, and the total quietly follows.

Course markers force the arithmetic

A pace held in minutes per kilometre still has to be checked against markers that may be in miles, or against a track lap of 400 m. Both checks land in seconds.

Devices disagree about the format

Watches show minutes and seconds, exported activity files store elapsed seconds, and treadmills show speed. Three formats, one effort.

Turning a Goal Time Into the Number on Your Wrist

This is the sequence used when a training block starts and a target pace has to become something checkable at every marker on the course.

Enter the pace as a decimal, not as a colon

The field takes a number, so 4:15 goes in as 4.25 and 5:41 as 5.6833. A comma works in place of the dot, so 4,25 is accepted exactly as written on a European entry form, and stray spaces are ignored.

Scale it to the split you are actually watching

Multiply the pace by the segment before converting. A 5 km rep at 4:15 pace is 21.25 min, which reads as 1 275 s; a single 400 m lap at the same pace is 1.7 min, or 102 s.

Reverse it to read a session back

The swap button (↔) gives s → min, which is the direction you need when an exported file hands you 1 275 seconds and the only question is whether that rep hit the target.

Copy the bare number onto the plan

The copy control on each field gives digits only, with no unit attached, which is what a spreadsheet column of splits or a pace-band draft wants. Ctrl + C inside a field does the same thing.

4.15 is not 4:15. Typing the clock format straight in is the most common pacing error there is: 4.15 min is 249 s, six seconds per kilometre faster than the 255 s you meant. Over a marathon those six seconds compound into more than four minutes of pace you never trained to hold.

Paces, Laps and the Finish Times They Produce

Each row is one steady pace, shown as the clock format a plan is written in, the seconds a watch and a coach work with, and what that pace produces at two distances. Lap times assume lane one of a standard 400 m track; marathon times use the official 42.195 km and are rounded to the nearest second.

Pace per km	Minutes	Seconds	400 m lap	Marathon finish
3:30	3.5	210 s	84 s	2:27:41
4:00	4	240 s	96 s	2:48:47
4:15	4.25	255 s	102 s	2:59:20
4:30	4.5	270 s	108 s	3:09:53
5:00	5	300 s	120 s	3:30:59
5:41	5.6833	341 s	136.4 s	3:59:49
6:00	6	360 s	144 s	4:13:10
7:00	7	420 s	168 s	4:55:22

Two rows do most of the work in real training. The 5:00 line is worth memorising because everything about it is round — 300 seconds a kilometre, a two-minute lap, 12 km/h on a treadmill — which makes it the reference point runners count up and down from. The 5:41 line is the sub-four-hour marathon, and it shows why paces are carried in seconds at all: 341 is easy to hold in your head and easy to adjust by two, where 5.6833 is neither.

What This Pair Does During a Pacing Session

Build a pace band a row at a time

Type a pace on the left and the second count keeps up as you go, so a whole column of target splits can be worked out in one sitting without clearing the field between entries.

Read an exported rep back as a pace

Swapping the pair turns the raw elapsed seconds an activity file stores into the minutes a training plan is written in, which is the direction post-session analysis runs.

Hours on the right for ultra distances

Both dropdowns list every time unit the app defines and are searchable, so a 100 km target totalling 780 minutes can be read straight in hours once the numbers stop fitting on a pace band.

Tenths of a second do not vanish

Up to eight decimals are kept, so the 136.4-second lap behind a four-hour marathon keeps its fraction instead of rounding into a lap you were never running.

Questions From the Start Line

Is 5:00 per kilometre the same information as 12 km/h?

The same effort, described upside down. Pace is time per distance and speed is distance per time, so one is the reciprocal of the other: 300 s per km divides into 3 600 s per hour exactly 12 times. The practical difference shows up when you change them. Speeding up from 10 to 11 km/h saves 32.7 s per kilometre, while going from 11 to 12 saves only 27.3 s — equal steps in speed are unequal steps in pace. That is why treadmill dials feel deceptively generous at the fast end, and why runners plan in pace and convert to speed only when a machine forces them to.

How do I read a min/km pace on a course marked in miles?

Multiply the seconds per kilometre by 1.609344. At 5:00/km that is 300 × 1.609344 = 482.8 s, or 8:03 per mile; at 4:00/km it is 386.2 s, or 6:26. The rough field version is to add about 60 % of your kilometre pace, which is close enough to notice a mile marker arriving too early. What catches people out is a watch quietly auto-lapping in miles on a course marked in kilometres — every alert then lands roughly 40 seconds after the sign you were using to check yourself, and the two sets of numbers never line up again for the rest of the race.

What does a negative split actually look like in seconds?

Smaller than most people imagine. A common marathon plan is to run the first half two to three seconds per kilometre slower than target and the second half the same amount faster. On a 3:30 goal — an average of 298.6 s per km — that means holding around 301 for the first 21.1 km and around 296 for the second, which produces the same finish while feeling completely different at 30 km. Expressed in minutes the adjustment is 0.05 either side of target, a number nobody can hold in their head, which is precisely why pacing conversations are conducted in seconds.

What should each 400 m lap read if I am pacing off the track?

Take the seconds per kilometre and multiply by 0.4. A 5:00/km pace is a flat 120 s per lap, 4:00/km is 96 s and 4:15/km is 102 s. The convenience of the track is that two-minute laps make a 25-minute 5K obvious after a couple of circuits, so drift is visible long before it costs anything. One caveat: those figures apply to lane one. Lane four measures roughly 415 m per lap on a standard track, so holding the same lap time out there is genuinely a faster pace, and a session that felt harder than planned is often a lane problem rather than a fitness one.

How much does one second per kilometre change a marathon time?

42.195 seconds — one second for every kilometre of the course, and the reason marathon pacing is argued over in single digits. Five seconds per kilometre is three and a half minutes, which is often the entire margin between a comfortable qualifier and missing one. Read the other way, it also shows how little a small early mistake buys you: going out four seconds a kilometre too fast for the first 10 km puts you barely 40 seconds ahead of schedule, a bank far too small to justify what running that pace does to the second half.