Louis Dallimore ·Strength & Conditioning
Essay—Quade Cooper at 37: What Six Years of GPS ShowAnalytics

Quade Cooper at 37: What Six Years of GPS Show

Six seasons of Quade's match and training GPS, from age 31 to 37, next to the backs around him and next to himself.

I was Head of Performance at Kintetsu for all six of Quade's years at the club. That means I've got all his match and training GPS from 2019, when he was 31, through to 2025, when he was 37. You don't often get six straight years of data on one elite player in the same environment, and I wanted to see what it showed. Part of that is professional interest, and part of it is that I was there for all of it.

First, what this isn't. GPS doesn't tell you whether someone is good at rugby, or whether they're doing the things that win games. I wrote about that in GPS Is a Receipt, Not a Target. I can't tell you from this how well Quade played. What I can show you is his physical output and his work rate, and how they changed as he got older.

There isn't a lot to compare it with. I couldn't find a study in rugby union that follows a player's match running as he gets older. The closest I could find is in soccer, where a LaLiga study of 154 players over eight seasons (Rey et al., 2022) had total distance falling about 0.6% a year. Distance is where that study starts, so it's where I've started too, and then I've gone a level deeper each time.

The short version is that his running in games didn't drop off. At 37 he was level with backs about ten years younger on volume and ahead of them on accelerations. Two things did come down: his high-speed running and his top speed in games.

What was the team doing in 2019 and in 2025?

Before reading anything into Quade's numbers I wanted to know whether the game around him had changed. Over those six years Kintetsu moved between competitions, changed coaches and changed how we played, with more kicking in some seasons and more running and passing in others. All of that moves GPS numbers. Wherever I could, I compared Quade with the other backs who played at least an hour in the same game. They had the same pitch, the same weather and the same opposition. I used the 43 league and playoff games where he played at least 60 minutes, and I worked things out per minute on the field.

The other backs' match numbers hardly moved between 2019/20 and 2024/25. They ran 78.5 metres a minute at the start and 77.0 at the end, and they covered about 6 km both times. The games were asking about the same of the backs in 2025 as in 2019, which makes it a fair place to measure him from.

Figure 01 — The team and Quade, then and now
Games of 60+ minutes, season medians. Each panel has its own scale.
QuadeOther backs
Minutes in a game687980802019/202024/25Kilometres in a game5.375.915.895.982019/202024/25Metres per minute79.078.575.577.02019/202024/25
The other backs’ games barely moved over those six years, and by the end Quade’s minutes and distance had caught up with theirs. Their median age was about 27 at both ends.

Level one: how far was he running?

Distance and metres per minute are the first level of GPS. They're the numbers that get quoted after a game, and they're where I started.

In a typical one of those games he covered about 5.4 km at 31 and about 5.9 km at 37. At 31 he was about half a kilometre short of the other backs, because he was playing 68 minutes to their 79. By 37 he was playing the same 80 minutes as them and he was within about 90 metres of their distance.

Per minute it went about 79, 74, 79, 78 and then 75 metres. It moved around from season to season more than it headed anywhere, and the 75 in his last season is still higher than the 74 he ran at 32.

