gtfs-rt Transport open dataset - Données en temps réel des horaires aux arrêts du réseau Astrobus for Réseau urbain Astrobus

Resource details

File name: Données en temps réel des horaires aux arrêts du réseau Astrobus

Format: gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts

This resource file is part of the dataset Réseau urbain Astrobus.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌301 errors, 27 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-10-30 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 7 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id ATOUMOD036:ServiceJourney:5610400279166976x0:LOC stop_sequence [12, 10] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:4594099884654592x1:LOC stop_sequence [18, 7] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:5935771096711168x1:LOC stop_sequence [20, 18] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:5754491142930432x2:LOC stop_sequence [17, 11] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:5712075241291776x1:LOC stop_sequence [13, 9] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 270 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:4875342597586944x1:LOC stop_sequence 11 arrival_time 08:05:00 (1793343900) is less than previous stop arrival_time 08:36:34 (1793345794) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC stop_sequence 11 arrival_time 08:05:00 (1793343900) is less than previous stop departure_time 08:15:14 (1793344514) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC stop_sequence 11 departure_time 08:05:25 (1793343925) is less than previous stop departure_time 08:15:14 (1793344514) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC stop_sequence 11 departure_time 08:05:25 (1793343925) is less than previous stop arrival_time 08:36:34 (1793345794) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC stop_sequence 20 arrival_time 08:17:27 (1793344647) is less than previous stop arrival_time 08:18:13 (1793344693) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 9 errors

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Sample errors

GTFS-rt trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5610400279166976x0:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4594099884654592x1:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:6005261666877440x2:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5935771096711168x1:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 7 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:4875342597586944x1:LOC stop_sequence 12 has stop_id FR:14366:ZE:35180002:ATOUMOD036 but GTFS stop_sequence 12 has stop_id FR:14366:ZE:33090002:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC stop_sequence 18 has stop_id FR:14366:ZE:652240007:ATOUMOD036 but GTFS stop_sequence 18 has stop_id FR:14366:ZE:35150004:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4594099884654592x1:LOC stop_sequence 18 has stop_id FR:14582:ZE:5162389924216832:ATOUMOD036 but GTFS stop_sequence 18 has stop_id FR:14625:ZE:6221161186721792:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5754491142930432x2:LOC stop_sequence 17 has stop_id FR:14366:ZE:33070004:ATOUMOD036 but GTFS stop_sequence 17 has stop_id FR:14366:ZE:5180281390628864:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5156513839579136x0:LOC stop_sequence 11 has stop_id FR:14625:ZE:5109580566626304:ATOUMOD036 but GTFS stop_sequence 11 has stop_id FR:14582:ZE:6195023425044480:ATOUMOD036 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 8 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:4875342597586944x1:LOC contains stop_sequence 26 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5610400279166976x0:LOC contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4594099884654592x1:LOC contains stop_sequence 7 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:6005261666877440x2:LOC contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5935771096711168x1:LOC contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 9 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:5610400279166976x0:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:4594099884654592x1:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:6005261666877440x2:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:5935771096711168x1:LOC does not have a vehicle_id

schedule_relationship not populated W009 18 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:4875342597586944x1:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:5610400279166976x0:LOC stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:5610400279166976x0:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:4594099884654592x1:LOC stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship

Validate this GTFS-RT now

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.	4,175	29 times (97 % of validations)
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	203	29 times (97 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	179	29 times (97 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	203	29 times (97 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	406	29 times (97 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	99	26 times (87 % 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	87	25 times (83 % of validations)
E050	All timestamps must be less than the current time	25	25 times (83 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-10-30 at 21:43 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-10-30 at 21:43 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1793392992"
  }
}