Resource details
File name:
Offre TC temps réel Colibri
Format: gtfs-rt
This resource file is part of the dataset Réseau urbain Colibri.
Download availability
2025-08-15
100%
2025-08-16
100%
2025-08-17
100%
2025-08-18
100%
2025-08-19
100%
2025-08-20
100%
2025-08-21
100%
2025-08-22
100%
2025-08-23
100%
2025-08-24
100%
2025-08-25
100%
2025-08-26
100%
2025-08-27
100%
2025-08-28
100%
2025-08-29
100%
2025-08-30
100%
2025-08-31
100%
2025-09-01
100%
2025-09-02
100%
2025-09-03
100%
2025-09-04
100%
2025-09-05
100%
2025-09-06
100%
2025-09-07
100%
2025-09-08
100%
2025-09-09
100%
2025-09-10
53.3%
2025-09-11
74.2%
2025-09-12
100%
2025-09-13
100%
2025-09-14
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-14 at 09:10 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 |
---|---|---|---|
E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 50 | 8 times (36 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3 164 | 8 times (36 % of validations) |
E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 57 | 8 times (36 % of validations) |
E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 42 | 8 times (36 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 53 | 8 times (36 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 57 | 8 times (36 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 114 | 8 times (36 % 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. | 3 | 3 times (14 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-14 at 10:55 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-14 at 10:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1757840127"
}
}