VDOT Explained: What Your Score Means and How to Use It

One race time holds more information than most runners ever get out of it. Jack Daniels worked out how to turn it into a single fitness score, VDOT, and from that score every training pace you need plus the time you should be able to run at any other distance. This guide covers what the score means, the formula behind it, what a good VDOT looks like at each level, a full reference table, and where VDOT beats heart rate and where it loses. Feed the VDOT calculator one race. It hands back everything below.

What VDOT means in running

A fitness score for runners, built from a race result. That is VDOT. The name is how physiologists say VO2 with the dot that marks a per-minute rate, vee-dot-oh-two, shortened to VDOT, and a score of 50 means your race is the performance you would expect from a runner with a VO2max of 50 ml/kg/min, given how race times and oxygen cost normally relate.

"Would expect" carries the weight there. VDOT is a pseudo-VO2max, Daniels' own phrase for it. A lab test measures how much oxygen you can process at your limit, and a race measures what you do with it: the fraction of that ceiling you can hold for the duration, plus the oxygen each metre costs you, which is running economy. Two runners with the same lab number can finish minutes apart. In a study of 12 elite 10 km runners with similar VO2max values, the lab number explained almost none of the spread in race times, while running economy explained about 65 percent of it (Conley and Krahenbuhl, 1980). Two decades later a review of trained distance runners reached the same conclusion. Hold VO2max similar and economy predicts performance better than VO2max does (Saunders et al., 2004).

VDOT skips the lab. It starts from the result, and economy, sustainable fraction and aerobic ceiling all come out in the wash because the race already priced them in, which is why the score prescribes paces so well: it describes the runner you are on the road, not the engine on a treadmill. Your Garmin or Apple Watch VO2max estimate is a third number again, a model of the engine from heart rate against pace on ordinary runs, and it will sit a few points from your VDOT either way. Use VDOT for the paces. It came from something you did.

The Daniels and Gilbert formula, explained

The formula comes from Oxygen Power, the 1979 tables Jack Daniels and Jimmy Gilbert built from treadmill data on trained runners, and it has two parts. Each answers one question.

The first: how much oxygen does it cost to run at a given speed? The answer is a curve that bends upward, each extra metre per minute costing a little more than the one before, and for speed in metres per minute the cost in ml/kg/min is minus 4.6, plus 0.182258 times the speed, plus 0.000104 times the speed squared. Both equations are the ones Daniels and Gilbert published in Oxygen Power, and they are the same constants running inside our VDOT calculator. At 6:00 per km, which is 167 m/min, that comes to about 29 ml/kg/min. At 4:00 per km, about 48.

The second: what fraction of your maximum can you hold for a race that long? Nobody holds 100 percent of VO2max for an hour. For efforts under about ten minutes the curve starts above 100 percent, because anaerobic energy lets you run faster than your aerobic ceiling for a while, then it falls: about 95 percent at 20 minutes, 89 percent at an hour, 84 percent at two hours, 82 percent at three, flattening near 80 percent beyond that. The equation is 0.8, plus 0.1894393 times e to the power of minus 0.012778 times the minutes, plus 0.2989558 times e to the power of minus 0.1932605 times the minutes.

That fraction is the same idea Michael Joyner used in his 1991 model of the fastest possible marathon, where the lactate threshold sets the share of VO2max a runner can hold in events beyond about 3,000 m and economy turns the result into speed (Joyner, 1991).

Put the two together and VDOT falls out. Divide the oxygen cost of your race speed by the fraction of maximum you could hold for your race duration.

A worked example. You run 5 km in 25:00, which is 200 m/min, and the oxygen cost at 200 m/min is minus 4.6 plus 36.45 plus 4.16, about 36.0 ml/kg/min, while the sustainable fraction at 25 minutes is 0.8 plus 0.138 plus 0.002, about 0.94. Divide 36.0 by 0.94. Your VDOT is 38.3.

