gtfs-rt Transport open dataset - GTFS-RT Réseau PYBUS for Réseau urbain Pybus

Resource details

File name: GTFS-RT Réseau PYBUS

Format: gtfs-rt

GTFS-RT pour le réseau urbain de Parthenay

This resource file is part of the dataset Réseau urbain Pybus.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌2 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-21 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt agency_id does not exist in GTFS data E034 2 errors

All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt

Sample errors

alert ID alert:6aaa42ae379da49685e395da agency_id 74 does not exist in the GTFS data agency.txt
alert ID alert:6aaa42ae379da49685e395da agency_id 75 does not exist in the GTFS data agency.txt

Validate this GTFS-RT now

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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	124	15 times (50 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	124	15 times (50 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	1,280	15 times (50 % of validations)
E028	The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.	62	15 times (50 % 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	29	10 times (33 % of validations)
E034	All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt	10	5 times (17 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-09-21 at 09:20 Europe/Paris.

service_alerts (1) vehicle_positions (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts

Service alerts

Here is a display of service alerts contained in this feed at 2026-09-21 at 09:20 Europe/Paris.

Merci d'avoir utilisé le Gratibus ! Unknown effect

Le Gratibus, c'est fini pour cette année, on se retrouve l'été prochain sur nos lignes. Toute l'équipe de Gratibus vous remercie d'avoir utilisé le Gratibus.

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-09-21 at 09:20 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "alert": {
        "descriptionText": {
          "translation": [
            {
              "text": "Le Gratibus, c'est fini pour cette année, on se retrouve l'été prochain sur nos lignes.\n\nToute l'équipe de Gratibus vous remercie d'avoir utilisé le Gratibus."
            }
          ]
        },
        "headerText": {
          "translation": [
            {
              "text": "Merci d'avoir utilisé le Gratibus !"
            }
          ]
        },
        "informedEntity": [
          {
            "agencyId": "74"
          },
          {
            "agencyId": "75"
          }
        ]
      },
      "id": "alert:6aaa42ae379da49685e395da"
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1789975237"
  }
}