India · Travel
Pick your waitlist code and number to see what it actually means — and an honest, indicative estimate of whether it will confirm.
General Waitlist
GNWL 12 · General Waitlist
Very likely to confirm
Confirmation chance indicatively 80–95%+. This is a rule-of-thumb estimate, not a prediction for your specific train.
At charting: If still fully waitlisted at charting, an e-ticket is auto-cancelled and refunded minus clerkage.
Issued when the journey starts at (or near) the train’s originating station. Draws from the largest quota pool, so it clears from the full set of cancellations — the best-confirming waitlist by far.
If still fully waitlisted at charting, an e-ticket is auto-cancelled and refunded minus clerkage.
Issued for journeys between intermediate stations. Clears only against cancellations in that remote-location quota — a much smaller pool than GNWL, so identical waitlist numbers confirm noticeably less often.
Same charting behaviour as GNWL: fully waitlisted e-tickets drop automatically with a refund minus clerkage.
A single small pool shared by several intermediate stations (typically origin-to-midway or midway-to-destination legs). Many stations competing for one tiny quota makes PQWL one of the weakest waitlists.
Fully waitlisted e-tickets are auto-cancelled at charting with a refund minus clerkage.
Issued when booking from the originating station to a smaller “roadside” station en route. The quota is modest and cancellations against it are few, so it clears slower than GNWL.
Fully waitlisted e-tickets are auto-cancelled at charting with a refund minus clerkage.
Waitlist against the Tatkal quota (older PNRs show CKWL). Tatkal tickets are booked at a premium a day before travel and cancelled confirmed Tatkal tickets get no refund — so almost nobody cancels, and TQWL barely moves. During charting, GNWL is also cleared into vacant Tatkal berths before TQWL.
A still-waitlisted Tatkal e-ticket is auto-cancelled at charting and refunded minus clerkage (the Tatkal charge component is part of the refunded fare only when the ticket never confirmed).
Not a waitlist — RAC guarantees you can board and travel, initially on a shared side-lower berth (two RAC passengers per berth). A full berth is allotted on board as confirmed passengers cancel or no-show.
RAC tickets are NOT auto-cancelled at charting. If you decide not to travel, cancel (or file a TDR) at least 30 minutes before departure or the fare is forfeited.
Read your PNR status
Find the code and number on your ticket, e.g. GNWL 12/WL 8 — the second number is your current position.
Pick code and number
Select the waitlist code, enter the current number, and set how far away the journey is.
Read the band honestly
The estimate is a rule-of-thumb ordering — GNWL clears best, PQWL and TQWL worst — adjusted for depth, time and season.
Have a plan B
For "unlikely" bands, look at alternate trains or dates now rather than at charting, when everything else is also sold out.
Every waitlisted ticket is a claim on future cancellations in one specific quota — which is why the code matters more than the number. GNWL 25 from the originating station regularly confirms; PQWL 25 on the same train usually will not, because the pooled quota it draws from might be a handful of berths shared across several stations.
Movement comes in two waves. Cancellations trickle in over the booking window as plans change. Then, about four hours before departure, chart preparation releases every unused reserved quota — emergency, headquarters, defence, vacant Tatkal berths — into the queue at once. This is why a stuck waitlist can jump twenty places at the end, and why the final answer only truly arrives at charting.
Know your downside before you wait it out. A fully waitlisted e-ticket that fails to confirm is auto-cancelled with a near-full refund, so waiting costs little. An RAC ticket travels either way. The trap is a Tatkal waitlist during festival season — the queue barely moves, and the time you spend hoping is time you are not booking an alternative. If your ticket does confirm and plans later change, our cancellation charges calculator shows what cancelling costs at each stage, and the TDR refund checker covers RAC and partial-confirmation refund cases.
Editorial Trust Panel
Author
Reviewed by
Last reviewed
July 19, 2026
Content update
Auto-updated on Jun 28, 2026
Scope: Quota definitions and charting behaviour follow published Indian Railways rules. The confirmation-chance band is a heuristic estimate — Indian Railways publishes no per-train probabilities, and actual outcomes vary by train, route, date and season.
A PNR status like GNWL 34/WL 12packs two facts: which quota’s cancellations you are waiting on, and how many people are ahead of you. This page decodes all six codes — GNWL, RLWL, PQWL, RSWL, TQWL and RAC — and turns your code, number, lead time and season into an honest indicative band instead of a false precise percentage.
It also tells you what happens if the ticket never confirms: waitlisted e-tickets drop automatically at charting with a refund, while RAC tickets stay valid for travel and need an active cancellation if you will not board.
GNWL 12 on a ticket booked three weeks out, outside festival season: a good-to-very-good chance — twelve general-quota cancellations over three weeks plus the charting release is a normal outcome. The same number as TQWL for tomorrow’s train is the opposite story: Tatkal tickets are rarely cancelled, and vacant Tatkal berths clear GNWL first at charting.
The estimate starts from each quota’s observed clearing strength (RAC > GNWL > RLWL > RSWL > PQWL > TQWL), scales it down as the waitlist number deepens, adds a lead-time adjustment, and applies a festival-season penalty. The result maps to five bands from “very likely” to “very unlikely” — deliberately a band, because no public data supports an exact percentage.
They are waitlists against different quotas. GNWL (General Waitlist) applies to journeys from the train’s originating station and clears best because it draws on the largest pool of cancellations. RLWL (Remote Location) and RSWL (Roadside Station) cover intermediate-station journeys with much smaller quotas. PQWL (Pooled Quota) is a single small pool shared by several stations, and TQWL is the Tatkal waitlist — the weakest of all, since confirmed Tatkal tickets are non-refundable and rarely cancelled.
No tool can promise it, but GNWL is the best-clearing waitlist. A low GNWL number (roughly under 15–20) booked well before the journey confirms on most trains and dates, because it clears from all cancellations plus the emergency-quota release at charting. High numbers, last-minute bookings, and festival-season travel pull the odds down sharply.
RAC (Reservation Against Cancellation) guarantees travel — you board with a shared side-lower berth, two RAC passengers per berth — but not a full berth. Most RAC tickets are upgraded to a full berth before or during the journey as confirmed passengers cancel or do not show up. Unlike waitlisted e-tickets, RAC tickets are not auto-cancelled at charting.
Two reasons. Confirmed Tatkal tickets carry no cancellation refund, so almost nobody cancels one — the queue barely moves. And at chart preparation, vacant berths in the Tatkal quota are used to clear the general waitlist (GNWL) first, ahead of TQWL.
A fully waitlisted e-ticket is automatically cancelled when the chart is prepared, and the fare minus a clerkage charge is refunded to the payment source — you cannot board with it. RAC and partially confirmed tickets are different: they remain valid for travel, and if you choose not to travel you must cancel or file a TDR at least 30 minutes before departure.
Two windows: the days right after booking opens (agents and plans churn), and chart preparation about 4 hours before departure, when unused quotas — emergency, defence, headquarters and vacant Tatkal berths — are released to clear the queue. A ticket that looks stuck at WL 8 for days can still confirm at charting.