Train PURI JU EXPRESS-18473 from PURI to JODHPUR JN
Station Name | Arrival Time | Depature Time | (Kms) | |
---|---|---|---|---|
PURI | ||||
SAKHI GOPAL | 1 Min | |||
KHURDA ROAD JN | 5 Min | |||
BHUBANESWAR | 5 Min | |||
CUTTACK | 5 Min | |||
NERGUNDI | 1 Min | |||
DHENKANAL | 1 Min | |||
TALCHER ROAD | 1 Min | |||
ANGUL | 2 Min | |||
RAIRAKHOL | 1 Min | |||
SAMBALPUR ROAD | 1 Min | |||
SAMBALPUR | 25 Min | |||
JHARSUGUDA JN | 20 Min | |||
BRAJRAJNAGAR | 2 Min | |||
RAIGARH | 5 Min | |||
SAKTI | 2 Min | |||
CHAMPA | 5 Min | |||
BILASPUR JN | 15 Min | |||
BHATAPARA | 2 Min | |||
RAIPUR JN | 10 Min | |||
DURG | 5 Min | |||
RAJ NANDGAON | 5 Min | |||
DONGARGARH | 2 Min | |||
GONDIA JN | 5 Min | |||
BHANDARA ROAD | 1 Min | |||
NAGPUR | 20 Min | |||
PANDHURNA | 1 Min | |||
BETUL | 1 Min | |||
ITARSI JN | 5 Min | |||
HABIBGANJ | 2 Min | |||
BHOPAL JN | 15 Min | |||
SEHORE | 2 Min | |||
SHUJALPUR | 2 Min | |||
UJJAIN JN | 10 Min | |||
NAGDA JN | 25 Min | |||
VIKRAMGARH ALOT | 1 Min | |||
KOTA JN | 10 Min | |||
SAWAI MADHOPUR | 20 Min | |||
JAIPUR | 10 Min | |||
PHULERA JN | 2 Min | |||
MAKRANA JN | 2 Min | |||
DEGANA JN | 3 Min | |||
MERTA ROAD JN | 5 Min | |||
JODHPUR JN |
Collect important information about train PURI JU EXPRESS before your travel. It helps you plan better for your food and other important needs. PURI JU EXPRESS travels from PURI to JODHPUR JN. We have provided below schedule and train route with list of stoppages with arrival time and departure time at each intermediate station.
For ease of prospective passengers we have provided halt times at each station and provided advisory whether to get down at that station for water / snacks / cold drinks / lunch or dinner break.
Total number of Halts : 44
Long Halts ( Meal breaks ) : 11
Total travel time : 88 hours 44 minutes
Short Halts ( Water / Cold Drink breaks ) : 31
Warning : We do not encourage you do get down at stations. Please do so if you have a genuine requirement and keep an eye on the train.
Other trains - travelling from PURI to JODHPUR JN
-
Sorry could not find appropriate data