Save the Train forum

Dedicate to campaigning to retain an appropriate "TransWilts" passenger train service ... Swindon - Chippenham - Melksham - Trowbridge - Westbury - Dilton Marsh - Warminster - Salisbury ... and to other services too

THIS FORUM IS NOW A READ-ONLY ARCHIVE. Please use our Coffeeshop Forum for new posts

link to main site
Save the Melksham Train

Welcome, Guest. Please login or register.
May 22, 2012, 12:31:26 AM

Login with username, password and session length
Search:     Advanced search
Recommended service - hourly, according to the GWRUS. Let's work towards that service and towards ensuring all services are used.
7889 Posts in 5009 Topics by 97302 Members
Latest Member: eydyyksmuu
* Home Help Search Calendar Login Register
+  Save the Train
|-+  General Discussion
| |-+  Greater Western
| | |-+  FGW Train Updates
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Print
Author Topic: FGW Train Updates  (Read 1921 times)
Steve Bray
Full Member
***
Offline Offline

Posts: 40


View Profile
FGW Train Updates
« on: February 14, 2007, 05:52:36 PM »

I am slightly confused by the accuracy of FGW's service updates.

Yesterday, a colleague from work went to catch the 1757 from Dorking West to Guildford; shortly afterwards, she phoned to say that the train had been cancelled. According to FGW, this train had "no report" next to it and no mention of a cancellation.

This morning, whilst looking at the Paddington arrivals, the 0856 arrival there from Bristol (the 0710?) was showing as "cancelled"; yet there was no mention of this according to the Service Update.

So as usual, maybe all this information should not be relied upon!
Logged
Graham Ellis
Administrator
*****
Offline Offline

Posts: 2062


View Profile
Re: FGW Train Updates
« Reply #1 on: February 15, 2007, 06:00:10 AM »

Steve, comparing the situation 'on the ground' with the various information feeds, I too have observed errors bothe ways - trains described as being cancelled that have, never the less, turned up ... and trains showing "no report" that simply fall off the radar and never show.  I've concluded that at times when only a few services are disrupted it's fairly accurate but it gets to be less and less useful at times of extreme chaos.

"No report *" (that's with a "*) tends to mean "We don't know - we've lost this train"  Grin
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Save the Train | Powered by SMF 1.0.5.
© 2001-2005, Lewis Media. All Rights Reserved.
Valid XHTML 1.0! Valid CSS!
Page created in 5.216 seconds with 19 queries.