Class 701 'Aventra' trains for South Western Railway: progress updates

[Robert Carroll]

701009 forming the 17:53 Waterloo-Dorking this evening required a reboot whilst at platform 1 with passengers on the train. It departed 17 minutes late.

 

[markle]

Interesting experience tonight on 2I53 (Guildford via Epsom), which was quite a crowded service. Train was taken out of service at Wimbledon. Guard announced that the train was terninating early, then closed the doors before the train had fully emptied. There then ensued a painfully slow process of announcing to people to walk to the rear of the train to get off - which not everyone did.

15 mins later the train is still at the platform whilst the guard tries to get people off. I'm surprised that there was minimal effort from platform staff at Wimbledon.

Surely there has to be a better / more effective way to terminate a service? And any hypothetical timetable recovery benefit from terminating a service early surely must be weight against the practicality of emptying a crowded late night train.

 

[Robert Carroll]

Interesting experience tonight on 2I53 (Guildford via Epsom), which was quite a crowded service. Train was taken out of service at Wimbledon. Guard announced that the train was terninating early, then closed the doors before the train had fully emptied. There then ensued a painfully slow process of announcing to people to walk to the rear of the train to get off - which not everyone did.

15 mins later the train is still at the platform whilst the guard tries to get people off. I'm surprised that there was minimal effort from platform staff at Wimbledon.

Surely there has to be a better / more effective way to terminate a service? And any hypothetical timetable recovery benefit from terminating a service early surely must be weight against the practicality of emptying a crowded late night train.

2I53? Waterloo-Guildford via Epsom are usually 2Dxx.

 

[markle]

2I53? Waterloo-Guildford via Epsom are usually 2Dxx.

There was me being dopey and reading the departure time from waterloo instead of the headcode. You are indeed right, it was 2D67

 

[43096]

Interesting experience tonight on 2I53 (Guildford via Epsom), which was quite a crowded service. Train was taken out of service at Wimbledon. Guard announced that the train was terninating early, then closed the doors before the train had fully emptied. There then ensued a painfully slow process of announcing to people to walk to the rear of the train to get off - which not everyone did.

15 mins later the train is still at the platform whilst the guard tries to get people off. I'm surprised that there was minimal effort from platform staff at Wimbledon.

Surely there has to be a better / more effective way to terminate a service? And any hypothetical timetable recovery benefit from terminating a service early surely must be weight against the practicality of emptying a crowded late night train.

Sounds like an incompetent guard as much as anything. Part of the problem is that the quality is so variable - many are really good. But there are some who seem incapable of making coherent manual announcements in such situations, which is not a good starting point.

 

[Robert Carroll]

There was me being dopey and reading the departure time from waterloo instead of the headcode. You are indeed right, it was 2D67

Makes sense now, thanks.

 

[bb21]

Surely there has to be a better / more effective way to terminate a service? And any hypothetical timetable recovery benefit from terminating a service early surely must be weight against the practicality of emptying a crowded late night train.

There is a train clearance mode which allows guards to close one coach at a time, however that isn't necessarily going to be quicker when you have a fully loaded train. You still have to make several announcements and allow people to empty the first coach before you can do anything with the others. In such cases making announcements and giving people sufficient time to get off, before closing all doors and directing any stragglers to a local door may be the most efficient way to do it.

 

[Nimbus020]

Interesting experience tonight on 2I53 (Guildford via Epsom), which was quite a crowded service. Train was taken out of service at Wimbledon. Guard announced that the train was terninating early, then closed the doors before the train had fully emptied. There then ensued a painfully slow process of announcing to people to walk to the rear of the train to get off - which not everyone did.

15 mins later the train is still at the platform whilst the guard tries to get people off. I'm surprised that there was minimal effort from platform staff at Wimbledon.

Surely there has to be a better / more effective way to terminate a service? And any hypothetical timetable recovery benefit from terminating a service early surely must be weight against the practicality of emptying a crowded late night train.

