Knowledge base

Help / Timing & solving

How timing works

Your smart cube has its own internal clock, and it stamps every turn with a timestamp. That’s good news — it means your solve time doesn’t depend on Bluetooth latency or a busy laptop. But cube clocks also drift relative to your computer’s clock, sometimes by enough to matter at speedcubing precision.

The linear fit

cubrs records both timestamps for every move of your solve: the cube’s, and your computer’s. When the solve ends, it fits a straight line between the two clocks across all of your moves and reads the solve duration off the fitted line. This is the same technique csTimer uses for smart cubes, and it’s the most accurate timing a Bluetooth cube can give.

Your displayed result says which source timed it: cube clock (linear fit) is the gold standard; local timestamps and host clock are fallbacks when the cube doesn’t stamp every move.

What the live clock shows

While you solve, the on-screen clock runs on your computer’s time — it’s a display. The recorded result is computed from the move timestamps at the end, which is why the final number can differ from the last thing you glimpsed mid-solve by a few hundredths.

Resolution

Times display in centiseconds (0.01s), and the math underneath runs in milliseconds.

This browser can’t reach your cube.

cūbrs talks to smart cubes over Web Bluetooth, which lives in Chrome, Edge, and Opera on desktop. Safari and Firefox don’t ship it, and iPhones and iPads can’t run it at all — that’s Apple’s call, not ours.

One email with the link, nothing else. Or open the app anyway if you know your browser supports Web Bluetooth.