Because the operator did not publish a live prediction for that departure. Quavsit never fabricates real-time data. A timetable time is shown as a timetable time.
The four states
Every list of departures carries a meta.freshness:
Value | Meaning |
| At least one item comes from a live feed |
| Every item comes from the timetable |
| Served from an expired cache because the upstream failed or its daily budget ran out; at most 15 minutes old |
| The sources in one answer disagree about their own state |
Each source in meta.sources[] also reports unavailable when it was asked and could not answer at all — no data, rather than old data.
What a scheduled departure looks like
realtime: false, expected_at: null, delay_seconds: null, and status: "unknown" unless the operator explicitly marks it on time. There is nothing to display as a delay, so nothing is invented.
On a departure board or in a widget, the same rule shows as ink rather than the amber contact: a real-time time is marked, a timetable row is not.
Why it happens
The network has no real-time feed at all, or none for that mode. Several of the 147 networks publish a timetable and nothing else.
The trip is not in the live feed yet. Feeds usually cover a short horizon; a departure in two hours is a timetable departure.
The upstream is down, or its daily quota is exhausted. Then you see
stalefirst, with aWarningheader, andunavailableafter that. Île-de-France Mobilités and SNCF have daily call budgets shared by everyone, so they are the ones this reaches first.
About delays
delay_seconds is always Quavsit's own arithmetic, never a republished operator number: about a third of the real-time feeds publish no delay field at all, only an absolute expected time, and the delay is derived from that against the ingested schedule.
What this is not
Quavsit is not the official information service of any operator. Published data can be late, incomplete or wrong, and a service can change without the data saying so. Check with the operator before relying on it for a journey that matters.
If a stop is always scheduled and you think it should not be
meta.sources in your own answer names the feed and its state, and the network's page says what that network publishes at all. Between them they explain nearly every case.
Quavern help reference: quavsit-scheduled-or-real-time/en