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
❌19 errors, 4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-02 at 09:08 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 16 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 2-4833738753 stop_sequence 13 arrival_time 09:12:00 (1748848320) is equal to previous stop arrival_time 09:12:00 (1748848320) - times must increase between two sequential stops
- trip_id 2-4833738753 stop_sequence 13 arrival_time 09:12:00 (1748848320) is equal to previous stop departure_time 09:12:00 (1748848320) - times must increase between two sequential stops
- trip_id 2-4833738753 stop_sequence 13 departure_time 09:12:00 (1748848320) is equal to previous stop departure_time 09:12:00 (1748848320) - times must increase between two sequential stops
- trip_id 2-4833738753 stop_sequence 13 departure_time 09:12:00 (1748848320) is equal to previous stop arrival_time 09:12:00 (1748848320) - times must increase between two sequential stops
- trip_id 2-4833738753 stop_sequence 22 arrival_time 09:20:00 (1748848800) is equal to previous stop arrival_time 09:20:00 (1748848800) - times must increase between two sequential stops
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-4833673217 stop_sequence 14 doesn't have arrival or departure
- trip_id 2-4848812033 stop_sequence 16 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 4 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-4833673217 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4849074183 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4848812033 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4833542145 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 | 148 | 23 times (77 % 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 | 128 | 23 times (77 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 259 | 21 times (70 % 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) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-02 at 20:27 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 2025-06-02 at 20:27 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-06-02 at 20:27 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": "1748888871"
}
}