Resource details

File name: GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Marinéo.

Download availability

2026-02-13
100%
2026-02-14
100%
2026-02-15
100%
2026-02-16
100%
2026-02-17
100%
2026-02-18
100%
2026-02-19
100%
2026-02-20
100%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
Learn more
We test this resource download availability every hour by making an HTTP HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.

For SIRI and SIRI Lite feeds, we perform a GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

49 errors, 39 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-14 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt stop_id does not exist in GTFS data E011 8 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • trip_id 21327672 stop_id wimmair3 does not exist in GTFS data stops.txt
  • trip_id 21327656 stop_id wimmair4 does not exist in GTFS data stops.txt
  • trip_id 21327695 stop_id wimmair3 does not exist in GTFS data stops.txt
  • trip_id 21327692 stop_id wimmair4 does not exist in GTFS data stops.txt
  • trip_id 21327693 stop_id wimmair3 does not exist in GTFS data stops.txt

stop_times_updates not strictly sorted E002 1 error

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors
  • trip_id 21327510 stop_sequence [7, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 28 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id 21327510 stop_id outlep2 arrival_time 08:43:33 (1773474213) is equal to previous stop arrival_time 08:43:33 (1773474213) - times must increase between two sequential stops
  • trip_id 21327510 stop_id outlep2 arrival_time 08:43:33 (1773474213) is equal to previous stop departure_time 08:43:33 (1773474213) - times must increase between two sequential stops
  • trip_id 21327510 stop_id outlep2 departure_time 08:43:33 (1773474213) is equal to previous stop departure_time 08:43:33 (1773474213) - times must increase between two sequential stops
  • trip_id 21327510 stop_id outlep2 departure_time 08:43:33 (1773474213) is equal to previous stop arrival_time 08:43:33 (1773474213) - times must increase between two sequential stops
  • trip_id 21327510 stop_sequence 1 departure_time 08:35:00 (1773473700) is less than previous stop departure_time 08:44:04 (1773474244) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 12 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors
  • GTFS-rt trip_id 21327225 stop_sequence 33 has stop_id semcord but GTFS stop_sequence 33 has stop_id semcord2 - stop_ids should be the same
  • GTFS-rt trip_id 21327672 stop_sequence 1 has stop_id wimmair3 but GTFS stop_sequence 1 has stop_id wimmair - stop_ids should be the same
  • GTFS-rt trip_id 21327656 stop_sequence 43 has stop_id wimmair4 but GTFS stop_sequence 43 has stop_id wimmair2 - stop_ids should be the same
  • GTFS-rt trip_id 21327739 stop_sequence 4 has stop_id smbecol but GTFS stop_sequence 4 has stop_id smbecol3 - stop_ids should be the same
  • GTFS-rt trip_id 21327736 stop_sequence 13 has stop_id smbecol but GTFS stop_sequence 13 has stop_id smbecol3 - stop_ids should be the same

Warnings

vehicle_id not populated W002 39 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 21327387 does not have a vehicle_id
  • trip_id 21327390 does not have a vehicle_id
  • trip_id 21327391 does not have a vehicle_id
  • trip_id 21327370 does not have a vehicle_id
  • trip_id 21327371 does not have a vehicle_id
Validate this GTFS-RT now

Previous validations

Here is a recap of all the error types encountered over the last 30 days.

Error ID Description Errors count Number of occurences
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 355 30 times (100 % of validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 375 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1,063 30 times (100 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1,747 27 times (90 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 95 26 times (87 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 7 7 times (23 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 7 7 times (23 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-15 at 07:59 Europe/Paris.

trip_updates (5) vehicle_positions (0) service_alerts (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-15 at 07:59 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "21328424", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1773559511", "uncertainty": 120 }, "stopId": "wimmair3", "stopSequence": 1 } ], "timestamp": "1773557954", "trip": { "directionId": 1, "routeId": "A", "scheduleRelationship": "SCHEDULED", "tripId": "21328424" } } }, { "id": "21328407", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1773561540", "uncertainty": 120 }, "stopId": "wimbast5", "stopSequence": 1 } ], "timestamp": "1773557954", "trip": { "directionId": 1, "routeId": "F", "scheduleRelationship": "SCHEDULED", "tripId": "21328407" } } }, { "id": "21328319", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1773559800", "uncertainty": 120 }, "stopId": "bsmcca9", "stopSequence": 1 } ], "timestamp": "1773557954", "trip": { "directionId": 0, "routeId": "D", "scheduleRelationship": "SCHEDULED", "tripId": "21328319" } } }, { "id": "21328369", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1773561000", "uncertainty": 120 }, "stopId": "smbwica", "stopSequence": 1 } ], "timestamp": "1773557954", "trip": { "directionId": 0, "routeId": "E", "scheduleRelationship": "SCHEDULED", "tripId": "21328369" } } }, { "id": "21328363", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1773560400", "uncertainty": 120 }, "stopId": "equmin", "stopSequence": 1 } ], "timestamp": "1773557954", "trip": { "directionId": 0, "routeId": "C", "scheduleRelationship": "SCHEDULED", "tripId": "21328363" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1773557954" } }