Due to something unfortunate today between Woking and Surbtion trains are disrupted. My heart goes out to those involved in this. Incidentally, although they don't like to say where it has occurred, it's actually very easy to work out where, as the station has been cancelled from services on the live depature boards and at the moment, only that station. The guard in the train said where it was though.
Based on pervious experiences I had been waiting to see how long it would take for the 8:07 to Waterloo via Cobham to be cancelled. That's how long it would take to be cancelled after it should have run, rather than in advance.
The 7:34 arrival, which makes up this service, was cancelled and what has happened in the last is that the 8:07 hasn't run but it's not been cancelled until some point after it should have run.
However today they actually ran the 8:07. We were told to stand back as the train pulling into platform 1 didn't stop there. Of course it did as it's a bay platform.
Initially it was expected at 8:07, then 8:08 and then it was delayed. Even that was fast. Eventually some station staff said we would be leaving once he got the addition of the people running the train. It left 5 minutes late. I'm not use to such quick turn arounds at Guildford for stopping trains
Not sure how I can check where it has come from. Was this the coaches that formed the 7:34 but they decided to run it out of service, fast between Waterloo and Guildford? You have expected the 7:34 to still run, abet non-stop, were it coaches from that service. Maybe they came from Wimbledon depot.
The 7:35 was running late but I was 4 minutes too slow to catch it. I hadn't planned to catch it and just didn't have time.
It left 7:48. The coaches to form that service arrived at 7:40. So 8 minute delay, which is the kind of turn around time I'd expect on stopping services at Guildford during disruption. I guess no incoming trains crossing the path of the 8:07 and staff being in the right place helped to keep it to just 5 minutes.
Another interesting thing was the 7:12 to London Bridge. That still ran from Guildford, despite fast services being pathed via Cobham but it left 4 minutes after the 7:16 stopping service. Now the 7:16 stops at all stations between Guildford and Effingham Junction. The London Bridge, only London Road. Needless to say its 20 minute delay became 27 minutes by the time it departed Effingham Junction. It had already lost 2 minutes by the time it departed London Road. So the in between stations accounted for 5 minutes of delay.
Another intresting thing was the 7:34 Guildford to Waterloo. This fast train was the first to travel via Woking, although it isn't booked to stop there. It departed 1 minute late and arrived into Waterloo just 3 minutes late.
Contrast that with the 7:45. It departed on time but got stuck at Woking Junction for 13 minutes. I assume all the platforms were blocked at Woking awaiting people to take the trains somewhere.
Based on pervious experiences I had been waiting to see how long it would take for the 8:07 to Waterloo via Cobham to be cancelled. That's how long it would take to be cancelled after it should have run, rather than in advance.
The 7:34 arrival, which makes up this service, was cancelled and what has happened in the last is that the 8:07 hasn't run but it's not been cancelled until some point after it should have run.
However today they actually ran the 8:07. We were told to stand back as the train pulling into platform 1 didn't stop there. Of course it did as it's a bay platform.
Initially it was expected at 8:07, then 8:08 and then it was delayed. Even that was fast. Eventually some station staff said we would be leaving once he got the addition of the people running the train. It left 5 minutes late. I'm not use to such quick turn arounds at Guildford for stopping trains
Not sure how I can check where it has come from. Was this the coaches that formed the 7:34 but they decided to run it out of service, fast between Waterloo and Guildford? You have expected the 7:34 to still run, abet non-stop, were it coaches from that service. Maybe they came from Wimbledon depot.
The 7:35 was running late but I was 4 minutes too slow to catch it. I hadn't planned to catch it and just didn't have time.
It left 7:48. The coaches to form that service arrived at 7:40. So 8 minute delay, which is the kind of turn around time I'd expect on stopping services at Guildford during disruption. I guess no incoming trains crossing the path of the 8:07 and staff being in the right place helped to keep it to just 5 minutes.
Another interesting thing was the 7:12 to London Bridge. That still ran from Guildford, despite fast services being pathed via Cobham but it left 4 minutes after the 7:16 stopping service. Now the 7:16 stops at all stations between Guildford and Effingham Junction. The London Bridge, only London Road. Needless to say its 20 minute delay became 27 minutes by the time it departed Effingham Junction. It had already lost 2 minutes by the time it departed London Road. So the in between stations accounted for 5 minutes of delay.
Another intresting thing was the 7:34 Guildford to Waterloo. This fast train was the first to travel via Woking, although it isn't booked to stop there. It departed 1 minute late and arrived into Waterloo just 3 minutes late.
Contrast that with the 7:45. It departed on time but got stuck at Woking Junction for 13 minutes. I assume all the platforms were blocked at Woking awaiting people to take the trains somewhere.
Last edited: