Railway · Reservation Insight
Understand which reservation quota controls your boarding station.
Indian Railways divides reserved seats into quotas attached to points along a train's route. That is why a train can show a hundred seats free from its origin and a wait-list from a station two hours later. This tool explains those quotas, and works out which stations appear to share one.
When you book a reserved ticket from an intermediate station, you are not drawing on the same pool of seats as someone boarding at the origin. Indian Railways splits reserved accommodation into quotas — General at the origin, Remote Location and Pooled quotas covering stretches further along the line — and it does not publish how those quotas are divided or how large each one is.
Railway Quota Insight does two things. It explains the quota system in plain language, so a wait-list code on your ticket actually means something. And it builds a picture, from repeated observation of public availability data, of which stations appear to share a reservation pool on a given train — always labelled as an inference, never presented as an official figure.
The wait-list code on your ticket tells you which pool of seats you are queued against. That matters far more than the number next to it.
Issued against the general quota, normally attached to the train's originating station. It is usually the largest pool on the train, so it sees the most cancellations. GNWL 40 will often confirm where RLWL 8 will not, because the number is measured against a much bigger pool.
Issued when you board at an intermediate station that holds its own small reservation pool, separate from the origin. It clears mainly through cancellations within that specific pool, which is why a low RLWL number can still be difficult. Seats going spare at the origin do not help an RLWL ticket.
A pooled quota is shared across several intermediate stations along a stretch of route rather than belonging to a single station. It is typically used for shorter journeys that do not run through to the train's final destination.
RSWL is a roadside-station wait-list, allotted for short-distance travel from smaller stations. RAC — Reservation Against Cancellation — is not a wait-list at all: it is a confirmed boarding right with a shared berth, and it sits between wait-listed and fully confirmed.
Here is a real observation from the dataset, on a single train and class, for the same journey dates.
| Journey date | Boarding at the origin | Boarding 200 km down the line |
|---|---|---|
| 09 Sep 2026 | Available 106 | RLWL 2 |
| 15 Sep 2026 | Available 169 | RLWL 6 |
| 24 Sep 2026 | Available 143 | RLWL 1 |
Over a hundred berths free at the origin, and a wait-list at the intermediate station on the very same day. Nothing is wrong with either figure — they are simply different pools. Knowing that changes how you read an availability screen, and whether a wait-listed ticket is worth holding.
Over 10,000 trains and 8,600 stations, with full stop-by-stop routes, timings, distances and day numbers.
Which station's pool appears to control each stretch, and which stations look like they share it.
Recorded enquiry responses over time, showing both the status a new booking would get and where the earliest existing booking now stands.
Each inferred quota group carries a score and the evidence behind it, so you can tell a well-supported finding from a working hypothesis.
Observed, inferred, estimated and presumed are marked distinctly. Nothing derived is ever dressed up as official.
Every page is backed by a public endpoint, so the data is usable in your own tools. No key, no sign-up.
Availability is collected from the same public passenger enquiry any traveller can use, one query at a time, with a person answering the site's verification question on every request. Nothing is automated around that step, and the pace is deliberately slow — roughly one operator session a day.
Because passengers within one quota pool draw on the same seats, their availability moves together and their wait-list carries the same prefix. Comparing boarding points and looking for where that prefix changes is what reveals the pool boundaries. The estimate of a quota's size is simply the most berths ever seen free at once, which makes it a floor rather than a figure.
What this means in practice: coverage is thin and growing. Most trains have no availability data yet, and the tool says so plainly rather than showing an empty table. Where a conclusion rests on limited evidence, it is marked low confidence and should be read as a hypothesis.
General Waiting List — the queue against the general quota, normally attached to the train's originating station. It is usually the largest pool on the train and sees the most cancellations, which is why GNWL numbers tend to clear better than remote-location ones.
Because the pool behind it is much smaller. An RLWL ticket clears mainly through cancellations in that one station's quota, so RLWL 5 can be a worse position than GNWL 50.
No. Quota boundaries and allocations are not published. Everything this tool says about them is inferred from observed availability and labelled as such.
No. This is informational only. For booking, official status, fares and final reservation information, use Indian Railways or IRCTC directly.
Yes, and there is no sign-up. The JSON API is open too.
No. Ornova Labs is an independent software studio and is not affiliated with, endorsed by, or operated by Indian Railways, IRCTC or CRIS.