FGW generally start the day recommending customers take a look at the Journey Check website. This site is supposed to list details of delays, cancellations, engineering works, etc. Now we won’t say they’re fiddling the figures, but on more than one occasion, We’ve stood for a train that was some 20 minutes late that didn’t appear on this Journey Check. It looks like the stats don’t match reality. Should customers really have to chase this up?
http://twitter.com/whatupashbash/status/294869941990084608
http://twitter.com/alasdair_buchan/status/294833722719608832
Good morning. @FGW operating our usual service this morning: short-formed and cancelled. Don't bother using Journeycheck as it isn't shown.
— Last Worst Western (@LastWorstWestrn) January 23, 2013
@FGW why can't you deliver your trains on time…and then you manipulate your punctuality by skipping Maidenhead and Twyford…not impressed
— Stephen Herbert (@s_herbs) February 21, 2013
@FGW are a waste of time. Seems they forgot to send the 18:18 from Paddington and are now ditching MAI as a stop. #railfail
— Chris Allmark (@chrisallmark) February 21, 2013
Hello @FGW At your * the Manager session, one if them said 80% of your trains are "on time". What does "on time" mean exactly in #fgw speak?
— Chris Dale (@chrisdaleoxford) February 21, 2013
@FGW @ghigo_sa somewhat biased figures provided by your own service provider. Would be fairer if an independent adjudicator supplied these.
— [email protected] (@Robbienosh) February 5, 2013
.. and from Rachael one we can probably all relate to: The Invisible Train:
@CommutingRants I saw a new one today. Board said "arrived". Train arrived 2 mins later. Board then changed to "delayed". Hmmm.
— Rachael Chrisp (@rchrisp) February 11, 2013
@FGW your 7:41 train from North Camp arrived into North Camp just before 7:38 and was leaving by 7:39, why so early?
— Dan Buckle (@DanielJBuckle) June 17, 2013
There's only one thing worse than a train running late, and that's a train running early. 08.41 and the 08.43 is leaving Chippenham. @fgw
— MrSlinkz (@MrSlinkz) June 11, 2013
@CoreyLiamB Really sorry for this. Needed to make up time to get to Cardiff on time ^Jess
— First Great Western (@FGW) June 7, 2013
@FGW Reading platform 10 – train is late but monitor says "on time". How does it happend? pic.twitter.com/Vxzzj6yIAV
— Alexandra (@bastinda) June 5, 2013
@rchrisp It will affect he punctuality figures if it is 5 mins late or more Rachael. ^Tara
— First Great Western (@FGW) May 22, 2013
#CowOnTheLine when the time on the clock says 07:59 the 07:56 is *NOT* on time @fgw pic.twitter.com/CBxYYt0V4x
— Judith Lewis (@JudithLewis) May 16, 2013
Maybe this explains daily delays into Padd? Read the date ;) @FGW @mrs_commuter @Swiss_uk @fgwkmc @CommutingRants pic.twitter.com/jaGEuHXNP0
— Pipsqueak (@lil_pippa) May 12, 2013
@2Scooppy Morning Kris. I do apologise for the early departure of the 0439 and I will report that for you.^John R
— First Great Western (@FGW) March 22, 2013
@fgwkmc We don't pick on a particular station but we have to make a decision that will affect the least amount of people ^Jess
— First Great Western (@FGW) March 20, 2013
@fgw 14.03 HAY to PAD just left early. I thought this problem had been sorted out…
— FGW passenger (@victorjones17) March 16, 2013
If you knew it was going to be stupidly busy why not do something to help the situation? Do you even give a sh*t about a good service @FGW?
— EPLTakeover (@EPLTakeover) March 16, 2013
@FGW so there are secret extra trains leaving paddington at times different to the regular timetable? Secret trains aren't much help IMO
— EPLTakeover (@EPLTakeover) March 16, 2013
@FGW Well that’s clever of it. Since it hadn’t even arrived then. Either all the clocks in Hayes are wrong or someone is fiddling your data.
— Matthew I (@Oishiiboy) March 12, 2013
@Stucox2000Cox Very sorry about this. This was due to another service being delayed so we had to cancel this service ^Jess
— First Great Western (@FGW) March 8, 2013
@fgw Another 'arrived' train at Reading I can just jump onto yes? pic.twitter.com/Fbf6BQ4dNK
— MellyM (@molanole) February 26, 2013
@FGW 8.53 HAY to PAD leaves HAY 9 mins late, but due at PAD 'on time', according to the data used for performance stats. How does that work?
— FGW passenger (@victorjones17) February 28, 2013
First Great Western: how "on time" can my train really be, when it was due at 16.59 and at 17.02 it still isn't here? Outrageous lies.
— Victoria (@VictoriaMonro) July 9, 2013
@FGW not aimed at you Jess… But FGW must employ some top statisticians to ensure 'targets' are not missed….that's not a 9 it's a 6!!!
— Louchjd (@louchjd) July 9, 2013
@FGW what delays? Your website said nothing about delays when i checked my journey.
— Laura Brennan (@HistorianLaura) July 9, 2013
Not happy; missed 7.49 from Tilehurst because it left at 7.48! One way of achieving your targets #FGW #CommuterLine
— Russell G Archer (@RussellGArcher) July 4, 2013
Let me just jump on the 07:39 that has 'arrived'… @FGW pic.twitter.com/8hj8TX1Ugs
— Rachel Snelgar (@Rachel_Snelgar) February 26, 2013
Thanks FGW for letting my train leave a minute early, despite me running down the platform to get it. I love being late for work #grr
— Damien A Passmore (@damien_a_p) July 18, 2013
First Great Western: how "on time" can my train really be, when it was due at 16.59 and at 17.02 it still isn't here? Outrageous lies.
— Victoria (@VictoriaMonro) July 9, 2013
@FGW not aimed at you Jess… But FGW must employ some top statisticians to ensure 'targets' are not missed….that's not a 9 it's a 6!!!
— Louchjd (@louchjd) July 9, 2013
@fgw You've done it again. 07.48 Best Drayton to Paddy left early. Greenwich is just down the road, so little excuse. Complaint please.
— Rich (@recklessrik) August 15, 2013
Hey @FGW glad to see the 1709 is on time. Oh wait..! pic.twitter.com/AlOEgroJK1
— the great whyte ✘ (@ukacw) August 19, 2013
@FGW what delays? Your website said nothing about delays when i checked my journey.
— Laura Brennan (@HistorianLaura) July 9, 2013
Not happy; missed 7.49 from Tilehurst because it left at 7.48! One way of achieving your targets #FGW #CommuterLine
— Russell G Archer (@RussellGArcher) July 4, 2013
Let me just jump on the 07:39 that has 'arrived'… @FGW pic.twitter.com/8hj8TX1Ugs
— Rachel Snelgar (@Rachel_Snelgar) February 26, 2013
@FGW Thank you FGW! Please explain why the 6.57 Taplow to Paddington left at 6.56????
— Martyn WW (@turboww) August 28, 2013
@FGW my train from hayes left 3mins early. Who can i complain about this?
— Thoughts Oasis (@Flexdeep) August 26, 2013
9 out 10 trains must run on time? Interesting. Britain's railways between 2014 and 2019 – ORR's final determination http://t.co/ZUpc4Ypn5U
— Rachael Chrisp (@rchrisp) October 31, 2013
We’ll be keeping a close eye on that!
My train is running ahead of schedule. Hopefully nobody was rushing to catch it. Why have timetables if they are ignored? Gotta love @FGW .
— Bren D (@Bren_D) November 4, 2013
@fgwkmc National Rail late: >5 min late on short journey or >10 on long. Everyone else's World such as my boss. >1 second late!=real Life
— Cheeky (@cheekychambers) November 5, 2013
@FGW I can't believe that when you mostly make me late, you actually went early this morning, without me! (1/2)
— James Doyle (@j_doyle) July 31, 2013
@FGW 7.39 doors shut for the 7.41, amazing. Not helped by the sarcastic ticket person stating I must have gone by my watch. (2/2)
— James Doyle (@j_doyle) July 31, 2013
Leave a Reply
You must be logged in to post a comment.