Skip to main content
install_mobileInstall STRIDD for offline access
Training Math

CALCU
LATORS.

Predict race times, convert paces, and find your training zones — instantly. Powered by the same Riegel and VDOT formulas the world's top coaches use.

// Predicted Times Across Distances
5K
25:00
5:00/km
10K
52:07
5:13/km
21.1K
1:55:00
5:27/km
42.2K
3:59:47
5:41/km
50K Ultra
4:47:02
5:44/km
Based on the Riegel formula: T₂ = T₁ × (D₂/D₁)1.06. Used by elite coaches worldwide. Predictions assume similar training and conditions.

READY TO TRAIN?

Numbers are great. A complete weekly plan is better.

How the Math Works

THE
EQUATIONS.

How does the Riegel race predictor work?

The Race Predictor uses Pete Riegel's 1977 formula: T₂ = T₁ × (D₂/D₁)1.06. You provide a recent race time (T₁) and distance (D₁), and the formula predicts your time (T₂) at any target distance (D₂). The exponent 1.06 reflects the physiological reality that longer races are run at progressively slower pace — you can't hold 5K pace for a marathon.

Riegel is most accurate when applied to a fresh race performance run in good conditions at a distance similar to your target. A 5K from two weeks ago predicts a half-marathon well. A half-marathon from six months ago predicts next weekend's 5K poorly. The closer your reference race is in time and distance, the more accurate the prediction.

For marathoners specifically, Riegel often over-predicts by 3-8% because it doesn't account for glycogen depletion and the cumulative muscular fatigue of 42 kilometres. Most runners should add 5-7 minutes to the Riegel marathon prediction as a reality check — especially on their first marathon.

When should I use the pace converter?

The Pace Converter is the tool runners reach for most often. Use it when: (1) translating between kilometre-based and mile-based plans (American plans often use miles; most Indian/UK/European plans use kilometres), (2) checking race-day splits for a target finish time, (3) calibrating a treadmill to match outdoor pace, (4) comparing two different runs where one was tracked by a GPS watch and one wasn't.

One kilometre equals 0.621371 miles. A 5:00/km pace equals 8:02/mile. A 4:00/km pace equals 6:26/mile. The converter also displays speed in km/h and mph — useful for treadmill calibration. At a 5:00/km pace, you're running 12 km/h (7.46 mph) — set the treadmill to 12.0 and you'll hit exactly that pace.

The race-distance splits section shows what a consistent pace produces across distances. Knowing that holding 5:00/km = 2:05:00 at a half-marathon = 4:13:00 at a full marathon helps calibrate race-day strategy without mental arithmetic at kilometre 32.

What are training pace zones and why do they matter?

The Training Paces tab uses Jack Daniels' VDOT methodology to derive seven calibrated training pace zones from a single race result. Each zone targets a specific physiological adaptation, and training at the correct zone unlocks the target adaptation — training above or below it dilutes the signal.

The most common mistake is running easy days too fast. Easy pace should feel almost embarrassingly slow — about 75-90 seconds per kilometre slower than your 5K race pace. This "dead slow" running is where capillary density grows, mitochondria multiply, and the aerobic engine genuinely adapts. Running easy days at moderate pace produces neither recovery nor development — the worst of both worlds.

The inverse mistake is running quality sessions too slow. Threshold pace (roughly half-marathon race pace) should feel "comfortably hard" — you can speak in 2-3 word bursts but not full sentences. Interval pace (3K-5K race pace) is "hard" — you'd want to stop if you had to hold it much longer than the rep. If you're hitting the target RPE but missing the pace, your race time is stale and needs updating.

Is VDOT accurate for beginners?

VDOT assumes a trained runner with an established base and reasonable pacing instinct. For runners with less than 6 months of consistent running, VDOT-derived paces are usually 10-20 seconds per kilometre too fast. The aerobic system hasn't caught up to the neuromuscular capacity — you can produce the pace for short bursts, but not sustain it in training volume.

Beginners should use VDOT as a ceiling rather than a target. Run your easy runs at VDOT easy pace + 15-30 seconds. Build aerobic base for 8-12 weeks before attempting VDOT threshold paces. As fitness develops, re-test with a 5K every 4-6 weeks and update your VDOT. The plan generator handles this ramp automatically — beginner fitness level applies a pace-padding factor to all zones.

How do heart rate zones compare to pace zones?

Heart rate and pace zones target the same adaptations but respond to different constraints. Pace is fixed by watch feedback — a 5:00/km pace is 5:00/km regardless of conditions. Heart rate is physiological — it responds to heat, altitude, cardiovascular drift, caffeine, sleep, dehydration. On a hot day, your heart rate at 5:00/km pace will be 5-10 bpm higher than on a cool day.

