Your opinion about Talguppa holds good. Almost Decade back, when Panchganga was non-existent & 16523/24 were running, Myself commuting to Blore from Kumta use to go to Talguppa & take 16228 to reach Blore faster & vice~versa. Even People from Byndoor/Kundapur taluks would do same.
Regarding connecting train to 16511, My opinion would be better to swap slots of 16511 with 16585, such that 16585 starts early from Blore take 16511 slot from Hassan, arrive early at Mlore & leave early towards Murudeshwar. That would also mean early arrival at Murudeshwar &...
more... possible extension till Karwar or even till Madgaon/Vasco.
Few Coastal rail users association also suggesting Rlys to find if it is technical feasible to carry out RSA with 17309/10 Vasco Exp. Incoming Vasco Exp from Yesvantpur can leave as Vasco - SMVT Exp via Karwar & SMVT-Vasco would leave as Vasco-Yesvantpur same Night. PM can be taken either at Vasco or SMVT, making pitline free at another end.
please wait...Translate to EnglishWhat's your take on Talguppa? About ten years ago, when Panchganga didn't even exist & 16523/24 were chugging along, I used to hop from Kumta to Blore by going through Talguppa & catching 16228 for a quicker ride. Folks from Byndoor/Kundapur areas would do the same, man.
As for the tie-up with 16511, I reckon it'd be smart to switch the schedules of 16511 with 16585. If 16585 kicks off earlier from Blore and nabs 16511's spot from Hassan, it'd roll into Mlore quicker and head to Murudeshwar without delay. This setup could mean an early arri to Murudeshwar and possibly extending all the way to Karwar or even up to Madgaon/Vasco.
Some Coastal rail riders crew is also throwing the idea at Railways to figure out if it's doable to swap slots with 17309/10 Vasco Exp. The Vasco Exp arriving from Yesvantpur could depart as Vasco - SMVT Express through Karwar & SMVT-Vasco would depart as Vasco-Yesvantpur on the same night. Crew change could go down either at Vasco or SMVT, freeing up pitline at the other spot.