Our new ticketing site is now live! Using either this or the original site (both 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!
Looks like the trains have been cancelled in the system, suspect XC have concerns over train crew availability on that day. I would plan for there not being any direct trains from Oxford to Derby on that day.
Again? I have read the thread, but it is not relevant when referring to the base timetable.
I imagine we'll see the same amendments released week by week as the STP amendments are published.
I'm referring to the base timetable (as I stated) not any variations which can vary week by week.
As for Weekends that isn't relevant as it isn't what 800001 was referring to.
These trains, along with others, are showing as unadvertised for the entire base timetable. This is why they have a blue background in the train list in detailed mode and don't appear in simple mode.
I suspect it does somewhat, as I've seen it on occasion where a GPS report has made it to RTT but not onto Darwin, causing the "delayed" message. Sounds like at least some of the GPS reports didn't make it to Darwin, along with a delayed manual report at Llandudno Junction.
There is actually an...
The presence of a panel does not mean there is a train describer. Llandudno Junction doesn't have one. Frodsham Junction only got one because of the closure of Norton box and new fringe to Warrington PSB.
In the OPs case this is of TfWs own doing, they have recently set all locations to expect...
The Train Describer data shows it ran back to Cricklewood, before then returning to St Pancras. All under the same headcode, 5F37.
RTT is showing the timings for its second journey from Cricklewood to St Pancras.
Most are booked platform 2, which RTT will show until it knows otherwise. Have you got any examples of RTT showing platform 2 post arriving platform 1? We can certainly look into why that happened, so it doesn't happen again.
That is because Realtime Trains has merged the Crossrail Core trains in with the trains at the main CRS code. Behind the scenes they are still timed at the secondary location.
RTT will only show the booked platform until it knows otherwise, so it won't identify the current pattern that they seem to be using platform 1 instead of their booked platform a significant proportion of the time currently.
There is no signalled route from signal 9821 to 9753.
Also one of your examples is incorrect, there isn't any signalled routes between the signals not in the normal direction of traffic between Lincoln and Peterborough. The routes from those signals are to cross to the other line or another...
I would treat berths like that as blank. Whilst the presence of **** can mean a train is present, it does not mean there definitely is. It would be unlikely that you would find a train in the platform with **** outside of severe service disruption anyway.
The data source for the platform...
An additional stop on the XC is fairly common when the TPE is late. It is to provide a connection to Edinburgh as the TPE misses the 0747 Scotrail departure.
The information on RTT for the Inverness area is currently all coming from the NR SMART system, whilst the codes mean something, I would not read into them as they don't always make sense. At some stage in the future RTT will update the area to give better information.
1T90 did the move you are...
I did think about that train just after posting, its the train I often travel home from Birmingham on.
I have seen it once since the timetable change where it has attached the other way around, the attaching set was a 5 car. Not sure on the specific reason. This is an edge case anyway, so is...
If the coach letters have been setup the correct way around, there should not be reservations in that coach. It would be either coach G or L, both don't take reservations.
You could have some unique scenarios where the coach letters are the other way around, however it won't be a regular thing.
We are aware of an issue with emails from the Forum to Microsoft-based email accounts (hotmail/outlook/live.com email addresses). This is being looked into currently, thanks for your patience meanwhile.