IRCTC Agent Ticket Booking Limits Explained

Say a customer asks you to book a Tatkal ticket for a family of six. You’ve heard “four” somewhere. You’ve also heard “24 a month” and “no cap”. So what are you actually allowed to do?

The honest answer is that those numbers don’t describe the same thing. One counts passengers on a ticket. One counts tickets in a month for a personal account. One is about what time of day an agent can start booking. When people mix them up, they promise customers things they can’t deliver. This article pulls them apart, so you know which number answers which question. Everything below was checked on 18 October 2026.

What does each published limit actually cover?

The trick is to stop looking for one number for the whole account. Look at each number and ask three things: who is it for, what is it counting, and where did it come from?

This table is a reading aid. It doesn’t create any new limit.

The sources are the IRCTC Aadhaar guide, the website terms (page 10) and the Indian Railways announcement published by PIB.

Notice the last row. We don’t have a verified number for it, so we haven’t made one up. At the counter, a blank is more useful than a guess. If you get a message that says only “four”, don’t write it down as a per-train booking limit. The four we’ve verified counts travellers on one PNR. It says nothing about how many PNRs you can make.

When can an agent book Tatkal?

The Indian Railways announcement published by PIB keeps authorised agents out during the first 30 minutes of opening-day Tatkal. So an agent can book eligible AC Tatkal from 10:30 AM, and non-AC Tatkal from 11:30 AM (checked 18 October 2026).

Here’s the part people miss. Having unused monthly capacity on your ID doesn’t change this. The restriction applies either way. Our Tatkal timing guide helps you explain the window to a customer before you even try the booking. Tell them at 9:50, not at 10:31.

What about the exact per-agent, per-train Tatkal cap? It needs to be confirmed against the current agent rules. Please don’t teach a number from an old support sheet or a personal-user guide as the agent limit. If you need it, ask support for the official wording. And ask whether the limit applies per ID, per train, per day or per PNR, because those are four different things.

Is the four-passenger Tatkal limit the agent cap?

No. IRCTC’s website terms say a Tatkal e-ticket PNR can carry at most four passengers (IRCTC terms, page 10, reopened 18 October 2026). That’s passengers per PNR. It isn’t a verified number of Tatkal PNRs an agent can book on a train.

Compare these two questions:

• “How many people can go on this one Tatkal reservation?”
• “How many reservations can this agent make for this train?”

The first has a source. The second doesn’t, at least not one we can quote here. Please don’t multiply the answer to the first by a guess at the second. That just gives you a made-up number that looks official.

For a larger party, tell the customer you need to check the request against the booking rules. Don’t promise seats next to each other, and don’t promise a workaround. Ask what they actually need before you try any permitted alternative.

Do the personal monthly limits apply to an agent ID?

They don’t. IRCTC’s personal Aadhaar guide says a user can book up to 24 tickets in a month, and that booking more than 12 needs the profile and at least one travelling passenger to be Aadhaar-authenticated (personal-user guide, checked 18 October 2026). It’s written for the personal profile. It doesn’t tell you an agent’s monthly capacity, so don’t copy it into the agent column.

Now, you might think: “I’ll just open a few personal IDs and use their monthly limits for my customers.” Please don’t. IRCTC’s Agent Policy prohibits commercial ticket sales through personal IDs. If your volume is high, handle it inside your authorised retail arrangement.

What does the agent charge have to do with it?

The agent charge is about money, not limits. SiOnline’s stated agent charge is ₹40 per AC PNR and ₹20 per non-AC PNR, printed on the ticket and collected from the customer, as of 18 October 2026. It’s per PNR, not per passenger. That tells you the unit the charge uses. It doesn’t set a booking quota. For the rate in detail, read the agent-charge explanation before you do your own sums.

Something else to say clearly to customers: SiOnline states that an agent sees the same seat availability as a personal user or a railway reservation counter. An agent ID gives you permission to book commercially. It doesn’t give you a private stock of seats. So never promise a berth.

And one note about your own planning. Account capacity isn’t customer demand, and it isn’t income. Keep three things apart in your records: enquiries, accepted requests and completed reservations. If you ever add up agent charges, use completed PNRs only. That total is gross charges. It isn’t profit, because it leaves out registration, renewals, maintenance and your own expenses.