Paces run the same machine in reverse. Daniels assigns each training intensity a percentage of VDOT, and threshold sits at 83 to 88 percent, so take the middle, 85.5 percent of 38.3, which is 32.75 ml/kg/min, and ask the first equation which speed costs that much: 185 m/min, or 5:24 per km. The same steps put easy pace near 6:35 and interval pace at 4:51. Equivalent race times hold the VDOT fixed and solve for time at another distance, 51:53 for 10 km, 1:55 for the half and 3:58 for the marathon, with training for those distances assumed.

How to calculate your VDOT

You can run the arithmetic by hand, as above. Nobody does. Enter one race in the calculator and it returns the score, the five pace bands in min/km or min/mile, and equivalents from 1500 m to the marathon. The input decides whether the output is worth anything.

• An all-out effort. A tempo run you finished with plenty left gives a VDOT below your fitness. The paces undertrain you.
• Recent. A result from the last month or so describes the runner you are now; a result from another season prescribes paces for someone else.
• 5 km to 10 km first. Long enough for the aerobic fraction to dominate, short enough that fueling, heat and pacing errors barely touch the result.
• Never the marathon. A marathon time carries the day's heat, the gel you skipped and the kilometres you went out too fast, and none of that is fitness, so marathoners get a cleaner number from a recent half.
• Flat, measured, cool, outdoors. Trail, hills, heat and wind pull the score down. Treadmills vary with belt calibration; the treadmill pace converter sorts out the paces, but take the score from an outdoor result.

No recent race? Run a 5 km time trial on a flat loop, after two easy days, with a proper warm-up, and treat it as a race.

What is a good VDOT?

Daniels' tables run from VDOT 30 to 85, the whole sport fits inside that span, and the score has no adjustment for sex or age: it describes a performance, not a rank, so "good" depends on who is asking. A few anchors, using times from the table below:

• Under 35: beginner or returning runner. 5 km slower than 27:00, marathon slower than 4:16, and the gains come from easy volume and consistency.
• 35 to 45: the typical recreational runner. 5 km between 27:00 and 21:50, 10 km between 56:00 and 45:00, marathon between 4:16 and 3:28. Nothing moves this band faster than one threshold session a week.
• 45 to 55: solid club runner. 5 km from 21:50 down to 18:20, half marathon 1:40 to 1:24, marathon 3:28 to 2:56, and interval work starts to matter as much as threshold.
• 55 to 65: competitive. 5 km 18:20 to 15:55, marathon 2:56 to 2:33. Points arrive one at a time, from specificity and recovery.
• 65 to 75: sub-elite. Sub-16 5 km and sub-2:33 marathon at the bottom of the band, 14:04 and 2:15 at the top.
• 75 and above: elite. A 2:05 marathon is VDOT 82. So is a 13:00 5 km.

Two caveats. The score is raw, so a woman or a masters runner at VDOT 45 is closer to her or his potential than a 25-year-old man at the same score; an age grading calculator gives the level-adjusted view. And it compares across distances only when you are trained for them. The 5 km runner at VDOT 50 will not run the 3:10 marathon next month without the long runs.

VDOT reference table: race times and training paces

Every fifth VDOT from 30 to 85, the race time it predicts at four distances, and the five Daniels training paces per kilometre, each at the middle of its band: that is the table, and the full slow-to-fast band for your exact score, in min/km or min/mile, is one race away in the VDOT calculator.

Times are h:mm:ss. The half is 21.1 km. Find a recent race time in its column, take the VDOT on the left, then read across; a time between two rows means a VDOT between them.

The pace columns are centres. The bands differ in width: easy is wide, 59 to 74 percent of VDOT, so at VDOT 45 the easy band runs from 6:22 to 5:19 per km, while threshold is narrow, 83 to 88 percent, at VDOT 45 from 4:51 to 4:38.

The five VDOT training paces and what each one trains

Daniels prescribes five intensities as percentages of VDOT. The percentages are the whole idea: rather than "run 4:44 per km", the system says "run at 85 percent of your current fitness", and the pace updates when the score does.

