LiveArrived at destinationUpdated 0s ago
53371 KQR-BRKA PASSENGER
KODERMA (KQR) → BARKAKANA (BRKA)
+18 min late
Current position: Arrived at BARKA KANA(BRKA) at 10:33 03-Oct (Delay: 00:18)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
UWAN06:19 03-Oct
MNDU09:08 03-Oct
All stations
LIVE- KQRKODERMAPF 1Actual 06:00 · On time
- PADHPIPRADIHPF 1Actual 06:15 / 06:26 · +6 min
- UWANURWANPF 1Sch 06:19 → 06:20 · Exp **UA** / **UA** · +15 min
- BRHIBARHIPF 1Sch 06:33 → 06:35 · Exp 06:49 / 06:51 · +16 min
- PDMAPADMAPF 1Sch 06:46 → 06:48 · Exp 07:09 / 07:14 · +23 min
- KAGAKURHAGADAPF 1Sch 07:01 → 07:03 · Exp 07:27 / 07:29 · +26 min
- KAUAKATHAUTIAPF 1Sch 07:10 → 07:11 · Exp 07:37 / 07:39 · +27 min
- KKASKATKAMASANDIPF 1Sch 07:22 → 07:24 · Exp 07:46 / 07:48 · +24 min
- KSNAKANASAR NAWADAPF 1Sch 07:32 → 07:34 · Exp 08:05 / 08:17 · +33 min
- HZBNHAZARIBAGH TOWNPF 1Sch 08:20 → 08:25 · Exp 08:28 / 08:30 · +8 min
- BESBESPF 1Sch 08:39 → 08:41 · Exp 08:40 / 08:46 · +1 min
- CHRICHARHIPF 1Sch 08:58 → 09:00 · Exp 09:02 / 09:06 · +4 min
- MNDUMANDU HALTPF 1Sch 09:08 → 09:09 · Exp **UA** / **UA** · +6 min
- KUJUKUJUPF 1Sch 09:18 → 09:20 · Exp 09:50 / 10:00 · +32 min
- ARGDARIGADAPF 2Sch 09:34 → 09:36 · Exp 10:21 / 10:23 · +47 min
- BRKABARKA KANAPF 5Sch 10:15 → Destination · Exp 10:33 · +18 min
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1GEN2GEN3SLRD4GEN5GEN
Is this train late? · क्या ट्रेन लेट है?
UNIQUEAt BARKA KANA, 53371 is usually +55 min late.
बरकाकाना में यह ट्रेन औसतन 55 मिनट लेट पहुंचती है।
| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| KQR KODERMA कोडेरमा | — | +10 min |
| PADH PIPRADIH पिपराडीह | +15 min | +17 min |
| UWAN URWAN उरवान | +17 min | +17 min |
| BRHI BARHI बरही | +17 min | +22 min |
| PDMA PADMA पदमा | +31 min | +33 min |
| KAGA KURHAGADA कुरहागड़ा | +29 min | +29 min |
| KAUA KATHAUTIA कथौटिया | +30 min | +35 min |
| KKAS KATKAMASANDI कटकामसांडी | +36 min | +38 min |
| KSNA KANASAR NAWADA कनासर नवादा | +45 min | +50 min |
| HZBN HAZARIBAGH TOWN हजारीबाग टाउन | +29 min | +31 min |
| BES BES बेस | +16 min | +47 min |
| CHRI CHARHI चढ़ी | +47 min | +54 min |
| KUJU KUJU कुजू | +31 min | +43 min |
| ARGD ARIGADA अरीगदा | +96 min | +99 min |
| BRKA BARKA KANA बरकाकाना | +55 min | — |
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: KQR
Data source: National Train Enquiry System (CRIS). Times in IST.
53371 KQR-BRKA PASSENGER — FAQs
- What is the route of 53371 KQR-BRKA PASSENGER?
- 53371 KQR-BRKA PASSENGER runs from KODERMA (KQR) to BARKAKANA (BRKA), covering 16 stations. See the full station list with live arrival and departure times above.
- What is the timetable of 53371 KQR-BRKA PASSENGER?
- 53371 KQR-BRKA PASSENGER departs KODERMA (KQR) at 06:00 03-Oct and arrives BARKAKANA (BRKA) at 10:15 03-Oct. Times are as per the railway schedule; live running status above shows today's actual timings.
- On which platform does 53371 arrive at BARKAKANA? · 53371 BARKAKANA में किस प्लेटफॉर्म पर आती है?
- As per the live feed, 53371 KQR-BRKA PASSENGER is expected at platform 5 at BARKAKANA (BRKA). Platform numbers can change — check the live station timeline above for the latest update. लाइव फीड के अनुसार 53371 BARKAKANA में प्लेटफॉर्म 5 पर आने की उम्मीद है।
- What is the coach position of 53371 KQR-BRKA PASSENGER?
- The live coach composition of 53371 KQR-BRKA PASSENGER — engine, sleeper, AC and general coaches in order — is shown in the coach strip above, updated from the railway feed.
- Does 53371 KQR-BRKA PASSENGER run daily?
- Yes, 53371 KQR-BRKA PASSENGER runs daily.
- Is 53371 KQR-BRKA PASSENGER usually late? · क्या 53371 अक्सर लेट होती है?
- 53371 KQR-BRKA PASSENGER is usually 55 minutes late at BARKAKANA. 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.