gtfs-rt Transport open dataset - GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt for Réseau urbain Marinéo

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

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

❌206 errors, 42 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-09 at 08:13 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 9 errors

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

Sample errors

trip_id 21725823 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
trip_id 21323514 stop_sequence [22, 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, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
trip_id 21323512 stop_sequence [22, 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, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
trip_id 21323513 stop_sequence [22, 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, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
trip_id 21323616 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

trip_id 21323855 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 1 error

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id SC does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id 21323855 stop_id smbsand does not exist in GTFS data stops.txt
trip_id 21323514 stop_id bsmtran2 does not exist in GTFS data stops.txt
trip_id 21323512 stop_id bsmtran2 does not exist in GTFS data stops.txt
trip_id 21323513 stop_id bsmtran2 does not exist in GTFS data stops.txt
trip_id 21323496 stop_id bsmtran2 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 159 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 21725823 stop_id outlep2 arrival_time 08:08:11 (1770620891) is equal to previous stop arrival_time 08:08:11 (1770620891) - times must increase between two sequential stops
trip_id 21725823 stop_id outlep2 arrival_time 08:08:11 (1770620891) is less than previous stop departure_time 08:10:18 (1770621018) - times must increase between two sequential stops
trip_id 21725823 stop_id outlep2 departure_time 08:10:18 (1770621018) is equal to previous stop departure_time 08:10:18 (1770621018) - times must increase between two sequential stops
trip_id 21725823 stop_sequence 1 departure_time 07:58:31 (1770620311) is less than previous stop departure_time 08:10:59 (1770621059) - times must increase between two sequential stops
trip_id 21725823 stop_sequence 1 departure_time 07:58:31 (1770620311) is less than previous stop arrival_time 08:10:59 (1770621059) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 9 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 21725990 stop_sequence 25 has stop_id wimmair4 but GTFS stop_sequence 25 has stop_id wimmair2 - stop_ids should be the same
GTFS-rt trip_id 21725979 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 21725957 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 21725967 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 21323583 stop_sequence 11 has stop_id smbheli but GTFS stop_sequence 11 has stop_id smbheli2 - stop_ids should be the same

Warnings

vehicle_id not populated W002 42 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 21323842 does not have a vehicle_id
trip_id 21323418 does not have a vehicle_id
trip_id 21323514 does not have a vehicle_id
trip_id 21323513 does not have a vehicle_id
trip_id 21725788 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	289	24 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.	2,414	24 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	843	24 times (100 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	122	20 times (83 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	35	15 times (63 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	13	13 times (54 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	13	13 times (54 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	18	11 times (46 % 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	73	9 times (38 % of validations)
E009	If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence	2	2 times (8 % of validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	2	2 times (8 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-10 at 01:58 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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-02-10 at 01:58 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1770685097"
  }
}