The AI Reader.
The Instruments

Gemini 2.5 Pro (Experimental 03-25) fell from 92% to 87% when the exam turned over

With only 15 problems a year, one of them is worth 6.7 points of any headline AIME score.

Why this matters

Every frontier lab now puts an AIME percentage in its launch materials. OpenAI, DeepSeek, and Google have each reported a number from the same annual high-school math competition, and the number gets read as evidence a model can reason. It is a real measurement of something, and it is also a coarse one: a competition written for a few thousand teenagers a year, 15 problems on any single sitting, repurposed into a repeatable score. This lesson builds that score from the exam up: what the Mathematical Association of America actually administers, how a lab turns a fixed problem set into a percentage, and how much of that percentage one problem is worth. Then it works through the one case where a headline AIME score did not survive contact with a fresh exam, and what that cost the claims built on the earlier number.

Background optional reading
01
Hand-writing HumanEval's 164 problems solved contamination in 2021 and caused it by 2024: the full mechanics of pass@k and sampling many completions per problem, assumed here rather than re-derived.
02
A passing contamination check on GSM8K would not catch a renamed problem: a different math benchmark, contaminated a different way, worth contrasting with AIME's annual refresh.

A three-hour exam built for teenagers, borrowed by labs

The American Invitational Mathematics Examination is a real exam. The Mathematical Association of America writes and administers it every year for high schoolers who already qualified through an earlier round, the AMC.1 It gives students three hours to solve 15 problems, and it runs twice a year, AIME I and AIME II, so a student can sit up to 30 problems total across both.1 Every answer is a single integer from 000 to 999. One point per correct answer, no partial credit, no penalty for a wrong guess.1

15Problems per exam
3 hrsTime limit
0–999Integer answer range

A lab turns that fixed problem set into a benchmark score by feeding the same 15 or 30 problems to a model instead of a student, generating one or more completions per problem, and checking each completion's final integer against the answer key. What differs from a human sitting is what happens next: a lab can run the model on a problem once and grade that single try, or run it dozens of times and average the results. OpenAI's announcement of o1 reports all three approaches on the same problem set and the same model. Graded on a single try, pass@1, it scores 74%. Graded by taking the model's most common answer across 64 tries, consensus@64, it scores 83%. Graded by generating 1,000 samples and re-ranking them with a separate scoring step, it scores 93%.2 Three numbers, one model, one exam. (The mechanics of sampling many completions and scoring them are taught in full in this course's HumanEval lesson, linked above; this lesson assumes them.) A separate line of research backs the practice of averaging. Grading a model on one random sample bakes in whatever randomness that sample happened to carry. Repeated sampling is how a lab estimates a score the single-run number cannot give on its own.3

One problem is worth 6.7 points of the score

Fifteen problems make a score out of fifteen possible points, so answering one more or one fewer moves the percentage by 1/15, or 6.7 points.1 Solve all but one and the score reads 93.3%, not 100%. Miss two and it reads 86.7%. Pool both exams into one 30-question score and each problem is worth half as much, 3.3 points, still a coarse grid for a number a system card often reports to a decimal place.

Put that grid next to a real comparison. DeepSeek's R1 paper reports 79.8% pass@1 on AIME 2024.4 OpenAI's o1 reports 74% pass@1 on the same exam, already cited above. The gap between them, 5.8 points, is smaller than the value of a single problem. A ranking built on a gap that size is one problem's difference dressed up as a margin. Before comparing two labs' AIME numbers at all, the relevant question is whether each used the same convention: pass@1 against pass@1, consensus@64 against consensus@64. Many system cards state a single percentage without naming which.

The 15-problem count is an extreme case of a general problem in small evaluation sets: how a test is formatted and scored changes the measured spread even before contamination or sample size enters the picture. Reformatting MMLU's multiple-choice questions into a different answer format, with the underlying model and questions unchanged, moved the measured run-to-run spread for one 7-billion-parameter model from 0.57 down to 0.22.5 Nothing about the model's actual ability changed. What changed was how the test counted an answer. AIME's per-problem arithmetic is just the most visible version of a fact that holds across most small benchmarks. A methodology choice a headline number does not disclose can move the score by more than the difference the headline is built to report.

The same 15 problems, circulating online for years

AIME problems do not stay secret. Solutions and discussion threads go up within days of each sitting, and sites built to archive competition math, including the one that documents the exam's own rules, host the full problem sets from prior years.1 A model trained afterward on a general web crawl can absorb the answer key along with everything else. A benchmark run against the same fixed problems year after year risks testing what a model memorized, not what it can work out.

MathArena tested for exactly that on AIME 2024. The researchers built their expected-score baseline from how actual human contestants performed across AIME's own two sittings. A model's AIME 2025 score sets a quantile, and that quantile predicts what the same model should score on AIME 2024 if only the difficulty had changed.6 Most leading models scored 10 to 20 points above that expectation on the 2024 exam. One, QwQ-Preview-32B, scored nearly 60 points above it, a gap the researchers called extreme contamination.6 The same paper ran the identical check on HMMT, a competition far less prominent online, and found a much smaller gap there. The authors attribute the difference to exposure: HMMT is less likely to have made it into training data at all.6 That 60-point figure is not a raw AIME percentage. It is a gap against an expected score, a different measurement answering a different question than "how many of 15 problems did the model solve." Both readings are true of the same result: a model can score a modest raw percentage and still be flagged as extremely contaminated, if that percentage is far above what its general skill predicts.

