LiveArrived at destinationUpdated 0s ago
58218 RAIPUR TITAGARH PASSENGER
RAIPUR JN (R) → TITLAGARH (TIG)
+110 min late
Current position: Arrived at TITLAGARH(TIG) at 08:50 02-Oct (Delay: 01:50)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
MNDH02:20 02-Oct
HSK04:42 02-Oct
All stations
LIVE- RRAIPUR JNPF 3Actual 03:27 · +87 min
- MNDHMANDIR HASAUDPF 1Sch 02:20 → 02:22 · Exp **UA** / **UA** · +84 min
- MSMDMAHASAMUNDPF 2Sch 03:03 → 03:05 · Exp 04:45 / 04:47 · +102 min
- BGBRBAGBAHRAPF 1Sch 03:30 → 03:32 · Exp 05:20 / 05:22 · +110 min
- KMKKOMAKHANPF 2Sch 03:42 → 03:43 · Exp 05:32 / 05:34 · +110 min
- KRARKHARIAR ROADPF 2Sch 04:00 → 04:02 · Exp 05:45 / 05:47 · +105 min
- NPDNAWAPARA ROADPF 1Sch 04:13 → 04:15 · Exp 05:58 / 06:00 · +105 min
- LKNALAKHNAPF 1Sch 04:27 → 04:29 · Exp 06:12 / 06:14 · +105 min
- HSKHARISHANKER RDPF 1Sch 04:42 → 04:44 · Exp **UA** / **UA** · +105 min
- TRKRTUREKALA ROADPF 2Sch 04:53 → 04:55 · Exp 06:45 / 06:53 · +112 min
- KBJKANTABANJIPF 2Sch 05:15 → 05:25 · Exp 07:08 / 07:18 · +113 min
- MRBLMURIBAHALPF 2Sch 05:45 → 05:47 · Exp 07:30 / 07:43 · +105 min
- RNBTRAHEN BATAPF 2Sch 06:14 → 06:16 · Exp 08:04 / 08:35 · +110 min
- TIGTITLAGARHPF 4Sch 07:00 → Destination · Exp 08:50 · +110 min
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1SLRD2GEN3GEN4GEN5GEN6GEN7GEN8GEN9GEN
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt TITLAGARH, 58218 is usually +148 min late.
टीटलागढ़ में यह ट्रेन औसतन 148 मिनट लेट पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| R RAIPUR JN रायपुर जं | — | +129 min |
| MSMD MAHASAMUND महासमंद | +175 min | +177 min |
| BGBR BAGBAHRA बागबहरा | +183 min | +183 min |
| KMK KOMAKHAN कोमाखन | +163 min | +164 min |
| KRAR KHARIAR ROAD खरियार रोड | +175 min | +177 min |
| NPD NAWAPARA ROAD नवापाड़ा रोड | +177 min | +179 min |
| LKNA LAKHNA लखना | +179 min | +180 min |
| HSK HARISHANKER RD हरिशंकर रोड | +192 min | +192 min |
| TRKR TUREKALA ROAD तुरेकेला | +182 min | +184 min |
| KBJ KANTABANJI कांटाबाजी | +170 min | +170 min |
| MRBL MURIBAHAL मूरीबहल | +164 min | +166 min |
| RNBT RAHEN BATA रहेनभटा | +154 min | +166 min |
| TIG TITLAGARH टीटलागढ़ | +148 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: R
Data source: National Train Enquiry System (CRIS). Times in IST.
58218 RAIPUR TITAGARH PASSENGER — FAQs
- What is the route of 58218 RAIPUR TITAGARH PASSENGER?
- 58218 RAIPUR TITAGARH PASSENGER runs from RAIPUR JN (R) to TITLAGARH (TIG), covering 14 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 58218 RAIPUR TITAGARH PASSENGER?
- 58218 RAIPUR TITAGARH PASSENGER departs RAIPUR JN (R) at 02:00 02-Oct and arrives TITLAGARH (TIG) at 07:00 02-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 58218 arrive at TITLAGARH? · 58218 TITLAGARH में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 58218 RAIPUR TITAGARH PASSENGER is expected at platform 4 at TITLAGARH (TIG). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 58218 TITLAGARH में प्लेटफॉर्म 4 पर आने की उम्मीद है।
- What is the coach position of 58218 RAIPUR TITAGARH PASSENGER?
- The live coach composition of 58218 RAIPUR TITAGARH PASSENGER — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 58218 RAIPUR TITAGARH PASSENGER run daily?
- Yes, 58218 RAIPUR TITAGARH PASSENGER runs daily.
- Is 58218 RAIPUR TITAGARH PASSENGER usually late? · क्या 58218 अक्सर लेट होती है?
- 58218 RAIPUR TITAGARH PASSENGER is usually 148 minutes late at TITLAGARH. 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.