bobm
|
|
« Reply #375 on: July 06, 2017, 20:27:48 » |
|
Realtime Trains is suggesting the 15:49 Paddington - Moreton-in-Marsh has been stationary near the Heathrow Airport Junction since 16:12 (as at 19:56). Is that really the case, or what have GWR▸ managed to do with services which had departed from Paddington and then got caught up in the chaos?
I think there have been problems with the feeds these sites rely on - see http://www.firstgreatwestern.info/coffeeshop/index.php?topic=15702.msg216277#msg216277
|
|
|
Logged
|
|
|
|
charles_uk
|
|
« Reply #376 on: July 06, 2017, 20:33:06 » |
|
Realtime Trains is suggesting the 15:49 Paddington - Moreton-in-Marsh has been stationary near the Heathrow Airport Junction since 16:12 (as at 19:56). Is that really the case, or what have GWR▸ managed to do with services which had departed from Paddington and then got caught up in the chaos?
I think there have been problems with the feeds these sites rely on - see http://www.firstgreatwestern.info/coffeeshop/index.php?topic=15702.msg216277#msg216277I suspected that might have been the case but - even so - what did happen to that service (and others)? Did it eventually get through to Reading or was it sent back towards Paddington? Edit - Realtime Trains is now showing it having arrived at Slough 269 minutes late, and National Rail Enquiries says it will arrive at Moreton-in-Marsh at 21:45!
|
|
« Last Edit: July 06, 2017, 20:38:51 by charles_uk »
|
Logged
|
|
|
|
Adelante_CCT
|
|
« Reply #377 on: July 06, 2017, 20:37:29 » |
|
Realtime Trains is suggesting the 15:49 Paddington - Moreton-in-Marsh has been stationary near the Heathrow Airport Junction since 16:12 (as at 19:56). Is that really the case,
Looks like it is, as it has just arrived Slough, 269 late
|
|
|
Logged
|
|
|
|
SandTEngineer
|
|
« Reply #378 on: July 06, 2017, 20:54:17 » |
|
Network Rail
London Paddington Signalling has been restored and lines are now open. Apologies for the disruption.
06 Jul 17 - 20:49 Well that apology really sounds sincere..........
|
|
|
Logged
|
|
|
|
lbraine
|
|
« Reply #379 on: July 06, 2017, 20:57:52 » |
|
Reading right now !
Three hours on and halfway home.
Reading overbridge is heaving - why - there are no local TV trains until 23:13
How is this justified ??
|
|
|
Logged
|
|
|
|
Adelante_CCT
|
|
« Reply #380 on: July 06, 2017, 21:13:41 » |
|
As if it wasn't bad enough for the passengers on the 15:49, it has now just been held at Kennet Loop for around 10 minutes whilst a class 7 freight was routed through, has now arrived Reading 292 late
|
|
|
Logged
|
|
|
|
charles_uk
|
|
« Reply #381 on: July 06, 2017, 21:35:56 » |
|
As if it wasn't bad enough for the passengers on the 15:49, it has now just been held at Kennet Loop for around 10 minutes whilst a class 7 freight was routed through, has now arrived Reading 292 late
And left 312 late - that's over five hours. That is some delay whatever the length of journey.
|
|
|
Logged
|
|
|
|
John R
|
|
« Reply #382 on: July 06, 2017, 22:04:15 » |
|
Actually arrived 312 late and terminated there (maybe not surprisingly, I'm sure the crew are out of hours). So still a bit longer to wait for those going towards the Cotswold Line.
|
|
|
Logged
|
|
|
|
NickB
|
|
« Reply #383 on: July 06, 2017, 22:21:42 » |
|
Ooooo I'm going to hit these f**** with a big taxi bill this evening. With a vengeance.
|
|
|
Logged
|
|
|
|
Adelante_CCT
|
|
« Reply #384 on: July 06, 2017, 22:23:43 » |
|
No, it arrived 292 late, and then as Charles said it departed 312 late, hence why RTT» says 16:19 - 21:11 (292). It says 312 late because that was the time it did depart, perhaps it continued empty or as a different headcode, but I saw it leave on OTT▸ around 21:30
|
|
|
Logged
|
|
|
|
BBM
|
|
« Reply #385 on: July 06, 2017, 22:48:23 » |
|
No, it arrived 292 late, and then as Charles said it departed 312 late, hence why RTT» says 16:19 - 21:11 (292). It says 312 late because that was the time it did depart, perhaps it continued empty or as a different headcode, but I saw it leave on OTT▸ around 21:30
Might it have become this service, 1Z41 2132 RDG‡ to Worcester Shrub Hill? http://www.realtimetrains.co.uk/train/O10218/2017/07/06/advanced
|
|
|
Logged
|
|
|
|
TaplowGreen
|
|
« Reply #386 on: July 06, 2017, 23:03:38 » |
|
Just leaving Waterloo on the 2258 to Windsor.. under normal circumstances I'd have been on the 1742 from Paddington-Maidenhead and may have been able to say goodnight to my kids......I believe there are some people who are "proud" to work on the railways. Time to look in the mirror & think very hard.
|
|
|
Logged
|
|
|
|
Adelante_CCT
|
|
« Reply #387 on: July 06, 2017, 23:07:31 » |
|
Might it have become this service, 1Z41 2132 RDG‡ to Worcester Shrub Hill?
Yup, that explains that then
|
|
|
Logged
|
|
|
|
teamsaint
|
|
« Reply #388 on: July 06, 2017, 23:13:20 » |
|
If it wasn't before, I think it is now time for a deep level cross-industry enquiry regarding the ongoing signalling reliability between Maidenhead and Paddington. There are far too many minor outages and far too many major ones such as today and yesterday. With the ever increasing numbers of people wanting to travel by train, this simply isn't good enough.
...and while they are at it, they could do something about the seemingly almost daily signalling problems around Wimbledon/ Clapham . Really sorry to hear about the problems in and out of Paddington, must be miserable for anybody affected,
|
|
|
Logged
|
|
|
|
NickB
|
|
« Reply #389 on: July 06, 2017, 23:17:43 » |
|
Absolutely TG. It is not the ineptitude that I resent but the comtempt that I'm held by GWR▸ workers for trying to just get home. I've taken Friday as holiday as I haven't seen my one year old since Monday due to gwr's doing. Utter utter dishclothes from start to finish.
|
|
|
Logged
|
|
|
|
|