For easy runs, prioritise heart rate (keep it in Zone 2) over pace. For quality sessions, prioritise pace (hit the target) over heart rate (let it rise). For races, prioritise pace and use heart rate as a guardrail — if HR spikes abnormally at goal pace, something is wrong (dehydration, overheating, GI distress) and you need to adjust.

Why does the calculator predict different times than my watch?

Watch predictions (Garmin "Race Predictor", Coros, Polar) use proprietary algorithms that account for: your recent training load (not just one race), heart rate efficiency trend, running economy from step-by-step sensors, and elevation-adjusted pace. These are often more accurate than pure Riegel when you have 6+ months of watch data.

STRIDD's calculator uses the classical equations because they're transparent and reproducible — you can verify them yourself. For ground-truth race readiness, trust the watch for short-distance conversions (within 1.5× your reference race). For longer extrapolations (5K to marathon), trust Riegel/Cameron because watch algorithms often overfit to the data they have.

Calculator Questions

PACE & PACE ZONES
ANSWERED.

01

What is easy pace in running?

expand_more

Easy pace is the foundation of every serious training plan, and it's almost always slower than runners think it should be. The correct easy pace feels almost embarrassingly slow — you should be able to hold a full conversation, breathe through your nose, and finish feeling refreshed rather than tired. In numbers: easy pace is typically 60-90 seconds per kilometer slower than your current 5K race pace. If you run 5K in 25 minutes (5:00/km), your easy pace is around 6:00-6:30/km. Heart rate zone: 65-75% of maximum, or roughly 140-155 bpm for most runners. The point of easy running isn't to get faster today — it's to build aerobic capacity, capillary density, and mitochondrial count without generating fatigue. Elite marathoners run 80% of their weekly volume at easy pace because the physiological adaptations from easy miles are different from (and complementary to) the ones you get from hard sessions. If your easy runs feel moderately hard, they're too fast. Slow them down — your Tuesday intervals and Sunday long run will be better for it.

paceeasy-runningaerobic
02

What is Zone 2 running?

expand_more

Zone 2 is the boring-but-effective backbone of endurance training. It's defined as the effort level where your body uses primarily fat as fuel, your blood lactate stays below 2 mmol/L, and your heart rate sits at 60-70% of your maximum. In practical terms: you can speak full sentences, breathe through your nose, and sustain the effort for 1-3 hours without undue fatigue. Why does it matter? Zone 2 training causes specific cellular adaptations that no other intensity can replicate — mitochondrial biogenesis, capillary growth around slow-twitch muscle fibers, improved fat oxidation, and reduced cardiac strain. These adaptations are what let elite marathoners hold 3:00/km pace for 2 hours. Most recreational runners run their easy days too hard (in Zone 3) and their hard days too easy, getting stuck in a 'grey zone' that builds neither aerobic capacity nor speed. The fix: do 70-80% of your runs in true Zone 2, even if it means walking hills to keep heart rate down. Track it with a chest strap HR monitor for accuracy — wrist devices often lag or spike.

zone-2heart-rateaerobic
03

What is the purpose of a long run?

expand_more

The long run is the single most important session in any endurance plan. It's where you make the adaptations that matter most for 10K+ racing: mitochondrial density, capillary networks, fat-burning efficiency, glycogen storage capacity, and tendon resilience. Running 90-120 minutes once a week produces physiological changes that three 40-minute runs can't match — specifically, it teaches your body to function well in a depleted state, which is exactly what racing feels like. The long run should be done at true easy pace, not moderate — typically 60-90 seconds per km slower than goal marathon pace. Duration matters more than distance: 90-150 minutes is the sweet spot for most marathon training, regardless of how far you cover. Going beyond 2.5 hours has diminishing returns and rapidly increasing injury risk. For race distances under the marathon, cap your long run at 25-30% of weekly mileage. Long runs also build mental toughness — they teach you what boredom, discomfort, and fatigue feel like, and how to push through them without panic. Skip long runs and your fitness plateaus within 6-8 weeks, no matter how hard your intervals are.

long-runmarathonendurance
04

How do I safely increase running mileage?

expand_more

