Train Chart Vacancy

RLWL: what a remote location waiting list really is

RLWL stands for remote location waiting list. It is the queue for a small block of berths that one intermediate station holds for passengers joining there. It clears only when someone cancels a confirmed berth from that same block, and it is settled by that station's own chart. A low RLWL number can be harder to clear than a much higher GNWL one.

Last verified .

What does RLWL stand for, and who says so?

The expansion — remote location waiting list — is settled usage across the reservation industry. It is not our invention. But we have to be straight with you about its standing: we have not found any Indian Railways document that defines RLWL for passengers.

If you have the string in front of you, the status decoder reads it and tells you which queue you are in.

We looked. The Ministry of Railways published a list of reservation quota types in January 2019, in a written reply to a question in the Rajya Sabha. That list names seventeen quotas, including General, Tatkal, Premium Tatkal, Roadside, Pooled and RAC. It does not contain an entry called remote location. We do not know why. It may be that the remote-location arrangement is treated as part of another quota, or that the list was written to answer a narrower question. We are not going to guess.

What official documents do confirm is the machinery underneath the name. Railway Board Commercial Circular 10 of 2025 ends with the sentence: "These instructions also cover charting at remote locations." So remote locations exist, they are charted, and the Board writes rules for them. That much is documented. The rest of this page is the operating convention as the reservation industry understands it, and we say so wherever it applies.

Which berths can an RLWL ticket draw on?

A long-distance train does not sell one undivided pool of berths. Blocks of them are set aside for different groups and different stretches of the journey. A remote-location block belongs to one named intermediate station.

The practical consequence is the part people get wrong. A cancellation somewhere else on the train does not reach you. If a passenger who booked from the originating station gives up a confirmed berth, that berth goes back where it came from. Your queue does not move. Only a cancellation of a confirmed berth booked from your station's own block frees one for you.

That is why the number beside the letters matters less than the letters do. Here is what actually feeds each queue.

Which cancellation helps which queue?

Which cancellation frees a berth for which waiting-list queue, and whose chart settles it.
CodeThe queue belongs toA berth is freed for you whenSettled by
GNWLThe train's general quota, for its whole runAnyone cancels a confirmed general-quota berthThe originating station's chart
RLWLOne named intermediate station's own blockSomeone cancels a confirmed berth from that same blockThat station's own chart
PQWLOne pooled quota shared by the whole trainSomeone cancels a confirmed pooled-quota berthThe train's chart
RSWLA small roadside station's token allotmentSomeone cancels a confirmed berth from that allotmentThe chart covering that station
TQWLThe Tatkal quota, opened one day before travelA confirmed Tatkal ticket is cancelled, which is rareThe train's chart

The waiting-list code overview sets out what each abbreviation stands for. This page is about the one in the second row.

Why is a low RLWL number often worse than a high GNWL one?

Because the two numbers count places in queues of completely different sizes.

GNWL is a wide funnel. It is attached to the general quota, which covers the full route, is sold for the whole booking window, and is cancelled against constantly. Thousands of tickets, thousands of second thoughts. A general waiting list of thirty on a busy train is ordinary and often clears.

RLWL is a narrow funnel. One station, one small block, a closed system. An RLWL of three can sit unchanged for a fortnight, because in that fortnight nobody who booked a confirmed berth from that station changed their plans. Nothing is broken. There is simply nothing flowing into the pipe.

So the two numbers are not comparable, and any site that converts either of them into a confirmation percentage owes you its method and its sample. We publish no such number, because we have not measured one.

Which stations get a remote location quota?

We cannot give you a list, and we are not going to publish one we cannot stand behind.

Indian Railways does not publish, anywhere we can find, the set of stations that hold a remote-location quota on a given train, or the size of the block. It is decided train by train. The general shape of it is visible from ordinary experience: the stations that get their own block are usually substantial ones a long way down the route, where a lot of people join and where waiting for the origin's chart would leave them guessing for most of a day.

The one official hint at the reasoning comes from South Central Railway. Announcing the current charting timings on 20 December 2025, the zone said the change was aimed at reducing uncertainty "especially those travelling from remote areas to catch long-distance trains". That is the problem remote-location charting exists to solve.

The only reliable way to know whether your journey draws on a remote-location quota is the code on your own ticket. If it says RLWL, it does.

When does an RLWL ticket settle?

At the chart for the station you are joining from, not at the chart for the train's origin.

This is documented, and it is the single most useful thing on this page. South Central Railway's announcement of the current rule measures the charting deadline from "the scheduled departure time at the charting station". Commercial Circular 10 of 2025 says the Board's timings "also cover charting at remote locations". So a remote location works to its own clock.

Now put yourself on a train that started twenty hours before it reaches you. A passenger who boarded at the origin knew their fate yesterday evening. You will not know yours until much later, because your chart has not been made yet. Your status can sit still for days and then resolve very late in the day. That is the system working as designed, not a fault.

The timings themselves, the letters they come from and where our evidence for them stops are all on when the reservation chart is prepared. We are deliberately not restating them here, because there is exactly one page on this site that owns that rule.

How should you read your own RLWL number?

Honestly, and with low expectations of arithmetic.

What happens if it does not clear?

The same rules that apply to any waiting list. If every passenger on an e-ticket is still waitlisted after the chart, Rule 8(5) of the Railway Passengers (Cancellation of Ticket and Refund of Fare) Rules, 2015 drops the whole PNR from the chart and credits the fare back, less clerkage. You do not file anything, and you must not board.

What to do next, what the charges are and how current booking works are set out in still waitlisted after the chart. If your ticket instead shows RAC, you are travelling — see what an RAC ticket gets you. If the journey is between two intermediate stations you may see a different code again: PQWL and RSWL covers those. A Tatkal booking has its own queue and its own arithmetic, on the TQWL page.

Where our evidence stops

Three things on this page are documented and we have read them ourselves: the Board's instruction that its charting timings cover remote locations, the zonal announcement measuring the deadline from the charting station, and the refund rule for a fully waitlisted e-ticket.

Three things are convention, and we have found no published rule for any of them: the expansion of the abbreviation, the fact that a remote-location block is closed to cancellations from elsewhere, and the criteria a station has to meet to get one. We have described the convention because it is what the system does, and we have labelled it so that you can weigh it properly.

If you find an Indian Railways document that settles any of the three, we would like to see it, and we will change this page.

Sources

Every factual claim above was checked against these documents on .