How Many Mock Tests Should You Take Before SSC, RRB or IBPS? A Working Answer

"Bhaiya, kitne mock lagane chahiye?" It is the question I get most, and the honest opening is that nobody knows the right number for you. Anyone who says "exactly 50" or "one hundred, minimum" is repeating a slogan.

There is a useful answer though, and it has three parts: a rough count that suits most people, a schedule for how those mocks should be spread out, and a way of judging whether you are taking too few or too many. Everything below rests on one idea. A mock is only worth its analysis. Ten mocks analysed carefully teach you more than forty taken like a video game.

Exam formats referred to here, as of September 2026: SSC CGL Tier 1 has 100 questions, 200 marks, 60 minutes and 0.5 negative marking. RRB NTPC CBT 1 has 100 questions, 100 marks, 90 minutes and one-third negative marking. IBPS PO prelims has 100 questions, 100 marks, 60 minutes with a 20-minute limit per section. These are patterns from recent notifications. Always read the current notification, because patterns and durations get revised.

What a mock is for

A mock test does four different jobs, and knowing which one you need at a given time changes how many you should take.

1. Diagnosis. Where do I stand? Which section is weak? Which topics keep costing marks?
2. Rehearsal. Can I sit for 60 or 90 minutes on a screen, manage time, and stay calm?
3. Skill building. Speed, question selection, guessing decisions. These only improve under timed pressure.
4. Exposure. Meeting question types you never practised.

Early in your preparation, you need job 1 and job 4. Later you need jobs 2 and 3. Which means the same number of mocks means different things at different times.

A number for most people

Here is a table of what I have seen work, with the caveat that it is a rough working range and not a rule:

Preparation window	Total full-length mocks	Plus sectionals
3 months	25 to 35	60 to 90
6 months	40 to 55	100 to 150
12 months	60 to 80	200+

If you fall well below these, you probably have not built enough exam stamina. If you go far above, you are probably running out of time to analyse. A student who takes 100 mocks in 6 months is averaging four a week, and it is almost certain that the analysis is thin.

Now, why do I keep saying "roughly"? Because the number of mocks is not the goal. The goal is to reach a stable, repeatable score, with a fixed approach to each section, before the exam. Some people hit that after 25 mocks. Others need 60. The mock count is a proxy.

The rhythm matters more than the count

Take the same 40 mocks and spread them differently, and you get very different outcomes.

Version A: 40 mocks, all in the last 6 weeks. That is almost 7 a week. Each is taken, glanced at, and forgotten. The score climbs a bit then plateaus.

Version B: 40 mocks across 6 months. Early on, one a fortnight, then one a week, then two a week, then three in the last month. Each is analysed in depth. The score climbs steadily.

Version B nearly always wins. Here is a schedule I like:

Phase	Mocks per week	What the mock is for
Months 1 to 2	0 to 1 (only a diagnostic at first)	Diagnosis, interface familiarity
Months 3 to 4	1	Diagnosis plus topic checks
Months 5 to 6	2	Skill building, timing
Final 6 weeks	3, with a rest day	Rehearsal, stamina
Final 3 days	0 to 1 light	Stay calm

Notice that you start early. Waiting until "the syllabus is done" is a mistake. You will never feel done. Take your first mock in the first month, and expect a low score.

Analysis: the part that decides everything

This is where most people cheat themselves. A mock takes 60 minutes. The analysis takes at least as long. If you skip it, you have wasted the mock.

Here is a method that works and does not take five hours.

Step 1: Sort your errors by cause

For every wrong or skipped question, ask one thing: why? Put it in one of these buckets.

Cause	Example	Fix
Concept gap	Did not know the formula for compound interest for half-yearly	Go back to the chapter
Calculation error	Right method, wrong arithmetic	Practise calculations, tables, squares
Misread the question	Solved for "not" instead of "is"	Slow down on the reading step
Time pressure	Left it because time ran out	Review question selection
Bad guess	Marked an answer in a coin-flip and lost 0.5	Review guessing policy
Silly	Marked the wrong option after solving it correctly	Add a two-second check on the option

Count them. After five mocks, you will see a pattern. Almost everyone finds that one or two buckets dominate. That is what to fix, not "everything".

Step 2: Look at time per section

The exam does not give you a separate clock per section in SSC. So it is up to you. Note how many minutes you spent on each section in each mock. If you always spend 28 minutes on Maths and 8 on English, the plan needs to change. Look at section-wise time management for target splits.

Step 3: Look at attempts and accuracy together

Two numbers per section: how many you attempted, and how many of those were right. Accuracy is right divided by attempted.

Here is a made-up but realistic example of two students with almost the same Tier 1 score.

	Attempted	Correct	Wrong	Score (2 per correct, minus 0.5 per wrong)
