PNR Status & Availability Codes

Reviewed on August 1, 2026 • Author: Railmonk Research Team • Reviewer: Travel Review Desk • 9 min read

Rules reviewed

A PNR tells you more than most people read off it. The status line is two pieces of information printed side by side, one of which is history and one of which is live — and confusing the two is why travellers panic about a confirmed ticket, or turn up at the station believing a waitlisted one cleared.

Railmonk does not carry live PNR data. Checking an actual PNR needs a live feed from Indian Railways — use the IRCTC portal or NTES for that. This page is about understanding what the answer means once you have it.

What the number itself is

A Passenger Name Record is 10 digits, and it covers the whole booking rather than one traveller — up to six passengers on the same journey share a single PNR. The leading digit identifies which Passenger Reservation System issued it, which is occasionally useful for understanding where a booking originated and almost never useful to a passenger.

What matters is that the PNR is the unit the railway thinks in. Cancellations, refunds, TDR claims and chart entries all attach to it, which is why a partly-cancelled group booking behaves the way it does: one record, several passengers, individual statuses inside it.

Booking status and current status are different columns

Every passenger on the PNR has two statuses:

  • Booking status — what the ticket was when it was issued. It is a frozen historical record. It does not update, ever.
  • Current status — where the ticket stands right now. This is the one that moves.

So a passenger showing booking status GNWL 42 and current status CNF/B4/21 is confirmed in coach B4, berth 21. The 42 is not a waitlist they are still sitting on; it is where they started. Equally, a booking status of CNF with a current status of CAN means a confirmed ticket that was later cancelled.

If you only read one field, read the current status. Screenshots circulated in family groups almost always show the booking status, because it is the one printed most prominently on the e-ticket. It is also the one that is out of date the moment anything happens.

Status codes you will see

CodeWhat it means
CNFConfirmed. A berth is yours. Coach and berth appear at charting if they are not shown already.
RACReservation Against Cancellation. You may board and you have a seat — a shared side-lower berth — but not a berth to yourself unless it clears.
WLWaitlisted. No seat yet. On an e-ticket, a fully waitlisted booking is cancelled automatically at charting.
CAN / CANCELLEDThe ticket was cancelled, either by you or automatically at charting.
MODThe booking was modified after issue — typically a boarding point change.
B4/21, S7/54Coach and berth. The letter group is the coach, the number is the berth within it.

Waitlist codes carry a prefix telling you which queue you are in — GNWL, RLWL, PQWL, TQWL and others. The prefix matters far more than the number, because the queues clear at wildly different rates. That is a subject in itself: the waitlist and RAC guide covers what each prefix means for your odds, and the confirmation chances tool will score a specific code and number.

Availability codes when you are searching for a train

Before you have a PNR at all, the availability grid uses its own vocabulary. These are not statuses — they describe what the railway will sell you right now.

CodeWhat it means
AVAILABLE 0126Berths free right now. Book and you are confirmed immediately.
RAC 12Confirmed berths are gone; you would be twelfth in the RAC queue and can still travel.
WL 45You would be issued a waitlisted ticket at number 45 in that queue.
REGRET / NOT AVAILABLEThe waitlist is full. Nothing further is being sold in that class and quota.
CURR_AVBLCurrent availability — berths released after charting, bookable until departure.
CHART NOT PREPAREDCharting has not run yet, so no allotment exists to show.
TRAIN DEPARTEDThe train has left. Nothing more can be booked on it.

REGRET is the one worth understanding properly. It does not mean the train is heavily booked and you should keep refreshing; it means the waitlist has hit its ceiling and the railway has stopped issuing tickets in that class and quota. Refreshing helps only if cancellations reopen the list. A different class, a different quota or VIKALP are the realistic moves.

What charting changes

The first chart is prepared at least 10 hours before departure — moved up from 8 hours in December 2025 — and the final chart around 30 minutes before. Charting is when the status you have been watching turns into an actual berth allotment.

At that moment several things happen at once:

  • Confirmed passengers get their coach and berth numbers.
  • RAC passengers are allotted their shared side-lower seats, and some clear to full berths.
  • Fully waitlisted e-tickets are cancelled automatically and refunded less clerkage.
  • Unused quota berths are released and start appearing as CURR_AVBL.

The chart preparation tool works out when charting falls for a given departure. The practical consequence of the earlier first chart is that you learn your fate with most of a day in hand rather than an evening — enough time to actually arrange an alternative, which was the point of the change.

Movement between the two charts is limited. Most waitlist clearing happens before the first chart, not in the ten hours after it. If you are still deep in a waitlist when the first chart runs, treating that as close to final is the realistic reading, not a pessimistic one.

The short version

  • A PNR is 10 digits and covers up to six passengers.
  • Booking status is frozen history; current status is live. Read the second one.
  • CNF without a berth number just means charting has not run yet.
  • REGRET means the waitlist is closed, not that you should keep trying.
  • CURR_AVBL is post-charting availability — worth checking even on a train that looked full.
  • Fully waitlisted e-tickets cancel themselves at charting; RAC tickets do not.

None of this requires checking a PNR more than a couple of times a day. The status changes when the railway runs a process, not when you refresh — and the processes happen on a schedule you can look up.