gtfs-rt Transport open dataset - Données en temps réel des horaires aux arrêts du réseau Néva for Réseau urbain Néva

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

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

⚠️21 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-13 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id ATOUMOD105:ServiceJourney:5483539630915584x1:LOC does not have a vehicle_id
trip_id ATOUMOD105:ServiceJourney:6572276058161152x0:LOC does not have a vehicle_id
trip_id ATOUMOD105:ServiceJourney:4876408959533056x0:LOC does not have a vehicle_id
trip_id ATOUMOD105:ServiceJourney:4876408959533056x1:LOC does not have a vehicle_id
trip_id ATOUMOD105:ServiceJourney:5372702027153408x1: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:5483539630915584x1:LOC stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD105:ServiceJourney:5483539630915584x1:LOC does not have a schedule_relationship
trip_id ATOUMOD105:ServiceJourney:6572276058161152x0:LOC stop_sequence 15 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD105:ServiceJourney:6572276058161152x0:LOC does not have a schedule_relationship
trip_id ATOUMOD105:ServiceJourney:4876408959533056x0:LOC stop_sequence 29 (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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	171	25 times (86 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	342	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	130	19 times (66 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	3	3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-14 at 03:49 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 2026-02-14 at 03:49 Europe/Paris. You can look at the GTFS-RT documentation.


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