@GWRHelp I'm highlighting how much I was delayed 2015.Over a days worth of delays + season ticket prices rise again pic.twitter.com/0BlOHA3lxH
— Hi. I'm Ralph. (@Hi_Im_Ralph) December 31, 2015
1 @GWRHelp @GWRUK late train, 1 min late, New Year is upon us, first train of year is LATE!😂
— oxfordgas (@oxfordgas) January 1, 2016
2 @GWRHelp @GWRUK late trains 17 mins delayed
— oxfordgas (@oxfordgas) January 1, 2016
@GWRHelp the 9:09 from Paddington to Slough hasn't left yet and the driver hasn't announced anything. What's going on?
— Jack Santos Silva (@JackLSilva) January 2, 2016
@JackLSilva Hi Jack. This has been delayed due to a train fault – we will get you on the move ASAP. Sorry about the lack of announcements.
— GWR Help (@GWRHelp) January 2, 2016
@GWRHelp it's just left. The trains on this line are ALWAYS delayed for some reason! Had to move trains as that one broke, ridiculous
— Jack Santos Silva (@JackLSilva) January 2, 2016
@GWRHelp any reason why the 1143 to reading is sitting in Langley for the past 10 mins? There has been no announcement why.
— jared (@jarerd) January 2, 2016
@GWRHelp do you know how long the delay is to 1232 Rdg to Ealing B?
— Steven Buckley (@stevenbuckley) January 2, 2016
@jarerd Hi Jared. I'm very sorry about the disruption today. There was a mechanical fault on the 11:43 train. Anne
— GWR Help (@GWRHelp) January 2, 2016
@stevenbuckley Hi Steven. Can't tell for sure I'm afraid. This has been delayed due to an earlier fault – will get this running ASAP. Anne
— GWR Help (@GWRHelp) January 2, 2016
@GWRHelp is the 17.32 reading to Penzance being held for those delayed put of Paddington?
— james abraham (@_jamesabraham) January 2, 2016
@_jamesabraham The 17:32 is delayed at present due to a fault. If you end up missing it then I would advise speaking to staff at RDG. Jim
— GWR Help (@GWRHelp) January 2, 2016
3 @GWRHelp @GWRUK late trains 40 mins delayed, 1 connection missed
— oxfordgas (@oxfordgas) January 2, 2016
4 @GWRHelp @GWRUK late trains 46 mins delayed, 1 connection missed
— oxfordgas (@oxfordgas) January 2, 2016
@gwrhelp first journey of 2016…. Late. And you wonder why we moan about price increases
— iwishihadaspacebar (@spacebar69) January 4, 2016
Day one of the commute 2016…..and train stuck behind another broken down train. Oh, joy! #commuterhell #GWR #fgw
— Clive Illenden (@cliveillenden) January 4, 2016
@GWRHelp @GWR_help @Crap_GWR @late_GW @gwr_apologises pic.twitter.com/SGed71GFUZ
— Fabrizio Corsaro (@corsarof) January 4, 2016
@CommutingRants @GWRHelp @naughtytrains @GWRUK 18.35 to westbury late as ever!! No refund for Jan ticket either grrr
— liz bj (@berth007) January 4, 2016
@berth007 Hi. Apologies for the delay. This got caught behind a service which had a fault. Grant
— GWR Help (@GWRHelp) January 4, 2016
First @GWRHelp train of 2016, and she's late. A foreboding start to the year. Is the excuse generator PRIMED?!
— Gordon Manners (@Gordon_Manners) January 4, 2016
@GWRHelp 613 bath to London pad 'Delayed'. Any further info please?
— (*-*) (@pheadtony) January 5, 2016
@pheadtony Apologies, being delayed with a train fault, don't have estimate for movement as yet. -Ollie
— GWR Help (@GWRHelp) January 5, 2016
.@GWRHelp I knew the punctuality wouldn't last! Delays between #Swindon & #Paddington #HappyNewYear
— Rob Simms (@robertsimms) January 5, 2016
.@GWRHelp the late one – 06:41. But the departure board shows a few delayed ones. It's due to a 'train fault'. No kidding, eh? #samerubbish
— Rob Simms (@robertsimms) January 5, 2016
@GWRHelp 07:15 also showing delays. Increase of service prices, no change in poor service #frustrating
— Rob Simms (@robertsimms) January 5, 2016
@robertsimms This is unfortunately due to the earlier train fault at Bristol (with the 06:41). -Ollie
— GWR Help (@GWRHelp) January 5, 2016
1st day back and train us delayed. Nice to see continuity. #GWR
— The Traveller (@scattem) January 5, 2016
Day two of 2016 commute and shock horror our train is delayed @GWRHelp. No info or apology at station. Where is it? 07.42 Henley-Paddington.
— Miss R Dubs (@miss_rdubs) January 5, 2016
@miss_rdubs This was due to a train fault. Apologies if no information was announced at Henley. James
— GWR Help (@GWRHelp) January 5, 2016
@GWRUK Day #2 of commuting with GWR for the New Year, Day #2 of delays with GWR
— Scott McCollum (@scottamcc74) January 5, 2016
@GWRHelp An apology would suffice but unfortunately I've been delayed every day since October when I started using your service.
— Ross McGlasson (@rossmcglasson) January 5, 2016
@rossmcglasson Apologies for this. Train was late starting at PAD because it was delayed on it's inbound journey to London. James
— GWR Help (@GWRHelp) January 5, 2016
2nd working day of the year. Second delay on @GWRHelp train already. 7.44 from Chippenham cancelled. Fare increase paying for itself…
— Ashley Wootton (@Awootton86) January 5, 2016
@GWRHelp 0759 from Mai to Pad just sitting in between Langley and Iver, no Comms to passengers, what's going on?
— Young Commuter (@YoungCommuter) January 5, 2016
@YoungCommuter Apologies, this is being delayed due to a train fault. -Ollie
— GWR Help (@GWRHelp) January 5, 2016
@GWRHelp 7.58 RDG-PAD is running slowly. Just went through Maidenhead. Will we be delayed getting into Paddington? Thanks
— Sophie (@miztransmission) January 5, 2016
@miztransmission Apologies, delays towards Paddington due to a broken down train near Iver. -Ollie
— GWR Help (@GWRHelp) January 5, 2016
@GWRHelp any idea why we're travelling at 10mph Reading to Pad?
— Dom Feurtado (@Feurtadom) January 5, 2016
@misslaylaj Apologies, currently being delayed due to a fault with the train. -Ollie
— GWR Help (@GWRHelp) January 5, 2016
