Resource details
This resource file is part of the dataset Réseau urbain Marinéo.
Download availability
Learn more
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
❌112 errors, 37 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-25 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 9 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 21327680 stop_id wimmair3 does not exist in GTFS data stops.txt
- trip_id 21327695 stop_id wimmair3 does not exist in GTFS data stops.txt
- trip_id 21327694 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21327696 stop_id wimmair3 does not exist in GTFS data stops.txt
- trip_id 21327511 stop_id outmds does not exist in GTFS data stops.txt
stop_times_updates not strictly sorted E002 5 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 21327372 stop_sequence [10, 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 21327371 stop_sequence [10, 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 21327370 stop_sequence [10, 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 21327337 stop_sequence [16, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21327338 stop_sequence [16, 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] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 84 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 21327372 stop_sequence 1 departure_time 09:15:00 (1777101300) is less than previous stop departure_time 09:35:45 (1777102545) - times must increase between two sequential stops
- trip_id 21327372 stop_sequence 1 departure_time 09:15:00 (1777101300) is less than previous stop arrival_time 09:35:45 (1777102545) - times must increase between two sequential stops
- trip_id 21327372 stop_sequence 2 arrival_time 09:16:23 (1777101383) is less than previous stop arrival_time 09:35:45 (1777102545) - times must increase between two sequential stops
- trip_id 21327372 stop_sequence 2 departure_time 09:16:23 (1777101383) is less than previous stop arrival_time 09:35:45 (1777102545) - times must increase between two sequential stops
- trip_id 21327371 stop_sequence 1 departure_time 08:46:01 (1777099561) is less than previous stop departure_time 09:07:37 (1777100857) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 14 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 21327680 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 21327695 stop_sequence 11 has stop_id wimmair3 but GTFS stop_sequence 11 has stop_id wimmair - stop_ids should be the same
- GTFS-rt trip_id 21327695 stop_sequence 16 has stop_id wimcrec but GTFS stop_sequence 16 has stop_id wimcrec2 - stop_ids should be the same
- GTFS-rt trip_id 21327694 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 21327696 stop_sequence 11 has stop_id wimmair3 but GTFS stop_sequence 11 has stop_id wimmair - stop_ids should be the same
Warnings
vehicle_id not populated W002 37 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 21327244 does not have a vehicle_id
- trip_id 21327243 does not have a vehicle_id
- trip_id 21327426 does not have a vehicle_id
- trip_id 21327261 does not have a vehicle_id
- trip_id 21327440 does not have a vehicle_id
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 | 235 | 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 | 384 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 925 | 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,315 | 26 times (87 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 70 | 19 times (63 % 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. | 4 | 4 times (13 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 14 | 3 times (10 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 | 1 times (3 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 | 1 times (3 % 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 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-26 at 03:21 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-04-26 at 03:21 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1777166480"
}
}