Resource details

File name: Données en temps réel de la position des véhicules du réseau Astrobus
Format: gtfs-rt

GTFS-RT (protobuff) de la position des véhicules

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

Download availability

2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
2026-01-15
100%
2026-01-16
100%
2026-01-17
100%
2026-01-18
100%
2026-01-19
100%
2026-01-20
100%
2026-01-21
100%
2026-01-22
100%
2026-01-23
100%
2026-01-24
100%
2026-01-25
100%
2026-01-26
100%
2026-01-27
100%
2026-01-28
100%
2026-01-29
100%
2026-01-30
100%
2026-01-31
100%
2026-02-01
100%
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:25 (1769929885) is 1 min 20 sec greater than 08:10:04 (1769929804890) - 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 27 27 times (90 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 715 22 times (73 % of validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 416 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 299 17 times (57 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 299 17 times (57 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 156 17 times (57 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 52 17 times (57 % of validations)
E052 Each vehicle should have a unique ID 27 15 times (50 % 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.

vehicle_positions

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" } }