Your grand test score on its own tells you almost nothing. A 320 could be real progress or a plateau — you only know once you look at the trend over time, the subject-wise breakdown, and the types of mistakes you keep making. Here is how to turn mock marks into a signal that actually moves your rank, including a mistake-classification system you can apply to every test.
Why a single GT score is meaningless
One test is a snapshot on one day, shaped by that paper's difficulty and your mood. Read in isolation, it tells you very little and often just triggers elation or panic. The value is in the pattern across many tests — and in why you lost the marks you lost, which the total score completely hides.
What to actually analyse
- Trend over time: is your score and percentile climbing across tests?
- Subject-wise breakdown: which subjects consistently drag you down?
- Mistake types: silly errors, gaps in knowledge, or misreading the question?
- Accuracy vs attempts: are you converting the questions you attempt into marks?
Classify every wrong answer into one of four types
Two candidates can both lose 40 marks and need completely opposite fixes. The way to tell them apart is to tag each wrong answer by cause. Most mistakes fall into four buckets, and each points to a different action:
| Mistake type | What happened | The fix |
|---|---|---|
| Didn't know | Genuine knowledge gap — never learned it well | First-time study of that topic, then schedule revision |
| Forgot | Knew it once, couldn't recall it in the test | Tighter spaced revision — the interval was too long |
| Confused options | Narrowed to two, picked the wrong one | Study the discriminating detail between close options |
| Silly mistake | Misread the stem, marked the wrong bubble, rushed | Process fix — slow the final read, not more studying |
The insight this unlocks: if most of your losses are "forgot", taking more mocks won't help — your revision spacing is wrong. If they're "silly", you don't have a knowledge problem at all, you have a pacing problem under the sectional timing. The label tells you where to spend the next week.
Track the trend, not the day
Judge yourself on the slope, not a single point. A dip on a hard paper while your percentile holds is fine; a flat line across many tests is the real warning sign that your method needs to change. Because NEET PG is scored relative to the field — the qualifying percentile is set by NBEMS each cycle — your percentile trend within a large, consistent test series is a truer signal than the raw mark.
Turn analysis into action
Analysis only matters if it changes what you do next. A weak subject becomes extra revision cycles; a recurring mistake type becomes a specific habit to fix — for example, slowing down on the last question of each section under the new sectional timing. Feed weak subjects back into your revision schedule. A simple loop works: test → classify every error → convert the top one or two causes into concrete revision tasks → retest.
The score tells you where you are. The breakdown tells you what to do next — and only the second one improves your rank.
How many grand tests, and how often?
Enough to see a reliable trend and to rehearse the exam format — a regular cadence (for many aspirants, one every week or two in the final months) works better than cramming several in a row without reviewing any. The review matters more than the volume: one fully analysed test beats three unread ones. Rehearsing in five 42-minute blocks also trains you for the format itself, which counselling-deciding ranks from the MCC ultimately depend on.
Make it effortless
Doing this by hand across dozens of grand tests is tedious, and most aspirants give up. RankPG's GT Tracker lets you log each test and see your trend and weak subjects at a glance; the subject-wise breakdown and the four-type mistake analysis above are part of Pro. It works alongside whatever mocks you take, so your analysis lives in one place. See how the planner works, and read how marks vs rank works in 2026 to interpret your trend correctly.
A worked example: reading one candidate's trend
Imagine five grand tests scored 300, 315, 305, 330 and 345. The one dip (305) looks like a setback in isolation, but the slope is clearly upward, so the method is working — no change needed except consistency. Now suppose the subject breakdown shows Pharmacology and PSM losing marks in every single test while other subjects climb. That is not a "score" problem, it is a two-subject problem, and the fix is targeted: extra revision cycles on those two, not more full mocks. Finally, suppose most of the lost marks in those subjects are tagged "forgot" rather than "didn't know" — then even the fix narrows further, to tighter revision spacing on topics you have already studied. That is three layers of insight the raw scores (300–345) could never give you.
Build a repeatable review routine
Consistency beats intensity. A simple routine after every grand test:
- Log the score and percentile the same day, into the same place, so the trend accumulates.
- Tag every wrong answer with one of the four mistake types above.
- Pick the top one or two causes — not all of them — and write a concrete revision task for each.
- Schedule those tasks into your revision queue before the next test.
- Re-check next time whether that cause shrank. If it did, move to the next one.
This loop is deliberately small so you actually do it. An aspirant who reviews every test this way will improve faster than one taking twice as many mocks with no review.
Accuracy versus attempts: the number most aspirants ignore
Two candidates can attempt the same 150 questions and score 40 marks apart purely on accuracy, because every wrong answer both fails to add four marks and subtracts one. So alongside your score, always read two ratios: how many questions you attempted, and what fraction you got right. If your accuracy is high but your attempts are low, you are leaving marks on the table by being too cautious — practise committing to educated guesses. If your attempts are high but accuracy is low, you are bleeding marks to negative marking — slow down and skip the genuine unknowns. Tracking this ratio across tests tells you which lever to pull, and it is invisible if you only ever look at the final score.
How do I analyse my NEET PG mock scores?
Look beyond the total: track your score and percentile trend across tests, your subject-wise breakdown, and your recurring mistake types — then turn each finding into a specific revision action.
How many grand tests should I take?
Enough to see a reliable trend and to rehearse the exam format — take them regularly through your prep, and always review each one rather than just noting the score.
Why is my GT score not improving?
Usually because analysis is not turning into action. Identify your weakest subjects and most common mistake types, then target them specifically in revision instead of taking more tests blindly.
What are the different types of mistakes in a mock test?
Broadly four: "didn't know" (a knowledge gap), "forgot" (recall failure from weak spacing), "confused options" (picked the wrong one of two close choices), and "silly mistakes" (misreading or rushing). Each needs a different fix, which is why tagging them is more useful than counting them.
Topics
