Stopwatch Challenge
Stop the timer at exactly 10.000 seconds.
🎮 Our new game is coming
Town Guardians launches in 2026 — drop your email and be first to play.
More from Pong Studio →About the Stopwatch Challenge
Tap once to start a clock, then tap again to stop it as close to exactly 10.00 seconds as you can. One start, one stop — that's the whole run. Your score is how many milliseconds you were off, and lower is better. It runs entirely in your browser, no signup.
How it works
- Tap or press Space once to start the clock.
- While it runs, the exact elapsed time is shown on screen the whole way, updating every frame down to the millisecond — you are not guessing blind.
- Tap or press Space again to stop it. We take the absolute difference between your stopped time and 10.00 seconds, in milliseconds, and that is your score.
Press try again for a fresh run — each attempt stands alone, there is no average across tries here.
What this is actually testing
Because the clock is visible and counting the entire time you're running it, this is not a test of your internal sense of ten seconds with your eyes closed. You are watching a live number climb and trying to release at the instant it crosses 10.000. That makes it closer to the reaction-time test than it looks: your stop is a reaction to a visual target, plus whatever skill you have at anticipating your own reaction lag and releasing a hair before the number you're aiming for actually arrives.
That's also the one deliberate difference from our reaction-time test: there, the trigger arrives at a random moment specifically so you cannot anticipate it. Here, you can watch the whole ten seconds coming, so anticipation is not just possible — it's the entire skill. Reaction lag alone would push most stops slightly past 10.00; canceling that by releasing a little early is what a good score actually requires.
One honest rough edge, and it is worth knowing because it affects what you see. Land it exactly and the game does flash a "perfect" message — but that message sits in the same slot as your rating, and once your score reaches the leaderboard that slot gets overwritten with your live percentile instead. So a perfect stop can be quietly replaced by "Top 5%" a moment later. Underneath, your exact millisecond gap is still what gets ranked, and it is still zero. The badge just cannot hold both things at once. We are not going to pretend that is not a little embarrassing.
What counts as a good score
These are our own tiers, not a research benchmark: under 20 ms off is Elite, under 50 ms is Pro, under 100 ms is Sharp, under 200 ms is Average, and under 400 ms is Casual. We invented these labels for this game — they are not thresholds from any study, so read them as a game mechanic rather than a scientific rating.
Frequently asked questions
What is the stopwatch challenge?
A one-shot timing game: start a clock, then stop it as close to exactly 10.00 seconds as you can. Your score is how far off you were, in milliseconds — lower is better, and each run is a single attempt.
Can I see the timer while it's running?
Yes. The exact elapsed time is on screen the entire run, updating down to the millisecond. You are watching the number the whole way, not guessing at ten seconds with no feedback.
What is a good stopwatch score?
Under 20 ms off is our Elite tier, under 50 ms is Pro, under 100 ms is Sharp. These are labels we picked for this game, not a scientific standard.
Does a perfect 0 ms stop get tracked specially?
The result screen shows a "perfect" badge for an exact 0 ms stop — literally zero, not close enough. Miss by even a single millisecond and you get the Elite label instead, which covers everything under 20 ms off and is a tier we picked rather than a benchmark. The badge is only a badge, though: the exact millisecond figure is what gets recorded and ranked either way.
Why do I always seem to stop a little late?
Because you're reacting to a number you can already see approaching, plain reaction lag tends to carry your stop past 10.000 rather than short of it, unless you deliberately release a fraction early to cancel that lag out.
Does practice help?
Plausibly, since this looks like a calibration skill — learning your own release offset — rather than raw speed. We don't have a study measuring that specifically for this test, so treat it as a reasonable guess, not a promise.