Resource details
File name:
Données en temps réel de la ligne Giverny Vernon Gare SNCF
Format: gtfs-rt
This resource file is part of the dataset Navette estivale SNGO! Giverny Vernon - Gare SNCF.
Download availability
2026-08-27
99.2%
2026-09-10
100%
2026-09-04
100%
2026-09-15
100%
2026-08-20
100%
2026-08-22
100%
2026-08-24
100%
2026-09-06
100%
2026-08-23
100%
2026-09-09
100%
2026-09-19
100%
2026-09-18
100%
2026-08-29
100%
2026-08-31
100%
2026-09-17
100%
2026-09-03
100%
2026-09-12
100%
2026-08-21
100%
2026-09-08
100%
2026-09-11
100%
2026-08-26
100%
2026-09-05
100%
2026-09-13
100%
2026-09-14
100%
2026-09-07
100%
2026-09-16
100%
2026-09-01
100%
2026-08-28
100%
2026-08-25
100%
2026-08-30
100%
2026-09-02
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 2026-09-19 at 09:03 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 5 | 2 times (7 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 5 | 2 times (7 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 9 | 2 times (7 % of validations) |
| E034 | All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt | 1 | 1 times (3 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 1 | 1 times (3 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-19 at 19:06 Europe/Paris.
vehicle_positions (1) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-09-19 at 19:06 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "vehicle:6231bcafdc19e2be2246dba3",
"vehicle": {
"currentStopSequence": 2,
"position": {
"latitude": 49.078739166259766,
"longitude": 1.50072181224823
},
"stopId": "4007",
"timestamp": "1789837603",
"trip": {
"routeId": "241",
"tripId": "10"
},
"vehicle": {
"id": "6231bcafdc19e2be2246dba3",
"label": "123",
"licensePlate": "AA-123-AA"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1789837603"
}
}