LiveArrived at destinationUpdated 5950s ago
41066 VELACHERY CHENNAI LOCAL
VELACHEERY (VLCY) → CHENNAI BEACH (MSB)
On time
Current position: Arrived at CHENNAI BEACH(MSB) at 18:48 03-Oct (On Time)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
PZV17:53 03-Oct
PRGD18:02 03-Oct
TRMN18:04 03-Oct
TYMR18:07 03-Oct
INDR18:08 03-Oct
All stations
LIVE- STMMST THOMAS MOUNT(MRTS)PF 2Actual 17:45 · On time
- PZVPUZHUTHIVAKKAMSch 17:53 → 17:54 · Exp **UA** / **UA** · On time
- VLCYVELACHERRYPF 2Sch 17:58 → 17:59 · Exp 17:58 / 17:59 · On time
- PRGDPERUNGUDISch 18:02 → 18:03 · Exp **UA** / **UA** · On time
- TRMNTHARAMANISch 18:04 → 18:05 · Exp **UA** / **UA** · On time
- TYMRTIRUVANMIYURSch 18:07 → 18:08 · Exp **UA** / **UA** · On time
- INDRINDRANAGARSch 18:08 → 18:09 · Exp **UA** / **UA** · On time
- KTBRKASTURBA NAGARSch 18:10 → 18:11 · Exp **UA** / **UA** · On time
- KTPMKOTTURPURAMSch 18:12 → 18:13 · Exp **UA** / **UA** · On time
- GWYRGREENWAYS ROADSch 18:14 → 18:15 · Exp **UA** / **UA** · On time
- MNDYMANDAVELISch 18:16 → 18:17 · Exp **UA** / **UA** · On time
- MTMYTHIRUMAYILAIPF 2Sch 18:18 → 18:19 · Exp 18:24 / 18:25 · +6 min
- MKAKMUNDAKAKANNI AMMAN KOILSch 18:20 → 18:21 · Exp **UA** / **UA** · +6 min
- MLHSLIGHT HOUSESch 18:22 → 18:23 · Exp **UA** / **UA** · +6 min
- MTCNTIRUVALLIKENISch 18:24 → 18:25 · Exp **UA** / **UA** · +6 min
- MCPKCHEPAUKPF 2Sch 18:27 → 18:28 · Exp 18:35 / 18:36 · +8 min
- MCPTCHINTADARIPETPF 2Sch 18:30 → 18:31 · Exp **UA** / **UA** · +6 min
- MPKTCHENNAI PARK TOWNSch 18:33 → 18:34 · Exp **UA** / **UA** · +6 min
- MSFCHENNAI FORTSch 18:36 → 18:37 · Exp **UA** / **UA** · +6 min
- MSBCHENNAI BEACHPF 6Sch 18:50 → Destination · Exp 18:48 · On time
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt CHENNAI BEACH, 41066 is usually on time.
चेन्नई बीच में यह ट्रेन आमतौर पर समय पर पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| STMM ST THOMAS MOUNT(MRTS) सेंट थॉमस माउंट(MRTS) | — | On time |
| VLCY VELACHERRY वेलच्चेरी | On time | On time |
| MTMY THIRUMAYILAI तिरुमेलाई | +4 min | +4 min |
| MCPK CHEPAUK चेपॉक | +5 min | +5 min |
| MSB CHENNAI BEACH चेन्नई बीच | 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: VLCY
Data source: National Train Enquiry System (CRIS). Times in IST.
41066 VELACHERY CHENNAI LOCAL — FAQs
- What is the route of 41066 VELACHERY CHENNAI LOCAL?
- 41066 VELACHERY CHENNAI LOCAL runs from VELACHEERY (VLCY) to CHENNAI BEACH (MSB), covering 20 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 41066 VELACHERY CHENNAI LOCAL?
- 41066 VELACHERY CHENNAI LOCAL departs VELACHEERY (VLCY) at 17:45 03-Oct and arrives CHENNAI BEACH (MSB) at 18:50 03-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 41066 arrive at CHENNAI BEACH? · 41066 CHENNAI BEACH में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 41066 VELACHERY CHENNAI LOCAL is expected at platform 6 at CHENNAI BEACH (MSB). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 41066 CHENNAI BEACH में प्लेटफॉर्म 6 पर आने की उम्मीद है।
- What is the coach position of 41066 VELACHERY CHENNAI LOCAL?
- The live coach composition of 41066 VELACHERY CHENNAI LOCAL — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 41066 VELACHERY CHENNAI LOCAL run daily?
- Yes, 41066 VELACHERY CHENNAI LOCAL runs daily.
- Is 41066 VELACHERY CHENNAI LOCAL usually late? · क्या 41066 अक्सर लेट होती है?
- 41066 VELACHERY CHENNAI LOCAL is usually on time at CHENNAI BEACH. See the "Is this train late?" section above for the full station-wise delay history. पूरा स्टेशन-वाइज देरी रिकॉर्ड ऊपर "क्या ट्रेन लेट है?" सेक्शन में देखें।
More trains from VELACHEERY
Popular trains
⚠️ Live feed isn't responding — this data may be outdated. Retrying automatically.