Student P	80	64	16	128 − 8 = 120
Student Q	65	60	5	120 − 2.5 = 117.5

They are near equal on score but they need different advice. P should improve accuracy, because 16 wrong answers cost 8 marks directly, and each of those questions could have been worth 2 marks, so up to 32 marks of potential. Q should improve speed and attempt more, because they got almost every answered question right. Same score, different problems. Without the split you would give both students the same advice.

Step 4: Re-solve the ones you missed

Not just read the solution. Close the solution and solve it again yourself the next day. If you can, do it again in a week. This is the most powerful step and the one most people skip.

Step 5: Add to your mistake notebook

One line per mistake: question type, cause, correct approach. Review the notebook every weekend. By the last month, you should have a list of 100 to 200 lines that describe your own repeating errors. Nothing you buy will be as useful.

A worked example of analysis

Imagine you took a CGL-style mock and got 96. Here is a simplified account of what analysing it could look like.

• Reasoning: 20 attempted, 16 correct. 4 wrong. Two errors were misread ("which is NOT the odd one out"), two were bad guesses on non-verbal figures.
• GA: 15 attempted, 9 correct. 6 wrong. Five of the wrong were current-affairs items from a period you had not read.
• Maths: 18 attempted, 11 correct. 7 wrong. Three were calculation errors on percentages, two were concept gaps in mensuration, two were time-pressure rushes.
• English: 22 attempted, 17 correct. 5 wrong. Three in cloze test, two in idioms.

You do not have to fix everything. From this you learn: stop guessing on non-verbal figures, add a monthly current affairs revision, drill percentage calculations for ten minutes a day, and do a cloze test every day for a week. That is a four-item list, which is usable. Compare with "I need to improve in everything", which is not.

How many is too many

Signs that you are taking too many:

• Your analysis of each mock is under 30 minutes.
• You cannot remember what you learned from the mock you took three days ago.
• Your score has been flat for eight mocks and you are still taking more of the same.
• You feel tired and stale on mock day, not sharp.
• You are skipping topic study to fit in another mock.

If two of these are true, drop a mock a week and use the time for a serious analysis and targeted practice. It sounds backwards but it works.

Signs you are taking too few:

• You have never sat 60 continuous minutes on a screen.
• Your first mock of the week is on Sunday and you feel awkward and slow every time.
• You do not know your usual score range.
• You still run out of time in the same section every mock.
• Your accuracy varies wildly between mocks.

Quality of mocks

Not every mock is worth taking. A mock that is far harder than the real exam can shake your confidence and teach you nothing. One that is far easier can inflate your score.

Here is what to look for.

Pattern match. Same number of questions, same sections, same marking scheme, same time. If the mock has 120 questions and the exam has 100, it is not preparing you for the real interface.

Difficulty in the right band. Compare with the real previous year papers. Try one or two real PYQ papers as mocks. SSC has released papers in the past, and past RRB papers are also available. Your score in a real PYQ paper is a much better predictor than a score in a mock written by someone else.

Explanations. A mock without solutions is a test. A mock with solutions is a lesson. You need solutions, particularly for Maths and reasoning.

Normalisation awareness. SSC and RRB both normalise across shifts. Your raw mock score is not your final score. Do not chase a number like "I must get 160 in every mock". Chase consistency.

Variety of sources. Take mocks from two or three providers, not ten. Each has its own style and it is good to be exposed to more than one, but going beyond that is noise.

The free mini-mocks and full-length tests on Pareeksha mock tests are structured to follow the official patterns, and after each you get a percentile and a section breakdown. Use the percentile as a trend indicator across mocks, not as a prediction. A percentile is relative to the people who took the same paper, and that group changes.

Section tests and topic tests

Full mocks are not the only tool. Sectional tests, 15 to 25 minutes on one section, are where you fix specific weaknesses and where you should spend most of your mock time in the first half of preparation.

A pattern that works:

• Months 1 to 3: topic tests (10 to 20 questions on one chapter) right after you finish the chapter.
• Months 3 to 5: sectional tests (25 questions, 15 to 20 minutes) two to four a week.
• Months 5 onwards: full mocks dominate, with sectionals for repairing a specific weakness.

The practice section has these sets, and it is a better use of a weekday evening than a full mock you have no time to analyse. See also free mock test: how to use.

Different exams, different counts

SSC CGL. A long Tier 1 preparation with full mocks and a Tier 2 that needs its own tests. Tier 2 mocks are longer, harder, and for the maths and English papers you need to take them separately. If you are going to Tier 2, factor in 10 to 15 Tier 2 mocks on top of the Tier 1 count. Not all before Tier 1 results, since you may not get through, but a few should be done in advance.

