Aim Trainer Statistics

An average of thirty is a different shape from a single reaction

A one-shot reaction time has a hard floor and a long slow tail. An average of thirty reaches still has the floor — nobody teleports — but the tail is shorter, because one very slow reach is diluted by twenty-nine ordinary ones.

That is why this chart is narrower than the reaction-time ones even though the typical score is higher. The extra time is travel, shared by almost everyone, and the variation between people sits on top of it rather than replacing it.

The mean and the median sit closer together here than they do on the reaction pages, which is what a thinner tail looks like in two numbers.

Mouse and touch are not the same sport

A mouse score compared to a touch score is a comparison of devices more than of people. The two charts exist so that comparison is never offered as if it were fair.

Until a mode has two hundred attempts, that mode’s chart shows the count and a note instead of a curve or a percentile. A thin sample dressed as a ranking is the thing this site was built not to do.

Keyboard attempts do not exist on this test and so they do not appear here. There is no key that corresponds to a location on the field.

What is and is not in the sample

Finished runs of thirty hits. A tab closed on target eleven produces nothing, so the distribution is not a mix of complete and abandoned attempts.

The opening click that starts the test is not one of the thirty. Including it would add a decision that is not aiming and would shift every score the same way, which is a bias rather than a measurement of anybody.

This is a browser toy on unknown hardware, not a training log from a game client. Nothing on this page is a claim about flick speed in a title, or about tracking as a coach would use the word.

Tracking lives on the same page and a different axis

The trainer’s Track button writes a percent, not an average time. Those clips sit on the second pair of charts on this page, split by mouse and touch the same way, because a thumb that covers the circle is not a cursor that has to stay inside it.

Higher is better on that pair. Mixing a flick millisecond with a tracking percent on one axis would invent a conversion this site does not have. The two-hundred-attempt gate is counted separately on each playlist.

A clip with no pointer movement is not stored. Standing on the spawn is not tracking, and farming that as a high percent would wreck the right edge of the tracking charts.

This is a measurement toy, not a medical or psychological test. No score here says anything about your health, attention or cognition, and it is not a screening tool of any kind.

Questions

What is the average aim trainer time?

It depends on the input, which is why this page keeps two charts. The breakpoints under each one are the current figures from the attempts recorded here.

Why is there no keyboard chart?

Because the test cannot be played with a key. A location on a field has no corresponding key press.

Does a slow first target ruin the score?

Less than it would on a shorter test. Thirty intervals absorb one bad reach, which is the reason the run is that long.

Where did the tracking curve go?

It is the second pair of charts on this page. Track is a playlist on the trainer, not a separate URL, and its unit is a percent.