Resource details
This resource file is part of the dataset Réseau scolaire de Flers.
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
❌13 errors, 25 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-21 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
trip start_time does not match first GTFS arrival_time E023 3 errors
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Sample errors
- GTFS-rt trip_id T19M start_time is 07:25:00 and GTFS initial arrival_time is 07:29:00 - times do not match
- GTFS-rt trip_id T5M start_time is 07:25:00 and GTFS initial arrival_time is 07:20:00 - times do not match
- GTFS-rt trip_id T11M start_time is 07:36:00 and GTFS initial arrival_time is 07:41:00 - times do not match
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 10 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id T5M stop_sequence 1 has stop_id 205 but GTFS stop_sequence 1 has stop_id 213 - stop_ids should be the same
- GTFS-rt trip_id T5M stop_sequence 2 has stop_id 203 but GTFS stop_sequence 2 has stop_id 205 - stop_ids should be the same
- GTFS-rt trip_id T5M stop_sequence 3 has stop_id 196 but GTFS stop_sequence 3 has stop_id 203 - stop_ids should be the same
- GTFS-rt trip_id T5M stop_sequence 4 has stop_id 200 but GTFS stop_sequence 4 has stop_id 196 - stop_ids should be the same
- GTFS-rt trip_id T5M stop_sequence 5 has stop_id 185 but GTFS stop_sequence 5 has stop_id 200 - stop_ids should be the same
Warnings
timestamp not populated W001 25 errors
Timestamps should be populated for all elements
Sample errors
- trip_id T21M does not have a timestamp
- trip_id T23M does not have a timestamp
- trip_id T24M does not have a timestamp
- trip_id T-3M does not have a timestamp
- trip_id T19M does not have a timestamp
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 227 | 11 times (37 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 20 | 9 times (30 % 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) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 16 | 3 times (10 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 16 | 3 times (10 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1,030 | 3 times (10 % of validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 20 | 2 times (7 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1,208 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-21 at 19:48 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-21 at 19:48 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769021314"
}
}