810016.Unsure which unit it is, but one is currently outside Newton Aycliffe, the end coach appears to have the EMR lettering on the side too
(Apologies for the camera quality!)
To be fair, they are "muzzled" in a similar way on GWR. They used to absolutely fly from a standing start, however they have had their acceleration slowed down up to approximately 15mph, on both diesel and electric. It gives a smoother start and prevents throwing passengers to the floor who are still stowing luggage/locating their seat. Excellent initial acceleration may be useful on metro stock, but for Intercity stuff, a slower initial acceleration is no bad thing in my view.I'm hearing a possible explanation for Class 810 slow acceleration leaving stations in diesel mode is because the traction system has been programmed to deliver low power until the train has left the platform for 'noise reduction purposes.
So even if the driver whacks the controller to full power, the system only delivers a set amount of power until the train speed rises.
Considering that the same engines are used under Avanti Class 805 trains and are essentially just delivering slightly more power than other 80x engine types, one wonde@rs why these are deemed too noisy?
Is it me, or are they actually quieter than the 222 Cummins units?
In electric mode the 810's seem to develop around 16% more power at rail than a 'healthy' Class 222 in their current state of engine tuning - giving them up to 20 seconds advantage from station stops.
Shame that only applies south of Leicester.
810006 still seems to be running, RTT says it was cancelled between "Sheffield and Sheffield" which is wierd, maybe they fixed a problem? Approaching Loughborough as I typeFirst Sunday in a few weeks in which all 3 810s are out. We’ve got 006 on 1F01 (albeit running quite late and cancelled between Chesterfield and Sheffield), 010 on 1D03 after staying the night in Cricklewood and 012 on 2A56.
Edit: Nevermind 810006 stayed on all the way to Sheffield for a quick turnaround, RTT still says it was canned on the return but timing say it ran the full journey.
Another cause could be that EMR were going to try and claw back the lost time on the inbound service by turning it back at Chesterfield like has been done before, but they changed their mind.810006 still seems to be running, RTT says it was cancelled between "Sheffield and Sheffield" which is wierd, maybe they fixed a problem? Approaching Loughborough as I type
The May 2026 timetable is a mix, some schedules are timed for 810s and others for 222s in the base. There would still be variations on top, but won't be as easy as 'VAR' means timed for one or the other.Another question, at the moment all the 810 timetables are 'VAR' timetables, where they've edited the base 222 timetable to have the 810s timing codes, power changeover etc, but how many timetables will it take for the 810's timetable to be the base timetable (and in turn not be 'VAR') and for the 222's timetable to then be the 'VAR' timetable?
Ok thanks.The May 2026 timetable is a mix, some schedules are timed for 810s and others for 222s in the base. There would still be variations on top, but won't be as easy as 'VAR' means timed for one or the other.
How do the schedules differ between 222 and 810s operating the same calling pattern?The May 2026 timetable is a mix, some schedules are timed for 810s and others for 222s in the base. There would still be variations on top, but won't be as easy as 'VAR' means timed for one or the other.
• Timing codes, the 810s have a different timing code than the 222s.How do the schedules differ between 222 and 810s operating the same calling pattern?
OK. thanks. So no difference in sectional running times?• Timing codes, the 810s have a different timing code than the 222s.
• Power modes, the 810s start under electric at St Pancras, 222s on diesel.
• Power changeover, the power changeover at Kilby Bridge Jn needs to be documented on an 810 timetable, whereas it doesn’t on a 222 timetable as it doesn’t happen.
There may be a few other little bits, but those are the 3 main ones I notice.
No clue, possibly, but I don’t really know.OK. thanks. So no difference in sectional running times?
Realtime Trains | 6Q57 1538 Merchant Park Sidings to Etches Park Sdgs | 23/03/2026
Real-time train running information for 6Q57 1538 departure from Merchant Park Sidings to Etches Park Sdgs on 23/03/2026. From Realtime Trains, an independent source of train running info for Great Britain.www.realtimetrains.co.uk
I highly doubt the 6Q run will run, it’s up for all weekdays, but it’s ROG operated who have been trying for a very long time now to get an 810 move under their belt, but every time GBRf have done it.Just looking on RTT (realtime trains) at Merchant Park, and tomorrow there are two interesting moves one is a move to Doncaster IEP, which seems strange as there are only EMR 810s at the factory, but strangely there is also a 6Q57 to Etches Park. The 6Q path is also showing for Wednesday as well.
Anyone have any knowledge of what (if anything) a booked to move?
I've attached the 6Q path below.
Why do they ask for paths if they won't use them? Isn't there a cost for each path request to be actioned and processed?I highly doubt the 6Q run will run, it’s up for all weekdays, but it’s ROG operated who have been trying for a very long time now to get an 810 move under their belt, but every time GBRf have done it.
As for the move to Donny, no clue, but I am also sceptical about that.
Yeah I think there is a cost, but clearly they’re willing to pay it. As for why though, no idea. I believe they managed to get a test with either 810003/4 out of Dalby the other month, so I wonder if that makes them think that they should be running others too, but other than that, not a clue.Why do they ask for paths if they won't use them? Isn't there a cost for each path request to be actioned and processed?
Diagrams already discussed here:The fourth 810 flow has been started today, with 810012 operating it. Weekdays it goes 5F00, 1F00, 1C20, 1D26, 1B46, 1F50, 1C80, 1F70, 1C10, 5C95
Some might say that makes it ready for passenger service considering how many of these fail dailyLooks like 810015 isn’t quite ready for passenger service debut after failing on it’s first mml test on Friday.
Are these 810 'failures/faults' higher in number than the 800/801/802s etc when they started being introduced into service?Difference is the 180s seemed to have years of problems, even the recent days of them on the MML were beset with them so let's hope these problems can be ironed out with the 810s.
I doubt there is any record of percentages of total failures whilst on revenue earning duties but it would be interesting.
009 is not a passenger accepted unit, it is still a test/crew training unit.First day of 4 810s on passenger not gone too well today, with all units being pulled from service due to the incident at Bedford. Most of the units have clearly been put back to Etches by being pulled from service in Derby, but a few that I just want to confirm actually returned to Derby are 810009 (Which was pulled at Luton on 3A15) and 810012 (Which was also pulled at Luton on 1D26, but appeared to then run 1Z26 to Nottingham where it then vanishes from timetables). I'm presuming both these units returned to Etches at the moment, but am happy to be corrected.
Yes, it was running a driver training run to St Pancras.009 is not a passenger accepted unit, it is still a test/crew training unit.
there were 4 units on passenger (006, 010, 012, 014) then 3 on driver training (008, 009 and 011)There seems to have been 5 out today ? 810006,810009,810010,810012 & 810014, although as commented above they seem to have vanished from the RTT as far as it is concerned.
I did notice that one of them from London was pathed as a DMU, so guessing that the incident resulted in all power being switched off and probably why they gave up with the 810s.
012 got to Nottingham off 1D26 and ran as 5Z26 to Etches ParkFirst day of 4 810s on passenger not gone too well today, with all units being pulled from service due to the incident at Bedford. Most of the units have clearly been put back to Etches by being pulled from service in Derby, but a few that I just want to confirm actually returned to Derby are 810009 (Which was pulled at Luton on 3A15) and 810012 (Which was also pulled at Luton on 1D26, but appeared to then run 1Z26 to Nottingham where it then vanishes from timetables). I'm presuming both these units returned to Etches at the moment, but am happy to be corrected.
Ah ok, thanks. Guessing that move was off timetable?012 got to Nottingham off 1D26 and ran as 5Z26 to Etches Park