The 10% rule is a good starting guideline, but the real answer is: increase mileage in a pattern of 3 weeks up, 1 week down. Week 1: 30 km. Week 2: 33 km. Week 3: 36 km. Week 4: 27 km (down week). Week 5: resume at 36-40 km. This rhythm respects two biological realities — your aerobic system adapts faster than connective tissue, and your tendons need planned recovery windows to consolidate gains. Adding mileage without down weeks is the #1 cause of stress fractures and Achilles problems in intermediate runners. Two other rules: add volume by extending existing runs before adding new run days, and never increase mileage AND intensity in the same week. If you're adding a speed session, hold volume flat. If you're adding a long run, hold intensity flat. Monitor these warning signs: resting heart rate up 5+ bpm, sleep quality dropping, morning stiffness lasting beyond warm-up, or any localized pain that persists more than 48 hours. Any one of these means hold mileage steady for 10-14 days before pushing again. The goal is consistent upward progression over months, not rapid jumps that end in injury.

mileageprogressioninjury-prevention
05

When should beginners start doing speed work?

expand_more

The answer most coaches won't give you: not yet, no matter when you're asking. Structured speed work — 800m repeats, tempo runs, VO2max intervals — damages untrained connective tissue and hormones in ways that easy running doesn't. You need a base of 30-40 km per week for at least 8-12 weeks before your tendons can handle threshold pace, and 6-12 months of consistent running before you should be doing maximal intervals. That said, you can introduce 'speed' carefully in earlier phases. After 8 weeks of run-walk, add 4-6 strides at the end of one run per week: 20 seconds of relaxed fast running, 60 seconds walking, repeat. This teaches your nervous system and biomechanics without creating fatigue. After 3-4 months, you can add light fartlek (unstructured pace changes during an easy run). True intervals and tempo work should wait until you can run 40 km per week comfortably with no aches. Speed work skipped for 6 months won't hurt your fitness — you'll gain 90% of possible improvements from easy running plus strides alone in year one. Speed work added too early will put you in a boot or ruin your tendons for a season.

speed-workintervalsbeginner
06

What is a tempo run?

expand_more

A tempo run, also called threshold run, is the cornerstone of endurance training for 10K to marathon runners. The purpose is to train your body to clear lactate as fast as you produce it at increasing paces — effectively raising your 'lactate threshold,' the point at which running shifts from aerobic to anaerobic metabolism. In practical terms, tempo pace is 'comfortably hard' — you can speak 2-3 word phrases but not full sentences, your breathing is controlled but deep, and you could sustain the effort for about an hour at maximum. For most recreational runners, that's somewhere between 10K and half marathon race pace, or 30-40 seconds per km faster than marathon pace. A typical tempo session: 15 minutes easy warm-up, 20-30 minutes at tempo pace, 10 minutes easy cool-down. More advanced variations include 2 x 15 minutes with 3 minutes recovery, or long tempo runs of 40-50 minutes at slightly slower pace. Do one tempo session per week during base and build phases. Done correctly, 8-12 weeks of tempo work can drop your 10K time by 30-90 seconds. Done too fast, it becomes a VO2max workout and produces burnout instead of gains.

tempo-runthresholdlactate
07

What is the difference between intervals and tempo runs?

expand_more

Tempo runs and intervals train different energy systems and produce different adaptations. Tempo runs are sustained continuous efforts — typically 20-40 minutes at 'comfortably hard' pace (85-88% of max HR), which is near your lactate threshold. The goal is teaching your body to clear lactate at faster speeds, raising the pace you can hold without blowing up. Intervals are short, hard repetitions at 5K pace or faster (90-95% of max HR), typically 400m to 1600m in length, with active rest between. The goal is to improve VO2max (oxygen uptake) and running economy. Example tempo session: 20 minutes at half-marathon pace, continuous. Example interval session: 5 x 1000m at 5K pace with 90 seconds jog recovery. You feel different during each: tempo is hard-but-controlled breathing; intervals leave you gasping for the first 30 seconds of each recovery. Most training plans for 10K-marathon distances include one tempo and one interval session per week during the build phase. Do both, not just one. Tempo alone makes you durable but capped; intervals alone make you fast but fragile. The combination is what lifts race times meaningfully.

intervalstempo-runtraining
08

How many rest days should runners take?

expand_more

Rest days are when adaptation actually happens — the hard sessions are the stimulus, recovery is the response. Skipping rest days means you're never capitalizing on the training you did. For beginners running 3 times per week, the non-run days should all be rest or active recovery (walking, yoga, easy cycling). For intermediate runners doing 4-5 runs per week, one full rest day is the minimum. For experienced runners doing 5-6 runs per week, you still need at least one no-running day, typically the day after the long run or a quality session. Elite runners who run 6-7 days per week usually include one 'double easy' day that functions as near-rest. Full rest means no structured exercise — you can walk, stretch, or foam roll, but nothing that generates fatigue. Active recovery is different: 20-30 minutes of very easy movement (cycling, swimming, walking) that promotes blood flow without adding stress. The signs you need more rest: resting heart rate elevated 5+ bpm, sleep disturbed, legs feel heavy 48 hours after hard sessions, motivation dropping, or minor aches becoming persistent. Take the rest before the injury forces you to.

