Train Ticket Reservation Android App with PNR Enquiry and Running Status

Booking a train ticket in India means juggling three separate jobs: finding the right train, checking whether a berth is available, and chasing the PNR and running status on different screens or apps. A traveller often checks the PNR in one app and live running status in another, and each hop risks a mistyped number or a stale status. For a student project, that fragmentation is the real problem to solve: one Android app must carry the whole journey — search, availability, booking, PNR enquiry and live tracking — against a single consistent data model. The Train Ticket Reservation app in this project does exactly that. It searches trains between stations, shows confirmed, RAC and waitlisted availability across 5 classes, books a berth, and then follows the same booking through its PNR record and the train's station-by-station running status. The demo uses published timetable values for the Mumbai–Delhi corridor, including the 12951 Mumbai Rajdhani Express.

The app is a thin client over a booking API: every screen reads the same reservation record, so a berth booked in search is what the PNR and running-status screens read. A passenger enters origin, destination, date and class; the train service returns trains with scheduled times, distance and berth availability. Choosing a train and berth creates a reservation, and the API returns a 10-digit PNR, the single pointer to that booking. The PNR screen sends the 10-digit number back to the API and renders the stored record: train, date, route, class, chart status and each passenger's berth. Running status instead reads the published timetable and latest station events, marking each of the 8 halts departed, due or arrived 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.

1. The passenger opens the app and enters origin (Mumbai Central), destination (New Delhi), journey date and class.
2. The app calls the train-search API, which returns matching trains with scheduled times, distance and berth availability in each class.
3. The passenger picks a train and class, adds passenger names and ages, and confirms the booking.
4. The API creates the reservation and returns a 10-digit PNR; the booking appears under My Bookings.
5. PNR enquiry sends the 10-digit number to the same API and renders the stored record — train, chart status and each passenger's coach and berth.
6. Running status reads the train's published timetable and station events, then renders the 8-station timeline with scheduled versus actual times and the delay at each halt.

Train app vs separate 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 train search with live berth availability, its 10-digit PNR enquiry with per-passenger berth details, and its station-by-station running-status timeline. Train search covers 5 classes — Sleeper, AC 3 Tier, AC 2 Tier, AC First Class and Chair Car — with confirmed, RAC and waitlisted status shown per train. PNR enquiry resolves a 10-digit number to the full reservation record, including chart status and each passenger's coach and berth. Running status follows the 12951 Mumbai Rajdhani Express across its 8 published halts with scheduled and actual times and the delay at every stop. The booking flow then turns a chosen berth into a 10-digit PNR, and the saved-bookings list keeps every journey in one place. Around those capabilities, the app adds a clean Android interface built for one-handed use on a phone.

• [Train search with berth availability] Search by origin, destination, date and class; results show departure and arrival times, journey duration, distance, fare and confirmed / RAC / waitlisted status for each train.
• [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.
• [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 current speed and stations covered.
• [Booking flow with passenger details] Add passenger names and ages, pick a class and berth preference, and confirm the booking; the app returns a 10-digit PNR and saves the booking.
• [My Bookings list] Saved bookings stay in one list with their current status, so upcoming journeys are visible without re-entering a PNR.
• [Class and fare comparison] All 5 classes are shown with per-person fares, so the traveller can compare Sleeper against AC tiers before choosing.
• [Demo dataset included] The demo ships with 6 trains, 3 sample PNR records and the 8-station running-status timeline, so every screen works end to end without a live railway connection.

• Complete Android app source code (Java, Android Studio project)
• MySQL database schema with a PHP REST API for trains, bookings and PNR lookup
• Working single-file HTML demo of the 3 screens (booking, PNR enquiry, running status)
• Demo dataset: 6 trains, 3 sample PNR records and the 8-station 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, berth allotment, 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.