Train delay codes?

[BingBong50]

Is there a place listing all train delay codes used for public viewing? Particularly interested in TD(SU) which has popped up on Realtime Trains.

Thank you.

 

[skyhigh]

Delay Attribution Guide - Open Rail Data Wiki

Too long to provide an entire quote but there isn't a TD or SU code.

 

[greatkingrat]

TD stands for Train Describer, nothing to do with delays. SU will be the code for the signalbox where the data has come from.

 

[MrJeeves]

TD stands for Train Describer, nothing to do with delays. SU will be the code for the signalbox where the data has come from.

Indeed. Delay attribution info will be at the top of a particular service's page in a red box.

What OP is talking about is the tooltip that appears when you hover over or tap a time at a specific timing point or station stop which tells you the source of the information (e.g., TD means RTT got the time from when the train entered the berth for that timing point).

You might also see TRUST or some other options (I think there's one like SMART which infers it from other places, but I don't really remember).

 

[BingBong50]

Thank you all for your helpful responses.

 

[CarrotPie]

Indeed. Delay attribution info will be at the top of a particular service's page in a red box.

But RTT only gives cancellation attribution. AIUI, if a train is delayed en-route, RTT doesn't tell you why: it leaves you guessing.

 

[Javelin_55]

But RTT only gives cancellation attribution. AIUI, if a train is delayed en-route, RTT doesn't tell you why: it leaves you guessing.

This is because trains are cancelled manually and must have a reason code entered into the system before it will cancel in TRUST - if you're cancelling it, you must know why.
Delays en route are recorded automatically but aren't explained until staff investigate them and assign them a reason code. In my area if it's a busy day, this could be several hours later or even the next day if there's lots of disruption (but I don't know if RTT would update to reflect the changes)

 

[MrJeeves]

If there is a reason code, it should be listed for the public and not to be the repeated reason.

It is, and will be done through the live passenger information system called Darwin which effectively every passenger-facing system uses.

 

[Bow Fell]

I don’t see anything wrong with transparency but the likes of RTT showing cancellation/attribution can cause confusion. You see the amount of comments and threads on here when they are used, that are unfortunately ill-informed through no fault of the poster of course.

Sometimes a delay code can change because it’s been disputed, gone to level 2 batted back, batted back again. So just going off what RTT and drawing conclusions isn’t the easiest picture.

 

[Horizon22]

It is, and will be done through the live passenger information system called Darwin which effectively every passenger-facing system uses.

Yes and this is separate to delay attribution. For example something on CIS might be cancelled due to “train crew being delayed by service disruption” whilst the fundamental attribution reason is say a points failure.

The former does not necessarily have any bearing on the latter.