GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Bibus (Brest)

Based on the feed this agency publishes

Service mode Tram + Bus + Aerial lift

51.8 / 100

First scorecard for this agency

Catalogued in Bretagne, France.

Covers 43 daysRealtime not yet published

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

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

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

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

Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 02

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.

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

Fix 03

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

Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +8 points in its category

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. Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    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. 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. · 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. Review the rule documentation for 'trip_distance_exceeds_shape_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · 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.

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 43 days.
Published accessibility data
Accessibility information is stated for 81.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
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

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

Correctness25.5 / 100

The MobilityData validator flagged 11 kinds of issue across 5395 instances (153 error, 4714 warning, 528 informational).

Freshness71.7 / 100

Service data covers the next 43 days.

Rider experience72.7 / 100

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

Accessibility88.3 / 100

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

2 accessibility depth signals

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

    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.

  • 14 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Chapelle St Yves", "St Herbot", "St Herbot", 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 qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

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

Skip to route and stop data

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

  • 2 (yellow)
  • 3 (orange)
  • 4 (purple)
  • 6 (red)
  • 10 (yellow)
  • 11 (teal)
  • 12 (purple)
  • 13 (red)
  • 15 (white)
  • 16 (yellow)
  • 17 (green)
  • 19 (brown)
  • 20 (pink)
  • 21 (gray)
  • 22 (gray)
  • 23 (gray)
  • 24 (gray)
  • 26 (white)
  • 27 (white)
  • 28 (white)
  • 30 (gray)
  • 31 (gray)
  • 91 (pink)
  • 92 (pink)
  • 93 (pink)
  • 94 (pink)
  • 96 (pink)
  • 97 (pink)
  • A (pink)
  • B (teal)
  • BLEU (teal)
  • C (pink)
  • CIEL (teal)
  • D (green)
  • PORT (white)
Routes in Bibus (Brest)'s feed
RouteTypeLine color
2 Port de Commerce - Fort Montbarey / TechnopôleBusyellow
3 AFPA - OcéanopolisBusorange
4 Liberté - Porte de GouesnouBuspurple
6 Fort Montbarey - Prat LédanBusred
10 PLOUZANÉ Bourg - BREST CHU QuestelBusyellow
11 PLOUZANÉ Bourg - PLOUZANE PiccardBusteal
12 GUILERS Croas ar Pennoc - BREST LibertéBuspurple
13 BREST Le Bergot - BREST StrasbourgBusred
15 GOUESNOU Lantel - BREST StrasbourgBuswhite
16 GUIPAVAS Aéroport - BREST Gare routièreBusyellow
17 LE RELECQ-KERHUON Le Mendy - BREST StrasbourgBusgreen
19 PLOUGASTEL Ty ar Menez - BREST LibertéBusbrown
20 Porte de GOUESNOU - AEROPORT Brest BretagneBuspink
21 Porte de GOUESNOU via Z.A. de KergaradecBusgray
22 BREST Liberté - BREST ChevillotteBusgray
23 PLOUGASTEL Ty ar Menez - BREST LibertéBusgray
24 GUIPAVAS St Herbot via Le DouvezBusgray
26 PLOUZANE Mairie - BREST BordenaveBuswhite
27 GUILERS Roberval - BREST Quatre PompesBuswhite
28 Porte de GOUESNOU - BREST Quatre PompesBuswhite
30 BREST Strasbourg - PLOUGASTEL KervenalBusgray
31 BREST Strasbourg - GUIPAVAS LanvianBusgray
91 BREST Vali Hir - BREST Centre funéraireBuspink
92 BREST CHU La Cavale - BREST Centre funéraireBuspink
93 BREST Roch Glas - BREST Place des FFIBuspink
94 GOUESNOU Place des Fusillés - Porte de GOUESNOUBuspink
96 GUIPAVAS Pen-an-Traon - LE RELECQ-KERHUON RésistanceBuspink
97 Porte de GUIPAVAS - GUIPAVAS PalarenBuspink
A Porte de Plouzané - Portes de Gouesnou / GuipavasTram / light railpink
B Gares - CHU La CavaleTram / light railteal
BLEU LIGNE BLEUE Gare routière - Palaren Stang AlarBusteal
C Jean Moulin - AteliersAerial liftpink
CIEL BREST Cité U - LE RELECQ-KERHUON Le PassageBusteal
D Gares - LambézellecBusgreen
PORT NAVETTE DU PORT Les Îles - LibertéBuswhite

This feed has 940 stops.

