Sprint Time Norms: 10m, 20m, and 40-Yard Benchmarks by Age and Sport

A club coach times a 13-year-old over 20 meters, gets 3.4 seconds, and has nothing to compare it to. Is that fast for the age group, average, or a sign the kid needs to see a physio about that limp on the left side? Norms tables exist to answer exactly that question, but most of the ones passed around on coaching forums quietly mix hand-timed 40-yard dashes from football combines with electronically-timed 10m splits from track meets, then present both as if they measure the same thing. They don't, and the gap between methods is often larger than the gap between a below-average sprinter and a genuinely good one.

Papaiakovou et al. (2009) tracked sprint performance across chronological age in a large school-based cohort spanning roughly ages 6 to 17 and found the improvement curve is far from a straight line: 10m and 20m times drop steadily through childhood, then split sharply by sex once puberty arrives, with boys showing a second wave of improvement around age 13-14 that the girls' data in the same cohort did not mirror to nearly the same degree. Little and Williams (2005), working with 105 professional soccer players, found something just as relevant for building a norms table in the first place — 10m acceleration and 20m-to-flying-speed correlate only moderately with each other in trained adults, meaning a single number compresses two distinct physical qualities and can hide which one actually needs work.

This guide separates 10m, 20m, and 40-yard benchmarks by age band and by sport, walks through why the testing method changes what counts as good, and ends with a short checklist for turning a percentile into an actual training decision instead of just filing the number away.

Before any norms table is useful, the test itself has to be standardized — method-driven variance between two testing setups is frequently larger than the real difference between a good and an elite athlete at the same age.

1. Start position and signal. Use a two-point or three-point staggered stance with a self-initiated start rather than a reaction to a whistle or gun. Reacting to an external signal adds 0.15-0.30s of reaction-time noise that has nothing to do with sprint mechanics and will make a fast athlete look slow on paper.
2. Gate or line placement. Set the front foot roughly 0.3m behind the first timing gate or start line. Placed any closer, forward lean at the set position can trigger the gate before the athlete actually starts moving, shaving fake time off the split.
3. Timing method. Hand-timing with a stopwatch consistently reads faster than electronic gates or laser systems — the timer's own reaction time (typically 0.2-0.3s) gets subtracted at the start but not corrected for at the stop. This single artifact is the most common reason a roster's hand-timed 40-yard number doesn't match what the same athlete runs on a laser-timed testing day. It's a measurement difference, not a fitness change.
4. Split distances from a single start. Test 10m and 20m off the same start rather than re-triggering the clock at 10m, so the 10m split reflects pure acceleration and the 20m split reflects acceleration plus early top-end speed.
5. Trials. Run at least two attempts with 4-5 minutes of recovery and keep the best. A single maximal sprint carries a same-day coefficient of variation around 1-2% even in trained athletes — small in isolation, but often larger than a full year of speed development in a youth athlete, which is exactly the range where over-interpreting one run does the most damage to a kid's confidence.

Related: our timing gates vs IMU sprint testing guide covers the accuracy trade-offs between these tools in more depth if you're deciding what to buy before you start testing.

The table below reflects the developmental trend documented by Papaiakovou et al. (2009) and consistent with subsequent youth-sprint literature — times improve steadily through childhood, and the male-female gap widens after puberty as boys gain a second growth-related jump in speed that girls' data does not show to the same extent. Treat the numbers as approximate bands, not exact cutoffs; a cross-sectional study like this one compares different children at one point in time rather than following the same athletes across years, so some of the age-to-age difference reflects cohort variation as well as true development, and the original sample was drawn from Greek school-sport programs, meaning absolute times may run a few tenths faster or slower in populations with different baseline activity levels.

Two things matter more than the exact cell an athlete falls into. First, timing of puberty (peak height velocity) varies by as much as two to three years between individuals of the same chronological age, so a 13-year-old who hasn't yet hit their growth spurt will often sit a full age-band behind a early-maturing peer despite equal training — this is biological timing, not a training gap, and coaches who don't account for it end up mislabeling late developers as untalented. Second, these bands describe general youth populations, not athletes already selected into competitive sport; a 14-year-old training three times a week in an academy program will typically sit toward the fast end of the band or beyond it.

