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 Brévibus.
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
❌46 errors, 3 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-24 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 28 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 18-1560412165 stop_sequence 13 arrival_time 09:10:57 (1756019457) is less than previous stop arrival_time 09:11:55 (1756019515) - times must increase between two sequential stops
- trip_id 18-1560412165 stop_sequence 13 arrival_time 09:10:57 (1756019457) is less than previous stop departure_time 09:12:40 (1756019560) - times must increase between two sequential stops
- trip_id 18-1616773284 stop_sequence 2 arrival_time 07:55:40 (1756014940) is less than previous stop arrival_time 08:15:49 (1756016149) - times must increase between two sequential stops
- trip_id 18-1616773284 stop_sequence 2 departure_time 07:55:40 (1756014940) is less than previous stop arrival_time 08:15:49 (1756016149) - times must increase between two sequential stops
- trip_id 18-1616773284 stop_sequence 3 arrival_time 07:52:55 (1756014775) is less than previous stop arrival_time 07:55:40 (1756014940) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 errors
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.
Sample errors
- trip_id 18-1616773284 stop_sequence 1 departure_time 07:51:41 (1756014701) is less than the same stop arrival_time 08:15:49 (1756016149) - departure time must be equal to or greater than arrival time
- trip_id 18-1616773402 stop_sequence 17 departure_time 08:51:00 (1756018260) is less than the same stop arrival_time 08:51:08 (1756018268) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 15 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 18-1560412165 stop_sequence 1 doesn't have arrival or departure
- trip_id 18-1560412165 stop_sequence 2 doesn't have arrival or departure
- trip_id 18-1560412165 stop_sequence 3 doesn't have arrival or departure
- trip_id 18-1560412165 stop_sequence 4 doesn't have arrival or departure
- trip_id 18-1560412165 stop_sequence 5 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 18-1560412165 and vehicle_id 61d843eed74c542cfad51ff3 pairing in VehiclePositions does not match trip_id 18-1549672264 and vehicle_id 61d843eed74c542cfad51ff3 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Warnings
ID in one feed missing from the other W003 3 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 18-1616773402 is in TripUpdates but not in VehiclePositions feed
- trip_id 18-1549672264 is in TripUpdates but not in VehiclePositions feed
- trip_id 18-1616773284 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 |
|---|---|---|---|
| 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 | 71 | 30 times (100 % of validations) |
| 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 | 90 | 29 times (97 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 83 | 11 times (37 % 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. | 16 | 11 times (37 % 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) |
| 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 2025-08-24 at 20:20 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-08-24 at 20:20 Europe/Paris.
ERRATUM horaires ligne 3 Modified service
ATTENTION : 3 horaires sont modifiés sur la ligne 3 au départ de SAINT-BREVIN Centre de l'Océan : 14h31 (au lieu de 15h06) 16h31 (au lieu de 16h26) 18h31 (au lieu de 18h26) Les autres horaires sont inchangés par rapport à ceux inscrits sur l'indicateur. Merci de votre compréhension.
Between 2025-07-01 at 02:00 Europe/Paris and 2025-09-01 at 01:59 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-08-24 at 20:20 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"end": "1756684740",
"start": "1751328000"
}
],
"cause": "OTHER_CAUSE",
"descriptionText": {
"translation": [
{
"text": "ATTENTION : 3 horaires sont modifiés sur la ligne 3 au départ de SAINT-BREVIN Centre de l'Océan : \n\n14h31 (au lieu de 15h06)\n16h31 (au lieu de 16h26)\n18h31 (au lieu de 18h26)\n\nLes autres horaires sont inchangés par rapport à ceux inscrits sur l'indicateur.\n\nMerci de votre compréhension."
}
]
},
"effect": "MODIFIED_SERVICE",
"headerText": {
"translation": [
{
"text": "ERRATUM horaires ligne 3"
}
]
},
"informedEntity": [
{
"routeId": "93"
}
]
},
"id": "alert:6863eb446e6b329dbe1ec105"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1756059639"
}
}