LiveArrived at destinationUpdated 0s ago
59040 VAPI VIRAR SHUTTLE
VAPI (VAPI) → VIRAR (VR)
+3 min late
Current position: Arrived at MUMBAI CENTRAL(MMCT) at 17:33 02-Oct (Delay: 00:03)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
KEB14:07 02-Oct
BVI16:32 02-Oct
All stations
LIVE- VAPIVAPIPF 3Actual 14:00 · On time
- KEBKARAMBELISch 14:07 → 14:08 · Exp **UA** / **UA** · On time
- BLDBHILADPF 3Sch 14:14 → 14:15 · Exp 14:17 / 14:19 · +3 min
- SJNSANJANPF 2Sch 14:21 → 14:22 · Exp 14:30 / 14:31 · +9 min
- UBRUMBARGAM ROADPF 3Sch 14:29 → 14:30 · Exp 14:41 / 14:42 · +12 min
- GVDGHOLVADPF 3Sch 14:36 → 14:38 · Exp 14:51 / 14:52 · +15 min
- DRDDAHANU ROADPF 2Sch 14:49 → 14:50 · Exp 15:02 / 15:03 · +13 min
- VGNVANGAONPF 3Sch 15:04 → 15:05 · Exp 15:15 / 15:16 · +11 min
- BORBOISARPF 3Sch 15:14 → 15:15 · Exp 15:23 / 15:24 · +9 min
- PLGPALGHARPF 2Sch 15:28 → 15:30 · Exp 15:35 / 15:36 · +7 min
- KLVKELVA ROADPF 3Sch 15:39 → 15:40 · Exp 15:44 / 15:45 · +5 min
- SAHSAPHALEPF 2Sch 15:44 → 15:45 · Exp 15:51 / 15:52 · +7 min
- VTNVAITARNAPF 2Sch 15:50 → 15:51 · Exp 16:00 / 16:01 · +10 min
- VRVIRARPF 5Sch 16:03 → 16:05 · Exp 16:11 / 16:12 · +8 min
- BVIBORIVALIPF 7Sch 16:32 → 16:35 · Exp **UA** / **UA** · +6 min
- MMCTMUMBAI CENTRALPF 1Sch 17:30 → Destination · Exp 17:33 · +3 min
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1SRD2GEN3GEN4GEN5GEN6GEN7GEN8GEN9GEN10GEN11GEN12GEN13GEN14GEN15GEN16GEN17GEN18GEN19GEN20GEN21GEN22GEN23SLRD
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt MUMBAI CENTRAL, 59040 is usually +3 min late.
मुम्बई सेन्ट्रल में यह ट्रेन औसतन 3 मिनट लेट पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| VAPI VAPI वापी | — | +7 min |
| BLD BHILAD भीलड़ | +10 min | +11 min |
| SJN SANJAN संजान | +16 min | +16 min |
| UBR UMBARGAM ROAD उमरगाम रोड | +16 min | +16 min |
| GVD GHOLVAD घोरवाद | +19 min | +20 min |
| DRD DAHANU ROAD दहानु रोड | +20 min | +22 min |
| VGN VANGAON वनगांव | +19 min | +20 min |
| BOR BOISAR बोईसर | +21 min | +21 min |
| PLG PALGHAR पालघर | +18 min | +17 min |
| KLV KELVA ROAD केलवा रोड | +17 min | +17 min |
| SAH SAPHALE सपहले | +20 min | +21 min |
| VTN VAITARNA वैतरणा | +22 min | +22 min |
| VR VIRAR विरार | +22 min | +22 min |
| BVI BORIVALI बोरिवली | +25 min | +23 min |
| MMCT MUMBAI CENTRAL मुम्बई सेन्ट्रल | +3 min | — |
Based on the train's recent running history — no other public site shows this per train. · यह आंकड़ा ट्रेन के पिछले रिकॉर्ड पर आधारित है।
Journey info
Journey start date: 02-Oct-2026 · Boarding station: VAPI
Data source: National Train Enquiry System (CRIS). Times in IST.
59040 VAPI VIRAR SHUTTLE — FAQs
- What is the route of 59040 VAPI VIRAR SHUTTLE?
- 59040 VAPI VIRAR SHUTTLE runs from VAPI (VAPI) to VIRAR (VR), covering 16 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 59040 VAPI VIRAR SHUTTLE?
- 59040 VAPI VIRAR SHUTTLE departs VAPI (VAPI) at 14:00 02-Oct and arrives VIRAR (VR) at 17:30 02-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 59040 arrive at VIRAR? · 59040 VIRAR में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 59040 VAPI VIRAR SHUTTLE is expected at platform 1 at VIRAR (VR). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 59040 VIRAR में प्लेटफॉर्म 1 पर आने की उम्मीद है।
- What is the coach position of 59040 VAPI VIRAR SHUTTLE?
- The live coach composition of 59040 VAPI VIRAR SHUTTLE — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 59040 VAPI VIRAR SHUTTLE run daily?
- Yes, 59040 VAPI VIRAR SHUTTLE runs daily.
- Is 59040 VAPI VIRAR SHUTTLE usually late? · क्या 59040 अक्सर लेट होती है?
- 59040 VAPI VIRAR SHUTTLE is usually 3 minutes late at VIRAR. 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.