RRB NTPC. CBT 1 is a screening test with a wide base and a general-awareness-heavy paper. Because the Tier 1 marks are for shortlisting and CBT 2 decides more, do fewer, well-analysed mocks for CBT 1 and shift focus to CBT 2 and, for some posts, the typing test or aptitude test. For Group D, mocks matter less for maths and more for science and GK volume. Check the notification of the specific recruitment, as the stages depend on the post. See RRB NTPC CBT 1, CBT 2 and typing test.

IBPS PO and Clerk. Prelims is a speed test with section-wise time. You need to train the 20-minute-per-section rhythm, so in the last two months, take mocks with sectional timers. Mains needs its own full-length mocks and a descriptive test practice for PO. See IBPS PO prelims vs mains sectional strategy.

Because banking exams are speed-heavy and the mock format is closest to the real thing, students often take more mocks here. A range of 50 to 80 full prelims mocks across a preparation cycle is common. I would still prefer 40 analysed to 80 skimmed.

What to do in the final month

Your last four weeks should not look like your first eight.

Week 4 before the exam: three full mocks, one or two sectionals a day for weak areas, full analysis on each.

Week 3: three full mocks. Start pulling your mistake notebook into a one-page summary.

Week 2: two or three mocks. Solve one real PYQ paper per week as a mock. Pick a fixed time for the mock that matches your exam slot (morning or afternoon).

Final week: two mocks at most, three if you feel good and the mocks are light. Concentrate on revision of formulas, current affairs and your mistake notebook.

Last 48 hours: no full mocks. If you must, one sectional. Read your one-page notes, and check your exam-day logistics: admit card, ID, route to the centre. See exam day checklist.

A very common mistake is to take a hard mock the day before the exam, score badly and panic. Do not do this. The exam-day mind is what you protect now.

Simulate the real conditions at least sometimes

Mocks are practice but a few should be rehearsals.

• Take the mock at the same time of day as your exam slot.
• Use a desktop or laptop, not a phone, if the exam is on a computer.
• Use only the on-screen calculator if the exam provides one, or none at all if the exam says no calculator. In the real exam you get a rough sheet, not a calculator.
• No pausing. No phone. No snack halfway.
• Practice with the interface features you will use: mark for review, question palette, language toggle. See CBT interface tips.

Two or three of these rehearsals, in the last month, is enough.

What your score trend should look like

A plausible pattern is a slow climb with noise. It is not a straight line. For example, a student's scores in a series of Tier 1 style mocks might go 82, 91, 88, 97, 103, 99, 108, 112, 110, 118. A drop after a rise is normal. What you look for is that the average of the last five is higher than the average of the five before.

Watch out for two things. A flat line means your analysis is not turning into changes. A sudden jump after a run of low scores usually means an easy paper, not an improvement. Compare to the percentile and to your accuracy, not just to the score.

Common mistakes

Taking mocks to feel prepared. Mocks that you take to reassure yourself are usually the ones you don't analyse.

Comparing your score to a friend's. Different papers, different days, different bases.

Changing strategy after every bad mock. Wait for three mocks before you change a method. One bad paper is noise.

Ignoring the sections you hate. If reasoning puzzles make you anxious, that is where mocks should go.

Skipping mocks in the last weeks because "the syllabus isn't finished". Finish what you can. Cut what you can't.

Never reading the question paper analysis. Many platforms publish shift-wise analysis with difficulty ratings after real exams. Reading these helps you calibrate what a "hard" mock really means. See SSC CGL Tier 1 shift-wise analysis and exam difficulty trends.

A short plan you can start on this week

1. Take a full diagnostic mock this weekend. Analyse it with the six-cause table.
2. Decide your window (3, 6 or 12 months) and pick the total count from the table above.
3. Put the mocks on the calendar, including the analysis slot, not just the test slot.
4. Start the mistake notebook today.
5. After five mocks, review the average of the last five against the first five.

If you want the weekly structure around these mocks, see SSC CGL 3, 6 and 12 month strategy.

Questions people ask

Is it okay to take a mock every day? Only in the last two weeks, and only if you have the energy to analyse. Earlier than that, every day is too much.

Should I attempt all questions in a mock? Not necessarily. Practise choosing what to attempt. In the real exam you will skip some, and you should learn to skip in a mock too. See negative marking: when to skip.

My mock score is much lower than my PYQ score. Why? Mocks from third parties can run harder than the real exam, and PYQs you have seen or practised feel easier. Neither number is the true one. Watch your trend.

Do I need to take Hindi and English mocks both? Take the language you will use in the exam. Only switch if you plan to change.

Should I take mocks for two exams at the same time? If two exams share a lot, yes. See preparing two exams together.

How do I know I am ready? When your last five mocks are within a narrow band, your accuracy is stable, you finish within time, and your mistakes are mostly "silly" rather than concept gaps. There is no better sign than that.