List every stop
  • 4 Chemins
  • 4 Moulins
  • 4 Moulins
  • 8 Mai 45
  • 8 Mai 45
  • Aber-Ildut
  • AFPA
  • Prat Lédan
  • Prat Lédan
  • Aéroport
  • Albert 1er
  • Albert 1er
  • Albert 1er
  • Albert 1er
  • Alfost
  • Alfost
  • Amundsen
  • Amundsen
  • Anjou
  • Anjou
  • Anne de Bretagne
  • Maison d'Arrêt
  • Maison d'Arrêt
  • Arthaud
  • Quai des Subsistances
  • Quai des Subsistances
  • Ateliers
  • Guipavas Awena
  • Guipavas Awena
  • Amiral Ronarc'h
  • Amiral Ronarc'h
  • Poul Ar Bachet
  • Poul Ar Bachet
  • Baradozic
  • Baradozic
  • Ste Barbe
  • Ste Barbe
  • Fou de Bassan
  • Fou de Bassan
  • Baudot
  • Beaumanoir
  • Beaumanoir
  • Le Bergot
  • Le Bergot
  • Le Bergot
  • Le Bergot
  • Berlioz
  • Berlioz
  • Bernard
  • Bernard
  • Berry
  • Berry
  • Beuzit
  • Beuzit
  • Bleuets
  • Bleuets
  • Boulogne
  • Boulogne
  • Bodonn
  • Bodonn
  • Bohars Bourg
  • Bohars Bourg
  • Le Bois
  • Le Bois
  • Bordenave
  • Bordenave
  • Baudot
  • Université
  • Université
  • Bourayne
  • Bourayne
  • Bourayne
  • Bourayne
  • Braille
  • Braille
  • Brasserie
  • Brasserie
  • Le Bras
  • Le Bras
  • Brazza
  • Brazza
  • Lannével-Braz
  • Lannével-Braz
  • Breleiz
  • Bruyère
  • Bruyère
  • BSM
  • BSM
  • Broussais
  • Broussais
  • Brasserie
  • Brasserie
  • Quatre Pompes
  • Quatre Pompes
  • Camfrout
  • Camfrout
  • CIMOB
  • CIMOB
  • Les Capucins
  • Les Capucins
  • La Carène
  • La Carène
  • Casabianca
  • Casabianca
  • Castelmein
  • Castel an Daol
  • Castel an Daol
  • Champagne
  • Champagne
  • Chapelle
  • Chapelle
  • Charcot
  • Charcot
  • Châtaigniers
  • Châtaigniers
  • Château
  • Château
  • Chapelle St Yves
  • Château d'Eau
  • Château d'Eau
  • Chevillotte
  • Chevillotte
  • Champ de Foire
  • Champ de Foire
  • Choiseul
  • Choiseul
  • CHU La Cavale
  • CHU La Cavale
  • CHU Accueil
  • CHU La Cavale
  • CHU Morvan
  • CHU Morvan
  • CHU Questel
  • Ecole Navale
  • Ecole Navale
  • Yves Le Gallo
  • Yves Le Gallo
  • Yves Le Gallo - Cité U
  • Yves Le Gallo - Cité U
  • Cité U
  • Cité U
  • Clinique Keraudren
  • Clinique Keraudren
  • Clauzel
  • Clauzel
  • Cloître
  • Coataudon
  • Coataudon
  • Coatmeur
  • Coatuelen
  • Coatuelen
  • Coat ty Ogant
  • Coat Jestin
  • Coat Jestin
  • Coat Mez
  • Coat Mez
  • Coat Tan
  • Coat Tan
  • Coat Tan
  • Coat Tan
  • Cocteau
  • Cocteau
  • Comte
  • Comte
  • Coppin
  • Coppin
  • Coriolis
  • Cormorans
  • Cormorans
  • Cosmao Prétot
  • Cosmao Prétot
  • Cosquer
  • Cosquer
  • Couperin
  • Couperin
  • Les Capucins
  • Les Capucins
  • Le Crann
  • Le Crann
  • Pen ar Créac'h
  • Pen ar Créac'h
  • Croas Ar Bis
  • Croas Ar Bis
  • Croas-ar-go
  • Croas-ar-go
  • Cruguel
  • Cruguel
  • Cuirassé
  • Cuirassé
  • Curie
  • Croix Neuve
  • Chapelle Croix
  • Chapelle Croix
  • Centre Funéraire
  • Campus Kérichen
  • Campus Kérichen
  • Centrale Réseaux
  • Centrale Réseaux
  • Daguerre
  • Danton
  • Danton
  • Dauphiné
  • Dauphiné
  • De Gaulle
  • De Gaulle
  • Demy
  • Demy
  • Deredec
  • Deredec
  • Deschart
  • De Rochon
  • De Rochon
  • La Digue
  • La Digue
  • Bassin 3
  • Bassin 3
  • Diwan
  • Diwan
  • Dixmude
  • Dixmude
  • Mathieu Donnart
  • Mathieu Donnart
  • Douric
  • Douric
  • Le Douvez
  • Dunant
  • Dunant
  • Dupleix
  • Dupleix
  • Dupuy de Lôme
  • Dupuy de Lôme
  • Duquesne
  • Duquesne
  • Eau Blanche
  • Eau Blanche
  • Eau Blanche
  • Ecoles
  • Ecoles
  • A11
  • A11
  • Enclos
  • Enclos
  • S.L.M.
  • S.L.M.
  • Emile Rousse
  • Emile Rousse
  • ESNLE
  • ESNLE
  • D'Estrées
  • D'Estrées
  • and 690 more (see the full list on the map or in the GeoJSON)

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
  • Error153 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Warning2762 instances

    Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning1700 instances

    Equal shape distance same coordinates (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning176 instances

    176 of 940 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.)

    Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning118 instances

    Some service calendars have no days of the week switched on.

    Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

    Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

    Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning94 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.)

    Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

  • Warning26 instances

    Stop too far from shape using user distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning13 instances

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

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

  • Warning1 instance

    Missing feed contact email and url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: missing_feed_contact_email_and_url · 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.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Info342 instances

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: unsorted_stop_times · See MobilityData GTFS Validator rules

  • Info185 instances

    Trip headsign matches intermediate stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • Info1 instance

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Validator rule: unknown_column · 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).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 81% of stops and 100% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 43 days.
Accessible Not yet
States wheelchair access on 81% 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 43 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 153 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 26 / 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 72 / 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 73 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
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.

Bibus (Brest) 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/bibus-brest/2026-07-18.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-07-18. 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.