GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Réseau urbain Ar bus

Based on the official feed source on file

Service mode Bus

49.5 / 100

First scorecard for this agency

Catalogued in Bretagne, France.

Covers 305 daysAccessibility gaps

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.3, validator 8.0.1.

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 3 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.

Top things to fix

Fix 01

Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool

Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

⏱ Usually an export-tool fix, not hand editing.worth about +24 points in its category

Fix 02

Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.

5 of 5 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.

⏱ A vendor data-mapping question.worth about +41 points in its category

Fix 03

Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline.

Realtime data was up to 1808 seconds old when sampled. Stale positions and predictions are worse than none: riders watch a bus that already left.

⏱ A vendor configuration question.worth about +29 points in its category

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.

Feed evidence
Some trips have stop times whose distances along the route go backwards.
Next action
Re-generate shape distances in your export; flag to your vendor if it persists.
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
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.

  1. Re-generate shape distances in your export; flag to your vendor if it persists.

    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. Self-check a feed before you publish.

  2. Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. · Read the fix guide

    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. Self-check a feed before you publish.

  3. Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline.

    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. Self-check a feed before you publish.

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 305 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% 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
Live-arrival data covered 0% of scheduled trips in the sampled window.

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.

Score by category

Correctness49.2 / 100

The MobilityData validator flagged 7 kinds of issue across 274 instances (143 error, 122 warning, 9 informational).

Freshness85.0 / 100

Service data covers the next 305 days.

Rider experience37.5 / 100

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

Accessibility0 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 5, 6).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Sébastien", "St Sébastien", "St Joseph", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime quality29.4 / 100

Sampled 3 times: 1 of 1 configured feed healthy; 0.0% of scheduled trips had live predictions; predictions ran a median of 141s behind schedule.

Routes and stops

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

This feed has 125 stops.

Skip to route and stop data

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 (teal)
  • 2 (pink)
  • 3 (red)
  • 4 (green)
  • 5 (black)
  • 6 (purple)
Routes in Réseau urbain Ar bus's feed
RouteTypeLine color
1 1: Kergreis - Gare RoutièreBusteal
2 2: Kerabec - Gare RoutièreBuspink
3 3: Hôpital - Gare RoutièreBusred
4 4: Tromeur - Gare RoutièreBusgreen
5 5: Ecossais - Gare RoutièreBusblack
6 6: Gorre Beuzit - Gare RoutièreBuspurple
List every stop
  • Edmond Michelet
  • Aulne
  • La Garenne
  • Diossin
  • Penaros
  • Kergoat
  • Allée des bois
  • Roches Blanches
  • Mimosas
  • Les Maraîchers
  • Kergoury
  • Caventou
  • Le Lech
  • Petit Paris
  • Kergreis-Izella
  • Mairie
  • La Colline
  • La Bascule
  • Calmette et Guérin
  • Kerloïs Pencran
  • Bourg Pencran
  • Roskelen Pencran
  • La Bascule
  • Kerloïs Pencran 2
  • Hôpital
  • J.F Kennedy
  • Victor Hugo
  • Les Maraîchers
  • Voas Glaz
  • Kergoury
  • Le Lech
  • Bel Air
  • Marie Curie
  • Petit Paris
  • Général Audibert
  • Parc Urbain
  • La Marne
  • St Sébastien
  • Hünfeld
  • Maison de Retraite
  • Trémaria
  • Pont Caernarfon
  • Amédée Belhommet
  • Lavallot
  • Petite Palud
  • Hôpital
  • Garenne du Sentier
  • Roskelen
  • St Joseph
  • Lavallot
  • Amédée Belhommet
  • Maison de retraite
  • Voas Glaz
  • Pont Caernarfon
  • Trémaria
  • Dixmude
  • Le Tourous
  • Hünfeld
  • Mescoat
  • Jacques Frimot
  • Centre de Secours
  • Penguelen
  • Quatre Vents
  • Amiral Ronarc'h
  • Cimetière
  • Bois Noir
  • Gendarmerie
  • Victor Hugo
  • Roger Salengro
  • Le Tromeur
  • Marie Curie
  • Petit Paris
  • Général Audibert
  • Kerzioc'h
  • Hermitage
  • Montcalm
  • Fosse aux Loups
  • Goulhéo
  • Georges Bizet
  • Kermoualec
  • Hector Berlioz
  • Kerlezerien
  • Kerabec
  • Le Broustic
  • Ar Vilinig
  • Four à Chaux
  • St Ernel
  • Piscine
  • Route de Quimper
  • Edouard Lalo
  • Quai de Léon
  • Gare
  • Rue Du Gaz
  • keranden
  • Chemin de Fer
  • Quinquis Lech
  • Bel Air
  • Pelletier
  • Kerlaran
  • Aber Wrac'h
  • Kermorvan
  • Milin Avel
  • Isole
  • Suffren
  • Maison de Quartier
  • Kerguelen
  • Porz Mae
  • Kerabiven
  • Kermab ar Follez
  • Gorré Beuzit
  • Prat guen
  • Cap Horn
  • Vuillemin
  • Maréchal Leclerc
  • Jean Monnet
  • St Sébastien
  • Parc Urbain
  • J.F Kennedy
  • Gare Routière
  • Quai de Léon
  • Mairie
  • La Marne
  • Quinquis Lech
  • Quinquis Lech
  • Gendarmerie

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

14 findings, ordered by severity.

Show every finding
  • Error143 instances

    Some trips have stop times whose distances along the route go backwards.

    Apps can show buses jumping backwards or mis-order stops.

    Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)

    Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules

  • Warning241 instances

    241 of 241 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning125 instances

    125 of 125 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 · See GTFS Schedule reference

  • Warning91 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning28 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

  • Warning5 instances

    5 of 5 trips scheduled during the sampling window had no live predictions.

    Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.

    Fix: Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. (A vendor data-mapping question.)

    Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference

  • Warning1 instance

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • 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 · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • 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 · See MobilityData GTFS Validator rules

  • 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 · See GTFS Best Practices

  • Warning1 instance

    Realtime data was up to 1808 seconds old when sampled.

    Stale positions and predictions are worse than none: riders watch a bus that already left.

    Fix: Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline. (A vendor configuration question.)

    Finding code: scorecard_rt_stale

  • Info9 instances

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules

  • 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 · See MobilityData GTFS Validator rules

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 305 days.
Accessible Not yet
States wheelchair access on 0% of stops and 0% 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 4 checks over the last 1 day, with 15672s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Live predictions vs schedule

Arrival predictions ran a median 141s late versus the schedule, and stayed within 300s nine times in ten. They were on time (about a minute early to five late) 95.7% of the time.

From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.

Clears the Google and Apple Maps four-week coverage bar. This feed has 305 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 143 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

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 49 / 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 38 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 29 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Réseau urbain Ar bus GTFS data quality grade: F

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-81459/2026-09-01.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-09-01. 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.

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