Statistics · Aim Trainer
Aim Trainer statistics
The whole distribution, where the numbers come from, and a calculator that places your own score inside it.
Where your score falls
Type a number to place it in the distribution below.
The percentile bands
| Band | Score | Percentile |
|---|---|---|
| Top 1% | ≤ 380 ms | 99th |
| Top 5% | ≤ 450 ms | 95th |
| Top 15% | ≤ 520 ms | 85th |
| Top 30% | ≤ 600 ms | 70th |
| Median | ≤ 700 ms | 50th |
| Bottom 25% | ≤ 850 ms | 25th |
| Bottom 10% | ≤ 1000 ms | 10th |
Bands built from the thirty-target format used across the category, where a mid-range score sits near 700 ms per target.
How we will replace these numbers
The bands above come from other people’s published datasets, named under each table. They are the honest option while this site is new: quoting a percentile from a handful of our own samples would be worse than quoting someone else’s from millions.
Once a test holds more than a thousand clean samples of its own, the percentile switches to our data and starts showing the sample size next to it. Runs that lost focus or looked automated never enter that pool — see how we measure.
Questions
What is the average aim trainer score?
The median is 700 ms. Half of players score better than that and half score worse.
What is a good aim trainer score?
Around 700 ms per target is average. Under 600 ms puts you in the top 30%, under 520 in the top 15%, and under 450 in the top 5%. Professional first-person shooter players sit near 400 ms.
Why is my aim score slower than my reaction time?
Because you have to move. Reaction time measures a press you were already positioned for; this adds seeing where the target is and travelling there, which is most of the time on the clock.
What sensitivity should I use?
Most competitive players use 30 to 50 centimetres per full 360 degree turn, which is lower than most casual settings. If you regularly overshoot targets, your sensitivity is too high.