Dead StopCan You Stop a Clock on Exactly .000?
Yes, but rarely. A player whose taps land within about 25 milliseconds of the target stops a clock on exactly .000 about once in 60 tries. On a phone there's a second limit too: the screen only registers taps on a beat, so on any one try most millisecond values can't come up at all.
How Often a Person Lands on an Exact Millisecond
Nobody taps the same way twice. Your stops spread around the moment you aim for, and the width of that spread decides how often you land on exactly .000:
| Typical miss | Exact .000 |
|---|---|
| Within about 12 ms (very steady) | About 1 try in 30 |
| Within about 25 ms (a good player) | About 1 try in 60 |
| Within about 45 ms (starting out) | About 1 try in 110 |
That's why a DEAD STOP feels like an event. Skill moves you closer to the target; landing on the exact millisecond is still partly luck.
Why Your Phone Only Taps on a Beat
A touchscreen doesn't record the instant your finger lands. It checks for touches on a fixed beat: 120 times a second on most iPhones, every 8.33 ms. Every tap's time snaps to that beat.
The beat barely drifts against the clock, so for minutes at a time it sits at the same spots around the second. That leaves only about 120 of the 1,000 millisecond values that can come up, the same ones again and again. If none of them sits on .000, an exact stop is impossible however perfect the tap; if one does, it comes up far too often.
Measured on an iPhone on October 29, 2026: nine taps, every gap between them a whole number of 8.33 ms beats, and only 7 different millisecond values among the 9. One pair landed exactly 2,000 ms apart, 240 beats.
How Dead Stop Keeps Every Millisecond Reachable
Each try, Dead Stop moves its clock by a fresh random fraction of a beat, never more than 17 ms. The clock you see and the clock that's scored move together, so what you stop is exactly what's on the screen. Because the beat lands somewhere new each try, every millisecond value, .000 included, comes up as often as it should over a run.
| Where the phone's beat falls | Without the shift | With the shift |
|---|---|---|
| Lined up with .000 | 13% of tries (far too easy) | 1.5% |
| Not lined up | 0% (impossible) | 1.5% |
| A screen with no beat at all | 1.6% | 1.6% |
A simulation of a good player, with taps within about 25 ms, on a 120 Hz phone. With the shift, every phone gets the fair rate.
How the Board Stays Honest
A tap is timed on the player's own device, so no server can prove a single score. What Dead Stop can do is make cheating stand out. Every stop is sent the moment it happens and the server works out the score itself, refusing stops that arrive late, come faster than the game allows or come from a clock that jumps. A player's own record of misses also shows how often they should land on .000; results far better than that keep them off everyone else's board.
Questions
Why do I keep getting the same number?
Because your phone registers taps on a beat. An iPhone checks the screen for a touch 120 times a second, so every tap's time lands on a grid 8.33 ms apart, and the grid barely moves against the clock. Dead Stop shifts its clock by a random fraction of a beat on every try, so the score you're given isn't stuck on the grid.
Is .000 possible on every try?
No, and on a phone it can't be. On a 120 Hz screen only about 1 millisecond value in 8 can come up on any one try. Dead Stop moves which ones every try, so .000 is in play about 1 try in 8 and every value gets its fair turn over a run.
How often does a good player hit .000?
About once in 60 tries. A player whose taps land within about 25 ms of the target lands on exactly .000 around 1.6% of the time; a steadier player hits it more often, a beginner less.
Can every Nine Lives zone be hit?
Yes, on any 120 Hz phone. The tiny 500 zone is 9 ms across, wider than the 8.33 ms beat, so some tap time always falls inside it. On an older 60 Hz screen, with a 16.67 ms beat, the wide and narrow zones always can and the tiny one can about half the time.
Can I see my phone's beat?
Yes. Open deadstxp.com/?timing and stop the clock ten or more times. A panel shows each tap's raw time, the beat your phone uses and how many different values came up. Nothing is sent anywhere.