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

RailFanning is our All-Rounder Glucose that gives us Instant Power in All Seasons - Kirti Solanki

Search Forum
<<prev entry    next entry>>
Blog Entry# 2498789
Posted: Oct 06 2017 (13:43)

2 Responses
Last Response: Oct 08 2017 (18:15)
General Travel
6040 views
0

Oct 06 2017 (13:43)   16613/Rajkot - Coimbatore Express (PT)
VijaySrini
VijaySrini   24 blog posts
Entry# 2498789            Tags   Past Edits
On 24-25 September 2017, I travelled from Ahmedabad to Bengaluru (K R Puram by 16613 Rajkot Coimbatore Express. I would like to share the nightmare of that travel.
The train was supposed to start at 10 am from Ahmedabad, but started at 12:30 pm i.e, 2 and half hours later. En-route, due to some work between Ahmedabad and Vadodara, the train become 5 hours later, but covered up till Vasai Road to 4 hours later.
Next Morning, it was again 5 hours late, and somehow reached Hindupur at 8 pm. But then, the
...
more...
real nightmare started. The train stopped at Penukonda for double crossing, and another small stop for triple crossing.
But the worst was at Gauribidanur, where there were 5 trains that crossed in the opposite direction, and our train was stationary for more than one hour. That was not all, it again stopped at Odarahalli for double-crossing, and Rajankunte for a crossing.
I was to get down at Yelahanka (if the train stopped). But ironically, the train didnt stop there, and by the time I reached K R Puram, it was already midnight (instead of regular arrival time of 4:20 pm). Because of this, I also missed the beautiful scenery of Makalidurga and Thondebhavi, since by the time the train arrived there, it was already dark.
Perhaps, this was the worst delay that a train faced FOR NO REASON AT ALL. Can anyone suggest what needs to be done to reduce this? (One possibility is doubling the Yelahanka-Guntakal line. Another possibility is giving incoming trains more priority.).

Translate to English
Translate to Hindi

5209 views
1

Oct 06 2017 (13:57)
Reva18~
Reva18~   56837 blog posts
Re# 2498789-1              
Avg. speed only 50, so this doesn't get priority.
Translate to English
Translate to Hindi

5196 views
0

Oct 08 2017 (18:15)
Nothing_Like_WDM2
Nothing_Like_WDM2   327 blog posts
Re# 2498789-2               Past Edits
Massive train delays are nothing new.
On 01 MAY17, 16613 reached KJM at 02:15 due to some goods train derailment near Solapur, and took 8 hours between DMM-KJM.
During the 90's it's predecessors 6333/35/37 occasionally ran late by +24 hrs...
It is a question of proper time table management on this single line section since ages and timings should have been adjusted by IR
...
more...
long ago.
This train has never reached KJM before 17:10 at the minimum. Just go back in history and see that this train was a replacement to 6333/35/37 trains when they were rerouted to KR during 1998.
IR should immediately revise timings between DMM-KJM as:
HUP 1425/30
KJM 1725/30
BWT 1825/45
just like its predecessor.

Translate to English
Translate to Hindi
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