Resource details
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
❌70 errors, 10 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-14 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 70 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 37919{3_24}-SCOLAIRE NOVEMBRE 2024_1_LMWJVS stop_sequence 13 arrival_time 08:53:33 (1749884013) is equal to previous stop departure_time 08:53:33 (1749884013) - times must increase between two sequential stops
- trip_id 40676{5_24}-SCOLAIRE NOVEMBRE 2024_1_S stop_sequence 29 arrival_time 09:06:31 (1749884791) is less than previous stop departure_time 09:06:38 (1749884798) - times must increase between two sequential stops
- trip_id 40857{6_24}-SCOLAIRE NOVEMBRE 2024_1_S stop_sequence 20 arrival_time 09:11:16 (1749885076) is equal to previous stop arrival_time 09:11:16 (1749885076) - times must increase between two sequential stops
- trip_id 40857{6_24}-SCOLAIRE NOVEMBRE 2024_1_S stop_sequence 20 arrival_time 09:11:16 (1749885076) is equal to previous stop departure_time 09:11:16 (1749885076) - times must increase between two sequential stops
- trip_id 40857{6_24}-SCOLAIRE NOVEMBRE 2024_1_S stop_sequence 20 departure_time 09:11:16 (1749885076) is equal to previous stop departure_time 09:11:16 (1749885076) - times must increase between two sequential stops
Warnings
timestamp not populated W001 10 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 39933{24_3}-SCOLAIRE NOVEMBRE 2024_1_LMWJVS does not have a timestamp
- trip_id 37919{3_24}-SCOLAIRE NOVEMBRE 2024_1_LMWJVS does not have a timestamp
- trip_id 40676{5_24}-SCOLAIRE NOVEMBRE 2024_1_S does not have a timestamp
- trip_id 40857{6_24}-SCOLAIRE NOVEMBRE 2024_1_S does not have a timestamp
- trip_id 37860{1_24}-SCOLAIRE NOVEMBRE 2024_1_LMWJVS does not have a timestamp
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. | 2 490 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 331 | 24 times (80 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 20 | 14 times (47 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 20 | 14 times (47 % 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. | 16 | 11 times (37 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 84 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-16 at 00:59 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-16 at 00:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1750028399"
}
}