• Easy, 59 to 74 percent. Where most of the week lives: warm-ups, cool-downs, recovery days and the bulk of the long run, with an adaptation that is structural, more capillaries, more mitochondria, tendons that tolerate the volume. Easy days drifting toward marathon pace is the error that undoes the most runners. It leaves nothing for the sessions that move the score. In heart-rate terms this is Zone 2, covered in the Zone 2 heart rate guide.
• Marathon, 75 to 84 percent. Race pace for the marathon. In a marathon block it is used as steady runs and long-run inserts, so the body learns fuel use and posture at the pace it will race; outside a marathon build it is mostly a pace to stay out of.
• Threshold, 83 to 88 percent. Comfortably hard. Near the pace you could race for an hour, this is the intensity that raises the lactate threshold, and the highest-return session for most runners between VDOT 35 and 55. Two shapes: a steady 20 minutes, or cruise intervals of 5 to 15 minutes with a minute of rest. Daniels caps a threshold session at about 10 percent of the week's mileage, and the session menu is in the tempo run guide.
• Interval, 95 to 100 percent. Close to 3 km to 5 km race pace, the speed that puts you at VO2max, in reps of 3 to 5 minutes with jog recoveries of about the same length. Shorter reps waste the session. Oxygen uptake needs time to climb: in a 2025 study of highly trained middle-distance runners, four reps of 3 minutes at 95 percent of vVO2max held the runners above 90 percent of VO2max for about 328 seconds, while 24 reps of 30 seconds at 100 percent managed about 201 seconds despite the higher speed (Fleckenstein et al., 2025). Daniels' cap is 8 percent of weekly mileage or 10 km in a session, whichever is less; the VO2max interval guide builds the sessions.
• Repetition, 105 to 110 percent. Mile race pace and faster. Reps of 200 to 400 m with full recovery, so every one is fast and relaxed; the target is speed and economy rather than fitness, and run tired they become a slow anaerobic grind. Daniels keeps a repetition session to 5 percent of the week or 8 km, whichever is less.

One gap in the system is deliberate. 88 to 95 percent, between the top of threshold and the bottom of interval, is too hard to accumulate threshold volume, too slow to reach VO2max, and where most "hard" runs land by accident. A runner at VDOT 45 grinding "steady" runs at 4:30 per km lives in that gap.

VDOT versus heart rate zones and RPE

Three ways to hold a session at the right intensity, and each is right about something the other two miss.

VDOT pace is immediate and repeatable: the watch shows it every second, the target does not move with the weather, and it is the direct expression of the fitness you raced. It knows nothing about today, though. The same 4:44 per km after a bad night's sleep, in 28-degree heat, or halfway up a hill.

Heart rate reads the body's response, which is what pace cannot see. But it lags. At the start of a rep it needs a minute or more to catch up, so it under-reports short intervals; in the study above, the 30-second reps spent more time above 90 percent of maximum heart rate than the 3-minute reps did, even though the 3-minute reps held the runners at VO2max for longer. Then there is drift. In prolonged exercise, heart rate creeps up from about 10 to 20 minutes in and stroke volume falls with it, and the rising rate itself is the main cause, since a faster heart has less time to fill between beats (Coyle and González-Alonso, 2001). An hour into a long run, the same easy pace sits higher on the heart-rate trace. The effort has not changed.

Daniels pairs each pace with a heart-rate band anyway. The bands are wide: easy at about 65 to 79 percent of maximum heart rate, marathon 80 to 90, threshold 88 to 92, interval 98 to 100, and no target for repetitions because the reps end before the heart catches up. The bands are from the intensity table in Daniels' Running Formula. Set the zones from a real maximum or a threshold test rather than an age formula; the heart rate zone calculator covers both.