Interesting - did they say why they had to terminate early? - Plat 9 at Clapham Jct was blocked for a while y’day eve due to a failed ‘450’ on an Alton train - not sure when this eventually moved

 

[Siemens Staines]

I make it 50 701s in passenger service this morning with both (of the 52 FO a.m) outstanding diagrams being two 2*458/4 (2U10 & 2R05).

 

[WWTownEnth]

010
012
016
026
036
038
045
051

are all not in service this morning. Looks like 50 diagrams are being operated by 701s

 

[norbitonflyer]

Surely there has to be a better / more effective way to terminate a service? And any hypothetical timetable recovery benefit from terminating a service early surely must be weight against the practicality of emptying a crowded late night train.

RTT says the cancellati0on was due to an issue with the train crew. So it doesn't look like timetable recovery was the reason for the early termination.

 

[Farnborough]

010
012
016
026
036
038
045
051

are all not in service this morning. Looks like 50 diagrams are being operated by 701s

A quick check... of the five days this week:

• 5 absences: 010, 016, 038, 051
• 4 absences:
• 3 absences: 001, 024, 026
• 2 absences: 011, 012, 025, 054
• 1 absence: 019, 020, 036, 045, 056

One or two days would be normal rotation... I assume the ever-absent four are undergoing servicing?

 

[brooklynbound]

I got on a Kingston bound 701 looper at Wimbledon yesterday. Another passenger was very worried when on boarding the recorded announcement said this was a service to London Waterloo. They clearly thought they were going the wrong way. Why haven't the announcements still not been changed back to the old school ones that changed en route? Surely that must be easier in kit that's 100% digital from day one than on the old 455's. Even Thameslink manages a tidy changeover on the 700's around Sutton.

 

[Vexed]

Even Thameslink manages a tidy changeover on the 700's around Sutton.

It's not all sunshine and rainbows on Thameslink, they've done it as seperate services and headcodes. This means journey planners will offer a 2 minute "connection" at Sutton where you stay on the train if going through that part of the loop.

 

[swr444]

A quick check... of the five days this week:

• 5 absences: 010, 016, 038, 051
• 4 absences:
• 3 absences: 001, 024, 026
• 2 absences: 011, 012, 025, 054
• 1 absence: 019, 020, 036, 045, 056

One or two days would be normal rotation... I assume the ever-absent four are undergoing servicing?

038 is on 5T80 training duties today

 

[bb21]

Just been given the heads up 028 should be reapproved today imminently.

 

[JonathanH]

5 absences: 010, 016, 038, 051

010 has been absent for ages.

 

[bb21]

010 has been absent for ages.

010 is awaiting parts following the lineside strike on 10th August.

 

[Meglos]

Just been given the heads up 028 should be reapproved today imminently.

Booked on the 2F91. 17:02 Waterloo-Guildford.

 

[WWTownEnth]