Figure 02 — Level one: every one of his 43 games
Metres per on-field minute, including stoppages.
Each of his gamesHis median, printed aboveOther backs, middle half of their games
60708090AchillesAug 20222019/20: other backs, middle half 75.6 to 81.02019/20: 75.5 m/min, 70 minutes2019/20: 77.9 m/min, 69 minutes2019/20: 78.9 m/min, 76 minutes2019/20: 79.2 m/min, 68 minutes2019/20: 79.2 m/min, 67 minutes2019/20: 82.8 m/min, 68 minutes79.02020/21: other backs, middle half 69.0 to 76.52020/21: 67.1 m/min, 80 minutes2020/21: 68.4 m/min, 80 minutes2020/21: 73.3 m/min, 68 minutes2020/21: 73.8 m/min, 61 minutes2020/21: 74.7 m/min, 69 minutes2020/21: 76.6 m/min, 62 minutes2020/21: 78.2 m/min, 79 minutes73.82021/22: other backs, middle half 71.0 to 81.02021/22: 71.8 m/min, 73 minutes2021/22: 73.1 m/min, 74 minutes2021/22: 77.9 m/min, 71 minutes2021/22: 78.5 m/min, 68 minutes2021/22: 80.3 m/min, 73 minutes2021/22: 80.8 m/min, 78 minutes2021/22: 81.7 m/min, 77 minutes78.52023/24: other backs, middle half 73.0 to 81.52023/24: 74.4 m/min, 85 minutes2023/24: 75.6 m/min, 80 minutes2023/24: 76.0 m/min, 65 minutes2023/24: 77.1 m/min, 83 minutes2023/24: 77.8 m/min, 61 minutes2023/24: 78.1 m/min, 70 minutes2023/24: 78.4 m/min, 80 minutes2023/24: 79.7 m/min, 83 minutes2023/24: 80.3 m/min, 75 minutes2023/24: 80.7 m/min, 76 minutes2023/24: 84.5 m/min, 61 minutes78.12024/25: other backs, middle half 73.6 to 80.52024/25: 68.9 m/min, 79 minutes2024/25: 69.2 m/min, 80 minutes2024/25: 70.8 m/min, 76 minutes2024/25: 72.7 m/min, 81 minutes2024/25: 74.3 m/min, 77 minutes2024/25: 75.5 m/min, 82 minutes2024/25: 77.2 m/min, 82 minutes2024/25: 77.4 m/min, 87 minutes2024/25: 77.5 m/min, 76 minutes2024/25: 79.8 m/min, 81 minutes2024/25: 81.0 m/min, 78 minutes75.52022/23: other backs, middle half 73.0 to 74.52022/23: 74.7 m/min, 65 minutes74.72019/20age 312020/21age 32–332021/22age 33–342022/231 game, age 352023/24age 35–362024/25age 36–37
He sits inside the other backs’ range in every season, and the Achilles doesn’t show up in it. 2022/23 is one game, the playoff on 13 May 2023, nine months after the rupture.

His median minutes in those games went 68, 69, 73, 76 and then 80. At 31 about one league game in six went past 75 minutes, and in his last season two in three did. That's a coach's decision and it depends on the scoreline, which is why I wouldn't use it as a fitness number. But a coach has to be happy to leave a 37-year-old out there.

The trouble with level one is that it averages everything together. A number like 75 metres a minute includes all the time standing around at scrums, lineouts and kicks at goal. It also says nothing about how often he had to stop and start. So I went down two more levels.

Level two: what happens when the ball is in play?

The second level is his running while the ball was in play, which was about 30 to 40 minutes of his game. We tagged the video for when the ball was live, and I lined those tags up with the GPS.

With the ball in play he ran about 119 metres a minute in 2023/24 and about 109 in 2024/25. The other backs ran about 111 and 107. Across all five seasons, his running with the ball in play stays within a few percent of theirs.

Figure 03 — Level two: while the ball was in play
Top: Quade’s median against the other backs, last two seasons. Bottom: all 43 games, running per minute as Quade ÷ the other backs.
Metres per min, 2023/24
119
other backs 111
Metres per min, 2024/25
109
other backs 107
Accels + decels per min, 2023/24
3.9
other backs 3.1
Accels + decels per min, 2024/25
3.3
other backs 2.7
1.01.20.8AchillesAug 20222019/20: 1.02 times the other backs1.022020/21: 0.98 times the other backs0.982021/22: 1.00 times the other backs1.002022/23: 1.01 times the other backs1.012023/24: 1.03 times the other backs1.032024/25: 0.98 times the other backs0.982019/20age 312020/21age 32–332021/22age 33–342022/231 game, age 352023/24age 35–362024/25age 36–37
Ball in play comes from our video tags, lined up with the GPS, and from the squad’s own GPS, so the bottom chart is only read against the other backs. 2022/23 is the 13 May 2023 playoff on its own. Accelerations and decelerations here have no half-second minimum, so they read higher than Figure 04.

The number that did come down in his last season is his high-speed running with the ball in play, to about 70% of the other backs'. It had been low once before, in 2020/21, and he came back from that. 2020/21 was one of our best seasons. We had some outstanding coaches, we won our pool and we made the final. I think the lower number that year says more about other people doing their jobs and a clear way of playing than about his legs. A fly-half who kicks and directs more gets fewer long chases, and I'd want to see the video from his last season before I put that one down to age.

Level three: how often did he accelerate?

The third level is accelerations. For a fly-half that's a lot of the job: getting up into the line, stepping, stopping to pass and chasing back.

Counting hard accelerations and hard decelerations together, per minute on the field, he was above the other backs in every one of the five seasons. It holds with the ball in play as well. In 2023/24 he made about 3.9 a minute to their 3.1, and in 2024/25 about 3.3 to their 2.7.

Per minute has a weakness, though. Time at scrums, lineouts or standing in a defensive line counts against you even though you can't accelerate in it, so a stop-start game eats into the number. I find ADI, the acceleration density index, more relevant to the effort in his running. It's acceleration load per 10 metres covered, so time drops out. On ADI he was level with the other backs at 31 and above them in three of the next four seasons, by 7% and then 4% in his last two. In his last season he was above them in 9 of his 11 games.

Figure 04 — Level three: accelerations against the other backs
The same 43 games. Quade ÷ the other backs that day. Efforts are 2.5 m/s² or more for half a second.
Hard accelerations and decelerations per minuteADI, acceleration load per 10 m
0.91.11.21.31.4AchillesAug 20221.02019/20: accelerations and decelerations per minute, 1.04 times the other backs1.042019/20: ADI, 0.99 times the other backs0.992020/21: accelerations and decelerations per minute, 1.05 times the other backs1.052020/21: ADI, 1.04 times the other backs1.042021/22: accelerations and decelerations per minute, 1.13 times the other backs1.132021/22: ADI, 1.00 times the other backs1.002023/24: accelerations and decelerations per minute, 1.27 times the other backs1.272023/24: ADI, 1.07 times the other backs1.072024/25: accelerations and decelerations per minute, 1.06 times the other backs1.062024/25: ADI, 1.04 times the other backs1.042022/23: accelerations and decelerations per minute, 1.14 times the other backs1.142022/23: ADI, 1.02 times the other backs1.021.0 means the same as the other backs2019/20age 312020/21age 32–332021/22age 33–342022/231 game, age 352023/24age 35–362024/25age 36–37
He’s above the other backs on hard efforts in every season. On ADI he’s level with them at 31 and above them in his last two seasons, in 9 of 11 games last season. 2022/23 is the 13 May 2023 playoff on its own.

The one that surprised me was what happened after the Achilles. His hard accelerations and decelerations went from 1.07 a minute before the injury to 1.22 after it, while the other backs stayed about where they were. 2023/24 was a hard season. We were in the top division and won one game out of 18, and when you're losing, key players try to do more and cover more ground. So I'm not saying higher numbers mean better rugby. But it shows the capacity was there at 35, after a serious injury, and he was doing more of it than the players around him.

Then I split out the backs under 28. On metres per minute he was ahead of them in two seasons, and in the other three he was never more than 1.6 metres a minute behind. On hard accelerations and decelerations he was ahead of them in four seasons and level in the other. On ADI he was ahead in four of the five, including his last.

