Rahul Gupta: How He Scored 120/120 in JEE Main Mathematics

Scoring 120 out of 120 in JEE Main Mathematics — a perfect score — is rarer than a 99 percentile. In the January 2025 session, Rahul Gupta from Lucknow achieved it. He was not a prodigy who found Math effortless; he was a student who had scored 85 in his first full-length mock in July 2024 and systematically eliminated every error type over six months. His journey from 85 to 120 is a masterclass in structured improvement.

The Starting Point: Diagnosing the 35-Mark Gap

"When I scored 85 in my first mock, I categorised every wrong answer," Rahul explains. "I got 7 questions wrong. Three were Integration — I didn't know the right technique. Two were 3D Geometry — I had the formula wrong. One was Probability — I set up the wrong sample space. One was Sequences — careless arithmetic. That analysis told me exactly what to fix and in what order." This precise diagnostic approach — not just noting which chapter but which sub-type and which error category — was Rahul's core method throughout his preparation.

He did not panic about the 35-mark gap. "85 to 120 is 7 questions. In Math, 7 questions is two chapters deeply fixed. I had six months. That's manageable." The reframe from "I need a massive improvement" to "I need to fix specific things in specific chapters" changed his emotional relationship with the gap. Take a diagnostic Math mock to identify your own specific gaps with the same clarity Rahul used.

How Rahul Mastered Calculus

Integration was Rahul's biggest weakness — not unusual, given that it is the most demanding Math topic for most JEE aspirants. His approach was to build a personal Integration Techniques Reference Card: a single laminated A4 sheet listing every integration technique (substitution, by parts, partial fractions, special forms involving quadratics, trigonometric substitution, reduction formulae) with one example for each. "I spent three days making the card properly. The act of curating it was itself a revision session. Then I reviewed the card every morning for the next four months."

For each integration technique, he followed this practise protocol: 3 easy problems (build reflex), 3 medium problems (build accuracy), 1 hard problem (build flexibility). Total: 7 problems per technique per week. Over 16 weeks and approximately 20 techniques, that was 2,240 integration problems — a volume that converted technique knowledge into automatic reflex. By November, he could identify the correct technique for any integration within 10 seconds of reading the integrand. For the technique framework he used, see our integration techniques guide and our definite integration guide.

The Mock Test System That Eliminated Errors

From October to January (4 months), Rahul took exactly two full-length Math section mocks per week — never more, never fewer. After each mock, he spent as much time on error analysis as on the mock itself. His error log had four columns: question number, error type (conceptual/formula/careless), root cause (specific sub-topic or technique), and fix applied (what he studied or practised to fix it).

By December, a pattern emerged: all his remaining errors were concentrated in two areas — permutation and combination (specifically, cases with identical objects) and definite integration with tricky limits. He spent the last three weeks before the exam doing nothing but P&C problems and specific definite integral types. On exam day, both areas appeared — and he got them correct. "If you have accurate error data, the exam is no surprise. The exam tests what the data told me to fix." For the mock strategy that underpinned his system, see our Math mock test strategy guide.

Rahul's Exam-Day Execution

"My sequence on exam day: I read all 30 questions first (8 minutes), starred the ones I was certain about (18 questions), crossed the genuinely hard ones (5 questions), and left the rest unmarked. I solved starred questions first, then unmarked, then revisited crossed questions if time permitted. I finished with 12 minutes remaining and used them entirely for verification — re-checking the integer-type answers especially." This sequencing strategy, practised identically in every mock, made exam-day execution automatic. He did not need to think about strategy when the clock was running — the strategy was already wired in. For the full sectional execution framework, see our Math attempt strategy guide.