Resource details
Ressources en temps réél GTFS-RT : Mise à jour des trajets en temps réel.
This resource file is part of the dataset Réseau urbain Jybus.
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
❌2 errors, 5 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-29 at 09:15 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id H1LMJV_Rumilly_Sept 2026C566428 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 1 error
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id ASJ5 does not exist in the GTFS data routes.txt
Warnings
vehicle_id not populated W002 5 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id H1LMJV_Rumilly_Sept 2026C566437 does not have a vehicle_id
- trip_id H1LMJV_Rumilly_Sept 2026C499162 does not have a vehicle_id
- trip_id H1LMJV_Rumilly_Sept 2026C498931 does not have a vehicle_id
- trip_id H1LMJV_Rumilly_Sept 2026C498902 does not have a vehicle_id
- trip_id H1LMJV_Rumilly_Sept 2026C498874 does not have a vehicle_id
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 | 84 | 25 times (86 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 | 2 times (7 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-30 at 04:01 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 2026-09-30 at 04:01 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "C499176",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1790709794"
},
"departure": {
"time": "1790709794"
},
"stopId": "0:PONE1",
"stopSequence": 15
},
{
"arrival": {
"time": "1790709836"
},
"departure": {
"time": "1790709836"
},
"stopId": "0:ANNE1",
"stopSequence": 16
},
{
"arrival": {
"time": "1790709980"
},
"departure": {
"time": "1790709980"
},
"stopId": "0:PLAR1",
"stopSequence": 17
},
{
"arrival": {
"time": "1790710034"
},
"stopId": "0:GAR1",
"stopSequence": 18
}
],
"timestamp": "1790733708",
"trip": {
"directionId": 1,
"routeId": "J4",
"scheduleRelationship": "SCHEDULED",
"tripId": "H1LMJV_Rumilly_Sept 2026C499176"
},
"vehicle": {
"id": "6",
"label": "6"
}
}
},
{
"id": "C498896",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1790705549",
"uncertainty": 120
},
"departure": {
"time": "1790705549",
"uncertainty": 120
},
"stopId": "0:FOR2",
"stopSequence": 19
},
{
"arrival": {
"time": "1790705574",
"uncertainty": 120
},
"stopId": "0:HOP2",
"stopSequence": 20
}
],
"timestamp": "1790733708",
"trip": {
"directionId": 1,
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"tripId": "H1LMJV_Rumilly_Sept 2026C498896"
},
"vehicle": {
"id": "1",
"label": "1"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1790733708"
}
}