What the aim trainer measures
This is a discrete target-acquisition test, not a tracking scenario and not a flick-only Kovaak playlist. A single target appears at a random position in the play area. You click it. The next one appears. You do that thirty times. Targets get slightly smaller as the run goes on, so the last ten shots are not the same task as the first ten. We record time from spawn to a successful hit, count clicks that miss the target, and report average milliseconds per target plus accuracy.
Accuracy here is hits divided by hits plus misses. You cannot skip a target — it stays until you hit it — so a miss is extra latency plus a penalty to the accuracy percentage. That pairing matters. A reckless spray can post a decent average time and a poor accuracy; a cautious hover can post the reverse. The score we percentile is time per target, because that is the number people search and compare. Accuracy sits next to it so you can see how you bought that time.
Aim trainer score guide
| Tier | Avg time / target |
|---|---|
| Getting started | 700 ms+ |
| Average | 500 – 650 ms |
| Good | 400 – 500 ms |
| Excellent | 320 – 400 ms |
| Sharp / trained | under 320 ms |
| Accuracy to aim for | 90%+ |
How to improve your score
- Lower the mouse sensitivity. Most people overshoot because the sensitivity is a flick-at-everything setting. A lower sens that lets you stop on the target is faster over 30 shots than a high sens you have to micro-correct.
- Move, then click — do not click on the way in. A miss costs more than a 40 ms pause. Wait until the cursor is on the disc, then press. The shrinking targets at the end of the run punish sloppy early clicks twice.
- Use the arm for large moves, the wrist for the last inch. Large random spawns need a bigger muscle group. If everything is a wrist flick, later targets become a lottery. Plant the forearm and let the wrist finish.
- Play full screen and disable mouse acceleration. OS pointer acceleration makes the same physical move land in two different places. Turn it off. This site already hides chrome during the run so the play area is the whole viewport.
- Warm up, then take one scored run. The first run of the day is usually 40–80 ms slower. Throw one away with Try again, then keep the second. Chasing twenty rerolls just trains frustration.
FAQ
What is a good aim trainer score?
An average of about 500–600 ms per target with 90%+ accuracy is a solid untrained result. Under 400 ms with high accuracy is genuinely good. Compare only against this test — other trainers use different target sizes, distances, and counts.
Does this help in FPS games?
It trains discrete acquisition — the “see it, stop on it, click” loop. It does not train tracking, recoil control, or peek timing. Use it as a warm-up, not as a full aim regimen.
Why do the targets shrink?
A fixed size lets you settle into one motor program. Shrinking forces you to keep confirming the cursor is actually on the target, which is closer to how late-round gunfights feel.
Can I play this on a phone?
Yes. The play area is touch-first and the targets stay above a 28 px floor so a thumb can still hit them. Times will be slower than a mouse; that is expected. Your personal best is still comparable to your other phone runs.
How is accuracy calculated?
Successful target hits divided by hits plus clicks that landed in the play area but missed the target. Clicks outside the stage do not count. The target does not despawn on a miss.
Try a related test
- Reaction Time Test — How fast can you respond when the screen goes green?
- Click Speed Test — How many clicks per second can you land? The classic CPS test.
- Visual Memory Test — Squares flash white. Click them all back. Three lives.