Search Forum
PNR Entry# 2161047
Posted: Feb 12 2017 (09:40)
120 Responses
Last Response: Jun 06 2017 (10:32)
120 Responses
Last Response: Jun 06 2017 (10:32)
PREDICTIONS: 59
Journey: Sat Jun 03, 2017
Dep: NDLS/New Delhi @ 16:00 PF#: 5
Arr: SC/Secunderabad Junction @ 15:55 +1 night
Distance: 1668 km / 1677 km
Class: AC 2-tier - 2A | Tot Seats: Avbl-0029# | Charting @12:00
12724/Telangana Express (PT)Dep: NDLS/New Delhi @ 16:00 PF#: 5
Arr: SC/Secunderabad Junction @ 15:55 +1 night
Distance: 1668 km / 1677 km
Class: AC 2-tier - 2A | Tot Seats: Avbl-0029# | Charting @12:00
PNR: 265-xxxxxxx | Similar PNRs
Entry# 2161047
NO PENDING REQUEST
Posted: Feb 12 2017 (09:40:34) View Posted Status
Latest Status: Jun 03 2017 (14:38:02)
Passenger 1: Confirmed: HA1/9 [LB]/LB (GN) (Booking Status: RAC# 8)Passenger 2: Confirmed: A1/6 [SU]/SU (GN) (Booking Status: RAC# 9)
Passenger 3: Confirmed: A1/8 [UB]/UB (GN) (Booking Status: RAC# 10)
Total Fare:
0Chart PREPARED
115 Posts
Where it got late....? It is not able to cover the late as well.. Too bad SCR...
It all started at kalmeshwar. Till there we were on time. From thereon we crawled till nagpur. Post Nagpur, the delay started to increase due to discontinuous MPS run due to alternate main line and loop line skips. Once raj OT was done at hinganghat, we had good clearance till bpq. After entering home zone, same story continued. A total of 8 loop skips happened in scr. 5 already mentioned in above blog posts and other 3 at jammikunta, hasanparthi road and jangaon.
We were stopped at komatipalli for 10 minutes as a freight rake was entering from wl side. Freight rake got the priority because at kazipet town 2 more freight rakes were waiting to enter the line.
Same...
more...
We were stopped at komatipalli for 10 minutes as a freight rake was entering from wl side. Freight rake got the priority because at kazipet town 2 more freight rakes were waiting to enter the line.
Same...
more...
Problem is always with Gondwana slot train anna....adi BPL just 10min delay tho depart ayina ..NGP vachesariki adi almost 40-50min delay ayipotondi..its almost daily case...
aa slot arrival at NGP is 9 and TG di 9:35 ..still as thats getting late and CR not giving overtake , it has to crawl behind till NGP...okko sari Raj venakale undi ante TG ni Godhani lo aapesi Raj ki clearence ichesthadu unless Godhani lo loops khali lekapotey thappa ...aa delay delay BPQ deggara oka 20-30min delay...manodu SCR lo aaadukuntadu inka ..min 1h delay lekunda KZJ reach avvatledu ee madya ...kani HYB matram just 15min delay ani update chesthadu :P
aa slot arrival at NGP is 9 and TG di 9:35 ..still as thats getting late and CR not giving overtake , it has to crawl behind till NGP...okko sari Raj venakale undi ante TG ni Godhani lo aapesi Raj ki clearence ichesthadu unless Godhani lo loops khali lekapotey thappa ...aa delay delay BPQ deggara oka 20-30min delay...manodu SCR lo aaadukuntadu inka ..min 1h delay lekunda KZJ reach avvatledu ee madya ...kani HYB matram just 15min delay ani update chesthadu :P
Oh..Then that is the problem... Ideally AP should OT Gondwana... Anyhow Rajdhani will OT AP after Nagpur...
Gondwana should be OT by TG only if Gondwana is too much delayed... but CR these days not giving OT for Gondwana..very rarely its happening..most of the times, its just trailing it all the way upto NGP and meanwhile Raj getting so close that overtaking becoming mandatory ...
if you take the NZM-BSL which takes the gondwana slot from NZM , most of the times CR giving OT for this train in a way that if TG overtkaing it then Raj too will as those all three has to arrive NGP on PF2 itself...
if you take the NZM-BSL which takes the gondwana slot from NZM , most of the times CR giving OT for this train in a way that if TG overtkaing it then Raj too will as those all three has to arrive NGP on PF2 itself...