Figure 05 — Quade and the backs under 28
The 42 games of his five full seasons. Numbers are Quade / backs under 28.
QuadeBacks under 28
2019/202020/212021/222023/242024/25Metres per minute70.075.080.02019/20: backs under 28 79.92019/20: Quade 79.079.0 / 79.92020/21: backs under 28 74.22020/21: Quade 73.873.8 / 74.22021/22: backs under 28 73.62021/22: Quade 78.578.5 / 73.62023/24: backs under 28 76.72023/24: Quade 78.178.1 / 76.72024/25: backs under 28 77.02024/25: Quade 75.575.5 / 77.0Hard accels + decels per minute0.400.801.202019/20: backs under 28 0.432019/20: Quade 0.480.48 / 0.432020/21: backs under 28 1.042020/21: Quade 1.031.03 / 1.042021/22: backs under 28 0.982021/22: Quade 1.071.07 / 0.982023/24: backs under 28 0.952023/24: Quade 1.221.22 / 0.952024/25: backs under 28 0.932024/25: Quade 1.011.01 / 0.93
Acceleration counts only compare within a season, because the equipment changed after 2019/20.

What happened after the Achilles?

He ruptured it in Argentina in August 2022. The season before the injury he ran 78.5 metres a minute in games, and in 2023/24, his first full season back, he ran 78.1.

I ran the Japan end of his rehab, which makes this the part of the data I know best. He did the first seven months in Australia and came back to us in March 2023. The whole rehab was built around getting him ready for our two playoff games in May.

The strength came first. In February his operated leg managed 18 single-leg calf raises to a metronome, and by April it was 31. His calf strength on the force plates came up to within about 10% of the other leg.

The first proper running on GPS is 8 March, seven months after the rupture, with a top speed of 6.5 m/s (23.4 km/h). His acceleration came back quicker than his speed. On 13 March, when his top speed in a session was still about 6.1 m/s (22 km/h), his best acceleration was already 4.1 m/s², close to his harder sessions before the injury. The plan had him at 90% of his top speed by mid-April and 95% by the first week of May. On 3 May, nine months after the rupture and at 35, he hit 8.86 m/s (31.9 km/h) in training. That's about 98% of the fastest he'd run for us. He was at 8.8 m/s (31.7 km/h) or above on three different days that month.

The volume came up with it. In the week of 13 March he did about 430 metres of high-speed running, and six weeks later he did about 2,100, when the plan said 1,400. He was ahead of the plan every week in April. We pulled it back in the game weeks on purpose.

On 22 April he played one minute to qualify for the playoffs. On 7 May he played 37 minutes in the first game against D-Rocks, and on 13 May he played about an hour in the second. That day he ran level with the other backs, with the ball in play as well as across the game. He was above them on hard accelerations and decelerations, and he hit 8.27 m/s (29.8 km/h). He played well, and we won them both.

