LiveArrived at destinationUpdated 0s ago
66041 SPE-NLR MEMU PASS
CHENNAI BEACH (MSB) → TIRUMALPUR (TMLP)
On time
Current position: Arrived at NELLORE(NLR) at 12:21 01-Oct (On Time)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
NLS11:31 01-Oct
All stations
LIVE- SPESULLURUPETAPF 1Actual 10:21 · +21 min
- PELPOLIREDDIPALEMPF 1Actual 10:31 / 10:32 · +22 min
- DVRDORAVARICHATTRAMPF 1Actual 10:40 / 10:41 · +21 min
- NYPNAYUDUPETAPF 1Actual 10:52 / 10:53 · +21 min
- PYAPEDAPARIYAPF 3Actual 11:07 / 11:08 · +25 min
- ODURODURPF 1Actual 11:14 / 11:15 · +22 min
- GDRGUDUR JNPF 2Actual 11:29 / 11:34 · +30 min
- MBLMANUBOLUPF 1Actual 11:43 / 11:44 · +34 min
- VKTVENKATACHALAMPF 2Actual 11:54 / 11:55 · +35 min
- VDEVEDAYAPALEMPF 1Actual 12:00 / 12:01 · +34 min
- NLSNELLORE SOUTHSch 11:31 → 11:32 · Exp **UA** / **UA** · On time
- NLRNELLOREPF 4Sch 12:30 → Destination · Exp 12:21 · On time
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1GEN2GEN3GEN
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt NELLORE, 66041 is usually on time.
नेल्लोर में यह ट्रेन आमतौर पर समय पर पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| SPE SULLURUPETA सुल्लुरुपेटा | — | +16 min |
| PEL POLIREDDIPALEM पोलीरेड्डीपलेम | +17 min | +17 min |
| DVR DORAVARICHATTRAM दोरवारिचत्रम | +15 min | +15 min |
| NYP NAYUDUPETA नयादुपेटा | +16 min | +16 min |
| PYA PEDAPARIYA पेडापारिया | +21 min | +21 min |
| ODUR ODUR ओडुर | +20 min | +20 min |
| GDR GUDUR JN गुडुर जं | +24 min | +30 min |
| MBL MANUBOLU मनुबोलु | +32 min | +31 min |
| VKT VENKATACHALAM वेंकटाचलम | +37 min | +37 min |
| VDE VEDAYAPALEM वेदायपालेम | +36 min | +36 min |
| NLS NELLORE SOUTH नेल्लोर साउथ | +41 min | +41 min |
| NLR NELLORE नेल्लोर | On time | — |
Based on the train's recent running history — no other public site shows this per train. · यह आंकड़ा ट्रेन के पिछले रिकॉर्ड पर आधारित है।
Journey info
Journey start date: 01-Oct-2026 · Boarding station: MSB
Data source: National Train Enquiry System (CRIS). Times in IST.
66041 SPE-NLR MEMU PASS — FAQs
- What is the route of 66041 SPE-NLR MEMU PASS?
- 66041 SPE-NLR MEMU PASS runs from CHENNAI BEACH (MSB) to TIRUMALPUR (TMLP), covering 12 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 66041 SPE-NLR MEMU PASS?
- 66041 SPE-NLR MEMU PASS departs CHENNAI BEACH (MSB) at 10:00 01-Oct and arrives TIRUMALPUR (TMLP) at 12:30 01-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 66041 arrive at TIRUMALPUR? · 66041 TIRUMALPUR में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 66041 SPE-NLR MEMU PASS is expected at platform 4 at TIRUMALPUR (TMLP). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 66041 TIRUMALPUR में प्लेटफॉर्म 4 पर आने की उम्मीद है।
- What is the coach position of 66041 SPE-NLR MEMU PASS?
- The live coach composition of 66041 SPE-NLR MEMU PASS — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 66041 SPE-NLR MEMU PASS run daily?
- Yes, 66041 SPE-NLR MEMU PASS runs daily.
- Is 66041 SPE-NLR MEMU PASS usually late? · क्या 66041 अक्सर लेट होती है?
- 66041 SPE-NLR MEMU PASS is usually on time at TIRUMALPUR. See the "Is this train late?" section above for the full station-wise delay history. पूरा स्टेशन-वाइज देरी रिकॉर्ड ऊपर "क्या ट्रेन लेट है?" सेक्शन में देखें।
More trains from CHENNAI BEACH
40001 CHENNAI BEACH TAMBARAM EMU 12 CAR40003 CHENNAI BEACH TAMBARAM EMU 12 CAR40005 CHENNAI BEACH TAMBARAM EMU40007 CHENNAI BEACH TAMBARAM EMU 12 CAR40009 CHENNAI BEACH TAMBARAM EMU 12 CAR40011 CHENNAI BEACH TAMBARAM EMU 12 CAR40013 CHENNAI BEACH TAMBARAM EMU 12 CAR40015 CHENNAI BEACH TAMBARAM EMU 12 CAR40017 CHENNAI BEACH TAMBARAM EMU 12 CAR40019 CHENNAI BEACH TAMBARAM EMU40021 CHENNAI BEACH PALLAVARAMEMU40023 CHENNAI BEACH ST THOMAS MOUNT FAST EMU
Popular trains
⚠️ Live feed isn't responding — this data may be outdated. Retrying automatically.