Resource details
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
Learn more
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
❌10 errors, 6 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-23 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 8 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 3-4833607681 stop_sequence 4 arrival_time 08:12:10 (1771830730) is equal to previous stop arrival_time 08:12:10 (1771830730) - times must increase between two sequential stops
- trip_id 3-4833607681 stop_sequence 4 arrival_time 08:12:10 (1771830730) is equal to previous stop departure_time 08:12:10 (1771830730) - times must increase between two sequential stops
- trip_id 3-4833607681 stop_sequence 4 departure_time 08:12:10 (1771830730) is equal to previous stop departure_time 08:12:10 (1771830730) - times must increase between two sequential stops
- trip_id 3-4833607681 stop_sequence 4 departure_time 08:12:10 (1771830730) is equal to previous stop arrival_time 08:12:10 (1771830730) - times must increase between two sequential stops
- trip_id 3-4833607681 stop_sequence 13 arrival_time 08:20:10 (1771831210) is equal to previous stop arrival_time 08:20:10 (1771831210) - times must increase between two sequential stops
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 3-4832624641 stop_sequence 12 doesn't have arrival or departure
- trip_id 3-4832624644 stop_sequence 12 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 6 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 3-4832624641 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-4849074177 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-4849336321 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-4849074186 is in TripUpdates but not in VehiclePositions feed
- trip_id 3-4832624644 is in TripUpdates but not in VehiclePositions feed
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 | 57 | 20 times (69 % 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 | 109 | 20 times (69 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 134 | 15 times (52 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-24 at 05:12 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-02-24 at 05:12 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 2026-02-24 at 05:12 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": "1771906336"
}
}