The GPS paradox
- Andri Freyr
- Apr 11
- 5 min read
Updated: Apr 12
A team that runs 12km per player and loses may have worked harder than the team that ran 10km and won. That gap is where things get interesting.
Picture two games. In the first, your team controls possession from the start. Quick decisions, intelligent movement, the opposition chasing shadows. You win comfortably. The GPS numbers are modest. In the second game you win again — but this time the numbers are significantly higher. Your players ran more because they gave the ball away more. They reacted instead of dictated. The performance was worse. The data looked better. That is the paradox.
This is the paradox at the heart of GPS data. High numbers feel like evidence of effort and hard work. Clubs look at post-match reports and see big distance, high sprint counts, elevated intensity zones and they read it as a good sign. But the number on its own tells you almost nothing. It tells you what happened. It does not tell you whether it was good or bad.
"The number doesn't lie. But it doesn't tell the whole truth either."
To understand GPS data properly, you need to read it through four categories. Because the same number means something completely different depending on how it was produced. Here is how to think about it.
Good performance, high numbers
Sometimes running hard is exactly the plan. A team built around high pressing, physical dominance and relentless intensity can absolutely use that as a winning tactic. When the game model demands it, high GPS numbers are not a warning sign — they are confirmation that the plan is working. The players are executing. The physical output is the point. This is good performance, and the data reflects it.
Good performance, low numbers
A team that dominates possession barely needs to run. When a team makes good decisions on the ball — quick passes, intelligent movement, positional discipline — the opposition has to do all the running. The ball moves the opponent, not the legs. Every good decision with the ball saves energy across the whole squad. Low GPS numbers in this context are not a sign of low effort. They are a sign of intelligence. The team that controlled possession may have run the least.
Bad performance, high numbers
When a team loses the ball repeatedly, every player has to react. Track back, close down, recover shape. That is reactive running. It is physically expensive and it is a direct consequence of poor decisions. When we look at high distance numbers and read them as effort and commitment may be looking at a team that gave the ball away all game. Every poor decision with the ball costs the whole team physically. The numbers are high. But the players at least tried. That is problaby a technical and tactical problem not a character problem or physical problem.
Bad performance, low numbers
When a team is being dominated — when the opponent controls the ball, dictates the tempo and pins them back — the only way back into the game is to run. You have to get on the right side of the ball first. Make contact. Win it back. Transition quickly. In those moments, physical capacity is not just useful. It is the only tool available. A team that is being outplayed and refuses to sprint harder is not being smart. Being passive under pressure is not efficiency. It is mental surrender or physical exhaustion. Low numbers in this context are the most damning reading of all.
The perfect recipe for high numbers
If you want to know what produces the highest GPS numbers, here is the formula. Take physically capable players that have been built properly over time. Add mental toughness and a genuine willingness to run for the team. Then add poor decisions on the ball that force constant transitions and reactive running. That combination produces the highest numbers you will ever see. And it tells you almost nothing useful. At the end of the day you do not want your team to be running on full gas. You want them to be capable of it — and smart enough not to need it. If your main goal is high numbers then have poor decisions part of your plan.
You can perform well and lose. You can perform badly and win. The tactics could be to run over the opposition The tactics could be to let the opposition run. Without context GPS is useless.
This is why result alone is never enough context for GPS data. A team can produce a good performance and still lose. Another team can produce a bad performance and win. The data tells you how much work the players did, not the outcome of the game. Once you understand that, you stop reading the scoreboard and start reading the performance. And that is where the real evaluation begins.
The paradox is we know being physically capable matters, alot. But we also know that the team that struggle they often run more then the teams that dominate. At the end of the day to goal is not to run, its to win a football match. So it all comes down to what is your style og play and what is the tactical plan?
Football first, numbers second.
So three questions worth sitting with.
How do you know which of the four categories your team was in last week?
How do you use that reading to make better decisions in training?
How do you use GPS daga to analyze your game performance?
And if your GPS numbers are high: are you proud of the reason, or uncomfortable with it?
Key takeaways
What this post is really saying
GPS numbers tell you what happened physically. They do not tell you why. The why is everything.
High distance plus good performance means the physical plan worked. Pressing and dominance are legitimate tactics.
Low distance plus good performance means the ball did the work.
The worst reading of all is low distance plus bad performance. The team was dominated, ran less than the opponent, and didn't fight to get back in. That is a physical exhaustion or a mental surrender. Or worst case, both.
High distance plus bad performance at least means the players tried. The decisions were poor but the effort was there. That is a technical and tactical problem, not a character or physical problem.
GPS data evaluates what happened on the pitch but it is up to you to evaluate if it is positive or negative.
