Resource details
GTFS-RT (protobuff) des horaires aux arrêts
This resource file is part of the dataset Réseau urbain Astrobus.
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
❌111 errors, 18 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-26 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 4 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence [19, 24, 23, 16, 17, 22, 20, 21, 18, 26, 25] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:5248567309500416x0:LOC stop_sequence [17, 9] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC stop_sequence [7, 4] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:5365269825323008x2:LOC stop_sequence [10, 3, 13, 2, 1, 11, 4, 9, 12, 14] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 94 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 ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 23 arrival_time 09:09:40 (1753513780) is less than previous stop arrival_time 09:12:37 (1753513957) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 23 arrival_time 09:09:40 (1753513780) is less than previous stop departure_time 09:12:47 (1753513967) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 23 departure_time 09:09:50 (1753513790) is less than previous stop departure_time 09:12:47 (1753513967) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 23 departure_time 09:09:50 (1753513790) is less than previous stop arrival_time 09:12:37 (1753513957) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 16 arrival_time 08:58:59 (1753513139) is less than previous stop arrival_time 09:09:40 (1753513780) - times must increase between two sequential stops
trip direction_id does not match GTFS data E024 6 errors
GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt
Sample errors
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:5248567309500416x0:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:4789093536890880x3:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:5365269825323008x2:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 4 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 ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 19 has stop_id FR:14366:ZE:36970002:ATOUMOD036 but GTFS stop_sequence 19 has stop_id FR:14366:ZE:7150003:ATOUMOD036 - stop_ids should be the same
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 24 has stop_id FR:14366:ZE:17240004:ATOUMOD036 but GTFS stop_sequence 24 has stop_id FR:14303:ZE:19280004:ATOUMOD036 - stop_ids should be the same
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:4789093536890880x3:LOC stop_sequence 22 has stop_id FR:14366:ZE:764280004:ATOUMOD036 but GTFS stop_sequence 22 has stop_id FR:14366:ZE:1210003:ATOUMOD036 - stop_ids should be the same
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:5365269825323008x2:LOC stop_sequence 10 has stop_id FR:14366:ZE:5170005:ATOUMOD036 but GTFS stop_sequence 10 has stop_id FR:14366:ZE:605820044:ATOUMOD036 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 3 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 ATOUMOD036:ServiceJourney:5248567309500416x0:LOC contains stop_sequence 9 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC contains stop_sequence 4 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id ATOUMOD036:ServiceJourney:4789093536890880x3:LOC contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip
Warnings
vehicle_id not populated W002 6 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:5248567309500416x0:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:4789093536890880x3:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:5365269825323008x2:LOC does not have a vehicle_id
schedule_relationship not populated W009 12 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC stop_sequence 19 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:6018088009990144x2:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5248567309500416x0:LOC stop_sequence 17 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5248567309500416x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC stop_sequence 7 (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 |
|---|---|---|---|
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 102 | 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. | 3 940 | 30 times (100 % of validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 215 | 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 | 111 | 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 | 166 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 215 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 430 | 30 times (100 % of validations) |
| E050 | All timestamps must be less than the current time | 7 | 7 times (23 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-27 at 01:47 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-07-27 at 01:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1753573663"
}
}