Sport-specific demands shape which part of the sprint gets trained hardest, and that shows up clearly once you compare 10m and 20m times across disciplines rather than age groups. Little and Williams (2005) tested 105 professional soccer players and reported 10m and 20m times that clustered noticeably slower than dedicated track sprinters — typical values in that cohort sat in the high-1.7 to high-1.8 second range for 10m and roughly 3.05-3.20s for 20m — because soccer rewards repeated short accelerations over a full match far more than it rewards a single maximal top-speed sprint. The same study's key finding for programming purposes was that a player's 10m rank and 20m rank often didn't match: several players who accelerated well from a standstill were only middle-of-the-pack once the sprint extended past 15-20m, and vice versa.

None of these rows should be read as a pass/fail bar. They describe where a competitive athlete in that population typically sits, and the spread inside any single sport is wide — a soccer center-back and a soccer winger can differ by two to three tenths at 20m and both be entirely appropriate for their role.

The 40-yard dash (36.6m) is a U.S. football-specific test distance, and Robbins (2010) remains one of the more thorough analyses of how it varies by position, drawing on multiple years of NFL Draft Combine testing data across the full range of drafted positions. The pattern that emerges is straightforward: skill positions built around open-field speed test fastest, and positions built around mass and short-area force production test slowest, with a gap of roughly half a second separating the two ends.

Two limitations matter before anyone uses this table as a target. First, this is a pre-selected population — these are athletes who were already good enough to be drafted, not a cross-section of everyone who plays the position, so treating the low end of a range as an entry requirement for a high school or college athlete sets an unrealistic bar. Second, many of the historical combine numbers circulating online are hand-timed and typically run 0.10-0.24s faster than the same athlete's official laser-timed result — a gap well documented in combine testing analyses and consistent with the reaction-time issue described earlier in this guide. When you see a headline-grabbing 4.3-second 40 attached to a name, check whether it's hand or laser time before comparing it to anything.

Mixing hand and electronic times in the same comparison. A 0.2s hand-timing advantage is enough to move an athlete up an entire tier on most norms tables. If you don't know how a number was captured, don't compare it directly to a laser-timed benchmark.

Ignoring surface and footwear. Sprinting on turf in training shoes versus a track in spikes can shift a 20m time by 0.05-0.10s purely from traction differences — enough to matter at the margins of a percentile band, though not enough to explain a large gap on its own.

Treating the 40-yard time as if it measures the same thing as a 10m split. Little and Williams (2005) showed acceleration and top-end speed are only moderately correlated in trained athletes; an athlete with an average 10m but a strong 20m has a different training need than one with the reverse profile, and a single combined number erases that distinction entirely.

Applying adult or late-maturing norms to a pre-pubertal athlete. A 12-year-old sitting near the slow end of their age band may simply not have hit their growth spurt yet. Retest in 6-12 months before concluding anything about long-term speed potential.

Reacting to one session. With same-day trial-to-trial variance around 1-2%, a single run that looks 0.05-0.08s off a previous best is well within normal noise, not evidence of regression.

A norms table only earns its keep if it changes what happens in the next training block. Before filing a result away, run through this short checklist:

• Was the test self-started, with the timing method (hand, gate, or IMU) recorded alongside the number? If not, retest before trusting the comparison.
• Does the athlete's 10m rank match their 20m rank relative to peers, or is there a gap? A large gap points to a specific quality — acceleration or top-end speed — that should get disproportionate attention in the next 6-8 weeks.
• For athletes under 16, has growth/maturation status been considered, or is the comparison happening purely on chronological age?
• Is the comparison being made against the right population — sport, competition level, and sex — rather than a generic table pulled from a different context entirely?
• Has the athlete been tested more than once? A single session shouldn't drive a programming decision on its own.

An athlete who scores mid-pack on 10m but well below their sport's 20m band, for instance, doesn't need more start-technique drilling — they need max-velocity mechanics work and probably more exposure to flying sprints, since their acceleration is already fine and the limiter shows up later in the sprint. The table tells you where someone stands; the gap between two splits usually tells you what to actually do about it.