You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 11, 2022. It is now read-only.
At 12:54 pm I used: !ov hilversum to find alternatives for the delayed train I was waiting for, which had been delayed 5 minutes after its scheduled departure time at 12:57.
This train showed up second in the list, before it was a train which had already departed at 12:34.
This might be a clock issue, an issue with the NS API, or I might need to tell the API not to show journeys that have already passed. The NS Reisplanner app, which uses the same API, also shows one journey which has already passed, but I have not noticed this issue before, so I assumed it was a parameter that I did not set.