RPE is free. It sees everything, including sleep, work stress and the cold you have not admitted to yet, and it is also less precise than runners assume: a meta-analysis of the Borg scale found that perceived exertion tracks heart rate and percent of VO2max with correlations of about 0.62 to 0.64, valid but well below the 0.80 to 0.90 often quoted (Chen et al., 2002).

The practical split: VDOT pace sets the target on the track and on flat road sessions, heart rate keeps easy days honest and flags drift on long runs, and RPE holds the veto. When pace and heart rate disagree, the disagreement is the information. Heat, fatigue, illness, or a score that has moved. The marathon heart rate guide shows how the two get combined across a full build.

When VDOT paces lie

The score is only as honest as the race behind it, and the paces only transfer to conditions like that race. Five cases where the number and the road disagree.

• Heat. Marathon performance slows progressively as the wet-bulb globe temperature rises from 5 to 25 degrees C, and slower runners lose more than the leaders: across seven marathons and decades of results, top men finished about 1.7 percent off course-record pace in the coolest weather quartile and 4.5 percent off in the warmest (Ely et al., 2007). Your VDOT did not drop on a hot day. Your available pace did. The environmental pace adjuster puts a number on it, and the heat acclimation guide covers how much training can win back.
• Hills and trail. Oxygen cost per metre climbs with the gradient. The equation assumes flat ground, so hold the effort the session asks for and let pace float, or check grade adjusted pace to see what the hilly run was worth on the flat.
• Altitude. Less oxygen per breath makes every VDOT pace slower than at sea level, by a margin that grows the higher you go and shrinks with acclimatisation. Racing high on a sea-level score prescribes paces you will not hold.
• A stale score. The most common lie of all. A VDOT from a spring race prescribes paces in autumn that are either too soft to progress or hard enough to injure.
• A mismatch between distances. If your half marathon gives VDOT 42.6 (1:45) and your marathon gives 37.9 (4:00), the formula is not broken; it is showing an endurance gap of about five points, where the fitness was there for 3:38 and the specific preparation was not. Use the higher score for the paces. The gap is the training brief, and the race time predictor shows the same gap the other way.

Moving your VDOT

The score changes with the training it prescribes, on its own schedule, and Daniels' rule for raising it is conservative: go up one point after a run of sessions where the paces feel right at the prescribed effort, never after one good day. Drop a point or two after illness, a break, or a string of sessions where the paces did not come, and stay there until they do. Training at a score you no longer own is how runners get hurt.

What a point is worth: about 38 seconds over 5 km at VDOT 35, 24 seconds at 45, 17 at 55 and 12 at 65. In the recreational band, a point every six to eight weeks of consistent training is realistic; higher up, points arrive one per block if at all. The lever is easy volume plus one threshold session a week, with intervals added when the race calls for it. Recalculate after every race. Inside a block, every six weeks. A score that has not moved in three months of consistent training says look at sleep, fueling and recovery before running harder, and the deload guide is where that look starts.

How Movement Rebels fits

Get your VDOT from the calculator. Write the score and your threshold and interval paces into "Notes for your coach", which lives under Coach, Start Here, My Equipment and Preferences. The Movement Rebels coach reads that field alongside everything else it sees, so the Sunday weekly plan lands with sessions at the paces you own rather than generic zones. After each run syncs from Garmin or Apple Health, the post-activity analysis reads your per-km splits against your average heart rate, so a threshold session that held 4:44 per km at a heart rate ten beats above the last one gets read as heat, fatigue or a score on the move, not filed as a pass. The coach also sees your HRV trend, resting heart rate and sleep from the same sync, plus the heavy squat session you logged in the calendar on Thursday, so when you check in with it before Friday it already knows your legs are not fresh and can move the session if you ask. Cutting weight for a race? Say so in the same notes field. The coach cannot read your meals, but it treats a rising resting heart rate and a falling HRV as fueling signals. Planned sessions push to your Garmin watch when auto push is on, so the session is on your wrist before you start.

Race a 5 km in the next month, take the number, and run the easy days at the slow end of the band. The score moves from there.