Distance Covered in Football Doesn't Measure Effort: Why the Number Misleads

Total distance covered is the most useless statistic football loves. It pops up on the half-time graphics, it fills the reports of non-league clubs that have just bought GPS vests, and it gets quoted in the dressing room as proof of who “put a shift in”. And it tells you almost nothing about a player’s real effort.

I’m not saying the number is wrong. It’s accurate. The problem is what people conclude from it. A central midfielder who covers 11.8 km hasn’t necessarily worked harder than a centre-back who covered 9.4 km. He may have worked a good deal less.

And that matters, because managers are making selection, load and even character decisions based on this number.

What Everyone Says (and Why It’s Wrong)

The usual logic is simple: more kilometres, more work, more commitment. A player who runs 12 km “doesn’t hide”. One who runs 9 km is “strolling about”.

The problem starts with what those kilometres are made of. In a professional match, around 70% of total distance is covered walking or jogging, below 14 km/h. The efforts that actually tire players out, sprints, accelerations, hard decelerations, changes of direction, make up a small slice of the distance but a huge slice of the physiological cost. Two players can cover the same 10 km and have completely different games: one did 600 metres above 20 km/h, the other did 150.

Then there’s position. A central midfielder covers more total distance because his role makes him shuttle between the lines in almost every phase of play. A centre-back covers less because he plays in a shorter space. But the centre-back makes dozens of short accelerations and decelerations, aerial duels and turns that total distance simply doesn’t capture. Decelerations in particular are among the actions with the highest mechanical load on muscles and tendons, and they barely register in the kilometres.

And there’s the game model. Teams that spend longer without the ball run more. Sean Dyche’s Burnley regularly sat near the top of the Premier League distance tables in games where they had far less of the ball. A side that controls possession makes the opposition run. In studies across European leagues, the link between total distance and winning is weak at best. In some analyses it’s even slightly negative.

So the player who “runs the most” might simply be playing in a position that demands more movement, in a team that spends more time out of possession, at a pace that doesn’t actually tire him that much.

What the Data and Experience Show

For half a season I worked alongside a National League North club that had just invested in GPS vests. By matchday 3, the manager had dropped the right winger. The reason: he was consistently the outfield player with the lowest total distance in the squad, around 8.9 km. “He doesn’t work”, was the explanation.

When we looked at the full data, the story was different. The winger had the most distance above 25 km/h per match in the squad, the most sprints and the highest number of accelerations above 3 m/s². He covered little total distance because he stayed wide and still, waiting for the right moment to attack the space in behind, which was exactly what the game model asked of him. When he went, he went flat out.

His replacement covered 10.3 km in the next match. And three sprints. The team stopped threatening in behind and, two matches later, the manager reversed his decision.

The practical takeaway isn’t to bin the GPS. It’s to stop reading the top line of the report. The measures that say more about effort are high-intensity distance (above 19.8 km/h), sprint distance (above 25 km/h), the number of high-intensity accelerations and decelerations and, above all, internal load: how the player responded to all of it.

That’s why, at clubs without GPS, I don’t recommend trying to guess distance. It makes more sense to record what the player did on and off the ball. I use the SportsLabTools Football Stats tool to cross-reference recoveries, duels won and attacking actions per player, and that picture shows the squad who’s influencing the game rather than who’s racking up metres.

Internal Load Is What’s Missing From the Conversation

Even with the right external-load measures, you’ve only got half the equation. The same sprint costs different players different amounts, and the same player different amounts in different weeks. A player who slept 5 hours after a night shift will feel 6 km very differently from a teammate who slept 8.

The simplest and best-validated way to measure this is sRPE: the player’s rating of perceived exertion (0 to 10 scale) multiplied by minutes played. A player who plays 90 minutes at RPE 8 has a load of 720 arbitrary units. One who plays 90 at RPE 5 has 450. It looks crude. But it correlates well with more sophisticated internal-load measures such as heart rate, and it costs nothing.

I’m not sure sRPE works as well with very young players, who tend to rate less consistently. With senior players, after three or four weeks of logging, the patterns become very reliable.

So Why Does the Number Still Rule?

If total distance says so little, why is it still the top line of every report? I’ve got three explanations. None of them is scientific.

The first is that it’s easy to understand. Everyone knows what a kilometre is. Explaining to a chairman what a deceleration above 3 m/s² means takes effort. The simple number always beats the useful number when the audience isn’t technical.

The second is that it confirms what we already think. The manager who reckons a player is lazy finds in total distance the proof he wanted. The one who thinks another player is a warrior does too. Hardly anyone opens a report hoping to be proved wrong.

The third is the most dangerous. When players know distance is being judged, they start playing for it. I’ve seen a midfielder make pointless runs in the last ten minutes of a game that was already won, just to climb the squad’s internal ranking. He ran more, helped less and turned up on Tuesday more fatigued than he needed to be. When a measure becomes a target, it stops measuring what it was built for.

So my position here is blunt: total distance should not be shared with the squad as a measure of commitment. Ever. If it is shared, it should be in context, next to the intensity metrics, and always compared within the same position.

When Total Distance Still Has a Use

It would be dishonest to say the number is worthless. It’s useful in at least three situations.

Comparing a player with himself. If a midfielder usually covers 10.5 km and drops to 8.7 km for three matches in a row, in the same position and the same game model, something has changed. It could be accumulated fatigue, it could be an injury that hasn’t shown itself yet. The absolute value doesn’t matter. The individual variation does.

Controlling training volume. In pre-season sessions, knowing total distance helps make sure volume doesn’t spike from one week to the next. There, as a measure of volume rather than effort, it does its job.

Return from injury. In the final phase of a reintegration protocol, total distance is one of the reference points for knowing whether a player can tolerate match volume. But never on its own: it has to come with the high-intensity metrics.

Outside those contexts, total distance is almost always a vanity metric. It looks good on a chart. It doesn’t help you decide anything.

See also: GPS in Football: Speed Zones and Distance to Optimise Training: how to set up the speed zones that actually count.

If your club has GPS vests, ask the sports scientist to hide total distance on the report for a month. Look only at high intensity, sprints, accelerations and sRPE. You’ll find some players you thought were lazy are the ones working hardest, and some of your marathon men spend the match jogging. Total distance doesn’t measure effort. It measures movement. Mixing the two up costs you wrong decisions every single week.

---

Measure what your player feels, not just how far he goes. Use the SportsLabTools Athlete Journal to log sRPE after every match and training session.

*This account is based on a real case, but the identities of the people and the club have been protected and some details of the setting have been recreated for illustrative purposes.*