How the projected score works
Practice sessions come in every length. The projected score turns them into one number on the real test's scale.
The formula
- Take your last 10 sessions of that section.
- Points per question = total points ÷ total questions answered. Points use the firm's penalty, for example +1 right and -1 wrong.
- Pace = total questions answered ÷ total seconds, using only sessions where answers were hidden until the end.
- Questions reached = pace × the real time limit, capped at the real number of questions.
- Projected score = points per question × questions reached.
Example
Optiver's Beat the Odds is reported as 30 questions in 25 minutes. You do 10 questions in 9 minutes and score +4, then 20 questions in 16 minutes and score +10. Pooled: 14 points over 30 questions in 25 minutes, so 0.47 points a question at a pace that reaches all 30. Projected score: 14.0 out of 30.
Why it pools instead of averaging
Averaging each session's percentage would let a 5-question session count as much as a 30-question one. Pooling weights every session by how many questions it had. Using your pace also matters for speed tests like 80 questions in 8 minutes: being accurate but slow projects lower, as it would on the day.
Limits
Real formats are reported by candidates, not published by firms, and difficulty varies. Treat the projection as a trend line, and check your own invitation for the exact format.