• Our booking engine at tickets.railforums.co.uk (powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

InfoBleep nerdy trip reports

Status
Not open for further replies.

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
So this morning I saw the 7:19 Guildford to Waterloo was delayed due to a level corssing fault South, so I knew I'd be unlikely to make the 7:32 from Woking. Thus I opted for the 7:35 via Cobham.

Alas today that got held up at Horsley, due to a late running train from Effingham Junction. We were 4 minutes late departing Effingham Junction and 6 minutes late departing Cobham.

Alas control decided that they needed to skip all the stations between Surbtion and Waterloo. Not for our benefit but the general benefit of overall train running.

The guard did say there was a train from Woking a few minutes behind that we could catch. Not sure which timetable they were looking at. Even of they were thinking off peak, the next service wouldn't be until x26. Today it's x31 due to the x26 running fast to Waterloo in the morning peak. There is nothing in between. Still at least passengers can claim delay repay, depending on their eventual destination. The x31 has a good chance of being on time at Surbtion.

This occurred last week too. I wonder now often the stations between Surbtion and Waterloo are cancelled. The train will now add to the number on the fast line to Waterloo, as I'm sure it does semi-regularly.

Be interesting to see how many others alight. It's most of my back carriage. Next train will be cosy.

For some stations it would be quicker to go into Waterloo and out again but they haven said they hags allowed so I assume they'd prefer to pay delay repay.

As the train left Surbtion, a fast line train zoomed through platform 2. I wonder at which point they will move the train onto the fast line or will they just make it wait north of the station.

If they do that they will delay the next fast train, which has just pulled into platform 1.

The train from Effingham Junction was delayed due to a late train in front of it. It had all it's stops between Raynes Park and Waterloo cancelled. At least Raynes Park has more trains running.

The train that came into Effingham Junction to form that service was 6 minutes late with no reason given. It was 2 minutes late into Ewell West and departed 3 minutes late.

It arrived into Epsom 5 minutes late and was 6 minutes late leaving there. I cannot see any passenger trains ahead of it.

It's possible it had to wait for the 7:17 Epsom to Victoira service to cross its path. That left a minute late. So by being 3 minutes late it could have simply lost its slot.

Will be interesting to see how late the 7:35 is into Waterloo. And to think they want to run even more fast line trains in the future. At least if they did that the Effingham Junction delayed inbound service wouldn't delay other trains north by reversing in the sidings, as it wouks head to Guildford.

The 8:26 was delayed so I expect the 8:31 will be delayed. Its currently showing as on time but departed Thames Ditton 2 minutes late.

The 8:31 has i
8 carriages and no station staff thought to tell people standing the whole length of the platform. Wonderful.

After this train the next one isn't until 8:57. Don't they care about passengers? Anyway I held the door open as it was closing, to ensure everyone who wanted to get on did. As far as I could tell they did. All the platform staff did was blow their whistle. No announcements at all.

I can't see how anyone from Berrylands, New Malden or Raynes Park can board this service. Well the odd person might. I need to cross everyone else in the carriage vestibule to potentially get out at New Malden. Surprisingly someone did get on at Berrylands.

The train left there 3 minutes late, although practically 4 down.

I of course alighted at New Malden. I was expecting to. I was now 24 minutes late.

Incidentally someone's bag stao got stuck in the door. It was so packed.
20190702_084018.jpg

There was a train just 3 minutes behind but no idea how packed that was. Under such circumstances I might wiat but it would depend on if I had a connecting train. If I was going to change for a train on the Sutton loop I most definitely wouldn't wait.

Nothing on Journey Check to say the 8:31 from Surbtion is short formed, yet I thought it was mew t to be 10 carriages. Certainly passengers k. The platform were expecting that. I've read that South Western Railway are meant to self report short formations and thus they should be showing on something like Journey Check.

The 7:35 got into Waterloo 6 minutes late. South Western Railway's argument would be that it would have been even more delayed had they not removed the stops. I cannot disagree with that.

Once off at New Malden I saw my bus was 7 minutes away. I noted below that there was now ticket barriers at one sides of the underpass. I'm surprised South West Trains didn't put in ticket barriers at both sides. I'm aware they tried something but not aware of it being ticket barriers at both ends.

The new ticket barriers, also have a door opposite them. The older ones were closed but the new ones, including the door, were open. I didn't see any staff.

As I got to the bus stop the traffic looked heavy. Yet soon by bus was only 1 minute away. We departed at 8:44, so a saving of 2 minutes over the predicted departure time. I just tried to look my bus up on Google Maps to see if I had the depart time right but it was giving me some rubbish. Their journey planning system isn't great. Don't know if that is due to TfL data or themsleves?

I think the bus I'm on maybe late. Either way it seems to be making good time. I should cut my overall delay down by about 5 minutes.
 
Last edited:
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
This evening I thought I'd take a unique journey with. That is a fast train from Wimbledon to Woking. These only occurring during Wimbledon.

In the past I've boarded direct trains to Guildford but those don't start until 20:41.

I thought I might have time to visit Sainsburys first but decided not so.

I walk down to platform 7 and 8. Now all fast lines are barrier off so you have to go through gates.

I heard an announcement about entering beyond the waiting area, so off I headed. I saw a lot of people standing here. My train was due at 19:20 and it must have been 19:18 by now. I couldn't figure out why the barriers weren't open, given the numbers wa ting to board the train. Are they only letting so many on.

It was reasonably deep but then I saw further up the platform an entrance gate that was open. Oh maybe this is for people waiting for a later train.

Once I got to the area, I noticed their was a 19:17 to Weymouth but it didn't sink in. I heard an announcement about next stop being Basingstoke but it didn't sink in.

Train pulled in and after letting others on, I got on it. It was a 10 car train. I again heard an announcement about Basingstoke and then it dawned on me, this may not be my train.

I happened to have joined where the guard was and asked, does this stop at Woking? No was the response and I got off. Phew.

I then waited for the train to Portsmouth Harbour, which runs via Basingstoke. It arrives at 19:25. So just 5 minutes late.

Unlike the previous train it was 8 carriages ans thus myself and others had to stand. They didn't declassify first class as a lot of this Wimbledon traffic would alight at Woking and that was only 15 minutes away.

Just before we were pulling into Woking, the guard helpfully informed us we'd be arriving to platform 5 for a change. This suited me as my next train was from there. If I didn't need to switch platforms though, I just happened to arrive at the right point to use the footbridge.

I won't be making this unique journey opportunity again any time soon but I'm glad I made it once this Wimbledon. Even if I did have to stand. Still at least we weren't as squashed as on the 8:31 Surbtion to Waterloo this morning. Both were though more rammed than that infamous Virgin Trains service Jermey Corbyn got.

When the 19:20 gets 12 carriages, if that is due to happen, I might reconsider it. Saying that I might just do it again next year, just the once, for thr hell of it, even if it's 8 carriages.

Once I got on the train to Guildford, I also happened to be in the right place to alight and use the footbridge. This train was also 8 carriages but less busy. It would be better for one to go up to Clapham Junction from Wimbledon and board this train there, if a seat was considered important to them. Obviously not every ticket would be valid via Clapham Junction.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
This morning I decided I wouldn't get the 7:35 from Guildford. Good job too as it was cancelled due to a train fault

Still at least everyone on the Cobham line was affected and delayed rather than just those wanting to get to New Malden and stations between Wimbledon and Vauxhall inclusive. More delay repay due. No one promoted the claiming of delay repay yesterday. I just happen to know it was due.

So I was aiming for the 8:07 today but as stopping to do something first I just missed it. I thought this might occur, yet still did that thing which caused me to miss it. Still there was a late running 8:02 fast service so I boarded that

We arrived into Woking on platform 4 on this. The sliver lining for missing my earlier train. This is mostly a down platform and I'm not away of any up Guildford trains regularly pathed to use it. So I was quite happy to alight here for a change. I like arriving or departing from unusual platforms.

There wasn't any useful stopping services from Woking that werebrunning late so I waited for the next stopping train, which incidentally I'd seen at Guildford. It was on platform 2 for a change. Normally is platform 3.

I could see that other trains were running three minutes late but this train was only showing as a minute late. I correctly predicted though that it would be three minutes late and it was. Congestion caused by earlier delays. Still this train is usually good at not incurring further delays on route to Surbtion. Not so sure beyond that though.

Sometimes there are no buses due within ten minutes, at a bus stop with six regular routes throughout the day, today there are seven! I got the first K2. Two bus stops down the road the other K2, that had been showing as a minute behind overtook us. Luck of the draw. Bus behind doesn't always overtake. Not sure what the average stats are on this when buses run close together. Still as long as we didn't need to stop at the next bus stop, we might yet overtake it. We did and the traffic was now too bad to overtake anyway. The K2s run every 10 minutes so no idea what cusses them to run together. I can't remember if they are a low frequency or high frequency service. I think it maybe high but I don't ever notice them having their service regulated Iike some of the other high frequency buses I use.

I got into Surbtion just before 8:59. The bus departed the bus stop at 9:04. We got passed the University bus stop at 9:13, where opposite was some university building works. I think a construction vehicle was reversing into the site.

We have reached my final destination today soon after. Whilst getting the bus was technically faster, today I didnt feel it was fast enough to justify not walking. Hindsight is a wonderful thing though.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Yesterday evening I debating weather to get the 16:57 from Surbtion. So glad I didn't as it was cancelled due to the train crew being delayed.

I got the train after it instead. My journey was uneventful but my connecting train experienced delay creep of about 6 minutes.

This morning I opted for a train with declassified first class at the rear. It was too busy for a seat so I decided to exercise my right to stand in the declassified first class vestibule. If I'd stood in the front one, I could have been penalty fared, so I was quite happy to stand in the rear. I was only going to Three Bridges and purely enjoyed standing there because I could.

Once at Three Bridges I picked up another class 700. As it stated from here, I was able to get a seat in the declassified section.

I was only going to Redhill on this service. By the time we got to Redhill we had experienced some minor delay creep. Now I stood on the platform where others were standing. It was in the 1b section so perfect or so I thought.

Alas it wasn't, as the 3 car train that pulled in, was further up the platform. Everyone had to move down and board the last carriage, which invariably would have further delayed the train, which was already slightly late, if it wasn't for the fact drivers a d guards change ends.

I didn't think I'd get a seat but to my surprise many stood in the vistubal or went right. As a bonus it was a former first class compartment now running as standard so contained the most comfortable seats of the three trains!

I got into Guildford 5 minutes late, the largest amount of delay creep of the morning.

I noticed that the 7:35 from Guildford was 5 minutes late leaving Wimbledon this morning but as it had only been 2 minutes late leaving Surbtion, it didn't have its Wimbledon stop removed.

It's the first day this week it's stopped at all the stations. The train to Effingham Junction, which delayed it earlier this week, was just 2 minutes late leaving Ewell West. It was able to enter Epsom Station prior to the train to London departing there and it appears to me, this is the reason why it didn't delay the 7:35 and that was allowed to stop at all its advertised stations.

In the last 100 days that 7:35 has had an 8% chance of it not stopping at New Malden or to be exact not stopping at Cobham or New Malden, save when it might skip Cobham but stop at New Malden.

This evening I needed to head to Kew Bridge. The train from Guildford was delayed due to a signalling problem. That actually suited me. I noticed that the 16:47 departure from Guildford stopped at all stations between Haslemere and Guildford, as did the 17:00. Yet I'm not aware of the reverse in the morning. That is stops at those stations going south, so close together. Usually a Fats train runs in between or the gap between services is larger. I must look again to be sure.

Whilst at Clapham Junction, awaiting my connecting train, a Reading service pulled in with only 5 carriages. It was rammed. To their credit someone announced over the tanoy it was only 5 carriages.

If only someone would do that on platform 13 when trains south on the Brighton Mainline are short formed it would be great.

East Croydon seem to be good, in that they even announce when trains are not short formed but of a shorter length than the maximum the platform can handle. If only more stations would do that.

When the train to Kew Bridge turned up, I was surprised at how rammed it was. Surely it's not a short formation they missed?

No it was just 10 rammed coaches. No wonder they want to introduce new rolling stock with more space than on the 707s. By about Putney it had thinned out a little and I got a seat.

I wonder if the he rail minister ever travels on rammed trains to get the full experience?

The train was 7 minutes late into Kew Bridge, having departed Clapham 4 down. Before it reached Clapham Junction it was only showing as 1 minute delayed. Definatly some delay creep.

I've now worked out the reason, the previous train to Weybridge was cancelled due to a shortage of train crew.

I hadn't realised just now delayed the flight rain had become. And nor how long it takes to cross the road at Kew Bridge. Crossing the bridge over the road he Thames, I also tripped over a paving slab sticking up.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
After a nice trip to Kew Bridge, including a walk along the River Thames - isn't it beautiful there, it was time to head home. I'd gone to The National Archives for an event.

I opted for the 21:26, which I just made because it arrived late. I kind of knew I would.

Once at Clapham Junction I walked along the underpass. I noticed that the newsagent was still closed but the notice said they hoped to reopen the unit as soon as possible. I must Tweet Network Rail and ask when this might be it's been closed for some months. If they weren't going to reopen it, surely they would say so.

I boarded the 21:52. It arrived late and departed a minute late. Nothing unusual there.

However as we neared Woking we slowed down. We kept stopping.There was radio silence about the situation. Well why should they tell us passengers what is going on. We were soon 4 minutes late at 23:14, which was 1 minute after we should have arrived into Woking. Eventually we got in 12 minutes late. A delay creep if I ever did see one.

I knew there was a signalling issue between Aldershot and Farnham and I could see a Weymouth train was on time leaving Waterloo but 6 minutes late departing Wimbledon.

I can see why they would stop trains at Wimbledon but it does seem to cause delays. I guess for two weeks they can put up with it but if it was all year around then pase gees would have to find alternative routes.

However I couldn't see yet but that Weymouth trisn lost another 6 minutes to Woking.

As we departed Woking the guys finally broke their silence and ended the usual message with a comment that we'd be in Portsmouth at 23:47. I guess as a stopping service it would make up timr where it usually waits at Haslemere.

Following the usual message the guard finally apologised for the delay and said we were 10 minutes late due to congestion. There seems to be quite a bit of congestion of late. I guess there always is, just that sometimes I notice it more.

At least the delay creep was converted into a reason. Interestingly the next train to Portsmouth only arrived into Guildford 4 minutes late, despite the fact it too stopped at Wimbledon. I wonder why there wasn't congestion delaying that as much. What caused the congestion to peter out? Especially as the next Portsmouth train skips Clapham Junction, not that the congestion was at Clapham Junction.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
This evening I decided to make use of a unique journey opportunity. The two week version of it. That us to catch a train from Berrylands at x47 rather than get a train from Surbtion at x50.

The Surbtion train was faster with air con, if it works and loos too but the Berrylands train was a unquie journey opportunity.

I'd have to run for it and save 9 minutes. I could do it though. So I went for it.

I kind of half needed the facilities but I reckoned I'd make it. Just don't drink or eat anything on route and I'd be fine. There is always a risk running for a train that has no loos and departs from a station with no loos. What if the train broke down in the heat? I'll take the risk I decided.

I crossed the first few busy roads fairly easily and continued my task. The train hadn't left Hampton Court yet and the trains in front of it from Surbtion were on time.

I slowed my pace a little for a breather. I soon felt my legs might be starting to stiffen a little so I picked up the pace and that seemed to help. Problem didn't come back.I checked the train and it left Hampton Court on time.

Eventually I got to near Berrylands with 5 minutes spare and 4 minutes to reach my destination. So I switched to a walking pace

I reached the path with roughly 1.5-2 minutes spare. Great. Then I saw a sign saying please stand back the next train doesn't stop here. What now? Have they forgotten to input the train.

Soon in the a came and out went a train without stopping. Surely the x41 has left. No.

The x38, which comes from Alton, actually stops additionally at Esher today,due to Horse racing. Therefore it was due to depart at x40. This meant the x41 from Guildford had to depart at x43. Note this train often departs Surbtion a minute late due to it arriving in a a minute, as although the x38, today x40, nearly always departs of time, it still manages to delay the x41, today x43. It must depart half a minute late or something and the next train needing the full three minutes to depart on time.

After the x43 today, the train was the x45, that was an additional service. Now the if the x43 can't keep to time, 3 minutes after the x40 has left, what chance does the x45 have, given it only has 2 minutes since the previous service Sure enough it departed 2 minutes late at Surbtion and at Berrylands, 3 minutes late. Thus I could have slackened my running sooner. The train made up one of the delayed minutes at least and I caught a connecting train at Clapham Junction.

The usual x46 today is retimed to x50. It is allowed 5 minutes between services and it stops additionally at Esher too. It managed to depart Surbtion on time due to the gap between services.the gap is usually 5 minutes, with it departing at x46. That seems a suitable gap.

I'm not saying they could do anything about the earlier ones though. I'm just recording it as facts

When I got out at Clapham Junction I headed to platform 12 via the subway. It said a train was due. Great so up the stairs I went. As I got to the train the doors were locked. Not so great. Haha. The departure screen still said the train was due.

At some stations they have a message saying please stand clear the next train is due to depart. Given Clapham Junction is Britain's busiest railway station, I'm surprised they haven't implemented it here. Most be some technical reason why they haven't, as it would be a no brainer. If they had, had such a message, I wouldn't have made such an effort to get up the stairs. Of course at places like Guildford, such a message is broadcast as trains pull in and passengers are getting off.

I guess the upside is that the train won't clear from the board 5 minutes in advance if the train is delayed but hasn't left. This occurs regularly at Waterloo and means if your changing platforms, you can never be sure which train will depart next. You could arrive 5 minutes before a train actually leaves and miss it.

The next train was due in 5 minutes but I looked around to see if there was a board advertising the next Victoria service from platform 14. As there was nothing other than boards advertising local services heading south on the south western mainline, I headed back into the subway to locate a platform 14 departure board. The next platform 14 train was in fact due in 8 minutes, so I headed back to platform 12 and waited. I'd eventually joined a train that was 3 minutes late. The train I just missed had been 4 down.

Once at my destination I could have done some more running but I decided being a few minutes late wouldn't be a problem.

Later on it was time to head back south. I had ppanett of time to make my train and did some with. Couple of minutes to spare. There was an ammouncememt about passengers boarding as it was about to depart.

Not sure if they do that at Waterloo in the morning peak.

Once I got to Clapham again, it was time to wait the fast train to Portsmouth. At one stage their was an announcement for the Fareham train and whilst it was on going a separate tsnog announcement started up. I'm surprised it didn't cut out the other announcement. So now you have two announcements competing. The manual one, asking a passenger to meet someone, won. However I have reasonable hearing.

Soon that train left. When I reach the platform my question had been, would my train be on time?

It was certainly listed as on time. In the end it arrived a minute late and departed a minute late. This is fairly common. The next question would be, would it be delayed passing through Wimbledon, given that trains were stopping additionally at Wimbledon.

Twice I've been through Wimbledon this week on fast lines, heading south and I've been delayed. For some reason today though, I wasn't further delayed. No idea way though. I can't believe less people were leaving Wimbledon at this time today, compared to Tuesday.

As it turned out, for three days this week, this train was on time. Its just that I travelled o. The two days it wasn't!

The train got to Woking on time and Guildford. I noticed that in coaches 5 to 8 t,hey had moved first class. For coaches 1 to 4, they had not as it hadn't been refurbished yet

When the class 444 trains are turned round, they often say that first class has shifted ends, on Journey Check and on station departure boards. Well for this service they didn't say anything. I guess with first class being spaced out across the train, rather than located at either end of just in the middle, they didn't feel the need.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
This morning I'd hoped to get one of the rare direct trains from Haywards Heath to Redhill but the one I needed to catch, in order to make my connection to Guildford, has been cancelled due to engineering works not being finished on time. There is of course no other way to make my connection, as every other train connects with a different service.

However this meant delay repay would be due as I'll have to set off later than I'd planned. If I was going to Gomshall or Chilworth I'd be 2 hours delayed so it's lucky for me I'm not. I'd only decided to go back this morning, so I could get the train all the way to Redhill. Otherwise I'd have travelled last night.

No other train this morning from Haywards Heath was cancelled of course. The over running engineering works only affected that single train. The reason for this is that the train came from Victoria and couldn't leave. All the other trains seem to have started from Haywards Heath or at least not Victoira. Of course by 7:30 the lines had reopened. Alas the train to Haywards Heath starts at 7:00am. There were of course other cancellations but none of them went to Haywards Heath.

My journey yesterday was interesting. I was hoping to get the 10:09 from Guildford to Gatwick Airport. I was running late, as I'd been trying to find something. However the trisn was also 5 minutes late so perfect. It departed 10:13 and I was on board. Now that isn't 5 minutes after 10:09. No the train actually should have departed 10:08 but I thought it was 09. In here lies the problems, the train departure times keep changing for different hours. I wonder if Rhyd occurs for any other train service as much.

You get:
5:10
6:12
7:08
8:09
9:09
10:08
11:08
12:10
13:08
14:10
And so on. You could just assume everything departs at x08. That's fine until you get to after 22:00 when the train departs 22:06! The only train on a Saturday to depart that early. I assume you could aim for the x06 but then there would be times when you'd arrive 6 minutes early, if you allowed yourself 2 minutes before the x06 and not everyone wants to do that.

Once I got to Gatwick Airport I just missed a train to Eastbourne and Littlehampton that was running late. Unbeknown to me the 10:58 had been cancelled due to an emergency alarm being pulled and a train fault. The emergency alarm was also delaying other trains. So I ended up on the 11:05, which to my surprise actually arrived on time. It wasn't coming from Victoria but still its a summer Saturday with nice weather so I'd expect delays. This was officially my connecting train.

As it was a class 700 it was time to locate declassified first class section. Now there was also a chance it woild be full but equally there was a chance it would have space due to the leisure passengers not realising it's declassified. Sure enough it was the latter. As I was getting my seat, so were two other other passengers. They said it had been announced that it was declassified.

Given that was the case, I'm surprised more people didn't bother going to that carriage. Perhaps they valued a quicker get away at Brighton. There were seats elsewhere but equally there were groups of people standing here and there.

The desssified section was busy but not full..it's hard to say whether it was more rammed than the service Jemery Corbyn got but probably and I wouldn't even class it was rammed! Haha.

Thai train then arrived into Haywards Heath on time. That must be quite rare for this train at that time of morning on a nice summers day.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I noticed today that trains to Reading at Redhill, which use platform 1b actually just stop so that the end of the train is just past the 1b marker board.

In addition to this, the front of the train is actually beyond the 1a master board!

I was planning on getting the 10:50 train today but it was delayed due to a lack of train crew and would thus be terminating short and not at Wimbledon.

I decided to go to the platform and see what happens and the train left on time. I wonder if the trai. Was always going to leave on time. If so then someone used the wrong delay reason.

The train today was formed of 8 carriages. It's not booked to run as 8 carriages so the additional ones must have been a stock move.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Today I am aware in advance of it being announced, that stops on my train could be removed. I'm not sure if control are aware. I wonder how many other passengers on my train are aware. What about the guard of this train. Unless they check the running information of trains ahead and why should they, they probably won't be.

The 7:30 arrival from Waterloo into Effingham Junction was 5 minutes late today. It was 3 minutes late at Ewell West and due to a train from Dorking going about its usual business, it missed it's path and was 5½ minutes late departing Epsom, as it was last Tuesday.

If its late departing Epson surely that shoo should lead to the same delay at Effingham Junction but necessarily so.

When this happened last Tuesday it delayed my train at Horsley, as it had to wait for the Effingham Junction train to do its journey from the Effingham Junction siding to the station and depart.

Surely enough we are currently waiting at Horsley. I wonder howong it will be before the guard and/or driving makes an announcement.

Anyway last week on Tuesday they cancelled all the stops between Surbtion and Waterloo due to this. If they do so again today. It will be 4 week day morning 7:35 Guildford to Waterloo trains, out of 6 that have had stops removed or been completely cancelled.

How interesting no announcement from the guard and we are leaving Horsley at 7:51. Why were we not so delayed as last Tuesday? I see last Tuesday it pick up additional delay at Ashtead, which for some reason it didn't today.

Last week the 7:30 arrival of 6¼ minutes late. Today it was 5 minutes late. Last week the 7:46 departed at 7:53. This week it was 7:50. So given it was only 1¼ minutes later arriving into Effingham Junction last Tuesday, why did it take an extra 1¾ minutes to depart back to Waterloo?

Last week we departed Effingham Junction at 7:56¾. Today we departed at 7:54¼.

It will be interesting to see if the 2¾ minutes makes all the difference, along with other trains running ahead. I guess it might depend on how the trains from Woking are doing, as if this train gets delayed outside Surbtion, that might give call to have its stops removed, even if other trains aren't running to bad ahead. I don't actually know but I find it fascinating all the same.

The train got to Cobham 3¼ minutes late. At Surbtion it only departed 1¾ minutes late though. So it made up half the time. Had it additionally been 2¼ minutes later departing Cobham and maintained that today at Surbtion, it still could have departed before the next fast train to Waterloo needed platform 1, as it could have last Tuesday too.

Today the train occupied platform 1 for just 1 minute. Last week it was 1½ minutes. The extra, half minute was for passengers needing to get off due to it skipping stations. What this shows is that when trains are late, staff need to turn around as quickly as they reasonably can. When stops are removed, the train will occupy the platform for longer.

Finally the margins for traj a having stops removed are very slight and tight. Just another 2 minutes and the train might have had it's stops removed.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Something rare happened today. The 7:35 Guildford to Waterloo left Hinchley Wood on time. Whilst, for as long as I can remember, it's been rare for the stopping Cobham line trains to arrive and depart Surbtion on time, it aascommon for the morning trains to be on time into Hinchley Wood.

Well checking the recent stats of the last 100 days, it appears it's no longer the case and getting into Hinchley Wood on time is also very rare. Anyway its to be celebrated and noted today, given how hard it is to now achieve. I don't know the reasons for this.

This evening I was thinking how good it is now that the 18:49 arrival into Woking from Waterloo carries on to Farnham and doesn't delay the 18:54 by much. No missed connections. Not that I'm on the 18:52 arrival after it, every day.

Well I almost spoke to soon. Tonight the 18:58 swichtrd to platform 4. It was only a minute late so unusual for this to happen. Usually the signaller also let's it be delayed and keeps it to platform 5.

Anyway I got out of the 3 minute delayed 18:52 arrival and noticed the next three trains listed were:
1. 18:54
2. 19:20
3. 19:11

Yes they were in that order. Obviously a CIS fault. So I then started running to see the other screen, for details of the 18:58, as I had been at the carriage 4 or 5 mark and the other screen covering all platforms is beer the stairs, which is around coach 9. I guess I could have glanced over to platform 4 but didn't think of that. Sure enough 18:58 had switched platforms.

Once on platform 4 I asked a member of staff if it had been announced. They said yes, 5 minutes ago. I asked if it woild be possible for it to be announced for passengers coming off the previous train, as its an official 5 minute connection.

They replied the guard may mot be aware. I responded that I was wondering if it could be over the tanoy and not the guard telling us They responded there are lots of trains and they can't announce it for all of them and it was a last minute change. I protested saying it is an official connection.

Soon in came the train and as it did, it was announced over the tanoy. It was hard to make out what was being said but ti probably was about the platform change. I suspect this was coincidental bug even so, who'd have time to get from platform 5 to 4, given the train was now in?

I think everyone caught the train. I kept an eye out to make sure. If they are mot able to announce it for passengers coming off an official connection, the least I can do to check to see if everyone managed to board. I made my point. I think it will fall on deaf ears though.

I don't know who works on the tanoy and I imagine they have other jobs to do. If they do though, I'm surprise they are able to announce such a change 5 minutes in advance, as surely they'd be busy doing something else half the time and not be able to announce it.

People could at least claim delay repay, depending on which station they are going to. Since the timetable change and the moving of the 19:14 to 19:11, delay repay wouldn't automatically be due to all stations north of Haslemere, if you missed the 18:58, save if the 19:11 is also delayed.

The 18:58 only had 8 carriages today, instead of 10 and it was shown on Journey Check. I'm sure this service use to be 12 carriages.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
On Wednesday morning I boarded the 7:35 at Guildford. As I got towards London Road I realised I didn't have one of my bags. Cue getting off the train and heading back to collect it. If at first you don't succeed, try again. So I did and my next journey was more successful.

In the evening I was lucky to avoid the trespass incident at Guildford by not going there.

I was actually on a train that passed through East Croydon. It incurred delay creep. At one stage the delay time just switched to delayed at Clapham Junction. No reason of course give but very soon they put back a delay time.

On Thursday morning I noticed there were signalling problems between East Croydon and Oxstead.

These were listed against the Guildford online departure board though and there was nothing against East Croydon, despite the 60 minute delays.

Of course no trains from Guildford go to East Croydon, let alone Oxstead. I think direct trains from Guildford to East Croydon stopped running in the 1960s.

Anyway I let National Rail Enquiries know on Tweeter and got a thanks. An hour later it still hadn't be corrected

No idea if it ever was a,s the disruption is no longer occurring. Maybe there was some technical issue causing it, that couldn't easily be resolved.

I'd love to have a demo of the systems they use.

I just missed a Victoria train this morning at Haywards Heath. I got to the platform just after the doors closed. It was however running 5 minutes late. It's original 6 minutes delay creep had occurred at Littlehampton, it's starting station and it had not managed to make up much time following that.

The next train was on time at this point but of course left late. I got to East Croydon late but was able to pick up the X26. We experienced some traffic but got to Wallington Green OK.

At this point I got have got a 407 but it higuht no maybe this will be faster. However is forgotten how short the journey time between Willington Green and Carshalton High Street is. It was long enough for me to get engrossed in something and almost miss getting off.

Sure enough as I got off, there was the 407 behind. I managed to board it and we set off first. I'd also forgotten that the X26 has some waiting time.

As we were going along the driver announced the bus would now be terminating at Sutton Post Office. Bang goes my time saving I thought, as I'd have to walk the final bit, which ever bus I'm on and if the X26 overtakes is, given we stop at more bus stops. There was no 407 bus directly behind us. In fact we were 4 minutes behind one in front.

However despite stopping at more bus stops, as I got off the 407 outside Sutton Post Office, there was the X26 pulling in to the stop in front.

Therefore the 407 change was still faster., even though I had to walk the final part of my journey. 407 bus stop was also closer to my final destination. We are talking metres but still.

This evening I could have got a fast train from Wimbledon to Woking but I decided as it's likely to be 8 carriages, I should just leave it for the Wimbledon crowds to use and board other trains, that although busy, will likely have seats free.

I was at Clapham Junction and the Haslemere train was 1 minute late. Then 2 and then 3. Eventually the Exeter St David's train was announced and was on the board as departing at 18:29.

At which point someone came over the tanoy to tell us to dismiss rhw announcement and that the Haslemere train would be first. About half a minute later the board updates to reflect this. Automated systems can be great but at times they can give out misleading information.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Usual delay this morning. Well its not extremely uncommon but uncommon in affecting the train I'm on.

A train has broken down in the Surbtion area. It's not affecting Hampton Court trains but it affecting everything else, well so National Rail Enquiries claim. There claims aren't known for always being accurate.

Needless to say the 8:23 from Hampton Court left Thames Ditton at 8:26, 1 minute late and Surbiton at 8:44, some 13 minutes late. Still they are not being affected by this. I knew even before looking there was a strong chance of them being affected. I decided to ask National Rail Enquiries the reason for the delay to those services.

I overslept today and was running slightly late when wishing to catch the 8:34 to Waterloo but which one? The 8:34 via Woking or the 8:34 via Cobham? The via Woking requires a change and involves fast trains but with a wait. The other is a slow train but direct to Surbtion. The fast connects are due in first but as they use platform 2 at Surbtion won't delay the slow, which night arrive early and thus be faster!

Anyway the situation was resolved for me. As I got to the station I noticed a fast train to Woking was departing from platform 3 and not 5. I was considering catching it. Then I heard an announcement telling passengers to board any train to complete their journey and passengers for Worpolesdon, Woking and Clapham Junction to use the 8:46. I think they said Clapham Junction

They made no reference to the 8:34 via Cobham, which I thought would have been a faster service to Clapham Junction, if you can call a 50 minute journey fast!

Anyway that train was due to leave at 8:34, so maybe that is why they didn't mention it or maybe it was due to the earlier signalling problems between Effingham Junction and Surbtion. They may not have been aware yet that they were in the past.

Anyway at 8:34 the train to Cobham was still there so I got on it. By rights I should have missed it. About 8:35 or 36 the guard said we were being held at a red signal. I could see no train arriving. The other 8:34 departed. As we departed at 8:38 I looked up the 8:34 via Woking. All its intermediate stops, that is Worpolesdon, Woking and Clapham Junction had been removed. Then it dawned on me, the 8:34 had been diverted up the Guildford New Line via Cobham. Thus we were held waiting for it to run ahead.

Now there is no 8:28 via Epsom as that starts at Effingham Junction. I wonder if they would have diverted it, had that service been running. Would it catch up with that service?

It's a good job the guards and drivers know that route.

Anyome going to Woking may be entitled to delay repay but only if the 8:46 is delayed getting into Working as it's due to arrive 14 minutes after the 8:34. The 8:34 takes 11 minutes to reach Woking and the 8:46, 14 minutes. It will probably make it OK too. No it didn't. It was 1 minute late. Lucky passengers.

As the train I was on departed the guard said there was a signalling issue between Effingham Junction and Surbtion and we'd be running slowly. Soon enough though he said the issue had been resolved. Wonderful.

Once we got to Horsley we just departed. Effingham Junction we just departed too. No delays from the Effingham Junction terminator because I departed on time. Now novel.

I thought it could interesting to see how delayed the connecting train at Woking would be, not that it would be possible to join it. I checked later and it was 14 minutes late. Rather surprisingly they didn't remove the Surbtion stop. Perhaps it was felt no time could be made up.

Also surprisingly was the 8;57 stopping service to Waterloo. That departed 7 minutes late and yet still stopped at Wimbledon, Earlsfield, Clapham Junction and Vauxhall.

Where as the 6:41; 711; 7:41 and 8:11 services, which were 5: 7: 8 and 7 minutes delayed respectively, due to signalling issues, had their new Malden, Wimbledon, Earlsfield, Clapham Junction and Vauxhall stops removed. I don't know if their turn around times at Waterloo are much tighter.

It did lead to there only be two trains between 8 and 9 stopping at such stations, one of which, the 8:31 is only 8 carriages. Thatt was also 13 minutes late. So a nice reasonable delay for passengers. They could claim 50% delay repay rate at least. Between 7 and 8, they had 3 other services they were allowed to use, although one of those runs fast beyond Earlsfield. Still there are more trains from Earlsfield.

Not sure how many carriages are on the 8:01 but I'll assume it was cosy.

I thought Cobham was a shorter route to London than via Woking but it night be slower track speeds. Not sure. The 8:34 fast that was diverted, ended up 13 minutes late at Hampton Court junction and got into Waterloo 24 minutes late.

We departed Effingham Junction 2 minutes late so had made up half our delay. We gained a minute at Cobham itself but that often happens.

Shows though what occurs when trains are not so busy. The guard was really good as he kept us up dated with the delay time and everything else. If only all guards could do this when there are delays and they aren't busy helping passengers or dealing with something else that's more important.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Yesterday morning I just missed the train by seconds. My fault though. I misjudge my time.

This morning I thought I'd judge the time better but then needed the loo agian. As the train I was boarding had no loos I needed to do this first.

This caused me to arrive at the same time as yesterday and thus promptly miss my train. I could have tried to squeeze through the doors both days, as they were closing, but I didn't wish to do such a thing. One shouldn't do such a thing. I saw someone do it this morning. In their case the train was late but I don't think the doors weren't closing for the final time, so they should have pressed the door release button.

It's a shame the 7:35 trains weren't delayed. The 7:16 was 4 minutes late today and had London Road, Clandon and Horsley removed. Alas they couldn't remove Wimbledon, Earlsfield, Clapham Junction and Vauxhall, as the train doesn't stop there. Hard luck for those wishing to catch a train from Effingham Junction at 7:46. Still delay repay should be due to them I'd they did. London Road passengers could at least board the 7:12 from Guildford to London Bridge as it stops there.

I boarded the 7:45. This however was delayed by almost 4 minutes. It turned up on time and had a green light to go, so I don't know what the cause of the sudden delay creep was. We weren't told anything. I don't think it was the lady who stopped the doors from closing when she could have just pressed the door release button. Just because the train is late doesn't mean the door release button stops working. Anyway staff told them not to do that, to which they side, out of range of the staff, I will do it again. Commuters for you.

I was hoping I don't miss the 8:02 to Waterloo, at my next port of call, Woking. We didn't wait at Woking Junction, which was a help and we even made up some of the delay time. What a novel thing to have happened. In fact passengers even had a chance to catch the 8:00 to Weymouth. It's an official cross platform change but that's still not a reason to be able to catch it. Today however it a. didn't arrive in until 8am and b. there was time even t board if it had arrived on time. Its waits for no one, other than staff needed to run the service of course.

They didn't feel the need to remove the Worpolesdon stop from the delayed 7:45., perhaps unlike the 7:16, they felt the time could be made up. Today it was justified, as it did.

In fact the 8:02 from Woking left on time. That is surely extremely rare, if the arrival from Guildford is delayed into Woking.

Good thing about these trains is that they have loos on board. Of course I don't need the loo now.

In the history of trains, the one thing I shall remember South Western Railway for, is the novel idea that all trains should have loos. Who'd have thought it. I don't doubt it might change my journey decisions at times. This morning I wouldn't have missed the train that's for sure. Anyway this is a future luxury to be looked forward too.

As a footnote, the 7:16 passed through Horsley on time. Could Thye not have only removed two stops rather than three.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Having just said I wouldn't board a train as I he doors we e closing, I will now given a reason where I would.

The 8:31 from Surbtion is just 8 carriages long. Station staff asked passengers to use all avilable doors. The 8:11 didn't have any stops removed but despite those passengers not wishing to board this train, there are still a lot of people wanting thus train. There isn't another stopping train until 8:57.

So station staff blew their whistle and the doors started to close, as passengers were still getting on. Every passenger got on but they had to reopen the doors so maybe something got caught in another carriage.

Now I didn't think it was safe to board whilst the doors were closing and a member of staff at Guildford told someone not to do it today. However it's not the first time I've send this happen at Surbtion. Maybe it's a regular occurrence for the 8:31.

Well someone needs to tell staff not to close the doors as passengers are still boarding. If I had been one the last passengers, I would have carried on boarding the train and I think today 3 or 4 had to go through the doors as they were closing. I'm sure they didn't wish to wait another 26 minutes for the next train.

Just think if the driver was the one closing the doors on this train.

One things for sure though, the train got delayed on its journey and more and more got on and squash in. I guess the next train would be just as squashed, which is why they don't wait.

I wonder if this train ever features in the top 10 busiest trains.

I he tain was held up outside Raynes Park as it stopped more than once but rather unusually this didn't occur at Wimbledon. Usually if stop starting occurs piror to Raynes Park, it carries onto Wimbledon.

I could have alighted at New Malden and got a bus but I opted to take my chance a d alight at Wimbledon for a train. I had time at least to make the connection, were we late, which of course we were but only 2 minutes.

I've been on trains from Guildford to here that have been 2 minutes late on leaving New Malden and I've missed trains at Wimbledon due to further delays. So not being further delayed between Raynes Park and Wimbledon, on an already delayed train, is unusual, especially during peak rush hour. I might even go so far as to say its rare.

I wouldn't be surprised if it was extremely rare.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
This evening I needed to pop into M&S before heading to the station. I then had to run for my next train. I reckoned I could make it.

As I got closer I wondered why Google map were showing one route I'd taken before, another than was 3 minutes slower but not one that involved a footpath. The footpath looked just as fast as the quickest route. So I decided to take it. Alas I missed a turning and ended up the longer route. Still with my rubbing I made the train.

I was at one stage thinking I'd leave 20 minutes later but I was fortunate I didn't as a train I was on, sadly had to be diverted via the Guildford New Line.

It was 3 minutes late leaving Clapham Junction and it would be interesting to see it would fair on this route, given it wasn't a train being pathed around stopping trains as planned in the timetable but just pathed this way because of circumstances.

There was some delays towards Oxshott but it then sped up. Once at Effingham Junction it understandably had to wait as it now caught up with one of the stopping trains. My guess would be the 18:03 from Waterloo via Cobham.

Our train will be about 20 minutes late. Half due to slow trains ahead and the reminder due to platform needing a free platform at Guildford.

The 18:07 Guildford to Waterloo was 3 minutes late to allow a fast train to depart first. We had to wait for both of these.

Then we had to wait whilst the 18:53 departed platform 3. We can't I believe reach platform 4. The guard said we were waiting for the 18:19 to leave but that hasn't reached Guildford yet.

That would now be waiting for us to depart. In fact we weren't even on the platform departure screen. That was the 19:19. Due to depart at 19:21. Needless to say the guard had to advise people of this as few people got on for Waterloo.

Passengers for Basingstoke were told at the station that they believed they could go via Reading.

By 19:21 they had updated the screens so say the Haslemere train would now depart platform 3 and the train to Waterloo was delayed. There was a red signal ahead so not sure what was delaying the Haslemere train.

The Haslemere train was now delayed too. Maybe there isn't staff to take the train forward. It is of course blocking a line that the 19:19 would use.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I managed to avoid todays signal failure by not traveling by trisn.

However if I had I wouldn't have been delayed because the train I'd plan to catch was on time throughout.

In fact the 17:24 from Hampton Court to Waterloo and the 18:07 from Guildford via Cobham to Waterloo were both in time at every station. Give the major delays at Waterloo of over an hour, due to earlier linesiss fire and mutual pe track circuit failures, it's amazing. If they managed every station to Vauxhall, you might expect a final delay into Waterloo, given platforms 16 to 22 were out of use I believe.

Thats very rare feet inseed. Your unlikely to see it again any time soon.

It of course only occurred because the 18:38 Surbtion to Waterloo was 11 minutes late and the 17:26 Surbtion to Waterloo was 15 minutes late. Those trains aren't known for always being late bur the former is known for delaying the 18:41 regularly, even if the former officially leaves on time.

Delving into the figures for the last hundred days I can see that thr 17:01 Surbtion to Clapham Junction service arrived on time 50% of the time. 18:07 Guildford to Clapham Junction arrived on time there just 14% of the time, with an average delay of 4 minutes. Into Surbtion it dropped to 10%, although the average delay was now 3 minutes. Into Cobham it did at least jump to 64% with a delay of 1 minute. At Hinchley Wood, the stop just before Surbtion it was 32% with an avwegae delay of 2 minutes. This goes to show how a further 22% of trains end up not being on time after leaving Hinchley Wood on time. It will be interesting to see if a future timetables, with changes train times, improves upon this.

I actually got a train to Gatwick Airport today. It was slightly delayed, which is to be expected. The train, the 17:09, has a 21% chance of arriving into Gatwick Airport on time, with an average delay of 3½ minutes. Today it was just a minute late.

My connecting train was also delayed, by a minute but it did arrive into Haywards Heath on time at 18:09. Whilst I wouldn't say that was extremely rare, in the last 100 days it's only occurred 51% of the time. Average delay is 2 minutes, which sounds about right.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Today the 6:51 arrival from Waterloo to Guildford was 4 minutes late. According to National Rail Enquiries the 7:03 was delayed by 6 minutes due to a late train in front.

It's the same train and I can't see what is late about it.

The 7:12 to London Bridge was also cancelled from Guildford and started short at Effingham Junction due to a late train. The inbound service itself was running late but it too was delayed due to a late train in front of it.

Maybe some other service was sent via the Guildford New Line. I can't spot anything obvious. Anyway it lead to all the stops between Cobham a d Hinchley Wood inclusive being removed so the trai would get to Surbtion right time, which it actult managed to do today.

Over night and last night South Western Railway gave the impression services would be OK today, following the signalling fault.

To quote them:
0000 Update - Repair work on the cables were completed by engineers and no further problems have been reported.
https://twitter.com/SW_Help/status/1151633522865688576?s=19

0100 Update - Earlier cable damage was rectified by engineers. No further issues have been reported since.
https://twitter.com/SW_Help/status/1151643333095284736?s=19

0200 Update - No further issues have been reported as we continue to monitor the area.
https://twitter.com/SW_Help/status/1151658143547559936?s=19

0300 Update - There are currently no further updates to report.
https://twitter.com/SW_Help/status/1151674991580258304?s=19

0400 Update - No updates to report at this time. We will continue to monitor the area through this mornings peak service.
https://twitter.com/SW_Help/status/1151688132439564288?s=19

0500 Update - There are no reported issues with the infrastructure this morning. The incident yesterday caused a high level of disruption resulting in stock being displaced across the network. We strongly advise you check journeys before travelling at https://t.co/mBbkFQEmEn
https://twitter.com/SW_Help/status/1151709154232426496?s=19

There response about displaces trains to one Twitter user complaining was:
Hi Lara, due to the severe disruption over the past two days, train units were unable to return to their scheduled depots for the start of service. Once we have been made aware from our depots of their stock/unit levels we provide this information.

Apologies for any disruption caused by this. ^AJ
https://twitter.com/SW_Help/status/1151741306705711104?s=19
https://twitter.com/SW_Help/status/1151741312250654720?s=19

I feel like they habe shot themsleves in the foot here. Under what circumstances would all the stock be back in place for the next morning, ffollowing such major disruption? Thus wouldn't it have been better to say we don't have the information yet but there is liable to be disruption in the morning due to stock displacement.

I knew last night there would be stock displacement, so you'd hope South Western Railway would know thus. Of course not everyone else would and even if they did, I imagine they'd like South Western Railway to acknowledge this is likely to be the case.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I just got on carriage 5 of an 8 carriage train just now and to my surprise, no one got off. It's the 17:30 from Waterloo to Portsmouth Harbour.

The train was busy though with people standing and all 2 + 3 seating seemed to be occupied. Clearly enough people didn't mind sitting in between two others, even if they might be hit and sweaty.

Two got off at Worplesdon and someone took one of the seats. I didn't take the other as my journey is too short.

At one stage this evening we were racing the Alton train, having previously been over wkne at Surbtion. However towards Woking we were cautioned due to the Kate running 17:43. That was delayed due to awaiting a member of train crew and then got further delayed behind the 17:48 stopping service to Guildford which was on time.

Worth nothing the 43 and 56 all stop at Woking and Worpolesdon but the 48 doesn't. So today within 6 minutes one has two services to Worpolesdon.

Once we pulled into Guildford our train stopped at the end of the platform. I thought 8 car trains stopped in the middle. Perhaps the driver forgot it was an 8 car train. Certainly the guard didn't mention it.

Another surprising thing at the weekend was the cost of travelling between Clapham Junction and Ealing Boardway. Just £1.50 for fully fare paying adults.

Given the journey time I was surprised.

I did hear from either of guards this evening. Must have been busy 0
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I was thinking of getting the 6:52 Guildford to Clapham Junction. So glad I didn't as the Clapham Junction stop was removed due to congestion.

The train arrived into Woking on time but was 2 minutes late leaving there. Was that due to passengers have to get off? They allow the train about a minute for passengers to alight and board normally.

It arrived just 4 minutes late into Waterloo. I am half expecting some criticism on Tweeter for this removal as it's the last fast train to Clapham Junction from Guildford and the last one from Woking full stop. Until 8:43 or thereabouts. I'm assuming the stop was taken out at Woking. I had a look yes criticism.

I wondered if they would tell passengers to circulate via Waterloo. If they didn't then it's a stopping train to Surbtion, of which you've just missed 1 but you might get lucky if you run around for the next one on platform 1. Running is good for you. Less so if you trip up of course.

Then you need to change at Surbtion to the 7:41, which incidentally left Guildford 11 minutes later than the 6:52

Then you would reach Clapham Junction around 8am, just over 35 minutes late. Still at least delay repay is due at the 50% rate.

The culprit for this seems likely to have been the 5:43 from Salisbury. It was 2 minutes delayed departing Salisbury, 4 minutes late leaving Woking and 9 minutes late leaving Clapham Junction. This delay creep as no reason given for it online journey planners. The Twitter staff said they were investigating why but I didn't see an update to that.

The 7:07 was delayed leaving Guildford by 4 minutes and delayed into Waterloo but had no stops removed. There aren't any left that could be removed, save for Waterloo itself!

I got the 7:35 myself. Today it wasn't delayed by the 7:46 from Effingham Junction to Waterloo, which was a bonus. It got to Hinchley Wood on time and was so close to arriving into Surbtion on time. Alas although the 8:08 left on time, as it mostly does, this train slowed down towarda Surbtion. Then it sped up again and at one stage we were overtaking a fast train, which doesn't even stop at Surbtion. However we soon slowed down as we pulled in and away they went.

Once at Surbtion the train waited for another minute. Couldn't see the reason for this and the previously on time train left Surbtion 2 minutes late! If this train leaves Hinchley Wood on time then this is a typical mornings delay from Surbiton, with it being typical for the 8:08 to depart on time.

Later looking at Twitter updates it seems there was a signalling issue in the New Malden area and / or Earlsfield. This clearly caused a delay for the 8:08 to join the fast line north of Surbtion.

If only fast trains didn't need to use the slow line platform at Surbtion. That way they wouldn't delay slow line trains when there are delays on the fast line.

I alighted at New Malden today and wished to catch a bus. The 213 was 4 minutes away. By the time I got to the bus stop it was 3 minutes away. However a X26 was due 5 minutes ahead.

It felt like the 213 was being delayed so could I get the X26. I started running. I saw a K1 pull into a side road bus stop but I wasn't sure if it would wait so I ran further

Eventually the bus overtook me near a stop but waited at it so I hopped on.

The X26 was soon arriving into the New Fountain bus stop. It clearly was 5 minutes away. Until the 213, which at the bus stop where I boarded my bus, it was 4 minutes away.

By the time we left the Worcester Park bus stop, the X26 was 3 minutes ahead of the 213. There have been times in traffic where the X26 hasn't been any faster but today isn't one of those.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
More recent travel surprises.

The person on the tanoy at Gatwick Airport today said please stand back as the train from Reading is a peak time train and will be full of people getting off with luggage.

I was in the centre of the platform at least. Hardly anyone got off. That surprised me. It might have surprised the person manning the tanoy too.

I think there was more luggage at either end of the train, which coincidentally are the narrowest parts of platform 3.

Which takes me back to last nigh when I changed at Gatwick Airport. There is hardly any space to get off and move. It's no congested with people waiting to get on and lots with luggage getting off. No idea if they advised people to stand up last night but if one carriage is now clear of people then they start to board. Of course those from firth back carriages are now queueing to leave.

The central of the platform has more space but there isn't room for everyone ons busy but not rammed train to be in the centre coach.

Compared to somewhere like London Bridge, which admittedly handles far more railway passengers, it's not a great experience.

This morning I had planned to catch two swrvices with declassified first class but both were running late and National Rail Enquiries App reported disruption. One service from Three Bridges was 10 minutes late, so no way would get get me to Redhill in time.

However it left Horsham on time so it would have been possible. I can only assume it was late into Horsham and the system or someone thought it needed more time to turn around than it actually used.@

Yesterday I noticed large gaps on the Portsmouth Direct line in the morning due to a brocken down Southern branded train at Bedhampton. They weren't able to turn any trains short at Guildford or extend any to Guildford either.

They did at least allow the 8:22 the luxury of stopping additionly at Worpolesdon. It made sense, even if it did lead to delays further up the line, given the previous service had been over an hour before that. They didn't allow the 7:37 to stop there, probably because it would lead to delays further up the line. There is a difficult balancing act during disruption.

Apparently if they stop a late running train at a station, when it's not arrived on time, it would lead to delays elsewhere, so said a response to a question I asked on Twitter, regarding the 7:16 the other week, which had it's first three stops removed but it had passed through on time at it's final stop of the three.

Many times are trains late by a minute for stops and they aren't removed. Had they said we felt it would not be on time by Horsley but as it transpires it made up more time than estimated, I might have understood more. I wasn't on the train myself.

The other evening, Tuesday, I was surprised at how trains arrived with hardly any delay. The 18:18 from Waterloo to Haslemere was late from the depot. I was at Clapham Junction and the helpful staff over the tanoy said it woild be 15 minutes late.

People were advised to get the 18:33 to Alton. This I did. In the mean time in came the Exter train, which despite the lack of the 18:24, only departed 1 minutes late.

You'd think if the other train is delayed, it would delay this train due to more people boarding it. I mean regularly the 18:18 departs 3 minutes late. Maybe the issue isn't stopping at Clapham Junction but the trains ahead which are not stopping at Clapham Junction.

Well maybe people are on holiday I thought but inside there were people standing on the train so clearly it wasn't empty when it departed. This may still be less than usual of course.

Soon the Basingstoke train zoomed through to Surbtion. It departed Surbtion on time.

How is that possible. Surely it should have been delayed by the Exeter train. In fact it got into Woking before the Alton train. Anyway the Haslemere train eventually departed 28 minutes late and they didn't remove the he Clapham Junction stop either

So glad I wasn't on the 18:40 from Surbtion to Woking last night. It passed West Byfleet 4 minutes late, having made up 1 minutes delay but got into Woking 16 minutes late. As I wasn't on it and didn't look it up last night, no idea what caused the additional 12 minutes delay. Actually I think I do from checking Real Time Trains

The 18:49 to Fareham was 12 minutes late. It waited for 4 minutes at Woking for some reason. Perhaps to allow trains across the junction ahead. I've not checked that but. The Alton train was late into platform 4 too and a fast Weymouth train was also due. So it seems the signaller allowed the Portsmouth train to go ahead of the Basingstoke train to clear the path for the Weymouth train. This then lead to the additional 12 minutes delay to the Basingstoke tarin, which still made use of platform 5. Had the Farnham train departed sooner, this may well not have occurred. They clearly couldn't path the Portsmouth train behind the Basingstoke train.

Of course the Farnham train was 5 minutes late leaving Waterloo and 8 minutes late by the time it reached West Byfleet.

I wonder if the delay was acknowledged on journey Check I could well imagine it wasn't. Also no stops were taken out to avoid further delays. It's certainly a balancing act.

At least passengers could claim delay repay if alighting at Woking or even changing trains there. No such luck from Brookwood to Basingstoke though, as it made up enough time to no longer be over 15 minutes late.

By train to Guildford this morning was 6 minutes late. No acknowledgement of the delay or reason for the creep from the guard but they did check the tickets. I suspect it was due to Kate running trains due to the earlier signalling problem in the East Croydon area.

Individual delays on South Western Railway of over 6 minutes often have a reason on National Rail Enquiries abet not always so. On Great Western Railway for the North Downs Line it see a to be that most don't but sometimes they do.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Tonight I could see how many people board the 17:39 Surbtion to Basingstoke, which runs fast to Woking, as the train started from there. This was due to a points failure at Waterloo.

Whilst clearly not as many as at Waterloo, it was more than I was expecting, given it's the holiday period. To think they want to take away fast services from Surbtion during the evening peaks. Peak period would be extended in length too. All these passengers would have to join stopping services to Woking or further.

I can't remember if the number of stopping services will be increased to Woking.

However what else can they do if they need to run more trains from Waterloo? Too many competing interests, some of which aren't as important.

Still it was interesting to board an empty train and see only Surbtion passengers board. The train was shown as being on time and then the time vanished.l with a blank gap. Not seen that before on the departure board. After a time it wqs replaced with due and the train left 2 minutes late.

As the train to make up this services should come from Clapham Yard, I don't know what they did to get it to Surbtion but it did arrive from the north. Maybe it came out of Clapham Yard and then headed south. I've not looked at the track layout there to see which route it could take to get to and through platform 9, assuming it took that route.

On route to Woking the train overtook the Alton train but slowed down on route to Woking and the Alton train went past once more. I then caught a delayed connection at Woking.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Unusual delay creep today. We came to a stand on the bridge over the River Wey as we headed up on the Guildford New Line. I've had this in the reverse, more than once but don't remember experiencing it going up before.

There was no train directly in front of us listed on Real Time Trains, although that's not to say one wasn't running that was added at the last minute. After 1 to 2 minutes we carried on.

There was no announcement from the guard but perhaps they didn't know what was going on either. The driver might know but they have an important job was driving the train rather than speaking to passengers.

The delay was long enough for me get up and walk down the carriage to get some photos through the dirty 455 windows and then consider moving carriages.

As I started to change carriages the train moved forward. I managed to get one reasonable, by my standards, photo though. It shows the River Wey and some people walking by it.

20190802_081058.jpg

Anyway it added 2 minutes delay but I got to enjoy a far less common unscheduled stop. Might as well find some benefit to being delayed rather than just thinking get a move on.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
The 8:07 pulled into platform 2 at Surbtion today 5 minutes late. Doesn't happen often. There was no suitable gap in the fast services for it to do that either. However had it use platform 1 it would have delayed the 8:48 Surbtion to Waterloo. So someone took the decision to delay the 6:50 Portsmouth Harbour to Waterloo via Basingstoke service instead. That was 1 minute late at Hampton Court Junction and 4 minutes late passing through Surbtion. Its not due to stop at Surbtion.

The 8:07 had been 1 minute late leaving Guildford due to a 3 minute late inbound service. That's 3 minutes late according to the passenger timetable and not the working timetable.

On route it then preceded to experience further delay creep. At one stage the train was at Horsley for 2 minutes, despite already being 2 minutes late.

Could have been some issue related to the train or maybe passenger needing help. It wasn't a train ahead as far as I could tell. Either way there was no announcement so I regarded it as delay creep.

It was 5 minutes late into Surbtion, arriving at 8:47. This is a minute before the 8:48, which was on time at Esher. So the signaller put the 8:42 into platform 2, allowing the 8:48 to arrive on time but delaying the non stop.

To my surprise both the delayed 8:42 and 8:48 departed at the same time. I wonder at which point would the 8:48 have joined the fast line.

Since there was no other stops bar Waterloo, they also couldn't remove any stops from the 8:42 to allow it to make up any of it's 6 minute delay.

Currently the 8:42 is due into Waterloo at 9:14, instead of 9:01 as it should be and the 8:48 just says delayed!

Wonder if the guard has commented on the delay yet they did seem busier earlier to give them their due but then they also found time to make announcements, whilst not referencing the delay.

Update: the reason for the continued delay is due to the emergency services being called. Thoughts to all those involved, affected etc. My interest in delays, including of the minor type, are insignificant compared to things like this.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I got to a bus stop this evening to find it closed. That explains why no buses were showing from it on the app, bar 65s. Although as it is closed, not sure why they would show up.

Would be helpful if the data could display a notice above saying the bus stop is closed.

So I ran to the next bus stop. As I was running a bus came past me. I carried on running and due to the number boarding it I managed to catch up.

Turns out there was a bus just behind but I couldn't be certain of this without stopping to find out. I decided if their was a large gap for some reason, I might then miss my train.

Once af the bus stop I squeezed on. I wasn't the last on. I manage to rest my rucksack on the luggage ledge as that was already busy.

Then I heard a medium volume automated announcement about space upstairs. So I squeezed myself though the people stood in the area between the driver and the stairs, one either side of me. I explain I wished to go upstairs as there was space.

No one followed me up. Upstairs most sets of two seat sections had a spare seat. So enough space for everyone standing downstairs to sit down and not block up the walkways.

Later on the announcement again but no one budging.

The driver could have siad the bus is going no further until some people go upstairs as we were close if not slightly over the line where passengers should not stand.

Once I got to the station the 17:11 Surbtion to Waterloo train was on time. Only because the 17:08 to Waterloo was delayed due to a train fault.

Alas a train from Shepperton departed there 4 minutes late and was 6 minutes late by the time it reached New Malden. This added 3 minutes delay to our train outside New Malden. Not that we stopped there. By the time we departed Wimbledon we were 6 minutes late with no announcement from the guard.

I will miss my connection I felt. I usually get an earlier train but today wasn't able to do so. That train I was able to catch of course was on time.

My only hope is a delay to my connecting train but looked like that would be 2 minutes late and it won't be enough. Such is life.

I'm surprised they didn't run the Shepperton train fast to avoid delaying later trains behind it. They have done that before now. In the oast when the Train from Surbtion has been 6 minutes late they remove stops to help ease congestion.

So I ended up on a train to Caterham and I'll change on route. When I boarded, I found myself in first class. People were standing in the first class vestibule. Well at least I thought it was first class.

I've just checked and it isn't. How first world travially annoying. I like sitting or standing in declassified first class. So much of it about in Govia Thameslink Railway land.

A train I was likely to miss at East Croydon was running with a 3 minute delay. There was however one due in 3 minutes behind it. Indeed as we arrived there was a train on the platform. I couldn't remember where the train was heading but it was 17:50 so it must be the train I'll miss.

So I rushed along the platform and up the bridge stairs, slowly as people in front.

Then down the next stairs were everyone was coming up both sides and I had to squeeze though at the side and they had to move out of the way. A couple of people waited at the top but I didn't wish to do that myself in case I missed the next train. The train I'd missed was still on the board but it must surely be like Clapham Junction were the trains disappear after they have left.

Once on the platform it became appearnt the trisn hadn't arrived yet. What I'd see was a previously delayed train.

In fact the trisn I hoarded arrived 7 minutes late. It had departed London Bridge just 1 minute late.

So jumping on the Caterham train was worthwhile. It isn't always as sometimes everything else dpsarts on time and you are just as better offer waiting for the 17:52 service from Clapham Junction.

The on board service personal to their credit apologised for the 8 minute delay by that point. Respect goes out to those guards to apologise. I do appreciate some are too busy to apologise but other simply don't, as was evidence by myself this morning when they made announcements other than delay ones.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
Another rare travel event. I got to depart south from platform 2 at Surbtion. Never done that before. I assumed it caused up fast trains to have to use platform 1 but looking at Real Time Trains it appeared it didn't. It appears there was a gap in services caused by a Fratton train being delayed. That was held outside Surbtion so was delayed by this Farnham train at least but it did pass through platform 2.as intended

Due to an earlier operational incident there is disruption. There was also a separate signing issue too affecting some trains, including the one I'm was on amd the one I should have got on.

I was nearing Surbtion station and saw that the 18:18 to Fareham hadn't left yet. Not only that it was running fast to Woking and it was on platform 2. I could see it. This is the line for trains heading up. It would soon be 18:45 so I imagine it could leave at any time. So I ran for it.

There was a delayed direct train to Guildford due to leave 18:45 and a delayed fast to Woking going to Basingstoke, due to leave at 18:46 or more likely 47 based on past experience. There was also a train to Portsmouth that departed Waterloo, three minutes after the delayed Basingstoke service.

As I wished to get that Portsmouth train I felt it best to go to platform 2 and board the Farnham train. It was at the platform, unlike the other two and surely would leave first

Of course this is the complex railways so anything is possible, given they need as smooth as possible running of the services overall.

As I got on a lady asked me where I was going. I explained Woking and I asked would it be leaving soon. The reply was yes.

Just after that the screen changes to say delayed. It was now 18:45. Previously I think it said due or maybe gave a time it was leaving. It didn't say delayed that's for sure. At which point the fast to Basingstoke had pulled in and the one to Guildford as well.

I now decided my best bet was that fast service.

At one stage the fast to Basingstoke was due in at 18:47 so you might have expected it to depart then, given the information systems tend to do the following

Due time 18:46
Updates to 18 :47
Changes back to 18:46
Arrives 18:46 hut actually departs 18:47

However today that wasn't the case. It arrived at 18:45 and departed 18:46¼. I just missed it due to the numbers getting off the trains and going up the footbridge. Imagine the numbers included those who would have been coming off the 18:18, had it actually departed Waterloo, in addition to two trains arriving at oncr. So equivalent of three trains. To their credit I saw no one using the side stairs going up. There was someone waiting at the top so I don't know if someone had just used it before I arrived These stairs that are narrow and reserved for passengers going down. I find it harder to go past people here when I'm going down, if they are using it going up.

So I then had to join all the people going up. I boarded the train on platform 2 which left at 18:50. If only I'd known which train would depart first. It maybe that the only person who'd know this would be the signaller and given how busy they would be, I wouldn't expect them to part that information on to others.

The train itswlf was very empty and the guard did apologies for the delay.

As we nearered Woking the guard announced the next stop and we then slowly pulled to a halt on the fast down line. I wasn't surprised, as there surely wouldn't be any platforms free.

In fact as I waited a not stopping at Woking Weymouth train went past on the slow line. Perhaps we were waiting for it to go ahead of us. Now the guard has said we are being held at a red signal waiting for the train in front to clear the platform.

Whilst there was a train using platform 5, we actually could have occupied it but in doing so would ha e delayed the Weymouth train our train to Farnham is an extra service about to go into a branch line so we wouldn't be as important. Saying this I'm still amazed we occupied the fast line on platform 2 at Surbtion.

Our train did make up 12 minutes of its delay though as it didn't stop at any stations between Surbtion and Woking.

Had I got on the previous train I would have had to run from platform 4 to platform 5, as they changed the platforms for the Basingstoke service.

As for delay repay. That maybe due to passengers travelling to stations towards Haslemere, as although the 19:11 to Portsmouth was only running 1 minute late, at 19:11 they announced that the next train would not be stopping at the station. Sure enough a non stopping Basingstoke train came through.

That train was running late but should pass first. After it had gone the new revised time was 19:14. I saw a train arriving towards the station and thought this is the train but no it was train to Portsmouth via Basingstoke. A bit later it became 19:17 and then 19:18. At 19:16 I could finally see the train first due in at 19:12 arriving.

Would a flyover help in cases like this? The system certainly can't cope with trains queueing into Woking.

As it got to 19:18 the ttain was pulling into Woking and it was now due to leave at 19:19. I now finished letting the platform seat taking the strain and got onto the train. It indeed departed at 19:19.

The departure time at Woking was revised 5 times. This doesn't occur at Surbtion. Instead they get trains going from being on time to delayed with no reason given and then a short time later a departure time appears. The reason is of course congestion.

Just think if I'd got the other fast train from Surbiton I'd have been into Guildford at 19:10, just 4 minutes late. Had I got the stopping direct serviced, I'd have been in at 19:21. As it is, I got in at 19:28. So just the additional 22 minutes, rather than 4. But I did get to depart South from platform 2.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
The other day, Sunday, I got a train to Waterloo. It was the 8:35 from Guildford. It departed Guildford on time but was late departing Woking. Eventually we got to Clapham Junction 5 minutes late.

What I could work out was the reason for this. The initial delay seemed to be at Woking Junction, yet I could see no train on Real Time Trains that was crossing our path. Perhaps it was a late entry. As we went up to Clapham Junction, we were not following any train according to Real Time Times.

In the evening I got the delayed 20:30. This left 204:5¾. By the time it departed Clapham Junction it was 17 late. So it was losing time.

However by the time it arrived into Guildford it was only 12 late. This shows how much slack there is in the Sunday timetable. I've read they run the railway in and out of Waterloo in the morning to work as if it is a two track railway, instead of four. I've yet to know the reason for the slack in the afternoon though. They surely wouldn't artificially delay trains, yet every train I've been on has got into Woking and waited for a time, assuming it wasn't disrupted like this service was. I've clearly not traveled at the times when they have needed to use this additional time for something, when there is no disruption.

Yesterdsy I got a train from Guildford. A stopping train. It was the 13:28. I boarded it and waited. Then I waited some more. The signal was green but no announcements.

I guessed the guard had not have arrived. It then got me wondering, at what point does the driver know he doesn't have a guard? Would station staff be aware? The board said on time until eventually it said delayed. Don't know if it was automatic or someone changing it once they realised it hadn't left yet.

At what point is the signaller informed? Eventually the green signal turned to red.

A guard arrived after five minutes and said they were a replacement as the guard for the service had not shown up. The train then left. Until the replacement guard arrived, passengers had no knowledge of what was going on, as there was no announcement. I just correctly guessed the reason.

This morning the 7:12 from Haslemere to Waterloo was cancelled due to a shortage of staff. Now this stops at all the stations between Haslemere and Guildford.

There is a 7:20 from there which stops at Godalming and Farncombe but not Milford or Witley. I boarded this at Guildford. It was now 7:45. The train was rather busy and it appeared in the coach I was in and those ahead of it, it was standing room only.

They rarely announce trains as standing room only any more. I'm sure it use to happen more. Maybe at the back it had more space. This surprised me through, as I thought there were extra trains running since May, they would soak up the passengers more generally and disruption wouldn't lead to standing room only. It's also the summer holidays. The 7:08 for example also stops at Farncombe and Godalming so you might think that would pick some passengers up.

Just goes to show that even with extra trains running, if one is canceled then the next train will be busy.

The 8:02 Woking to Surbtion left a minute late. It seems that even in the summer holidays there is still congestion. There are many factors causing this but I'd ha e thought with less people travelling in the morning, the congestion would be less. It may well be but it's still noticeable.

Then at Surbiton I boarded the 8:31, which departed a minute late. Not sure if it was cased by the 8:02, as although that departed a minute late, there was four minutes sitll between the services.

At New Malden I left the train and headed for the X26. It was due in seven minutes. I'd need to get a move on.

As I got two thirds of the way down the High Street, the bus was due in five minutes. That was a long two minutes. Buses I listed as due at 07 and 37. It was clearly neither of those times. According to Google we are currently 11 minutes early at Worcester Park. In fact we are only 3 minutes early. The bus was actually times to depart 8:47 from New Fountain Roundabout as it's running to a summer timetable. So passengers aiming for the X26, maybe left thinking it is always running late in the summer holidays.

A 213 has just gone past us. I'd expect us to overtake it shortly as we have now departed. What it does highlight though is that I could have got that 213 and switched buses at Worcester Park. However I couldn't be sure of that as the bus had been due in seven minutes.

I don't think the automatic estimating that my London Bus Times app does, is entirely accurate for limited stops bus services, as it doesn't seem to take into account waiting time at bus.

The 213 got to North Cheam before us. So I could have got it to that stop too and still picked up the limited stops X26. This is meant to be more of an express bus.

We weren't too long at North Cheam though. However the other bus was still ahead and it would appear that this journey will be slower than if I'd got that bus, even taking into account the fact we left the New Fountain Roundabout first!

As we got to Cheam Broadway, the other bus was ahead.

We would surely now overtake it. No we probably won't as we have to wiat to even out the service. It seems the 213 doesn't need to even out it's service.

I had thought the X26, with its limited stops might overtake any other bus, especially as it departed first. When traffic is heavy I expect it not to overtake but when it's lighter, as it is currently, I thought it might.

What I should have done was switched buses at Worcester Park. This will add 5 minutes onto my journey as the other bus got to the stop I'd use at 9:08. This bus will get to it's stop at 9:09 and then I have a walk.

I think the mistake I make with the X26 is to look at theive departure board. I should always look at its scheduled departure timetable according to the season.

I've not yet found a school holiday one that is mobile friendly though. Then unless the departure time from a always stopped at stop, is later than if should be, do you take into account the live times. Then you compare this to the live times of other more frequent buses. Only then should you work out which bus to get
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
This evening I was expecting delays due to a broken down train but I didn't expect my delay to be caused by a late train from the depot.

As a result I caught a train to Exeter from Clapham Junction. I had thought maybe I should wait for the Alton one, as the Exeter train is usually busy. However I decided to get on board and then there was no turning back as the door bleeps went.

The vestibule was busy with not too much space to stand, although sitting on the floor would just about me possible.

I knew there had been a window seat free but no doubt this was taken. However I decided to walk through the carriage in the small hope of a seat. To my surprise I came across two free window seats. Someone was moving for me and then I spied an asle seat of all things. So I thanked them and took the asle seat as it was easier with my bags.

There was a bag on this seat but the lady moved it. I also spotted another Isle seat with a bag on it. Even a table asle seat with bag on it. So five seats in the second carriage from the front.

Nowiff everyone in the vestibules took a seat I wouldn't have got one but by crowding in the vesttiubles it probably took longer to board and gives the false impression there are no seats avilable. I wonder if any of them moan about the lack of seats!

They did ask us to use all doors but I didn't move down as I wasn't sure what would happen if I was going for another door at this point. Would I suddenly find all the doors close and myself not on the train. What if it was very busy in another vestibule. There would of course be the Alton train.

However I think the cushions on this train are more comfortable. I appreciate the train may not be as safe as a 450 but it's more comfortable at least. That's my opinion.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
As I got into Woking tonight I checked the next fastest train board and it said next train to Guildford due at 18:54.

I headed from platform 4 to 5, in order to pick up the delayed 18:44 to Haslemere.

Once on the platform I could see the train to Basingstoke listed. It was due to depart at 18:54. So two trains at the same platform at 18:54. Never going to happen.

Soon it changed to the Haslemere train and that had an automated announcement. Still both trains due at 18:54.

Soon though there was a correction announcement. This was manual. They said that it was the Basingstoke train that was due to depart.

For some reason I could hear this announcement. I had been told previous manual announcements couldn't be loud due to the neighbouring flats and noise complaints. Apparently as automated announcements were triggered elsewhere, they were exempt form this.

Seems odd but its the railways and noise laws so anything is possible. So on reflection it's surprising I could hear this manual announcement.

The Basingstoke train arrived in shortly before 18:52. How wonderful that the stopping train carries on to Farnham and doesn't need to be locked out of use at Woking. Makes all the difference.

Still the Haslemere train was due at 18:54. Now there was an automated platform change announcement. The Haslemere train would be departing from platform 4.

An Alton train had already departed from there. So I headed over to platform 4. It was now 18:53cand some people, not myself, started running.

Someone on the footbridge going down the stairs shouted. Stop being so f word dangerous and keep to the left. Or words to that effect involving f word and keep to the left.

To be fair I'm not sure if I can see any signs saying keep to the left. Passengers didn't need to run as the train didn't depart until 18:57.

Those running will argue how could they know that given the board said 18:54.

It is clearly more dangerous to run but during delays if passengers can't be sure trains will be held then they will do it.
 

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I haven't had an amusing travel story for a while but here is one.

This morning I got the 7:41 from Haywards Heath. It goes to Bedford. My eventual aim was to reach Guildford.

By getting this train they official journey planner advise is to go to Three Bridges a d change for the 7:54 to Redhill, where one then picks up the 8:14 to Reading.

Now technically I would have more time to join the train to Reading if I boarded if at Gatwick Airport. However at Gatwick Airport the minimum connection time between branded Thameslink services and Great Western Railway services is 10 minutes.

At Three Bridges and Redhill it is just 5.

Cue this morning where at Three Bridges my connecting train was on time. All is good. Only it wasn't, as we got held up outside Gatwick Airport due to a signalling fault. The 8:03 to Reading thus left on time and I missed it.

I will also miss it at Redhill too. Thus delay repay will be due. I won't now get into Guildford until 09:36, as opposed to 8:42. There is irren an x33 but between 8 and 9 there isn't one and you have to get a 9:ț1. I'm so close to being able to claim an hours delay but alas can't. Such a shame. It's disappointing.

Money would have been saved of course if they allowed a 5 minute connection at Gatwick Airport rather than 10 or they made the connection times at Redhill and Three Bridges 6 minutes. If the latter then my journey wouldn't have been offered.

My real reason for changing at Three Bridges was due to getting in some declassified first clsss travel on a class 700. I rather enjoy travelling declassified first class and have so many opportunities to do so.

The signalling fault is affecting platforms at Gatwick Airport and platform 2 can't be used. Needless to say my train used either platform 1 or 2.

I've just realised my train is so delayed and the service to Reading so unequal, that I will get into Guildford just 6 minutes before the next fast train to Reading.

I could have stayed in bed an extra hour. Going up to Clapham Junction and down may of course have been faster but I didn't do that.
 
Last edited:

infobleep

Veteran Member
Joined
27 Feb 2011
Messages
12,556
I was up in London this evening. I was heading somewhere I'd been to before but took one road earlier to us. Although in hindsight this was fine, it throw me. No problem I'll open up Google Maps and get it to navigate my route from there.

Alas I didn't have enough O2 mobile reception. The problem was probably too many tall buildings no doubt.

Anyway I retraced my steps up the road and took my usual route, by which point I had reception. Not that I needed it now. The cricket was still working over my Internet at least. Given that's the case maybe it was another issue as to why the maps would load or maybe the cricket stream had been cahced far enough in advance not to be an issue with the drop out of data reception.

On my way back from London I decided I'd like to pop into Waitrose but which one? I eventually worked out if I made the 19:25 from Victoira, I'd have 20 minutes between trains at Clapham Junction.

As I boarded the 19:25 I found a queue of people trying to get through the last coach. Clearly like myself, last minute stragglers. I then asked someone if someone was sitting in a seat, which had a bag on it. Upon the reponse of no and the bag being moved, I sat down and avoided having to do the British thing of queuing. Everyone else was too polite or scared to ask. I can't read subtle body language do maybe they helps in these situations.

Once at Clapham I did indeed have 20 minutes to visit Waitrose. I then popped into M&S but didn't quite leave enough time as I thought, so had to leg it for the train. Now the x52 services to Portsmouth & Southsea are usually late departing but today it arrived on time.

I got onto the platform about 20:51 and 27 seconds. The service was still being announced. At this time or either precisely at 21:51 and 30 seconds, the doors closed. I wasn't on the train.

There was a member of staff who said the doors were closed. I then protested nicely that it's still being announced. At which point they directed me to the guard who was standing by a door and they let me on. Train left on time.

By rights they didn't have to be so nice and let me on. They do say that 30 seconds in advance the doors will close. I'm extremely grateful for this occurring. However I'm not so sure I would have been so bold as to protest, if the train hadn't still be in the middle of being announced. That spurred me on to question things. Had it not been announced I may have accepted my fate and got the next train.

Interestingly when I put in Clapham Junction to Woking on the National Rail Enquiries App the 18:27 and 19:27 don't show up. Maybe that is to stop Woking passengers using it, as there are other services. However I've never seen any at Clapham Junction told not to board it and I've regularly boarded it myself.

Had I missed the train I was thinking maybe I'd have got the 19:57. However the 17:50; 18:50 and 19:50 all skip Clapham Junction. You'd think may be some timing reason for this but they depart Woking at the same time. Turns out the first is when no fast tarns can stop at Clapham Junction and for the other two, there is a 19:02 to Alton from Clapham Junction and a 19:59. So that is the reason. They clearly feel Alton line passengers need trains at these times of the evening and thus the Salisbury trains must give. The 19:59 stops at Surbtion. Unfortunately the 19:02 doesn't. That's part of the more than an hours gap that exists between fast and semi Fats services heading south from Surbtion. On a purely selfish note, I'd like that plugged.
 
Status
Not open for further replies.

Top