LiveArrived at destinationUpdated 0s ago
68011 KGP TATA LOC
KHARAGPUR (KGP) → TATANAGAR JN (TATA)
+50 min late
Current position: Arrived at TATANAGAR JN(TATA) at 21:40 02-Oct (Delay: 00:50)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
KSO18:19 02-Oct
SUA18:26 02-Oct
BNB18:33 02-Oct
KATB18:48 02-Oct
GII18:56 02-Oct
All stations
LIVE- KGPKHARAGPUR JNPF 1Actual 18:00 · On time
- KKQKALAIKUNDAPF 2Actual 18:14 / 18:15 · +2 min
- KSOKHEMASULIPF 1Sch 18:19 → 18:20 · Exp **UA** / **UA** · On time
- SUASARDIHAPF 2Sch 18:26 → 18:27 · Exp **UA** / **UA** · On time
- BNBBANSTOLASch 18:33 → 18:34 · Exp **UA** / **UA** · On time
- JGMJHARGRAMPF 2Sch 18:40 → 18:41 · Exp 18:54 / 18:55 · +14 min
- KATBKHATKURA PHSch 18:48 → 18:49 · Exp **UA** / **UA** · +13 min
- GIIGIDHNIPF 2Sch 18:56 → 18:57 · Exp **UA** / **UA** · +13 min
- KNMKANIMAHULI PHSch 19:05 → 19:06 · Exp **UA** / **UA** · +13 min
- CKUCHAKULIAPF 2Sch 19:11 → 19:12 · Exp 19:21 / 19:22 · +10 min
- KKPRKOKPARAPF 2Sch 19:20 → 19:21 · Exp **UA** / **UA** · +9 min
- DVMDALBHUMGARHPF 5Sch 19:29 → 19:30 · Exp **UA** / **UA** · +9 min
- GTSGHATSILAPF 2Sch 19:41 → 19:42 · Exp 19:49 / 19:50 · +8 min
- GUDGALUDIHPF 5Sch 19:50 → 19:51 · Exp **UA** / **UA** · +7 min
- RHERAKHA MINESPF 3Sch 19:53 → 19:55 · Exp 20:23 / 20:24 · +30 min
- ASBASANBONIPF 4Sch 20:22 → 20:23 · Exp 20:47 / 20:54 · +25 min
- TATATATANAGAR JNPF 2Sch 20:50 → Destination · Exp 21:40 · +50 min
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1GEN2GEN3GEN4GEN
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt TATANAGAR JN, 68011 is usually +41 min late.
टाटानगर जं में यह ट्रेन औसतन 41 मिनट लेट पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| KGP KHARAGPUR JN खड़गपुर जं | — | +1 min |
| KKQ KALAIKUNDA कलाईकुंडा | +6 min | +6 min |
| SUA SARDIHA सरदिहा | +34 min | +34 min |
| JGM JHARGRAM झारग्राम | +41 min | +41 min |
| GII GIDHNI गिधनी | +32 min | +32 min |
| CKU CHAKULIA चाकुलिया | +35 min | +36 min |
| KKPR KOKPARA कोकपारा | +33 min | +33 min |
| DVM DALBHUMGARH दलभूमगढ़ | +65 min | +65 min |
| GTS GHATSILA घाटशिला | +24 min | +24 min |
| GUD GALUDIH गलुडीह | +51 min | +51 min |
| RHE RAKHA MINES राखा माइन्स | +42 min | +41 min |
| ASB ASANBONI आसनबोनी | +44 min | +47 min |
| TATA TATANAGAR JN टाटानगर जं | +41 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: KGP
Data source: National Train Enquiry System (CRIS). Times in IST.
68011 KGP TATA LOC — FAQs
- What is the route of 68011 KGP TATA LOC?
- 68011 KGP TATA LOC runs from KHARAGPUR (KGP) to TATANAGAR JN (TATA), covering 17 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 68011 KGP TATA LOC?
- 68011 KGP TATA LOC departs KHARAGPUR (KGP) at 18:00 02-Oct and arrives TATANAGAR JN (TATA) at 20:50 02-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 68011 arrive at TATANAGAR JN? · 68011 TATANAGAR JN में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 68011 KGP TATA LOC is expected at platform 2 at TATANAGAR JN (TATA). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 68011 TATANAGAR JN में प्लेटफॉर्म 2 पर आने की उम्मीद है।
- What is the coach position of 68011 KGP TATA LOC?
- The live coach composition of 68011 KGP TATA LOC — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 68011 KGP TATA LOC run daily?
- Yes, 68011 KGP TATA LOC runs daily.
- Is 68011 KGP TATA LOC usually late? · क्या 68011 अक्सर लेट होती है?
- 68011 KGP TATA LOC is usually 41 minutes late at TATANAGAR 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.