NTES live data · updated every minute
LiveArrived at destinationUpdated 26436s ago
22408 BSB GARIB RATH
ANAND VIHAR TRM (ANVT) → BANARAS (BSBS)
12 of 16 stations crossed75% of journey complete
+2 min late

Current position: Arrived at AMBIKAPUR(ABKP) at 18:52 30-Sep (Delay: 00:02)

Auto-refreshes every 45s · data: NTES

Next stations

KTMA14:56 30-Sep
BJRI15:15 30-Sep
BRH16:16 30-Sep
SJQ16:57 30-Sep

All stations

LIVE
  • NZMHAZRAT NIZAMUDDIN JNPF 5
    Actual 23:03 · +3 min
  • MTJMATHURA JNPF 1
    Actual 01:17 / 01:29 · +24 min
  • AGCAGRA CANTT JNPF 1
    Actual 02:12 / 02:17 · +32 min
  • GWLGWALIOR JNPF 1
    Actual 04:02 / 04:05 · +23 min
  • VGLJVIRANGANA LAKSHMIBAI JHANSI JNPF 3
    Actual 06:00 / 06:12 · +50 min
  • SGOSAUGORPF 2
    Actual 09:02 / 09:08 · +29 min
  • DMODAMOHPF 1
    Actual 10:11 / 10:15 · +33 min
  • KMZKATNI MURWARA JNPF 4
    Actual 11:50 / 12:03 · +50 min
  • UMRUMARIAPF 1
    Actual 13:03 / 13:07 · +22 min
  • SDLSHAHDOLPF 1
    Actual 14:12 / 14:27 · +27 min
  • APRANUPPUR JNPF 1
    Actual 15:02 / 15:06 · +37 min
  • KTMAKOTMAPF 2
    Sch 14:56 → 14:58 · Exp **UA** / **UA** · +46 min
  • BJRIBIJURIPF 1
    Sch 15:15 → 15:20 · Exp **UA** / **UA** · +43 min
  • BRHBAIKUNTHPUR RDPF 1
    Sch 16:16 → 16:18 · Exp **UA** / **UA** · +27 min
  • SJQSURAJPUR ROADPF 1
    Sch 16:57 → 16:59 · Exp **UA** / **UA** · +12 min
  • ABKPAMBIKAPURPF 1
    Sch 18:50 → Destination · Exp 18:52 · +2 min

Coach position

Numbered from the engine · → direction of travel
🚂ENGINE→1SLRD2GEN3GEN4H15A16A27PC8B19B210B311B412B513B614S115S216S317S418S519S620GEN21GEN22LPR

Is this train late? · क्या ट्रेन लेट है?

UNIQUE

At AMBIKAPUR, 22408 is usually +2 min late.

अम्बिकापुर में यह ट्रेन औसतन 2 मिनट लेट पहुंचती है।

StationAvg arr delayAvg dep delay
NZM
HAZRAT NIZAMUDDIN JN
हजरत निजामुद्दीन
—+3 min
MTJ
MATHURA JN
मथुरा जं
+24 min+34 min
AGC
AGRA CANTT JN
आगरा कैंट जं.
+32 min+32 min
GWL
GWALIOR JN
ग्वालियर जं
+23 min+24 min
VGLJ
VIRANGANA LAKSHMIBAI JHANSI JN
विरांगना लक्ष्मीबाई झाँसी रेलवे स्टेशन जं.
+50 min+54 min
SGO
SAUGOR
सागर
+29 min+33 min
DMO
DAMOH
दमोह
+33 min+35 min
KMZ
KATNI MURWARA JN
कटनी मुड़वारा जं
+50 min+53 min
UMR
UMARIA
उमारिया
+22 min+24 min
SDL
SHAHDOL
शहडोल
+27 min+37 min
APR
ANUPPUR JN
अन्नुपुर जं
+37 min+36 min
ABKP
AMBIKAPUR
अम्बिकापुर
+2 min—

Based on the train's recent running history — no other public site shows this per train. · यह आंकड़ा ट्रेन के पिछले रिकॉर्ड पर आधारित है।

Journey info

Journey start date: 29-Sep-2026 · Boarding station: NZM

Data source: National Train Enquiry System (CRIS). Times in IST.

22408 BSB GARIB RATH — FAQs

What is the route of 22408 BSB GARIB RATH?
22408 BSB GARIB RATH runs from ANAND VIHAR TRM (ANVT) to BANARAS (BSBS), covering 16 stations. See the full station list with live arrival and departure times above.
What is the timetable of 22408 BSB GARIB RATH?
22408 BSB GARIB RATH departs ANAND VIHAR TRM (ANVT) at 23:00 29-Sep and arrives BANARAS (BSBS) at 18:50 30-Sep. Times are as per the railway schedule; live running status above shows today's actual timings.
On which platform does 22408 arrive at BANARAS? · 22408 BANARAS में किस प्लेटफॉर्म पर आती है?
As per the live feed, 22408 BSB GARIB RATH is expected at platform 1 at BANARAS (BSBS). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 22408 BANARAS में प्लेटफॉर्म 1 पर आने की उम्मीद है।
What is the coach position of 22408 BSB GARIB RATH?
The live coach composition of 22408 BSB GARIB RATH — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
Does 22408 BSB GARIB RATH run daily?
22408 BSB GARIB RATH runs on Tue only — there is no live running status on other days.
Is 22408 BSB GARIB RATH usually late? · क्या 22408 अक्सर लेट होती है?
22408 BSB GARIB RATH is usually 2 minutes late at BANARAS. See the "Is this train late?" section above for the full station-wise delay history. पूरा स्टेशन-वाइज देरी रिकॉर्ड ऊपर "क्या ट्रेन लेट है?" सेक्शन में देखें।

⚠️ Live feed isn't responding — this data may be outdated. Retrying automatically.