701001 - In Passenger Service (2 Mar 26)
701002 - In Passenger Service (18 May 26)
701003 - In Passenger Service (27 Jul 26)
701004 - In Passenger Service (10 Jul 26)
701005 - In Passenger Service (27 Aug 25)
701006 - In Passenger Service (6 Mar 26)
701007 - In Passenger Service (24 Feb 26)
701008 - In Passenger Service (31 Mar 26)
701009 - In Passenger Service (17 Oct 25)
701010 - In Passenger Service (22 Dec 25)
701011 - In Passenger Service (26 Feb 26)
701012 - In Passenger Service (21 Jul 25)
701013 - In Passenger Service (28 Jul 25)
701014 - In Passenger Service (9 Jun 26)
701015 - In Passenger Service (7 Aug 26)
701016 - In Passenger Service (4 Jun 26)
701017 - In Passenger Service (25 Nov 24)
701018 - In Passenger Service (6 Jul 25)
701019 - In Passenger Service (18 Apr 26)
701020 - In Passenger Service (8 Oct 25)
701021 - In Passenger Service (15 Sep 25)
701022 - In Passenger Service (9 Feb 26)
701023 - In Passenger Service (7 Apr 26)
701024 - In Passenger Service (29 Jul 26)
701025 - In Passenger Service (24 Jun 25)
701026 - In Passenger Service (3 Nov 25)
701027 - In Passenger Service (29 Jun 26)
701028 - In Passenger Service (11 Sep 26)
701029 - SWR preparing for passenger service
701030 - In Passenger Service (9 Dec 25)
701031 - In Passenger Service (28 Oct 24)
701032 - In Passenger Service (15 May 26)
701033 - In Passenger Service (26 Nov 25)
701034 - In Passenger Service (18 Mar 25)
701035 - In Passenger Service (28 May 25)
701036 - In Passenger Service (7 Mar 24)
701037 - In Passenger Service (9 Jan 24)
701038 - In Passenger Service (5 Feb 26)
701039 - In Passenger Service (10 Jan 24)
701040 - In Passenger Service (15 Jun 26)
701041 - In Passenger Service (17 Jun 25)
701042 - In Passenger Service (21 May 25)
701043 - In Passenger Service (16 Jan 24)
701044 - In Passenger Service (5 Feb 25)
701045 - In Passenger Service (10 Apr 26)
701046 - In Passenger Service (17 Mar 25)
701047 - In Passenger Service (31 Dec 25)
701048 - In Passenger Service (8 Nov 25)
701049 - In Passenger Service (20 Mar 26)
701050 - In Passenger Service (17 Nov 25)
701051 - In Passenger Service (14 Jul 25)
701052 - In Passenger Service (23 Dec 25)
701053 - In Passenger Service (26 Aug 25)
701054 - In Passenger Service (3 Jan 26)
701055 - In Passenger Service (6 May 26)
701056 - In Passenger Service (8 Sep 25)
701057 - In Passenger Service (13 Aug 25)
701058 - In Passenger Service (11 Aug 25)
701059 - In Passenger Service (5 Dec 25)
701060 - In Passenger Service (1 Nov 25)

In Passenger Service: 59/60
Training duties: 1/60 (028 briefly served passengers before training duties)
SWR preparing for passenger service: 1/60


701501 - Stored at Derby Litchurch Lane
701502 - Stored at Derby Litchurch Lane
701503 - SWR preparing for passenger service
701504 - SWR preparing for passenger service
701505 - SWR preparing for passenger service
701506 - SWR preparing for passenger service
701507 - SWR preparing for passenger service
701508 - Stored at Derby Litchurch Lane
701509 - SWR preparing for passenger service
701510 - Stored at Derby Litchurch Lane
701511 - SWR preparing for passenger service
701512 - SWR preparing for passenger service
701513 - SWR preparing for passenger service
701514 - SWR preparing for passenger service
701515 - SWR preparing for passenger service
701516 - SWR preparing for passenger service
701517 - SWR preparing for passenger service
701518 - SWR preparing for passenger service
701519 - SWR preparing for passenger service
701520 - SWR preparing for passenger service
701521 - SWR preparing for passenger service
701522 - SWR preparing for passenger service
701523 - SWR preparing for passenger service
701524 - Stored at Derby Litchurch Lane
701525 - SWR preparing for passenger service
701526 - SWR preparing for passenger service
701527 - SWR preparing for passenger service
701528 - SWR preparing for passenger service
701529 - SWR preparing for passenger service
701530 - SWR preparing for passenger service

In Passenger Service: 0/30
SWR preparing for passenger service: 25/30
Stored at Derby Litchurch Lane: 5/30

Up to 59 ten cars now in passenger service.

 

[swr444]

028 already has a toilet out of use and the auto announcements aren’t working, shock

 

[traji00]

Why haven't the announcements still not been changed back to the old school ones that changed en route? Surely that must be easier in kit that's 100% digital from day one than on the old 455's. Even Thameslink manages a tidy changeover on the 700's around Sutton.

