Resource details
GTFS-RT (protobuff) des horaires aux arrêts.
This resource file is part of the dataset Réseau urbain Vikibus.
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
⚠️15 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-18 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 5 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id ATOUMOD012:ServiceJourney:300000387:LOC does not have a vehicle_id
- trip_id ATOUMOD012:ServiceJourney:300000349:LOC does not have a vehicle_id
- trip_id ATOUMOD012:ServiceJourney:300000350:LOC does not have a vehicle_id
- trip_id ATOUMOD012:ServiceJourney:300000239:LOC does not have a vehicle_id
- trip_id ATOUMOD012:ServiceJourney:300000346:LOC does not have a vehicle_id
schedule_relationship not populated W009 10 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD012:ServiceJourney:300000387:LOC does not have a schedule_relationship
- trip_id ATOUMOD012:ServiceJourney:300000349:LOC stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD012:ServiceJourney:300000349:LOC does not have a schedule_relationship
- trip_id ATOUMOD012:ServiceJourney:300000350:LOC stop_sequence 1 (and potentially more for this trip) 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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 35 | 11 times (37 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 70 | 11 times (37 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 10 | 10 times (33 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-18 at 19:38 Europe/Paris.
trip_updates (2) 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 2025-11-18 at 19:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:ATOUMOD012:ServiceJourney:300000401:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1763490300"
},
"stopId": "FR:76758:ZE:YVETOTxxxGarexS:ATOUMOD012",
"stopSequence": 16
}
],
"timestamp": "1763490485",
"trip": {
"routeId": "ATOUMOD012:Line:2:LOC",
"tripId": "ATOUMOD012:ServiceJourney:300000401:LOC"
}
}
},
{
"id": "SM:ATOUMOD012:ServiceJourney:300000365:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1763490300"
},
"stopId": "FR:76758:ZE:YVETOTxxxGarex1:ATOUMOD012",
"stopSequence": 10
}
],
"timestamp": "1763490485",
"trip": {
"directionId": 1,
"routeId": "ATOUMOD012:Line:2:LOC",
"tripId": "ATOUMOD012:ServiceJourney:300000365:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1763491095"
}
}