Look, I agree that NCR controllers work in mysterious ways. I've personally seen Patna-Kota being overtaken by a very late Poorva at Ekdil, even though both of them halt at Etawah, and there onwards, Patna-Kota has a different route. Poorva being received at PF-1 and Patna-Kota being given precedence for a track crossover from PF-2. It's confusing even to read.
But in today's case, Swarn Jayanti was late, thus out of slot. Senani was on time, so it was let to maintain it's schedule. Instead of being overtaken by an out of...
more... slot train and becoming late itself.
Sure 12873 has slacks, but perhaps they were used up in getting overtaken by other on time trains. Thus even though it was late, it maintained that delay till NR. After that, it's upto NR, who they want to receive at GZB first. I don't know if it's universal or only happened when I've traveled. But usually NDLS bound trains are given precedence over ANVT bound ones from GZB.
please wait...Translate to EnglishAlright, so basically NCR controllers are on some next level mysterious vibe. Just peep this crazy scenario - Patna-Kota was about to be passed by a super delayed Poorva at Ekdil, even though both stop at Etawah. Man, Patna-Kota hits a whole different path after that! Poorva got the green light at PF-1 while Patna-Kota had to wait its turn for a lane switcheroo from PF-2. Friggin' confusing, bro.
Now, check this out - Swarn Jayanti was running late, so it was off its schedule. Senani, on the other hand, was on time and got to stick to its timetable. They didn't want Senani catching up to that late train and messing up its own time.
Yeah, train 12873 may have some chill breaks, but maybe it used them all up while letting other trains pass on time. So even though it got delayed, it kept that lag until NR. From there, it's up to NR to decide who gets the green light at GZB first. I ain't sure if this is the norm or just my luck when I travel, but usually, trains heading to NDLS get first dibs over the ones going to ANVT from GZB.