Figure 06 — The way back, in strength, speed and volume
Top: testing on the operated leg. Below: GPS, March to May 2023, on the same clock. Rupture August 2022.
Single-leg calf raises, operated leg
18 to 31
February to April. Other leg 34
Seated calf strength, operated leg
994 to 1,358 N
February to April. Other leg 1,469 N
Standing calf strength, operated leg
2,111 to 2,340 N
February to April. Other leg 2,650 N
Top speed in a sessionFastest so farTrainingGame dayWeekly plan
Top speed in each training session, m/s56789High-speed running each week, metres01,0002,000MarchAprilMay2023-03-08: 6.48 m/s (23.3 km/h)2023-03-13: 6.12 m/s (22.0 km/h)2023-03-16: 6.04 m/s (21.7 km/h)2023-03-20: 6.81 m/s (24.5 km/h)2023-03-23: 6.23 m/s (22.4 km/h)2023-03-27: 7.11 m/s (25.6 km/h)2023-03-30: 7.17 m/s (25.8 km/h)2023-04-01: 7.38 m/s (26.6 km/h)2023-04-04: 7.83 m/s (28.2 km/h)2023-04-06: 7.72 m/s (27.8 km/h)2023-04-10: 7.79 m/s (28.0 km/h)2023-04-12: 6.69 m/s (24.1 km/h)2023-04-13: 7.66 m/s (27.6 km/h)2023-04-17: 4.57 m/s (16.5 km/h)2023-04-18: 7.89 m/s (28.4 km/h)2023-04-20: 6.73 m/s (24.2 km/h)2023-04-25: 5.83 m/s (21.0 km/h)2023-04-26: 7.63 m/s (27.5 km/h)2023-04-28: 6.80 m/s (24.5 km/h)2023-04-28: 8.27 m/s (29.8 km/h)2023-05-02: 7.37 m/s (26.5 km/h)2023-05-03: 8.86 m/s (31.9 km/h)2023-05-05: 8.80 m/s (31.7 km/h)2023-05-09: 8.13 m/s (29.3 km/h)2023-05-11: 8.85 m/s (31.9 km/h)2023-05-16: 7.63 m/s (27.5 km/h)2023-05-18: 7.44 m/s (26.8 km/h)3 May, 8.86 m/s(31.9 km/h)Week of 6 Mar: 486 mWeek of 13 Mar: 430 m430Week of 20 Mar: 553 mWeek of 27 Mar: 721 mWeek of 3 Apr: 916 mWeek of 3 Apr: plan 700 mWeek of 10 Apr: 1,791 mWeek of 10 Apr: plan 1,000 mWeek of 17 Apr: 1,755 mWeek of 17 Apr: 1,755 m, 609 m of it on game dayWeek of 17 Apr: plan 1,200 mWeek of 24 Apr: 2,129 mWeek of 24 Apr: plan 1,400 m2,129Week of 1 May: 1,097 mWeek of 1 May: 1,097 m, 271 m of it on game dayWeek of 1 May: plan 1,500 mWeek of 8 May: 1,161 mWeek of 8 May: 1,161 m, 664 m of it on game dayWeek of 8 May: plan 1,500 mWeek of 15 May: 1,150 m
Game day includes the warm-up, and on 22 April we added extra 50 m efforts around it. One session in March wasn’t recorded. The plan was set from early April.

How hard was he training?

You can't get this from a game, and it's the part of his GPS I most wanted to see. I went through every training session on file, 526 in all. The hard rugby drills are things like transition, game flow, attack against defence and small-sided games. In those he ran 2% more per minute than the other backs at 31, and 2% less at 37. On ADI he was within 2% of them in every season. Those were the same drills on the same clock, and by the end the backs around him were about ten years younger.

I also counted the sessions where his best five minutes reached his best five minutes in a typical game that season. In his last season there were 31 of them, about one a week: 14 across 11 weeks of pre-season and 17 across 19 weeks of the season. The season before, there were 18.

That season we also tagged 30 sessions of 15v15 at game intensity, 288 short reps in all. He ran 129 metres a minute in them, against 109 with the ball in play in his games, and he was at or above that game number in 26 of the 30 sessions. The other backs in the same reps ran 125.

One session shows what that looked like. I've picked one of his hardest from his last season rather than a typical one. On Christmas Eve 2024, when he was 36, he did 104 minutes on the field: units, a skills rotation and then a 15v15 at game intensity, played as three blocks of short reps, most of them one to two minutes long. He covered 6.4 km, more than in a typical game that season. He played the first and third blocks. Inside the reps he ran 138 metres a minute in the first block and 130 in the third, and in his games that season he ran about 109 with the ball in play. His high-speed running in the reps was 18 and 23 metres a minute, against 17 in play in a game, and he hit 8.10 m/s (29.2 km/h).

