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 Brévibus.

Download availability

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

10 errors, 2 warnings

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

Errors

Sequential stop_time_update times are not increasing E022 8 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 9-1616775121 stop_sequence 17 arrival_time 08:15:32 (1777702532) is less than previous stop arrival_time 08:38:15 (1777703895) - times must increase between two sequential stops
  • trip_id 9-1616775121 stop_sequence 17 arrival_time 08:15:32 (1777702532) is less than previous stop departure_time 08:38:51 (1777703931) - times must increase between two sequential stops
  • trip_id 9-1616775120 stop_sequence 17 arrival_time 08:08:30 (1777702110) is less than previous stop arrival_time 08:08:35 (1777702115) - times must increase between two sequential stops
  • trip_id 9-1616775120 stop_sequence 17 arrival_time 08:08:30 (1777702110) is less than previous stop departure_time 08:09:15 (1777702155) - times must increase between two sequential stops
  • trip_id 9-1616775120 stop_sequence 17 departure_time 08:08:30 (1777702110) is less than previous stop departure_time 08:09:15 (1777702155) - times must increase between two sequential stops

stop_time_update doesn't have arrival or departure E043 2 errors

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id 9-1616775121 stop_sequence 14 doesn't have arrival or departure
  • trip_id 9-1616775120 stop_sequence 14 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 2 errors

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 9-1616775121 is in TripUpdates but not in VehiclePositions feed
  • trip_id 9-1616775120 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
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 85 24 times (80 % 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 72 23 times (77 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 20 4 times (13 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 3 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-05-03 at 03:20 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-05-03 at 03:20 Europe/Paris. You can look at the GTFS-RT documentation.

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