Watchlist
Save a PNR and re-check it in one tap. It lives on your device; sign in only if you want it to follow you between devices — with merge and undo when it syncs.
Ten digits from your ticket, one live request to the source. Every field is shown exactly as returned, labelled with where it came from and when — never a guess, never an invented confirmation chance.
The 10 digits printed top-left on your ticket, or in your booking SMS.
| Stn | Destination | Km | Status |
|---|---|---|---|
| GA | The train, drawn | 012 | |
| 01 | Operating principles | 064 | |
| 02 | How it works | 138 | |
| 03 | The record you get | 212 | |
| 04 | Reliability | 318 | |
| 05 | On the roadmap | 407 | |
| 06 | More than a check | 530 | |
| 07 | Where it gets used | 644 | |
| 08 | Questions | 730 | |
| END | Run a check | 781 |
Take a check apart and each piece does one job: ask the source once, show exactly what came back, and say when. Nothing in it guesses.
Scroll · the drawing turns, comes apart, couples up and departs
Strict real-only policy: if the source is silent, the product says so and stops. Nothing on this sheet is a marketing estimate.
The 10-digit number printed top-left on your ticket, or in your booking SMS, punched in 3–3–4 as it appears there.
One live request to the railway source at the moment you press Run. Nothing pre-computed, nothing filled in.
Status, coach and berth, train and journey. Every field carries its source and the time it was retrieved.
A result is the reservation record as the source holds it: current status per passenger, coach and berth where allotted, the train and journey, and the retrieval time. Where the source did not send a field, the record says “not returned”. The specimen here is generated from the labelled development fixture — it is design material, not a real reservation.
One booking often holds several passengers in different states — this specimen shows a party of three: one confirmed, one RAC, one still waitlisted.
12627 · Karnataka Express · SBC → NDLS
Sun, 22 Nov · departs 19:20 IST · quota GN
| Passenger | Booked | Current | Coach · berth |
|---|---|---|---|
| Passenger 1 | WL | CNF | B1 · 12 LB |
| Passenger 2 | WL | RAC 4 | Not allocated |
| Passenger 3 | WL | WL 9 | Not allocated |
Retrieved 02:15 IST from the development fixture · every field as returned, none invented
Trakline asks for your reservation at the moment you check and shows exactly what comes back.
PNR checks operational
Read the data policyEach ships only when a verified source stands behind it — the same rule the check follows.
Save a PNR and re-check it in one tap. It lives on your device; sign in only if you want it to follow you between devices — with merge and undo when it syncs.
Plan a journey before you book. Pick the stations, a date and the classes you would travel in, and every train on the route answers at once — open berths and the fare, four dates at a time.
How results matched outcomes, published only once there are real outcomes to compare. Until then it reads “not available yet” — nothing on it will ever be invented.
A crowded platform in harsh daylight, or a moving berth at night — one hand free, low attention. The interface is built to be read in one glance, with day and night faces that follow your device.
Installable as an app, so the check stays one tap away for the days you keep re-checking the same ticket before the chart.
No. Trakline is an independent product. It requests your reservation record from a verified railway data source and shows exactly what came back.
No. A check needs only the 10-digit PNR. An account adds one thing: a watchlist that syncs between your devices. It stays optional.
PNRs and passenger names are never written to our logs. Your PNR is used to make the request; recent checks stay on your device and you can clear them any time.
Because the source did not send it. The product never fills a gap with a guess — it fails closed: no source, no claim.
No, and it never will here. Invented odds are the one thing this product exists to not show you. You get the record, its source, and its retrieval time.
From a third-party railway data service. Trakline asks it for your reservation when you run a check and shows only the fields it returned, with the time of retrieval. If the service does not answer, Trakline says so and shows nothing in its place.
The first reservation chart decides waitlisted and RAC tickets. It is prepared at least 10 hours before departure, or at 20:00 the night before for trains leaving between 05:00 and 14:00. Save the PNR to your watchlist and re-check as the chart approaches — in Indian Standard Time, everywhere.
Only what the railway returned — nothing filled in, nothing predicted.
The 10 digits printed top-left on your ticket, or in your booking SMS.
About once a month: new features and service changes.
One email to confirm. Unsubscribe in one click. We never sell your address. Privacy notice