2 weeks ago, girlfriend and me took a #nighttrain from Berlin Südkreuz to Budapest (EN 40457). On paper a 12 hour ride (20:25 - 08:29), in reality we arrived after 10 in the morning, since the train just stood around in Bratislava for at least an hour ("something with the rails" according to the conductor) and we started out with a >30minutes delay from Berlin.

I requested compensation through the #ÖBB -bot (which worked very well actually) and got a reply later on: denied, system says no, you arrived with less than an hour of delay.

What I noticed during our ride, is that somewhere after Břeclav (Czechia), our train state in the DB app stopped updating and it didn't take our Bratislava-delay into account anymore.

#crossBorderRail

@quin_antarctic I also often notice the same thing where delays are not properly tracked across borders. Train operators generally only see delay within their "home" country but default to "on time" once abroad.

In my opinion, this is why the upcoming EU regulation on passenger rights should include mandatory tracking of delays across Europe in an open data manner. There cannot be effective compensation if operators pretend delays don't happen. cc @erpu @jon @stefanlindbohm @bovine3dom

@cycling_on_rails IIRC the new TSI regs do have some clauses trying to prevent such orphaned trains. so in theory it should get better within the next five years

(and delay data must be released with a real open licence as opposed to the highly commercially sensitive stuff like "where is the Speisewagen?")

@wnd might know more

@quin_antarctic @erpu @jon @stefanlindbohm

@Sobex @bovine3dom Restaurant car in German 🙃
@cycling_on_rails How is that commercially sensitive ?

@Sobex @cycling_on_rails that would be a question for the railway undertaking.

Noting that on the GB network, which has a relatively permissive open data culture, it was only agreed to publish train consist information last year.

@wnd @cycling_on_rails
Edit: This was not an objection in the UK.

Well, train consist info is the sort of thing that can change unexpectedly last minute. ( @hopla how often do you end up with a different rolling stock as planned on your trains).

I've had a few instances of rolling stock changes on mandatory reservation trains (which leads to massive mess for plenty of reasons).

@Sobex @cycling_on_rails @hopla fair but that was not the objection. It was based on a concern about commercial advantage to competitors.

The vast majority of the time the consist is as planned and, if changed, this data is known and shared.

For example, a driver has know how to safely operate a train, a signaller has to know whether an alternative path through interlocking during perturbation is safe.

It's up to you if don't want to know, but don't make up reasons for those that do.

@wnd @cycling_on_rails @hopla I’m editing my message to reflect that my hypothesis was wrong then.
@Sobex @cycling_on_rails @hopla it is a reasonable statement though. RUs and IMs are very bad at sharing this information with passengers

@wnd @cycling_on_rails @hopla I do see this can be an issue, as a wrong information can be worse than no information, and this is typically a case where stale data can more likely remain.

(Cache invalidation is one of the two great problem in CS)