• Hey there! Welcome to TFC! View fewer ads on the website just by signing up on TF Community.

Tatkal: All tips, tricks and cards?

Batman

TF Premier
VIP Lounge
I booked a tatkal ticket ~3 years ago. It was thrilling, but easy.
I tried to book tatkal 3 days ago. I failed consistently.

So, here I am, looking for all tips and tricks to book a tatkal ticket - AC or sleeper.

Note that tickets go out in 2 minutes (10.02 or 11.02) in the route on which I travel. So I need all tips relevant to that.
 
Long ago I used to this but it failed to work now:

1. Use IRCTC official Android app (website on laptop is slightly slower).
2. Login at 9.58, check for 3AC tickets at exactly 10AM
3. Master user list, book ticket if confirmed only. All of this is done by 11.01 or last 11.02. Tickets are still available.
4. BHIM UPI option. BHIM gets autopay ping. Payment confirmed, ticket booked.

This time though, I got no ping on BHIM UPI.
 
Use the IRCTC gateway (It is the first option and is selected by default. So, save a few msecs by not changing it) for UPI payment instead of BHIM UPI.

Keep your UPI ID on the top of your mind. If your UPI ID is a simple one, that will be a plus.

Keep the UPI app, through which you do the payment, open in the background....Notification will come soon.

BHIM UPI gateway is great and shows (or at least it used to show) the QR code. But this gateway doesn't always work during the tatkal sessions.
 
Long ago I used to this but it failed to work now:

1. Use IRCTC official Android app (website on laptop is slightly slower).
2. Login at 9.58, check for 3AC tickets at exactly 10AM
3. Master user list, book ticket if confirmed only. All of this is done by 11.01 or last 11.02. Tickets are still available.
4. BHIM UPI option. BHIM gets autopay ping. Payment confirmed, ticket booked.

This time though, I got no ping on BHIM UPI.
Happened with me few times, now whenever I try to book tickets in tatkal I add money in irctc wallet
 
Use the IRCTC gateway (It is the first option and is selected by default. So, save a few msecs by not changing it) for UPI payment instead of BHIM UPI.

Keep your UPI ID on the top of your mind. If your UPI ID is a simple one, that will be a plus.

Keep the UPI app, through which you do the payment, open in the background....Notification will come soon.

BHIM UPI gateway is great and shows (or at least it used to show) the QR code. But this gateway doesn't always work during the tatkal sessions.
I do all of this bhai. I have the BHIM app open in a different phone, with autopay page refreshing.

No ping sadly.
 
I have been using JioFinance app and it is working fine. Booked two Delhi-Mumbai tatkal tickets yesterday and today..
Uff. Delhi Mumbai route. You're a God. Teach me more of your tricks.

I'll download this app right away.

Edit: What is this Jio Finance app? Android Play Store doesn't display it for some reason.
 
I booked a tatkal ticket ~3 years ago. It was thrilling, but easy.
I tried to book tatkal 3 days ago. I failed consistently.

So, here I am, looking for all tips and tricks to book a tatkal ticket - AC or sleeper.

Note that tickets go out in 2 minutes (10.02 or 11.02) in the route on which I travel. So I need all tips relevant to that.
Use chrome extension which is used to pre fill data
 
Uff. Delhi Mumbai route. You're a God. Teach me more of your tricks.

I'll download this app right away.

Edit: What is this Jio Finance app? Android Play Store doesn't display it for some reason.
I don't know any 'tricks'.. You have already mentioned all the things: I use the android app or the IRCTC website..use the timer shown on the IRCTC website only (you can find it on top, on some days it is not there though..IRCTC guys are mysterious) to click on the '3A/2A' button exactly at 10 AM. The key here is to NOT click on it 1-2 seconds before 10AM...because it will then show the loading animation for some time and you will have to click on it again since you had clicked before 10AM.

Since I mostly book the tickets for a single traveller, this works for me...I believe using the master user list is not optimal in such cases as fetching the master user list takes some time. I delete the master user list (if there is any) before going for the tatkal bookings. It saves a good amout of time which goes in fetching it. I then manually enter the traveller details (quickly 😛).

For the payment, as I said, I use the IRCTC UPI payment gateway.

I haven't been lucky with using chrome extentions to fill the details automatically. IRCTC seems to be behind fixing the loopholes which allow continued use of such extensions. If the extension fails to do its job, you have lost the ticket.

One more major thing could be: I have access to a really superfast internet connection...

