Resource details
Horaires de prochains passages aux arrêts
This resource file is part of the dataset Réseau urbain Mistral.
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
❌253 errors, 77 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-18 at 08:10 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 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 9526 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 0095 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 1 error
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 9526 stop_id SEBRG2 does not exist in GTFS data stops.txt
Header timestamp should be greater than or equal to all other timestamps E012 65 errors
No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp
Sample errors
- trip_id 5456407 timestamp 1768720450 is greater than the header
- trip_id 5456399 timestamp 1768720410 is greater than the header
- trip_id 5456410 timestamp 1768720440 is greater than the header
- trip_id 5456393 timestamp 1768720230 is greater than the header
- trip_id 5456409 timestamp 1768720440 is greater than the header
Sequential stop_time_update times are not increasing E022 122 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 5456407 stop_id TOCAMO arrival_time 07:55:06 (1768719306) is equal to previous stop arrival_time 07:55:06 (1768719306) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOCAMO arrival_time 07:55:06 (1768719306) is equal to previous stop departure_time 07:55:06 (1768719306) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOPESS arrival_time 07:59:37 (1768719577) is equal to previous stop arrival_time 07:59:37 (1768719577) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOPESS arrival_time 07:59:37 (1768719577) is equal to previous stop departure_time 07:59:37 (1768719577) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOPESS departure_time 07:59:37 (1768719577) is equal to previous stop departure_time 07:59:37 (1768719577) - times must increase between two sequential stops
timestamp is in the future E050 63 errors
All timestamps must be less than the current time
Sample errors
- trip_id 5456407 timestamp 08:14:10 (1768720450) is 4 min 8 sec greater than 08:10:01 (1768720201709) - the current time in milliseconds
- trip_id 5456399 timestamp 08:13:30 (1768720410) is 3 min 28 sec greater than 08:10:01 (1768720201709) - the current time in milliseconds
- trip_id 5456410 timestamp 08:14:00 (1768720440) is 3 min 58 sec greater than 08:10:01 (1768720201709) - the current time in milliseconds
- trip_id 5456409 timestamp 08:14:00 (1768720440) is 3 min 58 sec greater than 08:10:01 (1768720201709) - the current time in milliseconds
- trip_id 5456404 timestamp 08:12:30 (1768720350) is 2 min 28 sec greater than 08:10:01 (1768720201709) - the current time in milliseconds
Warnings
vehicle_id not populated W002 77 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5456399 does not have a vehicle_id
- trip_id 5456393 does not have a vehicle_id
- trip_id 5456404 does not have a vehicle_id
- trip_id 5456396 does not have a vehicle_id
- trip_id 5456405 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 8,629 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6,480 | 30 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 112 | 28 times (93 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 85 | 28 times (93 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 136 | 28 times (93 % of validations) |
| E012 | No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp | 6,748 | 28 times (93 % of validations) |
| E050 | All timestamps must be less than the current time | 6,181 | 28 times (93 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 24 | 24 times (80 % 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. | 19 | 11 times (37 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 930 | 11 times (37 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 23 | 10 times (33 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-19 at 00:53 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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-01-19 at 00:53 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "5459857",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": -246,
"time": "1768779354"
},
"departure": {
"delay": 13,
"time": "1768779613"
},
"stopId": "SMPSMS"
},
{
"arrival": {
"delay": -9,
"time": "1768779711"
},
"departure": {
"delay": 13,
"time": "1768779733"
},
"stopId": "SMPPRO"
},
{
"arrival": {
"delay": -450,
"time": "1768780470"
},
"departure": {
"delay": -450,
"time": "1768780470"
},
"stopId": "TOPTOS"
}
],
"timestamp": "1768780690",
"trip": {
"directionId": 1,
"routeId": "28M",
"scheduleRelationship": "SCHEDULED",
"tripId": "5459857"
},
"vehicle": {
"id": "990",
"label": "990"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768780429"
}
}