It clocked more distance in the past when it had loco reversals at Yesvantpur and Erode. Used to have less than 2 hrs Turnaround time at Tirunelveli back then. Now there is enough time to cover more distance and probably even more time to catch up if it can reach SMVB later like the Pondicherry Chalukya.
Rerouting to Tuticorin would not go uncontested. More passengers from the hinterland in the region would want to board this at Tirunelveli over Tuticorin due to it being centrally located. When this was extended to Tirunelveli,...
more... Tuticorin had 16235 and 17235 was yet to be introduced.
While Tuticorin does not have a train to Mumbai yet, similar case could be made to divert this to Tenkasi (via the shorter route) or Rameswaram, both of which don't have a train to either Mumbai or Bangalore and could offer large volume of passenger traffic.
please wait...Translate to EnglishYo, back in the day this train was putting in more miles with those loco flips at Yesvantpur and Erode. They used to hustle and bustle in less than 2 hours at Tirunelveli. Now, they got more time to roll and maybe even catch up if they hit SMVB later like the Pondicherry Chalukya.
Steering this bad boy to Tuticorin ain't gonna go down smooth. Folks from the boonies around here would rather hop on at Tirunelveli than Tuticorin since it's smack dab in the middle. When they stretched this bad boy to Tirunelveli, Tuticorin had 16235 and 17235 hadn't even rolled out yet.
Tuticorin may not have a ride to Mumbai as of now, but you could argue to reroute this bad boy to Tenkasi (through the shorter route) or Rameswaram, both of which don't have a direct line to Mumbai or Bangalore but have a ton of folks itching to ride.