lrbvoyager
Member
- Joined
- 2 Jan 2025
- Messages
- 372
I’m guessing this is a fault as I can’t see how it’s possible but rtt is showing are 18:24 from oxenholme as 11 coaches?
It's because RTT have put the wrong information on display, again, as before etc etc
RTT are not putting wrong information on as such.It's because RTT have put the wrong information on display, again, as before etc etc
They have ran 18 coach pendolinos on test before, there’s a video on YTExcluding the obvious signalling / platform issues of a train that long, could it theoretically run as a 22 car?
Excluding the obvious signalling / platform issues of a train that long, could it theoretically run as a 22 car?
They have ran 18 coach pendolinos on test before, there’s a video on YT
Ahh, OK, thanks!IIRC they can couple mechanically for rescue purposes, but aren't capable of operating in pairs regardless of infrastructure
When there's a thread pinned at the top of this forum titled "IT'S AN RTT DATA FAULT, STOP BLOODY MAKING THREADS ABOUT 22-CAR PENDOS AND 15-CAR IETS!!!!!"God when will threads like this end? How many more times has the same questions got to be answered
But it's not an RTT data fault, it's just to do with how long the relevant data takes to filter through when an allocation change is made.When there's a thread pinned at the top of this forum titled "IT'S AN RTT DATA FAULT, STOP BLOODY MAKING THREADS ABOUT 22-CAR PENDOS AND 15-CAR IETS!!!!!"
But it's not an RTT data fault, it's just to do with how long the relevant data takes to filter through when an allocation change is made.
But that is what happens.It manages to get one half of the data change through quickly enough for something to surely be awry though?
If it was just a data update speed issue you wouldn’t get half the swap in a timely manner and half of it lingering on.
And how many people read the pinned threads anyway?When there's a thread pinned at the top of this forum titled "IT'S AN RTT DATA FAULT, STOP BLOODY MAKING THREADS ABOUT 22-CAR PENDOS AND 15-CAR IETS!!!!!"
In this case. 9S80 was allocated:It manages to get one half of the data change through quickly enough for something to surely be awry though?
If it was just a data update speed issue you wouldn’t get half the swap in a timely manner and half of it lingering on.

There are issues with the data processes and feeds upstream of RTT that relate to this that everyone will discover in far more detail when it becomes open data but in the mean time, don't worry, just blame us![]()
When common sense finally starts to kick in. Surely people should know Avanti wouldn't be running a Twenty-two carriage long train??God when will threads like this end? How many more times has the same questions got to be answered
That's not the point though. Whoever's error it is, the point is that it is an error and people really should be able to figure that out. It should be obvious to people on this site that a train upwards of five-hundred metres is not going to be running from London to Glasgow.But it's not an RTT data fault, it's just to do with how long the relevant data takes to filter through when an allocation change is made.
Trains of up to 775 metres run every night from London to Glasgow! Departing Camden Jn at 20:05 and getting to Coatbridge by 6am!That's not the point though. Whoever's error it is, the point is that it is an error and people really should be able to figure that out. It should be obvious to people on this site that a train upwards of five-hundred metres is not going to be running from London to Glasgow.
Oh for goodness sakeTrains of up to 775 metres run every night from London to Glasgow! Departing Camden Jn at 20:05 and getting to Coatbridge by 6am!
But it's not an error for the people who actually need to know what sets are running what service.When common sense finally starts to kick in. Surely people should know Avanti wouldn't be running a Twenty-two carriage long train??
These threads infuriate me
That's not the point though. Whoever's error it is, the point is that it is an error and people really should be able to figure that out. It should be obvious to people on this site that a train upwards of five-hundred metres is not going to be running from London to Glasgow.
Thats a lot of data updates, I thought RTT only updated every hour or soIn this case. 9S80 was allocated:
(all times are in UTC, so +1 hour for UK)
- 2025-08-14 01:41 - 390132 on VW940
- 2025-08-14 03:21 - deallocated
- 2025-08-14 04:22 - 390115 on VW940
- 2025-08-14 07:16 - 390125 and 390115 on VW940
- 2025-08-14 07:21 - another message with the same content
- 2025-08-14 16:21 - 390125 on VW940
As always, it shows the data when it receives it.
There are issues with the data processes and feeds upstream of RTT that relate to this that everyone will discover in far more detail when it becomes open data but in the mean time, don't worry, just blame us![]()
It updates whenever the upstream feed sends out data.Thats a lot of data updates, I thought RTT only updated every hour or so
It depends on the input. This one is every 5 minutes.Thats a lot of data updates, I thought RTT only updated every hour or so
Any plans to include unit nos in the api? There are some cool projects that could be made and automatedIt depends on the input. This one is every 5 minutes.
It'll be open data on the Rail Data Marketplace soon (tm).Any plans to include unit nos in the api? There are some cool projects that could be made and automated