Resource details

File name: Horaires temps-réel du réseau BUSS - Saintes (GTFS-RT)
Format: gtfs-rt

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

Download availability

2025-10-19
100%
2025-10-20
100%
2025-10-21
100%
2025-10-22
100%
2025-10-23
100%
2025-10-24
100%
2025-10-25
100%
2025-10-26
100%
2025-10-27
100%
2025-10-28
100%
2025-10-29
100%
2025-10-30
100%
2025-10-31
100%
2025-11-01
100%
2025-11-02
100%
2025-11-03
100%
2025-11-04
100%
2025-11-05
100%
2025-11-06
100%
2025-11-07
100%
2025-11-08
100%
2025-11-09
100%
2025-11-10
100%
2025-11-11
100%
2025-11-12
100%
2025-11-13
100%
2025-11-14
100%
2025-11-15
100%
2025-11-16
100%
2025-11-17
99.7%
2025-11-18
99.5%
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, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-18 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 1 error

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id 5358309600133120:1 stop_sequence 22 arrival_time 08:09:22 (1763449762) is less than previous stop departure_time 08:09:27 (1763449767) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 6537368015208448:2 does not have a vehicle_id

ID in one feed missing from the other W003 1 error

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

Sample errors
  • trip_id 6537368015208448:2 is in TripUpdates but not in VehiclePositions feed
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
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. 20 12 times (40 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 11 11 times (37 % of validations)
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 11 11 times (37 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 10 8 times (27 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-18 at 22:04 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-11-18 at 22:04 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1763499843" } }