LiveArrived at destinationUpdated 0s ago
17603 PRASANTI NILAYAM EXPRESS
KACHEGUDA (KCG) → YESVANTPUR JN (YPR)
On time
Current position: Arrived at YELAHANKA JN(YNK) at 09:19 04-Oct (On Time)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
All stations
LIVE- KCGKACHEGUDAPF 3Actual 21:12 · +7 min
- SHNRSHADNAGARPF 4Actual 22:01 / 22:02 · +12 min
- MBNRMAHBUBNAGARPF 2Actual 22:39 / 22:40 · +11 min
- GWDGADWALPF 3Actual 23:45 / 23:47 · +16 min
- KRNTKURNOOL CITYPF 1Actual 01:15 / 01:16 · +32 min
- DHNEDHONE JNPF 1Actual 02:18 / 02:23 · +8 min
- GTLGUNTAKAL JNPF 6Actual 04:24 / 04:30 · +44 min
- GYGOOTYPF 5BActual 04:53 / 04:56 · +35 min
- ATPANANTAPURPF 1Actual 05:41 / 05:44 · +23 min
- DMMDHARMAVARAM JNPF 2Actual 06:12 / 06:16 · +7 min
- SSPNSAI P NILAYAMPF 1Actual 06:47 / 06:50 · +8 min
- PKDPENUKONDAPF 2Actual 07:10 / 07:12 · +11 min
- HUPHINDUPURPF 3Actual 07:41 / 07:48 · +12 min
- GBDGAURIBIDANURPF 3Actual 08:05 / 08:07 · +16 min
- DBUDODBALLAPURPF 2Actual 08:42 / 08:52 · +13 min
- YNKYELAHANKA JNPF 2Sch 09:35 → Destination · Exp 09:19 · On time
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1LPR2GEN3GEN4S15S26S37S48S59S610M111B112B213B314B415B516A117A218A319H120GEN21GEN22SLRD
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt YELAHANKA JN, 17603 is usually on time.
यहंलका जं में यह ट्रेन आमतौर पर समय पर पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| KCG KACHEGUDA काचेगुडा | — | +3 min |
| SHNR SHADNAGAR शादनगर | +14 min | +15 min |
| MBNR MAHBUBNAGAR महबूबनगर | +22 min | +22 min |
| GWD GADWAL गडवाल | +30 min | +31 min |
| KRNT KURNOOL CITY कुरनूल टाउन | +24 min | +24 min |
| DHNE DHONE JN डोन जं | +3 min | +6 min |
| GTL GUNTAKAL JN गुंतकल जं | +15 min | +16 min |
| GY GOOTY गूटी | +16 min | +21 min |
| ATP ANANTAPUR अनंतपुर | +14 min | +15 min |
| DMM DHARMAVARAM JN धर्मावरम जं | +4 min | +5 min |
| SSPN SAI P NILAYAM साई प्रशांतिनिलयम | +11 min | +15 min |
| PKD PENUKONDA पेनुकोंडा | +18 min | +19 min |
| HUP HINDUPUR हिंदुपुर | +22 min | +24 min |
| GBD GAURIBIDANUR गौरीबिदनूर | +29 min | +30 min |
| DBU DODBALLAPUR डोडबल्लापुर | +27 min | +31 min |
| YNK YELAHANKA JN यहंलका जं | On time | — |
Based on the train's recent running history — no other public site shows this per train. · यह आंकड़ा ट्रेन के पिछले रिकॉर्ड पर आधारित है।
Journey info
Journey start date: 03-Oct-2026 · Boarding station: KCG
Data source: National Train Enquiry System (CRIS). Times in IST.
17603 PRASANTI NILAYAM EXPRESS — FAQs
- What is the route of 17603 PRASANTI NILAYAM EXPRESS?
- 17603 PRASANTI NILAYAM EXPRESS runs from KACHEGUDA (KCG) to YESVANTPUR JN (YPR), covering 16 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 17603 PRASANTI NILAYAM EXPRESS?
- 17603 PRASANTI NILAYAM EXPRESS departs KACHEGUDA (KCG) at 21:05 03-Oct and arrives YESVANTPUR JN (YPR) at 09:35 04-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 17603 arrive at YESVANTPUR JN? · 17603 YESVANTPUR JN में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 17603 PRASANTI NILAYAM EXPRESS is expected at platform 2 at YESVANTPUR JN (YPR). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 17603 YESVANTPUR JN में प्लेटफॉर्म 2 पर आने की उम्मीद है।
- What is the coach position of 17603 PRASANTI NILAYAM EXPRESS?
- The live coach composition of 17603 PRASANTI NILAYAM EXPRESS — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 17603 PRASANTI NILAYAM EXPRESS run daily?
- Yes, 17603 PRASANTI NILAYAM EXPRESS runs daily.
- Is 17603 PRASANTI NILAYAM EXPRESS usually late? · क्या 17603 अक्सर लेट होती है?
- 17603 PRASANTI NILAYAM EXPRESS is usually on time at YESVANTPUR JN. See the "Is this train late?" section above for the full station-wise delay history. पूरा स्टेशन-वाइज देरी रिकॉर्ड ऊपर "क्या ट्रेन लेट है?" सेक्शन में देखें।
Popular trains
⚠️ Live feed isn't responding — this data may be outdated. Retrying automatically.