Run, Record, Reduce: A Leicester 5K Result Sheet as a Living Data Set

On a Saturday morning in Leicester, Victoria Park fills with the familiar sights of a 5K parkrun: marshals in hi-vis, a restless start line, and a finish funnel that turns hundreds of individual efforts into one beautifully ordinary spreadsheet. It is free, it is timed, and it produces a result sheet. That sheet is a data set waiting to be read.

The result sheet is a data set

Every finisher gets a position, a time, an age category and an age-graded percentage. Parkrun results are public, but in a classroom it is best to work with anonymised or invented numbers. The point is not to study named runners; it is to study the structure of the numbers. A result sheet is a lovely mix of ratios, averages, rankings and percentages, all produced by people who were mostly thinking about breathing.

Start with the obvious fact: the course is 5 kilometres. Everything else is arithmetic.

Pace is a ratio in disguise

Pace per kilometre is simply total time divided by five. The only trap is that times are not decimals. Convert to seconds first.

A runner finishing in 24:30 has taken 24 × 60 + 30 = 1,470 seconds. Divide by 5 and you get 294 seconds per kilometre, which is 4 minutes 54 seconds. A runner finishing in 27:15 has taken 1,635 seconds, or 327 seconds per kilometre: 5 minutes 27 seconds. The second runner is 165 seconds slower overall, which is about 11.2% slower relative to the faster time.

That single conversion opens up a whole lesson. Which is faster: 4:55 per kilometre or 24:40 for 5K? How much faster? If a runner improves from 5:30 per kilometre to 5:15 per kilometre, what does that do to their 5K time? Pace turns a race into a ratio problem with muddy shoes.

Negative splits: the second half story

Most runners have heard of a negative split: running the second half faster than the first. It sounds simple, but it is a ratio question in disguise.

Suppose a runner goes through halfway in 12:10 and finishes in 24:08. The second half took 11:58, which is 12 seconds faster. As a percentage of the first-half time, that is 12 ÷ 730 × 100, or about 1.6%. A small number, but over 5K it feels like a lot. A positive split works the other way: 11:50 and 12:20 gives a second half 30 seconds slower, which is about 4.2% slower than the first half.

This is where pacing strategy becomes mathematical. An even-pace plan is not just a slogan; it is a claim about the relationship between two halves. Students can compare a runner who fades with one who finishes strongly and ask which strategy produced the better time, and why.

Positions, percentiles and the arithmetic of the field

Finishing position is ordinal: 37th means 36 people finished ahead. But the field size matters. In a field of 412, finishing 37th puts you in the top 9%, because 37 ÷ 412 is about 0.09. There are 375 runners behind you, which is a fraction of 375 ÷ 412, or about 91% of the field.

A percentile is slightly more precise. One common classroom formula is:

percentile rank = (number of runners below you) ÷ (total runners − 1) × 100

With 36 runners below, that gives 36 ÷ 411 × 100, or about 8.8. It means roughly 8.8% of the field finished below you. Definitions vary at the edges, so the useful lesson is not memorising one formula but understanding what a percentile is trying to say: where you sit relative to everyone else.

Gaps between positions are arithmetic too. If first place is 17:05 and tenth place is 18:20, the gap is 75 seconds across nine places, an average of 8.3 seconds per place. That is not a prediction, but it is a useful way to describe how tightly packed the front of a race is.

Age grading: the percentage that levels the field

Age grading is the clever bit. It compares a runner’s time with a standard time for their age and gender, then expresses the result as a percentage. A simplified version is:

age grade = (standard time ÷ actual time) × 100

If the standard is 22:30 and the runner takes 25:00, the calculation is 1,350 ÷ 1,500 × 100, which is 90%. If another runner has a standard of 30:00 and takes 33:20, that is 1,800 ÷ 2,000 × 100, also 90%. Two very different times, one shared percentage. That is the point: age grading gives students a reason to compare ratios rather than raw totals.

Averages can hide the hill

Take five finishers with times of 22:00, 24:00, 25:00, 27:00 and 40:00. The mean is 27:36, because the total is 138 minutes and 138 ÷ 5 = 27.6 minutes. The median is 25:00, the middle time when the five are ordered. The range is 18 minutes. That 40:00 is doing a lot of work to the mean, which is exactly why medians are useful when a data set has an outlier.

A class can go further: what happens to the mean if the slowest runner improves by five minutes? What happens to the median? Which measure better describes a typical Saturday morning?

Five problems for a Tuesday lesson

1. Convert 23:45, 26:30 and 29:10 into pace per kilometre.
2. A runner splits 12:20 and 12:05. Is that a negative split? By what percentage did the second half improve?
3. In a field of 350, you finish 84th. What percentage of the field finished ahead of you? What is your percentile rank using the formula above?
4. An age standard is 21:00 and a runner finishes in 23:20. What is the age-graded percentage?
5. Five times are 21:30, 23:00, 24:30, 26:00 and 38:00. Find the mean, median and range. Which average tells the better story?

The finish line

A parkrun result sheet is not just a list of who beat whom. It is a compact problem-solving resource: ratios in every pace, percentages in every age grade, and positional data that rewards careful reading. Next time a Saturday morning produces a results page, treat it as a worksheet with a bit of mud on it. The maths is already there. The job is simply to notice it.