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 SNGO! Giverny Vernon - Gare SNCF.

Download availability

2025-05-23
100%
2025-05-24
100%
2025-05-25
100%
2025-05-26
100%
2025-05-27
99.5%
2025-05-28
100%
2025-05-29
100%
2025-05-30
100%
2025-05-31
100%
2025-06-01
100%
2025-06-02
100%
2025-06-03
99.4%
2025-06-04
100%
2025-06-05
100%
2025-06-06
100%
2025-06-07
100%
2025-06-08
100%
2025-06-09
100%
2025-06-10
100%
2025-06-11
100%
2025-06-12
100%
2025-06-13
100%
2025-06-14
100%
2025-06-15
100%
2025-06-16
99.5%
2025-06-17
100%
2025-06-18
99.5%
2025-06-19
100%
2025-06-20
100%
2025-06-21
100%
2025-06-22
100%
Learn more
We test this resource download availability every hour by making an HTTP 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 2025-06-22 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.

Validate this GTFS-RT now

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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 6 3 times (10 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 6 3 times (10 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 15 3 times (10 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 1 1 times (3 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 8 1 times (3 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 3 1 times (3 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 3 1 times (3 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-22 at 18:48 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-06-22 at 18:48 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1750610930" } }