Link to the JioFinance app (but I don't think the app is doing anything here, other UPI apps like GPay should work fine too): https://play.google.com/store/apps/details?id=in.jfs.jiofinance
 
Last edited:
Kabhi Bihar se Southern India ke tickets try kro, saare extension app dhare ke dhare reh jayenge
I used to consider myself a Pro. Did a lot of Bihar - Delhi Sleeper tickets long ago.

Those who travel this route would know how praised is this train "Sampark Kranti". It took 14 hours for a journey where Rajdhani took 12 hours, and Magadh express took 24.

I boasted about getting tatkal sleeper in that train. Good old days, long gone now.
 
I don't know any 'tricks'.. You have already mentioned all the things: I use the android app or the IRCTC website..use the timer shown on the IRCTC website only (you can find it on top, on some days it is not there though..IRCTC guys are mysterious) to click on the '3A/2A' button exactly at 10 AM. The key here is to NOT click on it 1-2 seconds before 10AM...because it will then show the loading animation for some time and you will have to click on it again since you had clicked before 10AM.

Since I mostly book the tickets for a single traveller, this works for me...I believe using the master user list is not optimal in such cases as fetching the master user list takes some time. I delete the master user list (if there is any) before going for the tatkal bookings. It saves a good amout of time which goes in fetching it. I then manually enter the traveller details (quickly 😛).

For the payment, as I said, I use the IRCTC UPI payment gateway.

I haven't been lucky with using chrome extentions to fill the details automatically. IRCTC seems to be behind fixing the loopholes that allows continued use of such extensions. If the extension fails to do its job, you have lost the ticket.

One more major thing could be: I have access to a really superfast internet connection...

Link to the JioFinance app (but I don't think the app is doing anything here, other UPI apps like GPay should work fine too): https://play.google.com/store/apps/details?id=in.jfs.jiofinance
Let me try this tomorrow. Downloading the app as well.

I had forgotten about the time trick on website, ever since I booked via app. Same for master list - I'll delete it right away.

It never hurts to be a pro in tatkal bookings.
 
I will tell you one interesting trick which I discovered to AVOID booking Tatkal. It's by no means, foolproof, and it's very likely that I got lucky. But the math seems to make sense. Don't hold me responsible if it doesn't work.

See the coach layout of your train and decide which class you want to book. See the number of seats in the said family of coach.

Now, go to indianrail website (not irctc), check availability 120 days from today by inputting the train number, source & destination.

Make a note of how many seats it shows available.

Now do the same for your required journey date and see what is the WL count and TYPE (RL/PQ/GN).

The chance of ticket confirmation priority is: (head office/defence quotas) > GNWL > RLWL > PQWL > everything else.

Head office & defence quotas are usually very small in number to make any significance.

  1. If your required-date availability enquiry is showing as RLWL, then change the source station to somewhere near the starting station of the train (may have to adjust the journey date accordingly). Keep doing this until you get GNWL.
  2. Once you arrive at a station which is giving you GNWL number, do some math as given below:
    • Total number of berths = berth per coach * number of coaches (A)
    • Berths that were confirmed-booked = number seen as available 120 days in advance for the same pair of source-destination. (B)
    • Effective number of berths which have been pushed under WL = (A) - (B) [C]
  3. WL will typically have two numbers, which says WL X/Y - where X is the max number, and Y is the current number (or the number you will get when you book).
  4. If the number Y is <= number obtained in Step 2 [C], you can take a risk & book the WL ticket, your ticket will most likely get confirmed at the time of charting. If you wish, you can consider some margin of safety in this.
I did this study on a few trains and discovered roughly 30% seats are only released for confirmed-booked status. Everything else is pushed by railways under WL, I don't know the reason behind this.

For highest possible chances - book GNWL only - it may even mean paying a bit higher fare compared to normal, but when you do that, mark the "boarding at" your station. It's very likely cheaper in comparison to Tatkal & Premium Tatkal though.

RLWLs also get confirmed, but it's a gimmick. GNWL has highest priority since AFAIK it is allocated only to full length passengers.

Based on the above math, I recently made a relative book WL 25,26 in a train having just ONE 2A coach. 2 hours before the charting time, the WL count went down to 15,16 and few minutes before charting, it was WL 8,9 and then it was confirmed.

Although for booking GNWL, the relative had to book a signifnicantly longer journey 1798 km journey vs 1048 km. Fare difference of ₹790.

Different charting time - the chart was prepared previous day at the origin station and relative boarded next day afternoon at their station which falls en route.
The extra fare difference was probably more than Tatkal, but at least significantly less uncertainty and headache compared to Tatkal.



That said, the best way to have certainty while booking Tatkal is to use a payment provider which doesn't require OTP - HDFC Credit/Debit cards can be authenticated with a static password, or you can take Axis Bank OneTouch Token (this I have used for Tatkal booking).

The milliseconds delay in payment processing is the game changer. OTP is usually the delay because too many parties involved in it (IRCTC, Bank, Telco, etc).
 
I will tell you one interesting trick which I discovered to AVOID booking Tatkal. It's by no means, foolproof, and it's very likely that I got lucky. But the math seems to make sense. Don't hold me responsible if it doesn't work.

See the coach layout of your train and decide which class you want to book. See the number of seats in the said family of coach.

Now, go to indianrail website (not irctc), check availability 120 days from today by inputting the train number, source & destination.

Make a note of how many seats it shows available.

Now do the same for your required journey date and see what is the WL count and TYPE (RL/PQ/GN).

The chance of ticket confirmation priority is: (head office/defence quotas) > GNWL > RLWL > PQWL > everything else.

Head office & defence quotas are usually very small in number to make any significance.

  1. If your required-date availability enquiry is showing as RLWL, then change the source station to somewhere near the starting station of the train (may have to adjust the journey date accordingly). Keep doing this until you get GNWL.
  2. Once you arrive at a station which is giving you GNWL number, do some math as given below:
    • Total number of berths = berth per coach * number of coaches (A)
    • Berths that were confirmed-booked = number seen as available 120 days in advance for the same pair of source-destination. (B)
    • Effective number of berths which have been pushed under WL = (A) - (B) [C]
  3. WL will typically have two numbers, which says WL X/Y - where X is the max number, and Y is the current number (or the number you will get when you book).
  4. If the number Y is <= number obtained in Step 2 [C], you can take a risk & book the WL ticket, your ticket will most likely get confirmed at the time of charting. If you wish, you can consider some margin of safety in this.
I did this study on a few trains and discovered roughly 30% seats are only released for confirmed-booked status. Everything else is pushed by railways under WL, I don't know the reason behind this.

For highest possible chances - book GNWL only - it may even mean paying a bit higher fare compared to normal, but when you do that, mark the "boarding at" your station. It's very likely cheaper in comparison to Tatkal & Premium Tatkal though.

RLWLs also get confirmed, but it's a gimmick. GNWL has highest priority since AFAIK it is allocated only to full length passengers.

Based on the above math, I recently made a relative book WL 25,26 in a train having just ONE 2A coach. 2 hours before the charting time, the WL count went down to 15,16 and few minutes before charting, it was WL 8,9 and then it was confirmed.

Although for booking GNWL, the relative had to book a signifnicantly longer journey 1798 km journey vs 1048 km. Fare difference of ₹790.

Different charting time - the chart was prepared previous day at the origin station and relative boarded next day afternoon at their station which falls en route.
The extra fare difference was probably more than Tatkal, but at least significantly less uncertainty and headache compared to Tatkal.

=================

That said, the best way to have certainty while booking Tatkal is to use a payment provider which doesn't require OTP - HDFC Credit/Debit cards can be authenticated with a static password, or you can take Axis Bank OneTouch Token (this I have used for Tatkal booking).

The milliseconds delay in payment processing is the game changer. OTP is usually the delay because too many parties involved in it (IRCTC, Bank, Telco, etc).
Thank you for sharing this detailed thread. This deserves a post of its own, please consider doing that - and add use cases so that people can understand better.

My use case is slightly different.
1. The route where I travel is a mass booking tourism route - meaning that planned bookings well in advance that don't get cancelled, and the waiting list doesn't move (yes, tried and tested over years).
2. Many times, travel is required in next 3 days - tatkal is the only option. Waiting list is too high on all the trains.

Other than that, I like your approach. My family and friends has employees in railways, so I know a lot of this already (such as quota for each class, at a particular station, in each train) - but it is surprising you spent time to learn these details.
 
HDFC Credit/Debit cards can be authenticated with a static password, or you can take Axis Bank OneTouch Token (this I have used for Tatkal booking).
1. Using the HDFC cards would mean a need to mention the card details on the payment page, right? Or am I not aware of something? (I would very much like to use a credit card for tatkal ticket payments but don't use it due to the time-cost).

2. What is this Axis OneTouch token? Is it also for an Axis bank credit/debit card?
 
1. Using the HDFC cards would mean a need to mention the card details on the payment page, right? Or am I not aware of something? (I would very much like to use a credit card for tatkal ticket payments but don't use it due to the time-cost).

2. What is this Axis OneTouch token? Is it also for an Axis bank credit/debit card?
Same questions. This is promising. I've so many CCs (thanks to TF) that I can keep one separate and hidden just for Tatkal tickets 😅.

At least it'll see some usage 😛
 
Back
Top