Resource details
Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau Le Bus
This resource file is part of the dataset Réseau urbain Le Bus.
Related resources
Arrêts, horaires et parcours théoriques (GTFS) - réseau Le Bus
Download availability
Learn more
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
⚠️5 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-22 at 09:15 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
schedule_relationship not populated W009 5 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 3009 does not have a schedule_relationship
- trip_id 1039 does not have a schedule_relationship
- trip_id 1034 does not have a schedule_relationship
- trip_id 2015 does not have a schedule_relationship
- trip_id 2038 does not have a schedule_relationship
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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 117 | 25 times (89 % of validations) |
| 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. | 12 | 11 times (39 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-22 at 10:02 Europe/Paris.
vehicle_positions (6) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-09-22 at 10:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:4021",
"vehicle": {
"currentStopSequence": 5,
"position": {
"bearing": 102.0,
"latitude": 49.386775970458984,
"longitude": 2.383610963821411
},
"stopId": "AGZEC1",
"timestamp": "1790064153",
"trip": {
"routeId": "4",
"tripId": "4021"
},
"vehicle": {
"id": "TCA517"
}
}
},
{
"id": "VM:1034",
"vehicle": {
"currentStopSequence": 9,
"position": {
"bearing": 22.0,
"latitude": 49.384979248046875,
"longitude": 2.4177520275115967
},
"stopId": "CLMCO3",
"timestamp": "1790064153",
"trip": {
"directionId": 1,
"routeId": "1",
"tripId": "1034"
},
"vehicle": {
"id": "TCA514"
}
}
},
{
"id": "VM:1040",
"vehicle": {
"currentStopSequence": 1,
"position": {
"bearing": 325.0,
"latitude": 49.378868103027344,
"longitude": 2.451371669769287
},
"stopId": "BRSPV1",
"timestamp": "1790064153",
"trip": {
"directionId": 1,
"routeId": "1",
"tripId": "1040"
},
"vehicle": {
"id": "TCA516"
}
}
},
{
"id": "VM:2058",
"vehicle": {
"currentStopSequence": 1,
"position": {
"bearing": 208.0,
"latitude": 49.38492202758789,
"longitude": 2.4177937507629395
},
"stopId": "BLVGA1",
"timestamp": "1790064128",
"trip": {
"directionId": 1,
"routeId": "2",
"tripId": "2058"
},
"vehicle": {
"id": "TCA700"
}
}
},
{
"id": "VM:2022",
"vehicle": {
"currentStopSequence": 9,
"position": {
"bearing": 321.0,
"latitude": 49.3780517578125,
"longitude": 2.414691209793091
},
"stopId": "CLMMA3",
"timestamp": "1790064091",
"trip": {
"directionId": 1,
"routeId": "2",
"tripId": "2022"
},
"vehicle": {
"id": "TCA4974"
}
}
},
{
"id": "VM:2038",
"vehicle": {
"currentStopSequence": 1,
"position": {
"bearing": 160.0,
"latitude": 49.36244201660156,
"longitude": 2.4214882850646973
},
"stopId": "BLVGA1",
"timestamp": "1790059115",
"trip": {
"directionId": 1,
"routeId": "2",
"tripId": "2038"
},
"vehicle": {
"id": "TCA716"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1790064159"
}
}