LiveArrived at destinationUpdated 0s ago
53016 AZIMGANJ KATWA PASSENGER
AZIMGANJ JN (AZ) → KATWA (KWAE)
On time
Current position: Arrived at KATWA(KWAE) at 14:52 03-Oct (On Time)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
LCAE13:23 03-Oct
JVT13:37 03-Oct
MIAN14:05 03-Oct
MHTR14:15 03-Oct
JHBN14:25 03-Oct
All stations
LIVE- AZAZIMGANJ JNPF 3Actual 13:15 · On time
- LCAELALBAGH CRT RDPF 1Sch 13:23 → 13:24 · Exp **UA** / **UA** · On time
- KGLEKHAGRAGHAT ROADPF 1Sch 13:31 → 13:32 · Exp 13:32 / 13:33 · +1 min
- JVTJIBANTISch 13:37 → 13:38 · Exp **UA** / **UA** · On time
- KNSNKARNA SUBARNAPF 2Sch 13:43 → 13:44 · Exp 13:45 / 13:46 · +2 min
- CWLECHOWRIGACHAPF 2Sch 13:52 → 13:53 · Exp 13:54 / 13:54 · +2 min
- BZLEBAZARSAUPF 2Sch 14:00 → 14:01 · Exp 14:01 / 14:02 · +1 min
- MIANMIANGRAMSch 14:05 → 14:06 · Exp **UA** / **UA** · On time
- TYAETENYAPF 1Sch 14:10 → 14:11 · Exp 14:13 / 14:14 · +3 min
- MHTRMALIHATI TBR RDSch 14:15 → 14:16 · Exp **UA** / **UA** · +3 min
- SALESALARPF 1Sch 14:19 → 14:20 · Exp 14:23 / 14:25 · +4 min
- JHBNJMTPUR BAHARANSch 14:25 → 14:26 · Exp **UA** / **UA** · +3 min
- GGLEGANGATIKURIPF 2Sch 14:30 → 14:31 · Exp 14:34 / 14:34 · +4 min
- SHBLSHIBLUNSch 14:35 → 14:36 · Exp **UA** / **UA** · +3 min
- NBKHNABA GRAM KANKURHATIPF 2Sch 14:40 → 14:41 · Exp 14:44 / 14:44 · +4 min
- KWAEKATWAPF 2Sch 15:00 → Destination · Exp 14:52 · On time
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1SLRD2GEN3GEN4GEN5GEN6GEN7GEN8GEN9GEN10GEN11SLRD
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt KATWA, 53016 is usually on time.
कटवा में यह ट्रेन आमतौर पर समय पर पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| AZ AZIMGANJ JN अजीमगंज जं | — | On time |
| LCAE LALBAGH CRT RD लालबाग सीआरटीरोड | +2 min | +2 min |
| KGLE KHAGRAGHAT ROAD खगराघाट रोड | On time | On time |
| KNSN KARNA SUBARNA करना सुवर्णा | +1 min | +1 min |
| CWLE CHOWRIGACHA चौरागाचा | +1 min | +1 min |
| BZLE BAZARSAU बाजारसाउ | +1 min | +1 min |
| TYAE TENYA तेन्या | +2 min | +2 min |
| SALE SALAR सलार | +4 min | +4 min |
| GGLE GANGATIKURI गंगाटिकुरी | +3 min | +2 min |
| NBKH NABA GRAM KANKURHATI नाबा ग्राम कंकुरहाटी | +1 min | +1 min |
| KWAE KATWA कटवा | 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: AZ
Data source: National Train Enquiry System (CRIS). Times in IST.
53016 AZIMGANJ KATWA PASSENGER — FAQs
- What is the route of 53016 AZIMGANJ KATWA PASSENGER?
- 53016 AZIMGANJ KATWA PASSENGER runs from AZIMGANJ JN (AZ) to KATWA (KWAE), covering 16 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 53016 AZIMGANJ KATWA PASSENGER?
- 53016 AZIMGANJ KATWA PASSENGER departs AZIMGANJ JN (AZ) at 13:15 03-Oct and arrives KATWA (KWAE) at 15:00 03-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 53016 arrive at KATWA? · 53016 KATWA में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 53016 AZIMGANJ KATWA PASSENGER is expected at platform 2 at KATWA (KWAE). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 53016 KATWA में प्लेटफॉर्म 2 पर आने की उम्मीद है।
- What is the coach position of 53016 AZIMGANJ KATWA PASSENGER?
- The live coach composition of 53016 AZIMGANJ KATWA PASSENGER — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 53016 AZIMGANJ KATWA PASSENGER run daily?
- Yes, 53016 AZIMGANJ KATWA PASSENGER runs daily.
- Is 53016 AZIMGANJ KATWA PASSENGER usually late? · क्या 53016 अक्सर लेट होती है?
- 53016 AZIMGANJ KATWA PASSENGER is usually on time at KATWA. 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.