Why Your GRE® Quant Score Is Stuck at 150-155

If your GRE® Quant score has stayed between 150 and 155 for a few practice tests, the obvious next move is more practice problems. Quant comes with a long content list, arithmetic through data analysis, and a bigger stack of solved problems is a reasonable response to a score that won't move. We understand the instinct, and it isn't wrong to want more reps.

But volume alone rarely moves a score at this band, because "stuck at quant" is usually several different problems at once, and more problems only fix one of them. A score that holds still through weeks of work usually means the effort is going to the wrong cause, not that the effort is missing. What follows: what 150-155 means on the current score scale, a four-cause diagnosis for quant misses, and the order we suggest for working on what the diagnosis finds.

What 150-155 means on the current scale

Quantitative Reasoning scores run from 130 to 170 in one-point increments. In ETS's most recent interpretive data, covering everyone who tested between July 1, 2022 and June 30, 2025, the mean Quant score is 157.6 across about 790,000 scores, and a 150 sits at the 23rd percentile, a 152 at the 29th, a 154 at the 34th, and a 155 at the 37th. Our percentiles guide explains why: the test-taker pool includes a large share of students from quantitative fields, and their scores pull the average up.

So a 150-155 score on Quant means something different than the same neighborhood does on Verbal, where the average sits near 151 in the same data. On Quant, this band sits below the pool's average, and the percentile table says the distance to the middle of the distribution is a few raw points. That's the encouraging half. The less encouraging half: the points between here and there usually require a more specific diagnosis than another stack of practice sets, because the same symptom, a wrong answer on a quant question, comes from several different causes.

Diagnose before you drill

The Quant measure runs 27 questions in 47 minutes, in two sections: 12 questions in 21 minutes, then 15 questions in 26 minutes, with an on-screen calculator available throughout. The content comes from arithmetic, algebra, geometry, and data analysis, and Quantitative Comparison makes up roughly 40 percent of the questions, about 11 to 14 of the 27, though ETS doesn't publish exact per-type counts.

Before sorting any misses, run one pre-check: count the blanks. An unanswered question scores nothing, while a guess on the GRE® carries no penalty, and you can skip, return, and change answers within a section. If your practice tests show blanks at the end, part of the fix is pacing rather than any of the causes below, and our timing guide covers that repair.

With no blanks in the way, take the misses from your last two or three full practice tests and sort each one into one of four causes:

• Cause A: an execution slip. You knew the method, the setup was right, and the miss happened in the carrying out: a dropped sign, a miscopied number, or a correct answer to a question the stem didn't ask, etc.
• Cause B: a setup error. The math underneath was familiar, and the equation you built from it was wrong: the wrong quantity named as the variable, or two times averaged when rates add.
• Cause C: a Quantitative Comparison trap. The answer came from one convenient value, and the edge cases that would change the relationship went untested.
• Cause D: a concept you haven't learned yet. The tool itself was missing: a geometry fact you never learned, or a statistics term you couldn't define.

The mix should guide where the work goes. We suggest working the causes in this order: blanks first, then execution slips, then setup errors, then concept gaps. The priority follows where the recoverable points usually are. An unanswered question scores nothing no matter how much content you know, a missed question you knew how to do gives new content nothing to fix, and a setup error repeats itself across every question of its type until the setup changes. Content study matters too, and in our experience it comes up less often than students guess, which is part of why the pure-content response can run for weeks while the score stays still.

Cause A: execution slips

Execution misses can be efficient to fix, because the method underneath is usually in place and the change is a checking habit rather than new math.

Two habits catch many of them. First, before you submit an answer, re-read the stem and confirm the answer responds to the question asked, since a question that asks for the combined cost can catch an answer computed for one item alone, etc. Second, when time allows, verify one step a different way: estimate the magnitude, or test your algebra's solution back into the original equation. The calculator can check arithmetic, but it can't check the setup, so the different-way check is the one that catches what the first pass missed.

Cause B: setup errors

Practice Problem (Problem Solving)

Working alone at a constant rate, a pump fills an empty tank in 6 hours. A second pump, working alone at its own constant rate, fills the same empty tank in 3 hours. Working together at their own rates, how many hours does it take the two pumps to fill the empty tank?

(A) 2

(B) 2.5

(C) 4

(D) 4.5

(E) 9

Try this one before reading on.

The work-rate setup converts each time into a rate first: the first pump fills 1/6 of the tank per hour, the second fills 1/3 of the tank per hour, and rates add, so together they fill 1/6 + 1/3 = 1/2 of the tank per hour. Half the tank per hour fills the tank in 2 hours, which is (A).

Choice (D) comes from averaging the two times instead of adding the two rates. The division is the easy part; what went wrong is which quantities the equation combined. That distinction matters for your error log. If the correction "rates add, times don't average" is enough for you to re-solve the problem cleanly, the gap was setup, and one re-solve, with the cue written down, is the repair. If the rates-add step itself is new to you, that's Cause D, and it needs a re-learn with fresh problems. Our two-list error log keeps these two kinds of misses separate, and each kind gets its own repair.