Figure 07 — One of his hardest sessions: Christmas Eve 2024
Age 36, in his last season. Metres covered in each minute. Picked as one of his hardest, not as a typical day.
Distance
6.4 km
typical game 5.9
High-speed running
657 m
typical game 590
15v15 reps, blocks 1 and 3
138 / 130
m/min; in play in a game 109
Top speed
8.10 m/s
29.2 km/h; best game that season 7.93 m/s (28.5 km/h)
050100150200UnitsSkills rotation15v15, block 1Block 2Block 315v15 rep, 91 s: 125 m/min15v15 rep, 71 s: 131 m/min15v15 rep, 100 s: 148 m/min15v15 rep, 60 s: 179 m/min15v15 rep, 77 s: 140 m/min15v15 rep, 76 s: 135 m/min15v15 rep, 62 s: 110 m/min15v15 rep, 69 s: 76 m/min15v15 rep, 82 s: 3 m/min15v15 rep, 122 s: 0 m/min15v15 rep, 50 s: 5 m/min15v15 rep, 32 s: 3 m/min15v15 rep, 64 s: 1 m/min15v15 rep, 118 s: 109 m/min15v15 rep, 39 s: 110 m/min15v15 rep, 70 s: 122 m/min15v15 rep, 116 s: 135 m/min15v15 rep, 28 s: 152 m/min15v15 rep, 81 s: 162 m/min15v15 rep, 149 s: 129 m/minMinute 0: 35 mMinute 1: 8 mMinute 2: 23 mMinute 3: 82 mMinute 4: 84 mMinute 5: 35 mMinute 6: 17 mMinute 7: 30 mMinute 8: 46 mMinute 9: 30 mMinute 10: 34 mMinute 11: 70 mMinute 12: 77 mMinute 13: 20 mMinute 14: 47 mMinute 15: 47 mMinute 16: 48 mMinute 17: 33 mMinute 18: 47 mMinute 19: 39 mMinute 20: 29 mMinute 21: 22 mMinute 22: 40 mMinute 23: 35 mMinute 24: 11 mMinute 25: 38 mMinute 26: 25 mMinute 27: 64 mMinute 28: 75 mMinute 29: 58 mMinute 30: 64 mMinute 31: 49 mMinute 32: 44 mMinute 33: 53 mMinute 34: 30 mMinute 35: 16 mMinute 36: 35 mMinute 37: 84 mMinute 38: 110 mMinute 39: 43 mMinute 40: 126 mMinute 41: 16 mMinute 42: 89 mMinute 43: 117 mMinute 44: 67 mMinute 45: 84 mMinute 46: 77 mMinute 47: 68 mMinute 48: 104 mMinute 49: 112 mMinute 50: 117 mMinute 51: 30 mMinute 52: 39 mMinute 53: 18 mMinute 54: 24 mMinute 55: 16 mMinute 56: 14 mMinute 57: 76 mMinute 58: 60 mMinute 59: 67 mMinute 60: 52 mMinute 61: 51 mMinute 62: 25 mMinute 63: 3 mMinute 64: 55 mMinute 65: 140 mMinute 66: 77 mMinute 67: 131 mMinute 68: 122 mMinute 69: 114 mMinute 70: 86 mMinute 71: 172 mMinute 72: 114 mMinute 73: 105 mMinute 74: 107 mMinute 75: 88 mMinute 76: 100 mMinute 77: 66 mMinute 78: 16 mMinute 79: 99 mMinute 80: 23 mMinute 81: 9 mMinute 82: 9 mMinute 83: 0 mMinute 84: 16 mMinute 85: 34 mMinute 86: 6 mMinute 87: 1 mMinute 88: 1 mMinute 89: 3 mMinute 90: 42 mMinute 91: 75 mMinute 92: 109 mMinute 93: 86 mMinute 94: 68 mMinute 95: 131 mMinute 96: 47 mMinute 97: 134 mMinute 98: 122 mMinute 99: 67 mMinute 100: 133 mMinute 101: 138 mMinute 102: 101 mMinute 103: 148 mMinute 104: 83 mHis game average, 75His best minute in a typical game, 172020406080100minutes into the session
The marks above the bars are the 15v15 reps, timed from the session’s Catapult tags and lined up with the GPS. Black bars are the blocks he played. He sat out block 2 after its first rep, so its other reps are grey. Each bar is a clock minute, so the rests between reps are in them. The game numbers are his own medians from that season’s games of 60+ minutes, and “in play” is from our video tags.

