Read more than one fast solve

Best

Best is the fastest valid time stored in the active session. It answers a simple question: what is the quickest solve recorded here? A single best can be influenced by an unusually easy scramble or an especially clean execution, so read it together with averages.

Ao3

Rubik's Timer calculates Ao3 as the arithmetic mean of the latest three times: add the three times and divide by three. For 18.20, 19.10 and 17.70 seconds, the Ao3 is 18.33 seconds. This moves quickly and is useful for a short snapshot, but each solve has a large effect.

Ao5 and Ao12

For Ao5 and Ao12, the app sorts the most recent group, removes one fastest and one slowest time, and averages what remains. In an Ao5, three middle times determine the result. In an Ao12, ten middle times determine it. Trimming the extremes reduces the effect of one unusually good or bad solve.

Why the active session matters

Every displayed value belongs to the selected session. Keeping full solves in Default and technique-specific work in named sessions prevents one practice type from distorting another. A fast last-layer drill should not quietly become the personal best for full solves.

Reading the session trend

The chart plots solve history and available rolling averages so you can see direction, not just a final number. Use the seven-, thirty- and ninety-day filters to compare recent practice with a longer period. Sorting the table is useful for finding extremes; chronological order is better for seeing momentum and fatigue.

Questions the numbers can answer

• Is Ao12 improving even when Best stays unchanged?
• Does a named practice session transfer into Default-session progress?
• Are late-session solves consistently slower?
• Is a new personal best supported by a stronger Ao5?

Numbers do not explain the cause on their own. Combine them with a specific practice plan and notes outside the timer when needed.