Ao5 and Ao12 Explained: How to Calculate Speedcubing Averages
If you only track your best single solve, your progress will look random. Averages are a better measurement because they reduce outliers and show your real performance trend.
Ao5 and Ao12 are the two most common average metrics in daily speedcubing practice.
What Ao5 and Ao12 mean
Ao5means āaverage of 5 solvesāAo12means āaverage of 12 solvesā
For both metrics, remove the fastest and slowest solve, then average the remaining times.
Formulas:
Ao5 = (middle 3 solves) / 3Ao12 = (middle 10 solves) / 10
This trimmed approach prevents one lucky solve or one major mistake from dominating your result.
When to use Ao5 vs Ao12
Use both, but for different purposes:
Ao5is better for short feedback loops during a single practice block.Ao12is better for judging whether your overall level is improving.
A practical routine:
- Use Ao5 during session work.
- Check Ao12 at the end of the day.
- Compare weekly Ao12 trends to evaluate improvement.
Calculation examples
Example Ao5 set:
18.42, 17.95, 19.11, 18.36, 17.80
- Remove fastest (
17.80) and slowest (19.11). - Average the middle 3:
18.42 + 17.95 + 18.36 = 54.73 54.73 / 3 = 18.24
Ao5 = 18.24
Example Ao12 works the same way: remove one fastest and one slowest, average the remaining ten solves.
How +2 and DNF affect averages
Penalty handling is critical.
+2: add two seconds to that solve before averaging.DNF: treated as the worst result in the set.
For average-of-N with one best and one worst removed:
- If there is one DNF, it is usually removed as the worst result.
- If there are two or more DNFs, the average becomes DNF.
Because of this, accurate penalty logging matters just as much as raw speed.
Use automatic averages in Speed Cube Timer
Manual calculations are good for understanding, but automation is better for daily consistency.
Speed Cube Timer calculates Ao5 and Ao12 automatically and applies penalties correctly, so you can focus on solving and review.