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

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

2 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-30 at 09:14 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update doesn't have arrival or departure E043 2 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 4-4832886785 stop_sequence 7 doesn't have arrival or departure
  • trip_id 4-4832886785 stop_sequence 12 doesn't have arrival or departure
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 99 19 times (63 % 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 103 18 times (60 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 34 8 times (27 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-07-31 at 00:33 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 2026-07-31 at 00:33 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 00:00 Europe/Paris and 2027-01-02 at 23:59 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-07-31 at 00:33 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "activePeriod": [ { "end": "1798930740", "start": "1672614000" } ], "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": "1785450825" } }