so if SEB with same rake composition as of TN can run at 130, this means TN was left out for some unknown reasons.

---

actually arrived RT in MAS, so it used its slack this time...lol

---

The ZBTT has nothing to do with zero "slack", if introduced ZBTT is based on Zero Sum Game theory, which means at a destination if 100 trains were sped up, there will be other 100 trains which need to be slowed down to help those 100 trains so net is 100-100=0. Now this is not for NDLS alone, its per destination so we will see trains slowed down in intermediate sections as well, while doing so some trains will get insane time slots affecting passengers while others will retain their VVIP status.

---

and Solapur, Wadi will miss the only direct link to NDLS

---

sir, how can a controller break the TT protocol ? why would he/she let one train over other when the order is set ?, SEB is supposed to reach BPL by 625 AM before TN, unless SEB is late and delaying TN.

---

I think the technical reasons are not clear yet why 02621/2 alone is being treated differently ( i will not address it as TN yet..), for sure SR has different plans which are quite baffling to comprehend at the time being , Iam not sure but SR must be targeting to speed-up Thirukural and TNSK (post LHB) in line with close to TN, and TN is kind of paying the price of 0 sum theory at NZM due to LTT-HW SF (+1-1=0), let's wait for TN to officially start..

---

The only way to do that is to let TN pass through loop near PF1-1 the way duronto used to OT TN, i think it has to do with the way points are setup near BPL, all north to south trains can only be routed through Pf-1 and loop.

---

not true always, sometimes depends on PF availability itself, trains having reversals at BPL might be taken on a different platform, and all PF pride aside, the most important reason is TN cannot be let before SEB unless SEB is late and delaying other trains, then an parallel OT is allowed through 3rd line before BPL. There are some trains which pass BPL having halted at HBJ so they need to be considered as well.

---

and better to stick with TN, why are we breaking our heads about PF theory ?, lets see some day if SEB is actually late and see how BPL handles that

---

02622 on 23rd was sitting in BZA for almost 23 mins as it was BT, and reached MAS at 530 AM

---

we have been consoling ourselves with all such theories about TN, but reality is TN is slowest in its group of trains now, i can't talk about priority anymore, but TT design is such that it stays ahead of trains and then gets overtaken one after the other, as i see it because there aren't enough loop lines for an earlier OT (we need to factor freights as well). Most likely TN will run with this schedule only post regular run as well but i will wait for it. PF3 has been generally given to trains taking NZM route due to interlocking at NDLS, as earlier TN used to depart from PF 12 (the entrance PF of NDLS, now we have 16 i guess)

---

TN shayad railfans ki premium train ban ke reh gayi hai, i think TN should absorb some of GT's stops, abb slow down kar hi diya hai to stops bhi add karne chaiyee, yeh bhi accha hai ke slow train hone ki wajah se ab NDLS ka departure sab premium trains ke baad hai. From MAS se bhi agar 1100 PM kar dein to accha hoga, it will remain behind all premium trains.

---