Search Forum
Blog Entry# 1584139
Posted: Sep 07 2015 (01:00)
29 Responses
Last Response: Sep 08 2015 (21:15)
29 Responses
Last Response: Sep 08 2015 (21:15)
Sep 07 2015 (01:00) 12553/Vaishali SF Express (PT) | LJN/Lucknow Junction NER (6 PFs) | LGD/WAP-7/30261
JudgeSahab^~
JudgeSahab^~ 38112 blog posts
An analysis of speed done this night over LUCKNOW-KANPUR stretch with New Delhi bound vaishali express which was running towards Delhi with the massive offlink LGD P7 From Lucknow Jn.
Our analysis reflected some useful information about the MPS of Lucknow Kanpur section.
1) MPS of LUCKNOW UNNAO section is 105 kmph
2) MPS of UNNAO KANPUR CENTRAL is 100 kmph
Snapshots...
more...
Our analysis reflected some useful information about the MPS of Lucknow Kanpur section.
1) MPS of LUCKNOW UNNAO section is 105 kmph
2) MPS of UNNAO KANPUR CENTRAL is 100 kmph
Snapshots...
more...
24 Posts
I have attached the screen shot.. U should had a look at that first.
Yes. Yesterday it was delayed around siwan due to disturbance created by Papu yadav & his supporters.
And day before yesterday it reached GKP late and could not cover the delay because even GD departed late from GKP. So ran behind it.
And day before yesterday it reached GKP late and could not cover the delay because even GD departed late from GKP. So ran behind it.
And Vaishali departed LJN 50 mins late.. how come it departed CNB right time. Don't get used to writing in casual manners always.
Listen man I check CNB arrival, further I don't have any intention to vilify vaishali against prayagraj express. NTES showed departed RT from CNB which I already stated in above reply
NTES error bro nothing else...!! It happens at cnb mostly either U.A. or wrong data. As vaishali monitored by RB NTES data got manipulated for obvious reasons.