How to Use a Cube Timer: Timing on Your Phone or PC and Practicing to Improve Your Times
Once you can solve a Rubik’s Cube, the next question is how fast you can do it. Timing your solves and keeping records makes your progress visible in numbers and makes it clear what to practice. This article covers how to time solves with a cube timer that runs in your phone or computer browser, how to read your ao5 and ao12, benchmarks and practice tips by level from sub-60 to sub-20, and how accurate a browser timer is and how to keep your records.
Why a cube timer helps you improve faster
You can time solves with your phone’s stopwatch, but a speedcubing timer has features that are essential for practice: it gives you a scramble every time, lets you start and stop without taking both hands off the cube, and calculates averages like ao5 and ao12 for you.
- Scrambles: a random scramble every time, so you don’t end up practicing the same scramble over and over
- Hold and release to start: getting set and lifting your hands mirrors the stackmat used at competitions
- Automatic averages: instead of riding the ups and downs of each solve, you can track real changes in skill through ao5 and ao12
- Building a history: from dozens or hundreds of timed solves, you can see how your best and average change over time
The Rubik’s Cube Timer works just by opening it in a browser, with no app to install. You can switch between 2×2, 3×3, 4×4 and 3×3 one-handed, and records are kept separately for each puzzle.
How to time a solve: space bar on a PC, tap on a phone
There are three steps: “hold and wait → release when it turns green to start → press when solved to stop”. The flow is the same on a computer or a phone.
- 1
Scramble as shown
Hold the cube with white on top and green in front, and turn it following the notation shown. Compare it with the net displayed for the scrambled state to check you scrambled it correctly. How to read the notation is explained in Rubik’s Cube notation.
- 2
Start inspection
If inspection is on, the space bar (on a phone, tapping the timer area) starts a 15-second countdown. Use this time to look over the cube.
- 3
Hold and wait for green
Keep holding the space bar or the screen, and after a moment the numbers turn green. You can set the hold time to 0.3 seconds, 0.55 seconds or none; it prevents accidental starts.
- 4
Release to start, press to stop
Timing starts the instant you lift your fingers. When solved, press any key (on a phone, anywhere on the screen) to stop; the result is recorded and the next scramble appears automatically.
On a phone, the whole screen becomes the timer while timing and doesn’t scroll, so you won’t miss the stop even if your finger slips. Lay the phone sideways in front of the cube and rest your fingertips on the screen with both hands, and it feels close to a stackmat. If watching the numbers makes you hesitate, try turning on “Hide time while timing” in the settings.
Reading your stats: should you aim at your best, ao5 or ao12?
As you keep timing, you’ll see your best, worst and mean, plus the current value and best of mo3, ao5, ao12, ao50 and ao100. What each one tells you is different.
| Stat | What it shows | When to use it |
|---|---|---|
| Best (single) | Your fastest solve ever | Celebrating a new PB. Heavily affected by luck |
| ao5 | Average of 5 with the best and worst removed | The same format as competition rankings. Shows the result of short focused practice |
| ao12 | Average of 12 with the best and worst removed | Just right for checking the day’s form and your level |
| ao50, ao100 | Long-term averages with the top and bottom 5% removed | Confirming you really get that time consistently |
| Mean | Simple average of all results, excluding DNFs | The trend across the whole session |
The standard approach is to set goals by average, like “sub-X ao12”. A best single can happen by chance, but ao12 and ao100 turn your everyday level directly into a number. How averages are calculated and how DNFs are handled is explained in detail in how to calculate ao5 and ao12.
Time benchmarks and practice tips by level
3×3 average times fall roughly into the following stages depending on your method and how much you practice. “Sub-X” means “under X seconds”. These are only rough guides, but they help you see where you are and what to do next.
| Average time | Typical stage | What to work on next |
|---|---|---|
| Over 1 minute | Just learned the layer-by-layer method (LBL) | Do lots of solves until you can finish without looking at the algorithms. Build the white cross the same way every time |
| Sub-60 | LBL feels natural | Cut down the second-layer moves and switch the last layer to “2-look OLL and 2-look PLL (4LLL)” |
| Sub-30 | The start of CFOP, using 4LLL | Learn F2L (inserting corner–edge pairs into the first two layers together) by understanding it rather than memorizing cases |
| Sub-20 | Can build F2L pairs on your own | Find the next pair without stopping (lookahead). Learn more OLL and PLL algorithms |
| Sub-15 | Know full PLL and most of OLL | Plan the cross and the first pair during inspection. Review your finger tricks |
From around sub-30, cutting down the time you spend stopped helps more than moving your hands faster. Practicing spotting the next F2L pair while inserting the current one sinks in when you focus on never stopping, even if you turn slowly. Deliberately doing ao12s at a slow tempo while timing is also effective.
How accurate a browser timer is, and how to keep your records
A browser timer measures the difference between the moment you release a key and the moment you press it, so screen rendering delays don’t affect the result. It does include the latency of the keyboard or touchscreen itself (a few to a few tens of milliseconds). That’s plenty accurate for practice records, but it won’t necessarily match a competition stackmat to the hundredth, so it can’t replace official results.
| Timing method | Best for | Things to watch |
|---|---|---|
| Space bar on a computer | Daily practice at home | How hard you hit the key can make stops inconsistent. Pressing with your palms is steadier |
| Tapping on a phone | Out and about, or where there’s no computer | Press the screen with your fingertips. Wet hands or gloves respond poorly |
| Stackmat (dedicated timer) | Practice under competition conditions | Times can be added to your records by typing them in |
Records are saved only inside your browser (localStorage) and are never sent to a server. Clearing your browser data deletes them too, so save the records you want to keep as CSV. CSV files open in spreadsheet software, so you can also chart your ao12 month by month.
FAQ
- Do I need an app to use a cube timer on my phone?
- No. The Rubik’s Cube Timer works just by opening it in a browser. Hold the timer area, release when the numbers turn green to start, and touch anywhere on the screen to stop.
- How do I start a cube timer?
- On a computer, hold the space bar; on a phone, hold the screen. When the numbers turn green, release to start. If inspection is on, pressing and releasing once starts the 15-second countdown, and then the same action starts the timer.
- What are typical Rubik’s Cube average times?
- Over a minute if you’ve just learned the layer-by-layer method, sub-60 once it feels natural, sub-30 at the start of CFOP, and sub-20 once you can build F2L on your own. It’s best to set goals by an average like ao12 rather than by a single.
- What should I practice to reach sub-20?
- The shortcut is learning to build F2L by understanding rather than memorized cases, and practicing lookahead so you find the next pair without stopping. Deliberately turn at a slow tempo without pausing, and check the effect with your ao12.
- Where are my records saved?
- Only in your browser’s localStorage; they’re never sent to a server. They’re kept separately for each puzzle. Clearing your browser data deletes them, so save them as CSV if you want to keep them.
- Can I also record times from a stackmat?
- Yes. Type a time like 14.52 into the input box in the times list and it’s added to your records and included in ao5 and ao12 calculations.
Tools in this article
Related articles
What Are ao5 and ao12? How to Calculate Them, the Difference, and What mo3 and ao100 Mean
Rubik’s Cube results are often written as "ao5 11.95" or "ao12 13.02". An ao5 is an average of five solves, but you don't just add them up and divide by five: you first drop the single fastest and single slowest solve. If you don't know this rule, your own averages won't match your timer, and you won't know what to do when a DNF turns up. This guide explains how to calculate ao5 and ao12 with worked examples, how they differ from mo3, ao50 and ao100, how DNF and +2 are handled, how times are rounded to hundredths, and how all this relates to official WCA results.
Read article →Rubik’s Cube Notation: How to Read R', R2 and Rw and Which Way to Turn
"R U R' U'", "F2 D' L2 Rw": Rubik’s Cube algorithms and scrambles are written in letters and symbols. Reading this notation is the starting point for following tutorial videos and guides, and for practising with the same scrambles used at competitions. This guide covers the letters for the six faces, what the prime (') and the 2 mean, the directions of L, D and B that people often get wrong, the Rw and 3Rw wide moves you meet on 4×4, the M, E and S slice moves and x, y and z rotations, and how to hold the cube and check that you applied a scramble correctly.
Read article →What Is Inspection? The 15-Second Rule and When You Get +2 or DNF
At Rubik’s Cube competitions you get 15 seconds to study the cube before you start solving: this is called inspection. Go even a moment past 15 seconds and you get +2; go past 17 seconds and the solve is a DNF (no result). However fast your solve, how you use inspection can wipe out the result. This guide covers how inspection works at WCA competitions, what the 8-second and 12-second calls mean, the common situations that lead to +2 and DNF, what to look at in those 15 seconds, and how to get used to competition conditions when practising at home.
Read article →