Resource details

File name: Données en temps réel au format GTFS-RT
Format: gtfs-rt

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

  • TripUpdate
  • VehiclePosition
  • Alert

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

Download availability

2025-11-05
99.1%
2025-11-06
99.2%
2025-11-07
99.1%
2025-11-08
100%
2025-11-09
99.7%
2025-11-10
99%
2025-11-11
99.1%
2025-11-12
99.1%
2025-11-13
98.9%
2025-11-14
99.8%
2025-11-15
100%
2025-11-16
99.2%
2025-11-17
100%
2025-11-18
99.2%
2025-11-19
99.2%
2025-11-20
98.5%
2025-11-21
98.4%
2025-11-22
99.2%
2025-11-23
97.6%
2025-11-24
97.8%
2025-11-25
96.2%
2025-11-26
99%
2025-11-27
98.4%
2025-11-28
98.4%
2025-11-29
100%
2025-11-30
98.1%
2025-12-01
98.5%
2025-12-02
98.1%
2025-12-03
98.8%
2025-12-04
83.5%
2025-12-05
97.9%
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

3 errors, 5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-05 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update doesn't have arrival or departure E043 3 errors

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id 2-4833542145 stop_sequence 14 doesn't have arrival or departure
  • trip_id 2-4832624644 stop_sequence 12 doesn't have arrival or departure
  • trip_id 2-4832624641 stop_sequence 12 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 5 errors

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

Sample errors
  • trip_id 2-4832624641 is in TripUpdates but not in VehiclePositions feed
  • trip_id 2-4832624644 is in TripUpdates but not in VehiclePositions feed
  • trip_id 2-4833542145 is in TripUpdates but not in VehiclePositions feed
  • trip_id 2-4849074177 is in TripUpdates but not in VehiclePositions feed
  • trip_id 2-4849074179 is in TripUpdates but not in VehiclePositions feed
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
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 178 21 times (70 % 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 107 21 times (70 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 93 13 times (43 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 4 4 times (13 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 3 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-05 at 23:44 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2025-12-05 at 23:44 Europe/Paris.

NOUVEAUTE RESEAU NOSBUS 2023 ! Unknown effect

Déplacez-vous, c'est gratuit pour tous sur le réseau NOSBUS !

Between 2023-01-02 at 01:00 Europe/Paris and 2027-01-03 at 00:59 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-05 at 23:44 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "activePeriod": [ { "end": "1798934340", "start": "1672617600" } ], "cause": "OTHER_CAUSE", "descriptionText": { "translation": [ { "text": "Déplacez-vous, c'est gratuit pour tous\nsur le réseau NOSBUS ! " } ] }, "headerText": { "translation": [ { "text": "NOUVEAUTE RESEAU NOSBUS 2023 !" } ] }, "informedEntity": [ { "routeId": "288" }, { "routeId": "289" }, { "routeId": "290" } ] }, "id": "alert:63b3ffcabe4cd033e6b5093f" } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1764974685" } }