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

❌1 error

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

Errors

timestamp is in the future E050 1 error

All timestamps must be less than the current time

Sample errors

header.timestamp 08:11:24 (1769929884) is 1 min 19 sec greater than 08:10:04 (1769929804743) - the current time in milliseconds

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
E050	All timestamps must be less than the current time	28	28 times (93 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	516	22 times (73 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	9,788	22 times (73 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	780	22 times (73 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	1,560	22 times (73 % of validations)
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	462	21 times (70 % 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	195	21 times (70 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	286	21 times (70 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	318	17 times (57 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	318	17 times (57 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	1,239	17 times (57 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	8	8 times (27 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-01 at 21:48 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-02-01 at 21:48 Europe/Paris. You can look at the GTFS-RT documentation.


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