Resource details

File name: Données en temps réel des horaires aux arrêts du réseau Néva
Format: gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts.

This resource file is part of the dataset Réseau urbain Néva.

Download availability

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

7 errors, 21 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-15 at 08:03 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 7 errors

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 ATOUMOD105:ServiceJourney:5001381225168896x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD105:ServiceJourney:5001381225168896x1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD105:ServiceJourney:5842311687700480x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id ATOUMOD105:ServiceJourney:5001381225168896x0:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x1:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x2:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5001381225168896x1:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5842311687700480x0:LOC does not have a vehicle_id

schedule_relationship not populated W009 14 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD105:ServiceJourney:5001381225168896x0:LOC stop_sequence 24 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5001381225168896x0:LOC does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x1:LOC stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x1:LOC does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x2:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 145 21 times (70 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 145 21 times (70 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 290 21 times (70 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 11 11 times (37 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-16 at 04:03 Europe/Paris.

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

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 2025-11-16 at 04:03 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1763262233" } }