Cause C: the Quantitative Comparison trap

Try this one before reading on.

x = 2 makes Quantity A greater, but one value can't establish a relationship for every valid x, so keep testing: x = 1 makes the two quantities equal, and x = 1/2 makes Quantity B greater, since 1/4 is less than 1/2. Different valid values of x produce different relationships, so (D) is the only answer consistent with all three cases.

A common QC failure mode is testing one convenient value and stopping. The repair is a testing habit rather than new content: when a QC question gives you a variable with a condition like "greater than 0," test the special values of that condition, starting with 1, where the quantities are equal, and a value between 0 and 1, where the relationship can flip. Our Quantitative Comparison guide covers the compare-don't-calculate approach that keeps these questions short.

Cause D: the concept gap

Sometimes it's content. A geometry fact that never made it into your prep, or a statistics term you could define only approximately, can cost a question on its own, and the fix is a re-learn of that one concept with official questions, since ETS's own material is the closest match to how the concept appears on the test.

The safeguard is the miss sort itself. Content study is the most time-expensive repair on the list, and it belongs in the plan when the misses point at it: if your sorted misses keep landing on Cause D, the re-learn is the right spend. If they keep landing on Causes A through C, the hours belong there first. The free PowerPrep tests are a useful place to check which is true, because their questions come from ETS.

The loop

The loop we suggest runs on the cause sort: after every practice test, sort the misses into the four causes, spend the bulk of your study time on whichever cause shows up most, and re-check the mix on the next test, because the mix changes as you improve and the work should change with it.

Practice tests fit into the loop by data rather than by calendar. When your focus area is reaching target accuracy at a time-per-question pace consistent with your target difficulty band, your numbers support another full test, and when they aren't, the focus area gets the hours instead. The mechanism behind section difficulty is worth knowing here: your second Quant section's difficulty depends on your first-section performance, and the reported score weighs your total correct answers together with the difficulty of the sections. The full method is in How to Break Through a GRE® Score Plateau, and how GRE® scoring works covers the adaptivity in detail.

Scores in this band move when the misses change what gets studied, not when the count of solved questions goes up. The diagnosis above usually fits on one page, and an hour with your last two practice tests is enough to build it.

FAQ

Why is my GRE® Quant score not improving?

Clear the blanks first, since they're a pacing issue, then sort your missed questions into four causes: execution slips, setup errors, Quantitative Comparison traps, and concepts you haven't learned yet. Spend study time on whichever cause shows up most, worked in that order. More practice problems add reps without changing what the misses are telling you.

What percentile is 150-155 on GRE® Quant?

A 150 is the 23rd percentile, a 152 the 29th, a 154 the 34th, and a 155 the 37th, according to ETS's most recent interpretive data (test takers from July 1, 2022 through June 30, 2025). The mean Quant score in that data is 157.6, so this band sits below the test-taking pool's average.

How much time do you get per GRE® Quant question?

About 105 seconds: 47 minutes across 27 questions, split into 12 questions in 21 minutes and 15 in 26. Treat that average as a budget rather than a per-question limit, and protect the section against blanks, since a guess carries no penalty while an unanswered question scores zero.

Is Quantitative Comparison hard to improve?

It improves with a format-specific habit rather than new math. A common QC failure mode is testing one convenient value and stopping, so the repair is testing the special values of the given condition, including 1 and a value between 0 and 1, and choosing (D) whenever two valid values produce different relationships.

How do I tell a setup error from a missing concept?

Re-solve the question after reading the correction. If the correction is enough and the re-solve goes cleanly, the gap was setup, and the fix is a written cue with the problem. If the correction itself is new to you, the concept was missing, and it needs a re-learn with fresh problems.

How do I get from 155 to 160 in Quant?

Diagnose the miss mix first, then train the cause that shows up most: checking habits for execution slips, rate-and-variable setup work for setup errors, special-value testing for QC traps, and targeted re-learning for content gaps. Retest when your focus area reaches target accuracy at your target difficulty band, so the next score reflects the repair.

Want to learn even more?

For the question type behind the Cause C traps:

• GRE® Quantitative Comparison: A Strategy Guide

For the pacing plan that keeps the section blank-free:

• GRE® Timing Strategy: Pacing 27 Questions Without Panic

For the Verbal twin of this diagnosis:

• Why Your GRE® Verbal Score Is Stuck at 152-156

For the log that separates the two kinds of misses:

• The GRE® Error Log: Done Right (and When It Becomes Procrastination)

For what 150-155 means against the full score distribution:

• GRE® Score Percentiles: What Your Score Actually Means

We also talk through prep strategy on our podcast.

And if you'd like help reviewing your own miss list, you're welcome to book a complimentary strategy session. We'll sort your misses by cause and help you decide where the next stretch of study hours belongs.