What was his top speed?

The game against Kubota in February 2024 is the one I enjoyed. He was 35, about 18 months on from the Achilles, and he hit 8.85 m/s (31.9 km/h). That's level with his best league speed from the whole period, 8.84 m/s (31.8 km/h) when he was 32. I can't call it the fastest he ever ran, because he touched 9.15 m/s (32.9 km/h) very briefly in a pre-season game in December 2021.

His last season is the one that looks low if you only read the match numbers. His best in a game was 7.93 m/s (28.5 km/h) and he never got above 8 m/s (28.8 km/h). But a match only shows you what the game asked of him. A fly-half can go a whole game without a clean 40 metres to run into, and that's a different thing from not being able to get there.

In training that season he got above 8 m/s (28.8 km/h) in six sessions, and not only in straight-line running, because they included units and that 15v15. His best was 8.25 m/s (29.7 km/h) when he was 36, and he hit 8.19 m/s (29.5 km/h) a couple of weeks after turning 37. It's lower than the 8.85 m/s (31.9 km/h) from the season before. But at 31 the fastest I have him is 8.68 m/s (31.2 km/h), and across the six years that's a drop of 0.43 m/s (1.5 km/h). A training number isn't a proper speed test either. The 8.25 m/s (29.7 km/h) tells you he could at least do that, not that it was his limit.

Figure 08 — His fastest each season, in games and in training
The 43 games, plus every training session on file. Metres per second, with the faster of the two in km/h.
Best league or playoff gameBest in training
7.68.08.59.0fastest2019/202019/20: best game 8.688.682019/20: best in training 8.318.3131.2 km/h2020/212020/21: best game 8.848.842020/21: best in training 9.029.0232.5 km/h2021/222021/22: best game 8.528.522021/22: best in training 8.808.8031.7 km/h2022/232022/23: best game 8.278.272022/23: best in training 8.868.8631.9 km/h2023/242023/24: best game 8.858.852023/24: best in training 8.728.7231.9 km/h2024/252024/25: best game 7.937.932024/25: best in training 8.258.2529.7 km/h
His 9.15 m/s (32.9 km/h) isn’t here because it was in a pre-season game. The 2022/23 game is the second playoff on 13 May.

So did he decline?

Not in the way you'd expect from a 37-year-old. On level one he finished within 100 metres of backs about ten years younger, and he was covering more than he did at 31 because he was playing the whole game. With the ball in play he kept pace with them. On accelerations, by the minute or by the metre, he was above them, and on ADI he was above them in both of his last two seasons. What came down was his high-speed running and his top speed in games, and even then he was still getting above 8 m/s (28.8 km/h) in training at 37.

This is one player across different competitions, coaches and game plans, and he's only in the data because he kept getting picked. My own view, and it's a view rather than a finding, is that the way he kept training is a big part of why he could still do this at 37. I watched him do it, and I don't think you stay level with backs ten years younger without it.

I should say that Quade and I built an app together called PRE SZN, and I'm not a neutral party here. His program, PRE SZN Elite, is in it if you want to see how he trains. The data here stops in May 2025 and the app came later, and nothing here shows what it would do for you.

If I were looking at an older player, I'd check which part of his running has actually changed before assuming all of it has. I'd look at his training before reading too much into a match top speed. And I wouldn't stop at level one.

All of this is Catapult 10 Hz GPS from October 2019 to May 2025: 43 league and playoff games where he played 60 minutes or more, and 526 training sessions. Every comparison is with the other backs who played an hour or more in the same game, or were in the same drill in training.

New essays in your inbox.

Programming, GPS, return-to-play, applied ML. No spam, unsubscribe anytime.