← All agencies

Feed status · checked 2026-10-16

Réseau urbain Pybus

Based on the official feed source on file

Service mode Bus

FDCBA

85.1 / 100

unchanged since 2026-10-15

Cataloged in Nouvelle-Aquitaine, France.

Covers 76 daysAccessibility gaps

Source feed: https://www.data.gouv.fr/api/1/datasets/r/95654461-59d1-4a33-8830-f90d55e8a217

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.4, validator 8.0.1.

Checked for changes 38 minutes ago; last changed 38 minutes ago.

Measured 4 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: high.

All four score categories were measured this run.
Realtime was sampled in one bounded window of 9 snapshots.
The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

Réseau urbain Pybus’s published feed lists 2 bus routes, 41 scheduled trips and 38 stops. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file last changed on 2026-10-16.

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

28 of 38 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

Fixing this covers 28 of 38 stops, about 74% of them.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +18 points in its category

Fix 02

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Two fields, set once in export settings.worth about +15 points in its category

Fix 03

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.

Copy handoff text

Agency: Réseau urbain Pybus
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 28 of 38 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/fr-pan-82619/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_missing_feed_info_dates
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_no_fare_data
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date is in 76 days.
Published accessibility data: Accessibility information is stated for 26.3% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information: No fare information is published in the feed.
Realtime information: One or more realtime feeds were reachable; live-arrival coverage is not known.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Hi,

Our GTFS feed (Réseau urbain Pybus) scored B (85.1 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 28 of 38 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Add feed_info.txt with feed_start_date and feed_end_date to your export.
   What: feed_info.txt is missing its start/end dates (the file itself is absent)
   Finding code: scorecard_missing_feed_info_dates
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_feed_info_dates/

3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/fr-pan-82619/

Score by category

Correctness95.2 / 100

The MobilityData validator flagged 2 kinds of issue across 42 instances (0 error, 1 warning, 41 informational).

Freshness85.0 / 100

Service data covers the next 76 days.

Rider experience59.1 / 100

26% of stops state wheelchair accessibility (26% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility53.9 / 100

26% of stops state accessibility (26% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime quality100.0 / 100

Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 38 stops.

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

1 (pink)
2 (purple)

Routes in Réseau urbain Pybus's feed
Route	Type	Line color
1 Ligne 1 - Campus des Métiers <-> Cité Leclerc	Bus	pink
2 Ligne 2 - Jules Ferry <-> ZAC des Loges	Bus	purple

List every stop

Aristide Briand
Aristide Briand
Base de Loisirs - Gatinéo
Base de Loisirs - Gatinéo
Centre Hospitalier
Campus des Métiers
Cité Maréchal Leclerc
Cité Maréchal Leclerc
Commandant Charcot
Commandant Charcot
Edgard Quinet - Cimetière
Edgard Quinet - Cimetière
L'Enjeu
L'Enjeu
Lycée Ernest Perochon
Lycée Ernest Perochon
Avenue François Mitterand - Bergeronettes
Avenue François Mitterand - Bergeronettes
Gare Routière - Pôle d'Échange Multimodal
Place Guy Marchand
Place Guy Marchand
Blaise Pascal - La Mara
Blaise Pascal - La Mara
Maison de l'emploi
Maison du temps libre
Maurice Caillon
Maurice Caillon
Place du Drapeau
Place du Drapeau
Domaine des Loges
Domaine des Loges
Jules Ferry
Terres Rouges
Terres Rouges
Village des Solidarités
Village des Solidarités
Centre Commercial des Loges
Centre Commercial des Loges

Over time

Overall score across the last 15 checks — unchanged since 2026-10-15.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	85.1	first check
2026-10-03	76.9	down 8.2
2026-10-04	85.1	up 8.2
2026-10-05	85.1	no change
2026-10-06	85.1	no change
2026-10-07	85.1	no change
2026-10-08	85.1	no change
2026-10-09	85.1	no change
2026-10-10	85.1	no change
2026-10-11	85.1	no change
2026-10-12	85.1	no change
2026-10-13	85.1	no change
2026-10-14	85.1	no change
2026-10-15	85.1	no change
2026-10-16	85.1	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change
Realtime quality no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-16	`4aacbf0098db`	2026-12-31	Current rubric: see the trend above
2026-10-15	`eac16a6fca7f`	2026-12-31	Current rubric: see the trend above
2026-10-14	`aa139fd6702b`	2026-12-31	Current rubric: see the trend above
2026-10-13	`9d1b2ec927e2`	2026-12-31	Current rubric: see the trend above
2026-10-12	`3193282f9dad`	2026-12-31	Current rubric: see the trend above
2026-10-11	`5175a3986dff`	2026-12-31	Current rubric: see the trend above
2026-10-10	`8bae4f724807`	2026-12-31	Current rubric: see the trend above
2026-10-09	`fe9a73d97ead`	2026-12-31	Current rubric: see the trend above
2026-10-08	`df3283945cc2`	2026-12-31	Current rubric: see the trend above
2026-10-07	`20a8cb739830`	2026-12-31	Current rubric: see the trend above
2026-10-06	`3d90661a47e4`	2026-12-31	Current rubric: see the trend above
2026-10-05	`eaf79f24d8e0`	2026-12-31	Current rubric: see the trend above

Showing the 12 most recent of 42 periods.

What changed in this feed

Overall grade and score held steady since 2026-10-15.

The feed file was re-published since 2026-10-15.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

What changed over time

On 2026-10-02 this feed started at grade B. On 2026-10-03 the grade moved from B to C. On 2026-10-04 the grade moved from C to B. As of 2026-10-16 it holds grade B.

A plain-language history of this feed, newest first.

2026-10-04 Grade went C to B, realtime rose 41 points.
2026-10-03 Grade went B to C, realtime fell 41 points.

Everything we checked

6 findings, ordered by severity.

Show every finding

Warning28 instances
28 of 38 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info41 instances
Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 26% of stops and 100% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 76 days.
Accessible Not yet: States wheelchair access on 26% of stops and 100% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-16, with 7s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.

Clears the Google and Apple Maps four-week coverage bar. This feed has 76 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 95 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 85 / 100: GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 59 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the France portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Nouvelle-Aquitaine

Other scorecards in Nouvelle-Aquitaine, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/fr-pan-82619/"><img src="https://gtfsscorecard.org/agency/fr-pan-82619/badge.svg" width="320" height="58" alt="Réseau urbain Pybus: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Réseau urbain Pybus: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/fr-pan-82619/badge.svg)](https://gtfsscorecard.org/agency/fr-pan-82619/)

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/fr-pan-82619/2026-10-16.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-10-16. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). Réseau urbain Pybus GTFS feed-quality record, dated 2026-10-16 (grade B (85.1/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 4aacbf0098db…). https://gtfsscorecard.org/data/artifacts/fr-pan-82619/2026-10-16.json

@misc{gtfsscorecard-fr-pan-82619-2026-10-16,
  title        = {Réseau urbain Pybus GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/fr-pan-82619/2026-10-16.json}},
  note         = {Checked 2026-10-16; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade B (85.1/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.