Pace Calculator: How to Find Your Running Speed

I Couldn't Figure Out Why My Splits Were All Over the Place

So last spring I signed up for a half marathon — my first one — and I started tracking my runs with a cheap GPS watch. The thing is, the watch would tell me my pace for each mile, but I had no real sense of what those numbers meant for my overall goal. I'd finish a 5-mile training run and see splits like 8:42, 9:15, 8:28, 9:03, and 8:55, and I'd just stare at them thinking.. am I getting faster? Slower? Am I on track to finish in under two hours?

It took me an embarrassingly long time to sit down and actually do the math. And honestly, once I did, everything clicked.

That's basically what a pace calculator does — it takes the guesswork out of your running speed and tells you exactly where you stand. Whether you're training for a race, trying to hit a PR, or just curious how fast you actually move when you jog around the neighborhood, knowing your pace per mile (or per kilometer) is the foundation of every training plan I've ever followed.

The Math Behind Your Pace (It's Simpler Than You Think)

Pace is just time divided by distance. That's it.

If you ran 3 miles in 27 minutes, your pace is 9 minutes per mile. If you ran 5K (which is about 3.1 miles) in 25 minutes, your pace is roughly 8:04 per mile. The formula looks like this:

And if you want to go the other direction — say you know your pace and want to predict a finish time — you just flip it around:

Let me walk through a real example. Say you ran 4 miles in 34 minutes and 20 seconds. First, convert that to pure minutes: 34 + (20/60) = 34.33 minutes. Then divide by 4 miles: 34.33 ÷ 4 = 8.58 minutes per mile. Now, 0.58 of a minute is about 35 seconds (0.58 × 60 = 34.8), so your pace is 8:35 per mile. Not bad! And if you wanted to predict your 10K time at that pace, you'd multiply 8.58 × 6.21 (since a 10K is 6.21 miles) and get about 53.3 minutes, or roughly 53:17.

The conversion from decimal minutes back to minutes-and-seconds trips people up constantly. I messed it up for weeks before I realized you have to multiply the decimal part by 60, not just read it as seconds.

Pace vs. Speed — They're Not the Same Thing

This confused me for a while.

Pace is time per distance (like 9:00 per mile). Speed is distance per time (like 6.7 miles per hour). They're inverses of each other, and runners almost always talk in pace, not speed. Cyclists and drivers talk in speed. It's a cultural thing, honestly, but it matters because if someone asks "what's your pace?" and you say "6.5 mph," you'll get a funny look at the running club.

Pace (min/mile)	Speed (mph)	5K Finish Time	Half Marathon Finish
7:00	8.57	21:45	1:31:47
8:00	7.50	24:51	1:44:54
9:00	6.67	27:58	1:58:01
10:00	6.00	31:04	2:11:06
11:00	5.45	34:11	2:24:12
12:00	5.00	37:17	2:37:17

That table is approximate — race distances aren't perfectly round numbers, and a half marathon is 13.1 miles, not 13 — but it gives you a solid ballpark. I keep something like this taped inside my training journal (yes, I still use a paper journal, fight me).

How to Actually Use Your Pace in Training

Knowing your pace isn't just trivia. It changes how you train.

Most decent training plans break your runs into zones based on pace. Your easy run pace might be 60 to 90 seconds slower than your race pace, your tempo pace is maybe 15 to 30 seconds faster than race pace, and your interval pace is considerably quicker than that — like, gasping-for-air quicker. If you don't know your baseline pace, you can't calibrate any of this, and you end up doing what I did for my first six months of running: going too hard on easy days and too easy on hard days and wondering why I wasn't improving.

Here's what I'd suggest. Go run a timed mile — warm up first, obviously — and push it to about 85-90% effort. Not a full sprint, but genuinely hard. Whatever that time is, that's roughly your current threshold pace. Use a

to extrapolate your predicted race times from there, and then build your training zones around those numbers.

For example, if your timed mile comes in at 7:45, your easy run pace is probably somewhere around 9:15 to 9:30, your tempo pace is around 7:30, and your 5K race pace is in the neighborhood of 8:00 to 8:10. These aren't exact — everyone's physiology is different — but they're a starting point that actually makes sense.

And if you're doing interval work on a track, you'll want to think in terms of shorter distances. A

can help you figure out what a 7:30 mile pace translates to for a 400-meter repeat (about 1:52, if you're curious).

Quick Tips I Wish Someone Had Told Me Earlier

Your pace on hilly terrain means almost nothing compared to flat-ground pace. Don't freak out if you're 45 seconds slower per mile on a hilly route — that's normal and expected. I used to get discouraged running in my neighborhood (which is basically a series of small hills) until I ran a flat 5K and realized I was way faster than I thought.

GPS watches aren't perfectly accurate. They can be off by 1-3% on distance, which throws your pace calculation off too. If precision matters to you — like for track workouts — use a measured track or a

to verify your routes.

Temperature matters more than most people realize. Running in 85°F heat can slow you down by 30 to 60 seconds per mile compared to running in 55°F weather, and that's not a sign of poor fitness — it's just physics and physiology doing their thing.

If you're tracking your

, pace factors into that calculation too. A faster pace burns more calories per minute but fewer calories per mile (since you cover the distance quicker). It's a weird paradox that I had to think about for a while before it made sense.

Also, don't sleep on tracking your

alongside your pace improvements. I dropped about 8 pounds over three months of consistent training and my pace improved by nearly 20 seconds per mile without any speed-specific work. Lighter body, same engine, faster pace — the math checks out.

And if you're into other fitness metrics, tools like a

or a

can give you a fuller picture of where your fitness actually stands. I use all of these together, honestly. The pace number alone doesn't tell the whole story.

What's a good pace for a beginner runner?

There's no single answer, but most beginners land somewhere between 10:00 and 13:00 per mile, and that's completely fine. I started at about 11:30 per mile and thought I was slow until I realized that a huge percentage of recreational runners are right in that range. The goal early on is consistency, not speed. Speed comes later, almost on its own, once you've built a base of regular mileage.

How do I convert pace per mile to pace per kilometer?

Divide your mile pace by 1.609. So a 9:00 mile is about 5:35 per km. Or just use a

and let it do the conversion for you — way less room for error that way.

Does running on a treadmill give an accurate pace?

Mostly, yeah. Treadmills display speed in mph, so you'd need to convert that to pace (divide 60 by the speed — so 6.0 mph = 10:00/mile). The bigger issue is that treadmill running is slightly easier than outdoor running because there's no wind resistance and the belt assists your leg turnover. Setting the incline to 1% roughly compensates for this, which is a trick I picked up years ago and still use every time.