Train PNR Status Android App with Coach Position and Running Status

A passenger with a confirmed railway ticket still faces three small questions at the station: is my PNR confirmed, which coach is mine, and where is the train right now? The Train PNR Status Android App answers all three from one 10-digit number, and its headline feature is a platform coach-position map that shows where each coach stops, so a passenger with luggage can stand at the right marker instead of running along the platform when the train arrives. The app reads a stored reservation record for the PNR, draws the train's coach order as blocks along the platform, and compares the published timetable with the latest station events to build a running-status timeline. The demo is built around the 12951 Mumbai Rajdhani Express from Mumbai Central to New Delhi, a 1,386 km overnight service, and it deliberately contains no booking flow, no fares and no payment — it only reports status, position and running information.

The app is a thin client over an enquiry API: every screen reads the same reservation record, so the coach and berth a PNR shows are the ones the coach-position map highlights. A passenger types a 10-digit PNR and the app sends it to the API, which returns the record — train, journey date, route, class, chart status and each passenger's coach and berth. The coach-position screen reads one ordered coach list for that train and date and draws each coach as a block along the platform, highlighting the block matching the PNR's coach code. Running status compares the published timetable against the latest station events, marking each halt departed, due or scheduled with its delay. A PNR is only a pointer to a reservation record, so the app never stores the ticket itself — it only reads the record's current state, which is why one booking can show confirmed, RAC or waitlisted passengers side by side.

1. The passenger opens the app and enters a 10-digit PNR, or picks one from the saved PNR list.
2. The app sends the PNR to the enquiry API, which returns the stored reservation record for that number.
3. The PNR screen renders the train, journey date, route, class, chart status and every passenger's coach, berth and status.
4. The coach-position screen reads the ordered coach list for the train and date and draws the 18-coach map along the platform.
5. The passenger's coach block is highlighted on the map with its stopping point and nearest coach-position board.
6. Running status reads the published timetable and station events, then renders the 8-halt timeline with scheduled versus actual times and the delay at each halt.

This app vs separate status apps

Tech stack:

• Android Studio, Java
• Android SDK (API level 33)
• Retrofit · REST API · JSON
• MySQL · PHP backend
• SQLite local cache
• HTML5 · CSS · JavaScript (working demo)
• Git

The app's strongest capabilities are its 10-digit PNR enquiry with per-passenger coach and berth details, its platform coach-position map that highlights the passenger's own coach, and its station-by-station running-status timeline for the 12951 Mumbai Rajdhani Express. PNR enquiry resolves a number to the train, journey date, route, class, chart status and each passenger's status — confirmed, RAC or waitlisted — shown separately. The coach map draws the train's 18-coach order from engine to tail along the platform, so the passenger can see that coach B4 stops near the middle of Platform 4 at Mumbai Central. Running status follows the train across its 8 published halts with scheduled and actual times and the delay at each stop. Around those three capabilities, the app adds a saved-PNR list and a demo dataset that works without any live railway connection.

• [10-digit PNR enquiry] Enter a PNR to see the train, journey date, route, class, chart status and every passenger's coach and berth, with confirmed, RAC and waitlisted shown separately.
• [Platform coach-position map] The train's full coach order is drawn as blocks along the platform; tapping a coach shows where it stops and the nearest coach-position board, and the passenger's own coach is highlighted.
• [Live running-status timeline] The 12951 Mumbai Rajdhani Express is followed across its 8 published halts, each with scheduled and actual times and the delay at that stop, plus journey progress and expected arrival.
• [Per-passenger berth details] Each passenger's coach, berth number and berth type (lower, middle, upper) are shown, so a family can see at a glance who sits where.
• [Chart-status display] The app shows whether the chart is prepared, which decides whether a waitlisted or RAC passenger has a confirmed berth yet.
• [Saved PNR list] Checked PNRs stay in one list with their current status, so a passenger can re-check a journey without retyping the 10-digit number.
• [Offline demo dataset] The demo ships with 3 sample PNR records and the 8-halt running-status timeline, so every screen works end to end without a live railway connection.
• [Coach-position reminder] The PNR result names the coach's stopping point on the platform, so the passenger knows where to stand before reaching the station.

• Complete Android app source code (Java, Android Studio project)
• MySQL database schema with a PHP REST API for PNR lookup, coach positions and running status
• Working single-file HTML demo of the 3 screens (PNR status, coach position, running status)
• Demo dataset: 3 sample PNR records, an 18-coach position map and the 8-halt running-status timeline
• Project report PDF (background, problem statement, methodology, system working, outcomes)
• PPT presentation for final review
• Viva Q&A preparation document (PNR lifecycle, coach-position logic, chart preparation, REST design)
• Typical build timeline: approximately 3–4 weeks from requirements confirmation to delivery (expected)
• To get this project, message Projectech on WhatsApp with the project name, your branch and your deadline — you receive a written quotation stating the exact scope, the price and the delivery date before any payment.