Resource details

File name: GTFS RT
Format: gtfs-rt

Partage des données de transport real time ponctuel de la façon suivante : le flux real time vient en complément du fichier static qui est transmis chaque jour et envoie uniquement les timetables des trains qui sont impactés par une modification du plan de transport le jour J.

This resource file is part of the dataset Réseau européen Thalys.

Download availability

2024-04-07
100%
2024-04-08
100%
2024-04-09
100%
2024-04-10
100%
2024-04-11
100%
2024-04-12
100%
2024-04-13
100%
2024-04-14
100%
2024-04-15
100%
2024-04-16
100%
2024-04-17
100%
2024-04-18
100%
2024-04-19
100%
2024-04-20
100%
2024-04-21
100%
2024-04-22
100%
2024-04-23
100%
2024-04-24
100%
2024-04-25
100%
2024-04-26
100%
2024-04-27
100%
2024-04-28
100%
2024-04-29
99.5%
2024-04-30
100%
2024-05-01
100%
2024-05-02
100%
2024-05-03
100%
2024-05-04
100%
2024-05-05
100%
2024-05-06
100%
2024-05-07
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.

Validation details

No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-02 at 09:08 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
W008 The data in a GTFS-realtime feed should always be less than one minute old 14 14 times (82 % of validations)
E009 If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence 5 3 times (18 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 2 2 times (12 % of validations)
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 (12 % of validations)
E040 All stop_time_updates must contain stop_id or stop_sequence - both fields cannot be left blank 2 2 times (12 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-06 at 22:12 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 16 862 seconds. Try to update your feed at most every 30 seconds.

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-05-06 at 22:12 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "0091262024-05-0611690", "trip_update": { "stop_time_update": [ { "departure": { "delay": 1200 }, "stop_id": "st_pancras_international_batiment_voyageurs" }, { "arrival": { "delay": 2400 }, "departure": { "delay": 3600 } }, { "arrival": { "delay": 4800 }, "departure": { "delay": 6300 }, "stop_id": "bruxelles-midi/brussel-zuid" }, { "arrival": { "delay": 7980 }, "departure": { "delay": 9660 }, "stop_id": "rotterdam_centraal" }, { "arrival": { "delay": 11520 }, "stop_id": "amsterdam_centraal" } ], "timestamp": "1715019120", "trip": { "start_date": "20240506", "trip_id": "9126-0506" }, "vehicle": { "id": "009126" } } }, { "id": "0091582024-05-0611690", "trip_update": { "stop_time_update": [ { "departure": { "delay": 2100 }, "stop_id": "st_pancras_international_batiment_voyageurs" }, { "arrival": { "delay": 4680 }, "departure": { "delay": 7260 } }, { "arrival": { "delay": 9840 }, "stop_id": "bruxelles-midi/brussel-zuid" } ], "timestamp": "1715019120", "trip": { "start_date": "20240506", "trip_id": "9158-0506" }, "vehicle": { "id": "009158" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1715026342" } }