Resource details
File name:
Données en temps réel au format GTFS-RT
Format: gtfs-rt
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
TripUpdate
VehiclePosition
Alert
This resource file is part of the dataset Réseau urbain PondiBUS.
Download availability
2025-08-22
99.4%
2025-08-23
100%
2025-08-24
99.4%
2025-08-25
99.3%
2025-08-26
99.3%
2025-08-27
99.3%
2025-08-28
99.3%
2025-08-29
99.3%
2025-08-30
99.3%
2025-08-31
99.3%
2025-09-01
99.3%
2025-09-02
99.2%
2025-09-03
99.2%
2025-09-04
99.3%
2025-09-05
99.3%
2025-09-06
99.3%
2025-09-07
98.6%
2025-09-08
99.3%
2025-09-09
99.3%
2025-09-10
99.3%
2025-09-11
99.3%
2025-09-12
99.3%
2025-09-13
99.3%
2025-09-14
98.6%
2025-09-15
99.3%
2025-09-16
98.6%
2025-09-17
99.3%
2025-09-18
99.3%
2025-09-19
99.3%
2025-09-20
100%
2025-09-21
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-21 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 64 | 16 times (50 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 116 | 10 times (31 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 15 | 4 times (13 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 45 | 3 times (9 % 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. | 1 | 1 times (3 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-21 at 18:49 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-21 at 18:49 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758473365"
}
}