Only the 450’s changed en route , following recent updates. On the older units/707s, the guard had to re-enter the calling pattern code en route, else the service would be announced as terminating at Hounslow/Richmond/Wimbledon.

Annoyingly on the 701, the PIS software is based on the service ID/headcode — so it reads off the whole pattern regardless of where the service started from.
(So if anyone on a rounder service has heard the PA cut off after saying Hounslow/Kingston/Strawberry Hill /Richmond … that’s my attempt to mitigate confusion.)

An internal email a month or so ago suggested Alstom are working on an update. But no ETA thus far..

 

[NCT]

^^ Very interesting, thank you. When boarding at Wandsworth towards Richmond hearing ‘this service is for London Waterloo’ does make one jump a bit.

 

[NewStreetBlues]

What is happening with 029? I heard it was almost ready to enter traffic about three weeks ago

 

[norbitonflyer]

^^ Very interesting, thank you. When boarding at Wandsworth towards Richmond hearing ‘this service is for London Waterloo’ does make one jump a bit.

Conversely, some passengers get concerned when the ultimate desination changes en route - "I was on a Strawberry Hill train, but now it says it's going to Richmond - has it been diverted?"

== Doublepost prevention - post automatically merged: 13 Sep 2026 ==

010 is awaiting parts following the lineside strike on 10th August.

Shown on RTT as back in service today, Diagram starting 2c17 0809 Waterloo to Staines (Maintenance work has closed the line between Staines and Reading)

 

[nctd2306]

It was covered in another thread but fell into the auto merge void, but 701010 has returned to service today after a considerable amount of time out.

 

[NCT]

Conversely, some passengers get concerned when the ultimate desination changes en route - "I was on a Strawberry Hill train, but now it says it's going to Richmond - has it been diverted?"

Perhaps there can be three types of announcements for rounders

- 'This train is for Strawberry Hill' when leaving Waterloo
- 'This train is for Strawberry Hill and London Waterloo' once the service is sufficiently far into the 'country' and becomes useful for journeys beyond Strawberry Hill
- 'This train is for London Waterloo' after Strawberry Hill

 

[Ian Hardy]

Perhaps there can be three types of announcements for rounders

- 'This train is for Strawberry Hill' when leaving Waterloo
- 'This train is for Strawberry Hill and London Waterloo' once the service is sufficiently far into the 'country' and becomes useful for journeys beyond Strawberry Hill
- 'This train is for London Waterloo' after Strawberry Hill

On the Hounslow rounders on the 450s & 707s:
Leaving Waterloo it was a Hounslow via Brentford service
On departure from Barnes Bridge it became a Mortlake service
Between Isleworth and Hounslow it became a Waterloo via Richmond service

Going the other way around the loop
Leaving Waterloo it was a Hounslow via Richmond service
On departure from Mortlake it became a Chiswick service
Between Whitton and Hounslow it became a Waterloo via Brentford service

The CIS on the stations also showed the same information.

 

[Recessio]

I got on a Kingston bound 701 looper at Wimbledon yesterday. Another passenger was very worried when on boarding the recorded announcement said this was a service to London Waterloo. They clearly thought they were going the wrong way. Why haven't the announcements still not been changed back to the old school ones that changed en route? Surely that must be easier in kit that's 100% digital from day one than on the old 455's. Even Thameslink manages a tidy changeover on the 700's around Sutton.

This can cause odd situations on Platforms 7 and 8 at Vauxhall, where the platform displays will say Waterloo only and Strawberry Hill, but both trains say the destination is Waterloo. Definitely does confuse some customers.

I think this, along with some other oddities such as "London W'loo" being displayed - despite the displays both being large enough and having the ability to scroll text anyway - is because the data was copied verbatim from some of the older stock with ancient PIS. Hopefully will be fixed soon.

 

[bb21]

It was covered in another thread but fell into the auto merge void, but 701010 has returned to service today after a considerable amount of time out.

Yes, all required work was completed overnight on Saturday.