Resource details
File name:
Données en temps réel au format GTFS-RT (TripUpdate)
Format: gtfs-rt
This resource file is part of the dataset Réseau urbain Kicéo.
Download availability
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
99.5%
2026-03-14
100%
2026-03-15
100%
2026-03-16
100%
2026-03-17
100%
2026-03-18
100%
2026-03-19
99.1%
2026-03-20
100%
2026-03-21
99.5%
2026-03-22
100%
2026-03-23
99.4%
2026-03-24
100%
2026-03-25
100%
2026-03-26
100%
2026-03-27
100%
2026-03-28
99.6%
2026-03-29
100%
2026-03-30
100%
2026-03-31
100%
2026-04-01
100%
2026-04-02
100%
2026-04-03
99.4%
2026-04-04
99.4%
2026-04-05
100%
2026-04-06
99.3%
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 2026-04-06 at 09:13 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 |
|---|---|---|---|
| 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 | 101 | 14 times (54 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 10 | 10 times (38 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 30 | 6 times (23 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 30 | 6 times (23 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 30 | 6 times (23 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 72 | 4 times (15 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-06 at 21:28 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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 2026-04-06 at 21:28 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "76",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1775503882"
},
"departure": {
"time": "1775503882"
},
"stopId": "548",
"stopSequence": 10
},
{
"arrival": {
"time": "1775504002"
},
"departure": {
"time": "1775504002"
},
"stopId": "533",
"stopSequence": 11
},
{
"arrival": {
"time": "1775504242"
},
"departure": {
"time": "1775504242"
},
"stopId": "27",
"stopSequence": 12
},
{
"arrival": {
"time": "1775504362"
},
"departure": {
"time": "1775504362"
},
"stopId": "21",
"stopSequence": 13
}
],
"timestamp": "1775503712",
"trip": {
"directionId": 0,
"routeId": "346",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260406",
"tripId": "2-5805113347"
},
"vehicle": {
"id": "76",
"label": "97220",
"licensePlate": "GD 936 JD"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775503712"
}
}