 |
|
| FmT LIVE | Advanced Search |
Trip# 363487
Journey Date: Fri Apr 06
22706/Jammu Tawi - Tirupati Humsafar Express
Trip Entry# 363487
22706/Jammu Tawi - Tirupati Humsafar Express
Trip Entry# 363487
Number of PNRs on this Trip: 2
Pax# 2
UMB/Ambala Cantt. Junction --> HBJ/HabibGanj
Departure: Fri Apr 06 2018 @ 13:20 Class: 3A
Pax# 1
JRC/Jalandhar Cantt. Junction --> TPTY/Tirupati
Departure: Fri Apr 06 2018 @ 09:20 Class: 3A
TRIP HAS ENDED
Train Status: 7h 53m late
Last Update: at TPTY/Tirupati @ Apr 08 2018 (14:33)
Last Update: at TPTY/Tirupati @ Apr 08 2018 (14:33)
Arrived at Trip Destination
Blog Time-Table
135 Posts
Yeah... Initially this train statrted late from Jammu and from there itself delay and less priority started.. Somewhere it was like almost 6 hrs delay but covered up to 3 hrs and again let it go after BPQ to reach TPTY late almost 3:30 hrs..
by BPQ it was just 2h 5min delay when we were tracking and then all of sudden it lost its plot because of that trolling and never recovered after that and back to its 4h+ delay
yeah.. Correct.. Passengers who had to get down in Secunderabad were excited that it covered so mucj delay.. But still reached late at night...
it owuld have reached SC by 11:30 easily....typical SCR trolling this is ...Jai SCR _/\_ _/\_
40mins stoppage at BPQ just to let TN ahead senseless controlling by CR..
Humsafar would have maintained enough gap with TN even if starts first will be miles ahead of TN.
Humsafar would have maintained enough gap with TN even if starts first will be miles ahead of TN.
Scroll to Top