हमसे सीखे कोई जीने का सलीका। सफर कैसा भी हो, मौज़ उडाये जाते हैं।। - Amir

Today 12295 is late because it started frm SBC late by 2.5 hrs yesterday, and 12295 has a very strict schedule in SCR till BPQ which it couldnt maintain in this run. CR has not allowed 12615 GT and Mas Jaipur to overtake Sangha till now.

---

I don't think the delay will further increases...if you see the TT then the slack it got at SKZR-BPQ,GDYA-ET(70KM 2h 12m),STA-MGS (all most all the section it has slack till it reaches MGS) and slack at the last leg of journey ...so combining this slack with the priority it gets in SR and SR ..I don't think it will have problem covering its path with the prescribed schedule even thought it started late from source....if there is any other issue like fog n all then we cant do much about that :)

---

And see delay hasn't increased for Sangha , it's still running with initial delay of 2.5 hrs

---

Even slack doesn't help in maintaining the delay of sanga after mgs

---

its actually maintaining its schedule which we should be feel happy rather than getting further delayed... if it reached with the same 2.5 hours delay which was there starting from source then that's great feat as it will be easily get delayed due to multiple things... :)

---