What if the booking is refused?

A refusal is something you observed. It isn’t a diagnosis. Here’s what to do:

1. Check you’re on the right account, using the agent login help.
2. Write down the exact message on screen.
3. Note the quota, class, train and journey date, and keep the request reference if there is one.
4. Contact support with your agent ID and that message.

Never send your password or an OTP to anyone, including us.

A refusal doesn’t always mean you’ve hit a numerical cap. It could be about the booking window, account verification or the particular transaction you tried. Ask your PSP what the message means and which instruction applies to your account. If the reply mentions a limit, ask for three things: what it counts, whom it applies to, and the official basis for it.

Try not to keep retrying just to find the boundary. If money left your account during a failed attempt, that’s a separate payment enquiry, so treat it as one and give support the transaction details.

What do customer requests change?

The Agent Policy says you book only when a customer approaches you, and with their knowledge and agreement. It also says booking and cancellation requests, written or electronic, and copies of ID proof must be kept for six months (Annexure A, section II, checked 18 October 2026).

That has two practical effects. Monthly capacity doesn’t let you book ahead of a request “in case someone wants it”. And the policy prohibits sharing the RSP ID, so nobody else should be booking on yours.

If a customer asks for more than you can show is permitted, stop and ask first. Don’t quietly split their request into pieces and call the result the original booking. Agree each permitted alternative with the customer, and tell them plainly that you can’t promise the outcome.

Three misreadings to avoid

These are made-up examples. They aren’t real cases.

The wrong “four”. A counter employee gets a message with just “four” and types it into the per-train column because they remember it from a Tatkal guide. But the verified four counts travellers on one PNR. The right next step is to ask what the message is counting and what current agent rule backs it up.

The personal “24”. Another person sees the personal-user figure and assumes it caps their agent account. It was written for a personal profile. They should keep that audience visible and ask for the agent rule instead.

The “no cap” promise. A third person reads the provider’s monthly statement and tells customers they can book anything at the opening minute. Check the table again. Monthly capacity and the opening-time restriction answer different questions. Before you accept work, ask three things: is this transaction permitted for the account, is the booking window open, and is the journey available?

In each case, the fix is the same: keep the unit in view.

How do you ask support a clear question?

If you need a number confirmed, don’t write “is the limit 4?”. Support can only approve or deny a number you already have, which doesn’t help if the number is wrong. Ask it the other way round. For example:

• Which numerical limit applies to my account for Tatkal on one train?
• What is it counting: PNRs, passengers, or attempts?
• What’s the official basis, and from what date?

Add the train, class, quota and journey date. Take sensitive customer details out of the message.

When you get a reply, keep its full wording, who said it and the date. Write down what it counts, which account, what period, and any conditions. If the reply answers only the booking window, mark that topic answered and leave the per-train question open. If two replies disagree, show both to your PSP and ask which one applies. Don’t pick the biggest number from one and the loosest condition from the other.

Common questions

Does the four-passenger Tatkal maximum mean four bookings per train? No. That source is about passengers on one Tatkal PNR. A per-agent, per-train booking cap is a different question, and it’s still unconfirmed here.

Does monthly capacity mean the account can book in every opening minute? No. The opening-day Tatkal restriction for authorised agents is a separate rule. A monthly statement doesn’t change when a booking is allowed.

Will a higher plan get me more seats? No. Don’t infer seat stock from your registration plan. SiOnline states that agents see the same availability as personal users or railway PRS counters.

What should I tell a customer while the cap is being checked? Say you need to confirm the applicable rule before taking the work. Name exactly what you’re unsure about. Offer only a permitted alternative that the customer is happy with.

Sources

• IRCTC retail agent policy, retrieved 18 October 2026.
• Indian Railways Tatkal announcement, published by PIB on 11 June 2025, retrieved 18 October 2026.
• IRCTC website terms, reopened 18 October 2026.
• IRCTC personal Aadhaar guide, reopened 18 October 2026.

Reconfirm applicable rules and charges before payment or booking.