Spotting
 Timeline
 Travel Tip
 Trip
 Race
 Social
 Greeting
 Poll
 Img
 PNR
 Pic
 Blog
 News
 Conf TL
 RF Club
 Convention
 Monitor
 Topic
 #
 Rating
 Correct
 Wrong
 Stamp
 PNR Ref
 PNR Req
 Blank PNRs
 HJ
 Vote
 Pred
 @
 FM Alert
 FM Approval
 Pvt

RailCal app

site support

Mumbai Local - RailFanning nirvana.

Search Forum
<<prev entry    next entry>>
Blog Entry# 2169865
Posted: Feb 19 2017 (06:24)

23 Responses
Last Response: Feb 23 2017 (10:40)
2 Followers
Rail Fanning
25836 views
36

★★★
Feb 19 2017 (06:24)   12802/Purushottam Express (PT) | NDLS/New Delhi (16 PFs) | GZB/WAP-7/30230
Kaushal Vivek^~
Kaushal Vivek^~   5911 blog posts
Entry# 2169865            Tags   Past Edits
1 compliments
Nice trip diary
The month of December. A month about which most of the railfans of India know. Fog, delayed, resch and cancelled trains. Well the date of the trip was decided well in advance even before I left Bokaro for NDLS and to come back. But this time, i wanted to try something else. Equally confused, should I take my fav Rajdhani or go for something else.. like 12826 or 12818 or 12802. Could not decide it. The trains were running on time, till mid November. I risked it, and booked a tkt in Purushottam Express, though I was well aware, that fog may ruin the 130 madness. But still I risked it. Then suddenly one night, everything changed. It happened almost 15 16 days before my trip. The Rajdhanis were delayed by 5 to 6 hrs between MGS and CNB and the delay was increasing. I took it as a common incident,...
more...
maybe some issue. The next day I came to know, it was the notorious FOG. Anyways in the hope that situation would improve, I didn't cancel the tkts, keeping in mind, Purushottam has a long TAT. But the situation was getting worse and worse day by day and my hopes for 130 and timely arrival at BKSC were demolishing with each day passing. After a week attack, the weather cleared. My hopes were back on track. But the continuous resch from both sides kept me in dilemma. Anyways, I was thinking, 130 MPS can do something, and then the fog attacked again. More severly. My hopes lost.I was badly confused, to take 12440 or 12802. Finally, I decided to go with 12440. But seems, God was is=n no mood to spare me. The prices were much higher. I cancelled the thought of Booking. I kept on keeping my hopes high. While my PNR was moving at snail's pace. When it reached WL 8, I posted it on the DOJ, as I had made up my mind to go by 12802 now. /pnr/post/2077666.
.
I was still thinking in the morning, should I book in 12440 :p. Finally, i said.. Jo hoga dekh lenge. These decisions we often take in our lives. :p. The train arrived NDLS at abt 6 PM. I was damn sure, it wud depart ontime or a maximum of 30 mins delayed. Suddenly after few mins my frnd called " bhaiyya, train to raat 1 baje jaayegi ". And for few moments, my mind went blank. In Hindi, we have a proverb --- " jab okhli mai sar de diya to ab kya darna". Anyways I collected myself back. My everything was packed. I left my PG at app 23:00 hrs. Booked a cab, and reached at 23:25. Thanks to nil traffic. Shivganga was being placed and Prayagraj was in pitline. TN was yet to be placed alongwith GT. AP was being placed. Poorva, as usual, running extremely delayed and ETA was 2 AM. I arrived at PF 9. BSP Rajdhani was in the sickline with ET WAP 4. A shatabdi came at PF 9. While Mahabodhi was placed few minutes before that. All were speculating, once shatabdi goes to yard, the train would be placed on PF
.
Mahabodhi was full. Heavily crowded even in such winters. Finally the shatabdi was taken to pitline. an announcement was done - "Passengers your attention please, Saharsa - Amritsar Garibrath is arriving on PF 9.".. " Yatrigan kripya dhyan dijiye, Saharsa se chalkar AMritsar ko jaane wali, Amritsar garib Rath, Platform number nau pe lagayi jaa rahi hai aur gaadi sankhya 12802 nayi dilli se chalkar puri ko jaane wali, purushottam express, abhi takniki dekhrekh ke liye yard mai khadi hai. Jaise hi gaadi platform pe lagayi jayegi, aapko soochit kiya jayega." I was like.. WTH... I had become Jethalal. Finally, the train was placed at app 01:50 AM. It departed at 02:04 AM. I exchanged my UB with SLB.
.
.
More to be followed in subsequent sub blogs.

