Resource details
horaires en temps réel du réseau Tedbus
This resource file is part of the dataset Réseau urbain TEDbus.
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
❌116 errors, 21 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-12 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 102 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 1000494-1004395 stop_sequence 10 arrival_time 09:07:30 (1749712050) is equal to previous stop arrival_time 09:07:30 (1749712050) - times must increase between two sequential stops
- trip_id 1000494-1004395 stop_sequence 10 arrival_time 09:07:30 (1749712050) is equal to previous stop departure_time 09:07:30 (1749712050) - times must increase between two sequential stops
- trip_id 1000494-1004395 stop_sequence 10 departure_time 09:07:30 (1749712050) is equal to previous stop departure_time 09:07:30 (1749712050) - times must increase between two sequential stops
- trip_id 1000494-1004395 stop_sequence 10 departure_time 09:07:30 (1749712050) is equal to previous stop arrival_time 09:07:30 (1749712050) - times must increase between two sequential stops
- trip_id 1000494-1004395 stop_sequence 12 arrival_time 09:08:30 (1749712110) is equal to previous stop arrival_time 09:08:30 (1749712110) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 14 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 1000388-1003134 stop_sequence 24 doesn't have arrival or departure
- trip_id 1000388-1003134 stop_sequence 25 doesn't have arrival or departure
- trip_id 1000388-1003134 stop_sequence 26 doesn't have arrival or departure
- trip_id 1000388-1003134 stop_sequence 27 doesn't have arrival or departure
- trip_id 1000388-1003134 stop_sequence 28 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 21 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 1000494-1004402 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000388-1003135 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000441-1003742 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000323-1001602 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000389-1003199 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 842 | 26 times (87 % 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 | 492 | 24 times (80 % 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 | 311 | 19 times (63 % 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. | 5 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-13 at 05:44 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-13 at 05:44 Europe/Paris.
L5 Centre ville de Trans non desservi Modified service
En raison de travaux le centre ville de Trans-en-Provence n'est plus desservi. Se reporter aux arrêts de La Gare ou St Bernard.
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-06-13 at 05:44 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"cause": "CONSTRUCTION",
"descriptionText": {
"translation": [
{
"text": "En raison de travaux le centre ville de Trans-en-Provence n'est plus desservi. Se reporter aux arrêts de La Gare ou St Bernard."
}
]
},
"effect": "MODIFIED_SERVICE",
"headerText": {
"translation": [
{
"text": "L5 Centre ville de Trans non desservi"
}
]
},
"informedEntity": [
{
"routeId": "1000007"
},
{
"stopId": "1000179"
},
{
"stopId": "1000183"
},
{
"stopId": "1000185"
}
]
},
"id": "alert:672a409d6d0515a8bf801338"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1749786291"
}
}