Class15
Established Member
There should definitely be a way to put multiple places into the search feature. Would save people a great deal of time.
There’s a thing for all non passenger services isn’t there?The other benefit of this would be for us spotter types to check for railtour operator workings etc. I will usually check RTT on a daily basis for freight workings (ZZ) in various locations in my area, to spot anything interesting running, but on occasions I’ve missed things like loco-hauled stock moves by Locomotive Services (LS), because it would be a drag checking each individual tour operator on RTT - if you could select all alongside freight then that would make it easy to pick these up.
That also includes ECS journeys which in some places may pollute the list a bit but yes.There’s a thing for all non passenger services isn’t there?
But West coast railways and locomotive services are “passenger” operators in RTT.There’s a thing for all non passenger services isn’t there?
But West coast railways and locomotive services are “passenger” operators in RTT.
Some of the DBS charters are WTT?Then surely doing a line up for a location and just selecting STP would catch anything like charters, ECS moves and ad hoc freight flows etc.
As far as I can see, the only thing that counts as "passenger" is the Jacobite, everything else still comes up. For example, see below:But West coast railways and locomotive services are “passenger” operators in RTT.
Can you give any examples? I can't think of any regular charters that would be WTT other than the Jacobite (which, given the sparsity of services on the Mallaig line, you can just use RTT on "all services" for)Some of the DBS charters are WTT?
DB Cargo have WTT paths from London Victoria to places such as Bath and Chesterfield for regular VSOE programmes.Can you give any examples? I can't think of any regular charters that would be WTT other than the Jacobite (which, given the sparsity of services on the Mallaig line, you can just use RTT on "all services" for)
You can tell I'm not from London then!DB Cargo have WTT paths from London Victoria to places such as Bath and Chesterfield for regular VSOE programmes.
Check this: https://www.realtimetrains.co.uk/se...1/0000-2359?stp=WVS&show=all&order=wtt&toc=ZZAs far as I can see, the only thing that counts as "passenger" is the Jacobite, everything else still comes up. For example, see below:
View attachment 138951
There is no change to the list, whether it's on "all services" or "non-passenger".
Can you give any examples? I can't think of any regular charters that would be WTT other than the Jacobite (which, given the sparsity of services on the Mallaig line, you can just use RTT on "all services" for)
2100 would be the HST on Sundays in the normal timetable but may be different when there's diversions in place anywhere on the XC route, even in the South West. On weekdays it's usually about 1900 from Darlington.For example, Traksy shows the 1959 and the 2100 Dar to EDI today being HST - RTT shows one of these as Voyager and has no info for the other.
.... This is extremely helpful to me as a railway photographer. I often have problems searching on RTT even when I have the headcode but that's probably down to me I think.
RTT takes its data from the operational Network Rail feeds, where other systems such as NationalRail and operator sites take their feed from a system called Darwin which is focused on customer information. It's not uncommon for updates such as cancellations to be input into Darwin before they are put into the Network Rail feeds. It's a bit less common for it to happen the other way round, but it can happen because it's a lot easier to correct things with Network Rail later, whereas if you put a cancellation into Darwin then customers will not turn up for the train.There appears to be a strange quirk in RTT for some LNER trains tomorrow morning:
https://www.realtimetrains.co.uk/se.../0000-2359?stp=WVSC&show=all&order=wtt&toc=GR
A number of southbound trains are shown as "VCN" (VSTP Cancellation), but they are not shown cancelled elsewhere, as they are running.
Thank you for taking the time to write a comprehensive reply. However, in this specific case, I am in a position to believe something is amiss.RTT takes its data from the operational Network Rail feeds, where other systems such as NationalRail and operator sites take their feed from a system called Darwin which is focused on customer information. It's not uncommon for updates such as cancellations to be input into Darwin before they are put into the Network Rail feeds. It's a bit less common for it to happen the other way round, but it can happen because it's a lot easier to correct things with Network Rail later, whereas if you put a cancellation into Darwin then customers will not turn up for the train.
This difference could easily mean that the trains are running and somebody has made a mistake, or that the train is likely to be cancelled but they aren't sure yet and don't want to put the passengers out if it's not going to be necessary, or that a cancellation will follow later and they want to input into Darwin when they have more information about replacement services and ticket acceptance etc. Basically, don't read too much into it
Thank you for taking the time to write a comprehensive reply. However, in this specific case, I am in a position to believe something is amiss.
It looks like there is an RTT quirk with a couple of those trains. The trains were indeed cancelled but the cancellation records were deleted but... not all of them got deleted properly. Looking into that now -- together with having a royal go at the advertising provider who appear to be unwilling to work with Google to solve the ad problem.
The ads aren't going away for reasons I've declared ad infinitum
Absolutely, it's a brilliant tool - which is why I felt it worth highlighting an issue I'd become aware of, as it helped @Tom and the team to get to the bottom of it.Someone says it every so often so I'll be that guy, this time -- yes there might be the occasional quirk that affects your site (see posts above), but it's still bloody brilliant and I for one (and I'm sure the vast majority of others on here) appreciate all the efforts you put in to making it successful. Thank you!
Does anyone know what happened to Realtime Trains yesterday morning? It seemed to have one of its meltdowns and wasn't tracking anything, and most services were coming up as No Record, it didn't seem to rectify itself until later in the afternoon from what I can gather.
.... Very frustrating when you have travelled just to photograph one train. But mustn't complain, RTT do an excellent job most of the time.Just a hiccup with the data feeds that happens from time to time. Affected all tracking sites not just RTT.
That's extremely unfair - as someone else has pointed out, it was the Network Rail data feedDoes anyone know what happened to Realtime Trains yesterday morning? It seemed to have one of its meltdowns and wasn't tracking anything, and most services were coming up as No Record,
WNXX Forum has a thread on Cross Country HSTs which shows the diagrams for the following day.I am trying to find out which XC services are operating as HST today/tomorrow.
Is RTT or Traksy more likely to be correct for this?
For example, Traksy shows the 1959 and the 2100 Dar to EDI today being HST - RTT shows one of these as Voyager and has no info for the other.
.... Very frustrating when you have travelled just to photograph one train. But mustn't complain, RTT do an excellent job most of the time.
I didn't get the shot of the Midland Pullman I was after due to the RTT hiccup but managed to grab just this one.
View attachment 139154