GTFS realtime comparison
SNCB and Belgian Mobility trip updates.
Loading report…
Download snapshot JSONWhat’s announced
SNCB is the reference · red indicates BMC differencesSNCB
LoadingBMC
LoadingLoading feed statistics…
How closely do they match?
Loading comparison…
Trip IDs in the static GTFS feeds
Checking static trip identifiers…
Both lookups use exact trip IDs after removing BMC’s namespace. An ID match does not establish that an update can be applied: service dates, start times and stops also matter. Service-date and start-time counts cover only trips with an ID match.
Trips with an announced delay
Largest delay firstMaximum explicit delay per trip. Expand a trip for arrival and departure delays at each reported stop. Δ = BMC − SNCB.
iRail and Belgian Train links use the train number from a static GTFS match and the realtime service date. They open the website’s latest information, which may differ from this snapshot. Links are unavailable when the train number or service date is unknown.
| Trip / service instance | SNCB | BMC | Δ | In SNCB static GTFS? | In BMC static GTFS? | Stop details |
|---|---|---|---|---|---|---|
| Loading trip details… | ||||||
Reading this comparison
Trip matching
Exact trip ID, service date and start time, after removing BMC’s gt:nmbssncb: namespace. Missing dates or times stay empty. Different identifiers are not guessed to be the same train.
What counts as a delay
A positive, explicit arrival, departure or trip-level delay, in seconds. A trip’s headline value is its largest reported delay, including past stops. Cancelled trips and skipped or NO_DATA stops are excluded from delay counts. Missing delay fields stay unknown; no delays are derived from timestamps.
Snapshot timing
Both feeds are fetched concurrently for each report. Different publication times can explain discrepancies. Feed timestamps older than five minutes are flagged. The report refreshes daily at 07:00, 08:00, 09:00, 17:00, 18:00, 19:00 and 20:00 Europe/Brussels; GitHub may delay scheduled runs.