Resource details
This resource file is part of the dataset Réseau urbain Lignes d'Azur.
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
❌707 errors, 2,752 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-14 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 451 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 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 8 departure_time 08:33:00 (1773473580) is less than previous stop departure_time 08:38:49 (1773473929) - times must increase between two sequential stops
- trip_id 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 8 departure_time 08:33:00 (1773473580) is less than previous stop arrival_time 08:38:49 (1773473929) - times must increase between two sequential stops
- trip_id 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 9 arrival_time 08:34:24 (1773473664) is less than previous stop arrival_time 08:38:49 (1773473929) - times must increase between two sequential stops
- trip_id 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 9 departure_time 08:34:24 (1773473664) is less than previous stop arrival_time 08:38:49 (1773473929) - times must increase between two sequential stops
- trip_id 6699442-07_R_97_0705_07:54-JANV2026-07-Samedi-37 stop_sequence 21 arrival_time 08:13:01 (1773472381) is less than previous stop arrival_time 08:13:03 (1773472383) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 254 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 6613479-42_R_95_4201_10:00-PROJET2025-42-Samedi-09 stop_sequence 34 has stop_id 4147 but GTFS stop_sequence 34 has stop_id 4001 - stop_ids should be the same
- GTFS-rt trip_id 6613479-42_R_95_4201_10:00-PROJET2025-42-Samedi-09 stop_sequence 37 has stop_id 4304 but GTFS stop_sequence 37 has stop_id 4151 - stop_ids should be the same
- GTFS-rt trip_id 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 1 has stop_id 314 but GTFS stop_sequence 1 has stop_id 1152 - stop_ids should be the same
- GTFS-rt trip_id 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 2 has stop_id 87 but GTFS stop_sequence 2 has stop_id 1202 - stop_ids should be the same
- GTFS-rt trip_id 6832913-30_A_50_3001_08:30-JANV2026-30-Samedi-31 stop_sequence 3 has stop_id 1283 but GTFS stop_sequence 3 has stop_id 1005 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 2 errors
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Sample errors
- GTFS-rt trip_id 6682602-20_R_99_2003_07:49-JANV2026-20-Samedi-37 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 6613476-42_R_95_4202_07:30-PROJET2025-42-Samedi-09 contains stop_sequence 40 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 689 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 6860155-12_A_50_1209_10:02-JANV2026-12-Samedi-05 does not have a timestamp
- trip_id 6700687-16_R_97_1602_10:12-JANV2026-16-Samedi-33 does not have a timestamp
- trip_id 6804513-69_R_90_6901_12:08-PROJET2026-69-Samedi-12 does not have a timestamp
- trip_id 6613498-42_A_48_4202_11:45-PROJET2025-42-Samedi-09 does not have a timestamp
- trip_id 6599263-61_R_99_6102_07:55-PROJET2025-61-Samedi-28 does not have a timestamp
vehicle_id not populated W002 689 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 6860155-12_A_50_1209_10:02-JANV2026-12-Samedi-05 does not have a vehicle_id
- trip_id 6700687-16_R_97_1602_10:12-JANV2026-16-Samedi-33 does not have a vehicle_id
- trip_id 6804513-69_R_90_6901_12:08-PROJET2026-69-Samedi-12 does not have a vehicle_id
- trip_id 6613498-42_A_48_4202_11:45-PROJET2025-42-Samedi-09 does not have a vehicle_id
- trip_id 6599263-61_R_99_6102_07:55-PROJET2025-61-Samedi-28 does not have a vehicle_id
schedule_relationship not populated W009 1,374 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 6860155-12_A_50_1209_10:02-JANV2026-12-Samedi-05 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6860155-12_A_50_1209_10:02-JANV2026-12-Samedi-05 does not have a schedule_relationship
- trip_id 6700687-16_R_97_1602_10:12-JANV2026-16-Samedi-33 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6700687-16_R_97_1602_10:12-JANV2026-16-Samedi-33 does not have a schedule_relationship
- trip_id 6804513-69_R_90_6901_12:08-PROJET2026-69-Samedi-12 stop_sequence 9 (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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 26,050 | 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 | 9,623 | 30 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 23,022 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 23,022 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 45,896 | 30 times (100 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 71 | 25 times (83 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 62 | 10 times (33 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 2 | 1 times (3 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 2 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-15 at 02:38 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-03-15 at 02:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773538705"
}
}