Translate to English
Translate to Hindi

1 Public Posts - Sun Feb 19, 2017

936 views
7

Feb 19 2017 (19:37)
Kaushal Vivek^~   5911 blog posts
Re# 2169865-2               Past Edits
Followup - Part 2 of the trip
The train departed finally, I was still wondering why was it in yard, it wasn't cleaned. Just for namesake, they had kept in yard. The train departed and was showing no signs of slowdown, ripping MWC at flat 110. I thought, a great start is showing good sign as there was no sign of fog in NCT area. After entry, into NCR the train though didn't touch 130, the weather was very much clear, with dense fogs in patches. The train was continuously accelerating and decelerating. I dozed off before ALJN.. it was near about 03:30 or 40. And then I woke up at about 8. I saw my watch.. I thought, atleast we should
...
more...
had been near ETW atleast, as the train was halted and dense fog was there. I tried to locate by using auto location feature of IRI. But it failed. after few attempts, it showed we are near Tundla. And I was dumbstruck. Four hours.. for such a less distance. Ahead of us was Mahabodhi, then Prayagraj and the leader was Shivganga. We were running at snail's pace. Crossing happened with 24 hours delayed 12453 Ranchi Rajdhani via DTO. The train was at MGS at 10 AM the previous day. Then, i went to brush my teeth and other daily chores. The train was still halted near TDL. I had the breakfast which was very tasty and surprisingly served hot. I had two plates of it. And 4 cups of tea. :p. And after such a nice breakfast with no signs of the train moving, I decided to have another round of sleep. The breakfast consisted of 1 bread slice and 2 veg cutlets, costing rs 35.
.
I finally woke up near SKB, and the train was running in a very good speed. almost close to 110. But the 2 110 trains were keeping us slow. 6 hours were already added to the delay ex NDLS departure. So we were close to 9 hrs of cumulative delay. There was no fog. Clear weather, but... Well but post Bharthana, it started doing 130 in patches but not continuously. Finally we were trolled massively Between BPU and PNK. Lost another 30 45 mins. And another 60 mins between PNK CNB. All I did was to walk in the meantime to the 1st Sleeper coach to click a loco pic, as my coach was almost at other end. Clicked the pic, had a small RF session and came back to coach as the lunch was to arrive. The lunch was delayed. Till that time, Mahabodhi was near FTP and PR SG were way ahead of us. At CNB 12877 RNC GR arrived at abt 4 PM.. delayed by 10 hours with Duronto Liveried WAP 7, and SG xed us at CNB outer towards NDLS. Had a tasty lunch and the train was running in good pace. But the bad thing was, the delay was accumulating. At Sirathu, we faced Dual Overtakes by 12306 and 12314. We finally Arrived ALD and I rushed to get some night snaps of the loco. The windshield was being cleaned. Went back to the coach and had dinner.
.
Follow more to know the rest in the subsequest blogs :D
Till then enjoy the pics.

Translate to English
Translate to Hindi

9 Public Posts - Sun Feb 19, 2017

6 Public Posts - Mon Feb 20, 2017

1 Public Posts - Wed Feb 22, 2017

5 Public Posts - Thu Feb 23, 2017
Scroll to Top
Scroll to Bottom
Go to Desktop site
Important Note: This website NEVER solicits for Money or Donations. Please beware of anyone requesting/demanding money on behalf of IRI. Thanks.
Disclaimer: This website has NO affiliation with the Government-run site of Indian Railways. This site does NOT claim 100% accuracy of fast-changing Rail Information. YOU are responsible for independently confirming the validity of information through other sources.
India Rail Info Privacy Policy