How to play
- Press StartThe timer starts running from 0.00.
- Catch the paceWhile the numbers show, watch how fast one second goes by. A tap in these 3 seconds does not count, and that try starts over.
- Count and tapWhen the numbers vanish, keep counting and tap anywhere on the panel at what feels like 10 seconds. On a keyboard, Space or Enter works too.
- Do it three timesEach tap shows your real time and how early or late you were. Your score is the average miss across the three tries.
Why 10 seconds is hard to count
You have no clock inside you. For spans of a few seconds, the brain makes a running estimate, and the longer the span, the bigger the error. Most people can hit one second quite closely, but at ten seconds a miss of a few hundred milliseconds is normal. Timing researchers describe this as error that grows in step with the length of the interval.
How you count matters a lot. In a 2015 study by Bartholomew and colleagues, 647 people held down a key for set times between 1 and 15 seconds, with no feedback. When they were allowed to count, their 12 seconds came out about 15% short on average. When they were told not to count, it came out 36% short, so 12 seconds ended before 8 had passed. Without feedback, most people stop too early.
That is why this challenge shows the first 3 seconds. Matching your count to the real pace before the numbers go away gets you far closer than counting cold. After that, the game is about holding that beat all the way to ten.
What counts as a good score
The grade on your result follows the table below. Your score is the average miss across three tries. It is stored in milliseconds, so both units are shown. The top three lines come from human reaction time and counting rhythm. The bottom two come from timing research.
| Average miss | Grade | Why the line is here |
|---|---|---|
| Under 0.1 s (100 ms) | Superhuman | This is the false-start line in sprinting. Your miss was smaller than the fastest reaction a human can make to a signal. |
| 0.1 to 0.25 s (up to 250 ms) | Pro tier | You missed by less than one ordinary reaction to a signal. |
| 0.25 to 0.5 s (up to 500 ms) | Skilled | Within half a beat when counting one per second. You never lost the count. |
| 0.5 to 1 s (up to 1000 ms) | Standard | Timing over a few seconds usually wobbles by about 10%, and 10% of ten seconds is one second. |
| 1 to 1.5 s (up to 1500 ms) | Warming up | In the study above, people who counted without feedback ended 12 seconds about 15% short. |
| 1.5 s or more | Needs practice | A bigger miss than that. Losing your place in the count is the quickest way here. |
These lines are a first estimate. No public norms exist for this exact format, with 3 seconds of preview and an average of three tries. Once enough scores build up on this site, the lines will be checked against real results.
Real scores recorded on this site
So far, - runs of this test have been recorded here. Computers and phones score quite differently, so each gets its own table.
Computer (mouse)
| Range | Share |
|---|---|
| Under 0.1 s (100 ms) · Superhuman | |
| 0.1 to 0.25 s (up to 250 ms) · Pro tier | |
| 0.25 to 0.5 s (up to 500 ms) · Skilled | |
| 0.5 to 1 s (up to 1000 ms) · Standard | |
| 1 to 1.5 s (up to 1500 ms) · Warming up | |
| 1.5 s or more · Needs practice |
Phone (touch)
| Range | Share |
|---|---|
| Under 0.1 s (100 ms) · Superhuman | |
| 0.1 to 0.25 s (up to 250 ms) · Pro tier | |
| 0.25 to 0.5 s (up to 500 ms) · Skilled | |
| 0.5 to 1 s (up to 1000 ms) · Standard | |
| 1 to 1.5 s (up to 1500 ms) · Warming up | |
| 1.5 s or more · Needs practice |
Every finished run counts, so someone who plays five times adds five runs. The numbers are recounted every day, and a device table shows up once it passes 30 runs. Last updated: -.
What this test measures
It measures time sense: how well you can judge passing time without looking at a clock. You hold on to the pace you caught in the first 3 seconds and keep it steady to the end. Attention plays a part too. If another thought slips in while you count, it is easy to skip a number or say one twice.
The result shows your three real times and your closest try. If all three were a little early, your beat runs fast. If they were scattered, your pace drifted while you counted. Knowing which one it was tells you what to fix next round.
How to get closer
Set the beat in the first 3 seconds
While the numbers show, say "one, two" in your head right as 1.00 and 2.00 tick over. Once they vanish, all you have to do is keep that pace.
Count "one Mississippi"
A plain "one, two" is short, and it speeds up without you noticing. Adding syllables to each beat, as in "one Mississippi, two Mississippi", keeps each count close to a full second.
Tap as "ten" begins
If you finish saying "ten" and then tap, you are late by the time your hand takes to move. Tapping as the word starts lands closer to 10.00.
Count the same way each try
Switching methods between tries makes your average jump around. Use one method for the whole round, look at the result, then adjust next time.
Frequently asked questions
What happens if I tap while the numbers are showing?
That try does not count, and you take it again. Tapping while you watch the numbers tests reaction speed, not time sense, so it stays out of your score.
Why an average of three instead of one try?
One try is mostly luck. A careless tap can land on 9.99, and a careful count can end with a slow hand. Averaging three tries gives a number closer to real skill.
Why does switching tabs cancel a try?
Browsers slow down timers in hidden tabs, so the time cannot be measured fairly. That try is cancelled, and tapping the panel starts it again.