Perceptle scoring, with a calculator

A Perceptle score is not “how many tests you got right.” Each test returns an integer from 0 to 100 using score = round(100 × exp(−0.5 × (error / σ)²)). The total is round((Count + Track + Angle + Tempo + Split) / 5). I checked that formula against the public client and against three worked examples on 22 October 2026. The letter cuts are S ≥ 95, A ≥ 85, B ≥ 70, C ≥ 55, D ≥ 40, and F below 40.

Here is the average I use when I explain a close call. Scores of 80, 90, 70, 85, and 95 sum to 420, which is 84, a B. Raise the 70 to 73 and the sum is 423, which rounds to 85, an A. Three points on the weakest test cross a grade. Across 9–22 October the public average total was about 64, and Tempo was the test sitting in the 30s and 40s. A 65 matches that crowd. It is not “top third,” because the API does not publish a histogram.

Calculator

Normal σ. Friday uses 0.32, 90, 14°, 85 ms, and 0.10.
TestErrorσ
Count|guess − actual| / actual0.20
TrackHorizontal units from the landing60
AngleDegrees, shortest arc on a normal day8
Tempo0.6×|mean offset| + 0.4×spread, in ms60
SplitMiss distance / line length0.05
perceptle.com start screen for puzzle 98 on 23 October 2026
Start screen of perceptle.com on 23 October 2026, puzzle #98, a Friday. Captured from the live site.
Beat timeline with four listen beats and eight tap beats
Tempo plays four beats, then you continue for eight.

The game can show “beats this percent of today’s players” only after a score is submitted to its server. I do not reprint those lines as if they were stable. The stats API gives a player count and five averages, which is what the stats page uses. If your grade seems to use 1,000 points or ten tests, you are on a different site. The version page separates them.

Is a Perceptle score a percentile?

No. 80 means the curve, not “better than 80% of players.” A percentile line appears only inside the game after you submit, and it changes as more people play.

How is the total rounded?

The five test scores are averaged and then rounded to the nearest integer. 84.4 is 84. 84.5 rounds with the usual half-up behavior of the client’s round function.