A separate check, VAR-MATH, rewrites AIME problems with new numbers plugged into the same structure and the same required method, then re-scores the same models.7 Accuracy fell by an average of 58.8% on the 2024 set and 72.9% on the 2025 set once the specific numbers changed, with DeepSeek-R1 alone dropping from 81.5% to 61.3%, a 24.8% decline, on the reworked 2025 problems.7 The models really did answer that share of the original problems correctly. What VAR-MATH exposes is how much of that answering held onto the exact problem as written rather than the method behind it, on years both stale and fresh. Some of what reads as "solved AIME" is closer to matching a memorized problem than to running its method on a new one. Benchmark leakage is not unique to this exam. Scraped training data has been shown to raise scores on other fixed test sets the same way, and models that solve older competitive-programming problems easily often struggle on problems written after their training data was collected.8

The score that fell when the exam turned over

Google's Gemini 2.5 Pro Preview Model Card, published April 16, 2025, carries the fix. It lists 92.0% on AIME 2024 and 86.7% on AIME 2025 for one checkpoint, Gemini 2.5 Pro (Experimental 03-25), both rows labeled "single attempt (pass@1)."9 Same document, same checkpoint, same label, both years. The card's own methodology note adds a caveat: Google averaged over multiple trials for smaller benchmarks even under "single attempt," the same noise-reducing practice the earlier section described. Neither number is one raw try.9 What is stated plainly is the change: a 5.3-point drop, on the same checkpoint, when the problems it faced changed.

Same benchmark, different question each time: model, checkpoint, year, and counting rule together decide what an AIME score means.24910
Model Exam Counting rule Score
o1 AIME 2024 pass@1 74%
o1 AIME 2024 consensus@64 83%
o1 AIME 2024 re-rank of 1,000 93%
DeepSeek-R1 AIME 2024 pass@1 79.8%
Gemini 2.5 Pro (Experimental 03-25) AIME 2024 single attempt (pass@1) 92.0%
Gemini 2.5 Pro (Experimental 03-25) AIME 2025 single attempt (pass@1) 86.7%
Gemini 2.5 Pro (GA) AIME 2025 single attempt (pass@1) 88.0%

Google's own next update to the card shows why naming the checkpoint matters. Updated June 27, 2025, that document carries no AIME 2024 row at all. Its only AIME 2025 figure, for the shipped model, unqualified "Gemini 2.5 Pro," is 88.0%, different from the preview checkpoint's 86.7% on the same exam months earlier.10 A citation that just says "Gemini 2.5 Pro scored 86.7% on AIME 2025" could point to either document, and only one carries an AIME 2024 figure to compare against.

Size the drop against the arithmetic already built. A 5.3-point fall is smaller than the 6.7 points a single problem is worth on a 15-question sitting. Taken alone, a move that size does not prove contamination. It is consistent with a checkpoint that got unlucky on roughly one extra problem's worth of difficulty, nothing more, and the drop by itself does not say which explanation is true.

What makes the 2024 number suspect is the independent evidence from the previous section, not its own later fall. MathArena found leading models scoring 10 to 60 points above their expected performance specifically on the 2024 problems. VAR-MATH found accuracy on both years collapsing once the same problems were reworded with new numbers. Neither result depends on the 2025 score existing at all, and together they point the same direction. At least some of the near-saturated 2024 claims that circulated through 2024 reflected exposure to problems that had been public for months. They did not reflect a math ability that transferred cleanly to a test the model had never seen. That is what the fresh exam cost the earlier claims. None of these results run a controlled test of what any one model memorized, so this is not a disproof. A year and a differently worded problem set were still enough to undercut the earlier headline.

The takeaway

An AIME percentage measures one thing: how many of a fixed set of 15 or 30 integer-answer problems a model matched, under whatever counting rule the lab chose to run and report. Fifteen problems means one of them is worth 6.7 points, so a gap of a few points between two labs is often smaller than a single problem, not a real ranking. The Experimental 03-25 checkpoint of Gemini 2.5 Pro fell from 92.0% on AIME 2024 to 86.7% on AIME 2025, a move that sits inside that same margin by itself. It reads as more than noise only alongside separate evidence that the 2024 problems had circulated online long enough, and far enough, for memorization to inflate the earlier number. Before treating any AIME percentage as a verdict on a model's reasoning, ask which year and which sitting produced it. Ask whether it is a single pass or an average over many tries, and how many tries that average is over. The exam grades to the point. A headline number rarely says which question it actually answered.

Go deeper optional reading
01
The Mathematical Association of America's AMC program page: how a student qualifies for the AIME, and where the exam's own rules are published.
02
Cao and colleagues, "VAR-MATH" (2025): the full parametrized re-scoring methodology and per-model results this lesson draws one figure from.

Sources

  1. Mathematical Association of America · American Mathematics Competitions program page
  2. OpenAI · "Learning to Reason with LLMs"
  3. Multiple authors · "Beyond the Singular: Revealing the Value of Multiple Generations in Benchmark Evaluation"
  4. DeepSeek-AI · "DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learning"
  5. Multiple authors · "Quantifying Variance in Evaluation Benchmarks"
  6. MathArena · "Evaluating LLMs on Uncontaminated Math Competitions"
  7. Cao and colleagues · "VAR-MATH: Probing True Mathematical Reasoning via Symbolic Multi-Instance Benchmarks"
  8. The Batch (DeepLearning.AI) · "The Problem with Benchmark Contamination in AI"
  9. Google DeepMind · Gemini 2.5 Pro Preview Model Card, April 16, 2025 (mirror; Google's original hosted copy now returns AccessDenied)
  10. Google DeepMind · Gemini 2.5 Pro Model Card, updated June 27, 2025