rest-daysrecoverytraining
09

What is the best cross training for runners?

expand_more

Cross training serves three purposes for runners: adding aerobic volume without impact, building strength to prevent injury, and maintaining fitness during injury or peak weeks. The top choices: Cycling replicates aerobic demand closest to running and lets you accumulate easy Zone 2 time without joint load — it's the #1 substitute for easy runs when you're nursing a niggle. Swimming offers full-body movement, excellent for recovery days and building lung capacity, though it uses different muscle patterns so fitness transfer is partial. Strength training is the most underrated — 2 sessions per week of squats, deadlifts, single-leg work, and core reduces running injury rates by roughly 50% (per a 2020 meta-analysis) and improves running economy by 2-8%. Elliptical, rowing, and stair climbing are decent aerobic alternatives. Avoid high-impact cross training like jump rope or plyometrics if you're already high-mileage — they add to your impact load. A typical week: 4 runs, 2 strength sessions, 1 easy cycle or swim. When injured, maintain fitness with aqua running or cycling at the same time/intensity you'd run. Cross training doesn't replace running-specific adaptation, but it's how smart runners stay healthy for decades.

cross-trainingstrengthinjury-prevention
10

What is 80/20 training for runners?

expand_more

The 80/20 principle, popularized by coach Matt Fitzgerald, comes from studying how elite endurance athletes actually train. When researchers tracked Olympic distance runners, Kenyan marathoners, and Norwegian cross-country skiers, they consistently found that 80% of training time was spent at low intensity (Zone 1-2, easy pace) and only 20% at moderate-to-high intensity (Zone 3-5). Importantly, this isn't just about elites — controlled studies in recreational runners showed the 80/20 split beat 'threshold training' (where most running is at moderate-hard pace) by meaningful margins in race performance over 10 weeks. The problem most recreational runners have is the 'moderate grey zone': they run their easy days too hard (Zone 3) and their hard days too easy, so nothing is truly easy and nothing is truly hard. The 80/20 fix: run your easy days embarrassingly slow (true Zone 2), and run your hard days genuinely hard. Measure by time or distance across the week, not per run. For a 40 km week: 32 km easy, 8 km in faster efforts (tempo, intervals, strides). The paradox: running slower most of the time makes you faster.

80-20polarizedtraining
11

What is a good 5K time?

expand_more

'Good' depends heavily on age, sex, training history, and body type, but here are honest benchmarks for reference. For men: 30+ minutes is typical for complete beginners, 25-30 is average for recreational runners, 22-25 is solid for trained amateurs, sub-20 is competitive amateur territory, and sub-17 is serious local club level. For women: 33+ for beginners, 28-32 average, 25-28 solid, sub-23 competitive amateur, sub-20 very fast. Age affects these significantly — a 35-minute 5K at age 50 is equivalent to around 29 minutes at age 25 on age-graded tables. Rather than chasing external benchmarks, focus on your own trajectory: most runners can drop 2-5 minutes from their first 5K within 6 months of consistent training. Beyond that, improvement slows to 30-90 seconds per year for trained runners. Your VO2max, genetics, and lifestyle set a ceiling, but almost anyone can reach sub-25 within a year of proper training. The best 5K time is the one that represents honest progress from where you started, not a comparison to someone else.

5kbenchmarkspace
12

What is a good 10K time?

expand_more

10K times scale roughly as 2.1x your 5K time plus 15-30 seconds. For men: 65+ minutes is typical for beginners, 55-65 average, 45-55 solid amateur, sub-45 competitive, sub-40 very fast amateur, and sub-35 serious club level. For women: 70+ beginner, 60-70 average, 50-60 solid, sub-50 competitive, sub-45 very fast. Age-graded benchmarks matter: a 55-minute 10K at age 55 is roughly equivalent to a 46-minute 10K at 25. The 10K is often considered the 'most honest' distance — too long to fake through with raw speed, too short to reward only endurance. Training for it requires both threshold work and aerobic volume. Improvement trajectory is similar to 5K: beginners drop 3-8 minutes in the first year of training, then gains slow to 1-3 minutes per year. Breaking 60 minutes is a major milestone that most recreational runners can reach within 12-18 months of consistent training. Breaking 50 requires structured threshold and tempo work plus 40-50 km per week. Breaking 40 means you're in the top 5% of amateur distance runners and requires 70+ km per week with strategic intervals.

10kbenchmarkspace