bobm
|
|
« Reply #90 on: March 15, 2019, 21:30:39 » |
|
Very frustrating after no reported cancellations for a month up to last Sunday.
|
|
|
Logged
|
|
|
|
grahame
|
|
« Reply #91 on: March 15, 2019, 21:44:09 » |
|
Very frustrating after no reported cancellations for a month up to last Sunday.
My log shows Melksham misses on 6th and 7th ... http://www.mrug.org.uk/record.html ... not sure if they were cancellations all the way through.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
bobm
|
|
« Reply #92 on: March 15, 2019, 22:16:20 » |
|
I was going by the, usually, accurate log on this thread.
|
|
|
Logged
|
|
|
|
Lee
|
|
« Reply #93 on: March 15, 2019, 22:20:17 » |
|
20:08 from Swindon also went via Bathampton missing Melksham.
Rescue loco on the way to move the striken freight train.
|
|
|
Logged
|
|
|
|
grahame
|
|
« Reply #94 on: March 16, 2019, 08:16:36 » |
|
I was going by the, usually, accurate log on this thread.
I suspect the thread is around the 95% accurate rate (not a bad stat if you compare it to trains on time) which is remarkable as it's generated in a way that it requires an asynchronous action from members here to generate it. A simile. It's rather like someone saying "keep coming back to my web site and you'll find what you're looking for there when we publish it" rather than "we'll send you an email / phone you when the data's available". Concerns at missing the odd "happening", especially last minute things (arguably the most irritating to passengers) which don't make JourneyCheck (etc), and the addition of live departure board for Melksham (buses and trains at or near the station - http://www.mrug.org.uk/live.html ) have a allowed us the Melksham Rail User Group site to generate an automatic log at http://www.mrug.org.uk/record.html . That's still "keep coming back" mode, but it's now automated ... we have a visual egg timer that's set every time the page is visited by a real user, and if no-one's been there for 10 minutes the server checks the status to keep a perpetual log.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
Timmer
|
|
« Reply #95 on: March 16, 2019, 15:04:49 » |
|
There were problems this morning with the 8.22 WSB» - SWI» which sat at Trowbridge for 25 minutes causing me to miss my London connection at Bath. I was on the train behind it. It then got held at Bradford Junction. Journeycheck was saying traincrew issues. I also noticed Network Rail staff were at Bradford Junction so there may have been issues there as well. Shame delay repay doesn’t start until April 1st
|
|
|
Logged
|
|
|
|
grahame
|
|
« Reply #96 on: March 16, 2019, 16:35:23 » |
|
There were problems this morning with the 8.22 WSB» - SWI» which sat at Trowbridge for 25 minutes causing me to miss my London connection at Bath. I was on the train behind it. It then got held at Bradford Junction. Journeycheck was saying traincrew issues. I also noticed Network Rail staff were at Bradford Junction so there may have been issues there as well. Shame delay repay doesn’t start until April 1st The 06:30 Cardiff to Portsmouth was very late - 35 minutes late at Bath Spa and 64 minutes late by Trowbridge. The Swindon train left (according to Real Time Trains) a minute after the Portsmouth train arrived (08:58, 08:59), so it is possible that the Swindon train had to wait for someone with route knowledge. There was a Paddington to Penzance train on the TransWilts - passed through Melksham at 09:02, so that would have cause a further few minutes hold at Bradford Junction. Real time trains shows no time for the 08:22 ex Westbury at Melksham, and neither does http://www.mrug.org.uk/record.html - I suspect it ran up to Batheaston and reversed after all that. The extra 10 minutes of delay when it re-appears at Thingley, 47 minutes late, provides further evidence to confirm that.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
bobm
|
|
« Reply #97 on: March 16, 2019, 16:39:54 » |
|
Yes the 08:22 did skip Melksham.
|
|
|
Logged
|
|
|
|
grahame
|
|
« Reply #98 on: March 19, 2019, 07:26:49 » |
|
07:04 Westbury to Cheltenham Spa due 09:05 07:04 Westbury to Cheltenham Spa due 09:05 is being delayed between Trowbridge and Melksham and is now expected to be 15 minutes late. This is due to congestion. Line closed between Swindon and Didcot / emergency services dealing with an incident near the railway. Congestion almost certainly due to this diversion: 06:33 Bristol Temple Meads to London Paddington due 08:14 will be diverted between Chippenham and Reading. It will no longer call at Swindon. It will be delayed due to the diversion and is expected to be 20 minutes late. This is due to the emergency services dealing with an incident near the railway. Roll on a capacity increase ...
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
grahame
|
|
« Reply #99 on: March 19, 2019, 07:36:11 » |
|
My understanding is that the incident is between Swindon and Didcot (near Uffington), not on the TransWilts, but ... 07:33 Westbury to Swindon due 08:15 07:33 Westbury to Swindon due 08:15 will be cancelled. This is due to the emergency services dealing with an incident near the railway. 08:53 Swindon to Westbury due 09:41 08:53 Swindon to Westbury due 09:41 will be cancelled. This is due to the emergency services dealing with an incident near the railway.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
grahame
|
|
« Reply #100 on: March 22, 2019, 18:01:57 » |
|
17:41 Cheltenham Spa to Southampton Central due 20:44 17:41 Cheltenham Spa to Southampton Central due 20:44 will no longer call at Dilton Marsh. This is due to a problem currently under investigation.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
bobm
|
|
« Reply #101 on: March 22, 2019, 18:09:00 » |
|
According to BBC» Wiltshire it seems to be a problem at Dilton Marsh rather than an issue with the train.
|
|
|
Logged
|
|
|
|
bradshaw
|
|
« Reply #102 on: March 22, 2019, 18:19:32 » |
|
Safety issue with the platform according to Journey Check, lasting for rest of service
|
|
|
Logged
|
|
|
|
bobm
|
|
« Reply #103 on: March 22, 2019, 18:38:50 » |
|
Seems to be both platforms. A service from Portsmouth Harbour not calling either.
|
|
|
Logged
|
|
|
|
bradshaw
|
|
« Reply #104 on: March 22, 2019, 19:07:52 » |
|
Might it be problem with station lighting?
|
|
|
Logged
|
|
|
|
|