Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
This resource file is part of the dataset Réseau urbain MAT.
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
❌122 errors, 125 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-17 at 09:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 47 errors
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 3690647 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3682135 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3682202 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3690801 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3690779 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt stop_id does not exist in GTFS data E011 75 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 3796519 stop_id 1288 does not exist in GTFS data stops.txt
- trip_id 3796519 stop_id 1324 does not exist in GTFS data stops.txt
- trip_id 3796519 stop_id 1046 does not exist in GTFS data stops.txt
- trip_id 3796519 stop_id 1320 does not exist in GTFS data stops.txt
- trip_id 3796519 stop_id 1280 does not exist in GTFS data stops.txt
Warnings
vehicle_id not populated W002 31 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 3682135 does not have a vehicle_id
- trip_id 3682202 does not have a vehicle_id
- trip_id 3690801 does not have a vehicle_id
- trip_id 3690779 does not have a vehicle_id
- trip_id 3788146 does not have a vehicle_id
schedule_relationship not populated W009 94 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 3690647 stop_id 1554 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 3690647 does not have a schedule_relationship
- trip_id 3682135 stop_id 1596 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 3682135 does not have a schedule_relationship
- trip_id 3682202 stop_id 1147 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 156 | 29 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 599 | 29 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 312 | 29 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 350 | 18 times (62 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-18 at 04:33 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 2025-06-18 at 04:33 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1750214020"
}
}