Resource details

File name: Horaires temps réel des lignes du réseau COLIBRI
Format: gtfs-rt

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

Download availability

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

⚠️9 warnings

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

Warnings

vehicle_id not populated W002 3 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 20-003T2 does not have a vehicle_id
  • trip_id 10-003T7 does not have a vehicle_id
  • trip_id 10-104T7 does not have a vehicle_id

schedule_relationship not populated W009 6 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 20-003T2 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 20-003T2 does not have a schedule_relationship
  • trip_id 10-003T7 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 10-003T7 does not have a schedule_relationship
  • trip_id 10-104T7 stop_sequence 20 (and potentially more for this trip) does not have a schedule_relationship
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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 81 20 times (87 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 162 20 times (87 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 3 3 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-07 at 17:25 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-03-07 at 17:25 Europe/Paris. You can look at the GTFS-RT documentation.

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