Interesting, thanks.
It's a 168/3 that does that, it goes to Stratford u a, goes to Leamington and back, then heads down to Marylebone, while a 165 comes up from Marylebone at the same time
The Cross-Country trains may have been diverted at short notice via Aston or Camp Hill before arriving in New Street
However from December timetable change the 0733 service will longer go to Marylebone it will terminate at Hatton and go ecs to Dorridge to then form a service to Birmingham Moor Street and will remain on Leamington Shuttles.
Be careful at New Street, they sometimes make their own additions to the screens, and this has on many occasions resulted in incorrect information being displayed. One example I experienced was an XC train that was Voyager vice HST and the screens at New Street said "formed of 8 coaches" (this bit is automatically added by XC), but then it also had a formation in coach letters for an HST (this is the bit New Street add themselves).
Probably best reporting it to RTT rather than posting on a random forum thread.
They probably ought to be more polite about it, too. Given all the work that goes into RTT, we could do without people having that attitude to the site's owner and developer. It is, after all, a free resource that is unmatched anywhere else.
And in this case I will reply and have put it in the work to-do list for the next site release (although I'm not sure where you'd see 1 coach on the network these days other than on the Stourbridge branch, maybe TfW? Will look.). But @cakefiend is correct: emailing for any problem will get eyes on it far quicker than posting on a random forum thread, whether or not it is to do with RTT, as I don't read this place that often.
I’m sure if you asked such requests in less of a demanding, arguably entitled manner, those able to do something would be more motivated to
To be fair, in software development, bug reports in the official channels are generally just phrased as a statement of erroneous behaviour and, if non-obvious, what the fix should look like. There's not much politeness involved because the role of the system is simply to produce a database of all the bugs, and then developers can choose which ones they want to fix. More like a shopping list than a wishlist!I’m sure if you asked such requests in less of a demanding, arguably entitled manner, those able to do something would be more motivated to
Same thing happened to me on a TFW service about a month ago, RTT was rather slow at picking up the fact the train was running, just starting up the track, (starting Chester vice Holyhead). Took about an hour for it to realise what was going on but it was rather off-putting. I had to check multiple systems as the majority said starting at Chester, RTT opted for cancelled throughout.
Isn't the root cause of these instances the usual one - RTT accurately reflecting the content of its feeds?
It showed as cancelled for the whole journey and while I was on the train, we got as far as Shrewsbury before it changed to show the train was running (with the on time, +/- thing) and that the train wasn't cancelled.
For things like this I'd use the official sources; the TfW website or Journeycheck which will be updated by a person in the Control office who can see what's happening first hand.
Chiltern units get turned everyday.
RTT does take a real-time feed of VSTP changes and on-the-day cancellations, same as Traksy and OTT. The main timetable information from Network Rail however comes in the form of a daily update. All of that used to be a viable plan in a world of operators who attempted to plan a timetable in advance and actually run, taking responsibility for cancelling trains on the day when they found they had to do it.
The bigger issue is the disconnect between NR and TOCs - VSTPs on the NR open feeds are done by NR. On the Darwin feeds, it is done by the TOCs. Trying to build a coherent picture between those two in itself is problematic as neither are truly representative of reality.
Alas, such a version of RTT actually exists and there is use of it inside the industry. I am not permitted to release it to the wider world (I only pick certain data bits out of Darwin - not advance platform numbers unless Darwin disagrees with RTTs logic for instance) for legal reasons.
I've been too busy working on a job that actually pays money to add new features to Traksy for a while, but when I do get time to spend on it it's difficult to escape the feeling that a separate industry-only site is the only way to get the schedules side of things working usefully. It's frustrating because until the Thameslink debacle, quickly followed by lockdown, things were generally working really well.
