Feed status · checked 2026-08-31
Réseau interurbain - Charente (16)
Based on the official feed source on file
Service mode Bus
up 8.1 since 2026-08-30 · F → F
Catalogued in Nouvelle-Aquitaine, France.
Heads-up: The score fell 21 points in one step, from 69 on 2026-08-07 to 47 on 2026-08-30. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-08-30). This can be a brief vendor export glitch; watch the next update before acting.
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.
Checked for changes 3 hours ago; last changed 9 hours ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 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
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 +18 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
228 of 228 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
⏱ Two fields, set once in export settings.worth about +15 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
- Feed evidence
- 228 of 228 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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 362 days.
- Published accessibility data
- Accessibility information is stated for 91.8% 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
- 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
The MobilityData validator flagged 11 kinds of issue across 885 instances (16 error, 595 warning, 274 informational).
Service data covers the next 362 days.
92% of stops state wheelchair accessibility (0% marked accessible, 92% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
92% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (120, 124, 134, 164).
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.
507 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("L'HABIT carf RD14/VC", "LA CROIX DU FILS RD41 AB", "POINTE AVOCAT carf RD14", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
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.
This feed has 938 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.
- 184 (gray)
- 121 (gray)
- 122 (gray)
- 124 (red)
- 161 (green)
- 136 (orange)
- 135 (orange)
- 134 (brown)
- 133 (gray)
- 132 (teal)
- 130 (pink)
- 160 (teal)
- 131 (gray)
- 162 (red)
- 182 (teal)
- 183 (yellow)
- 120 (brown)
- 181 (teal)
- 163 (yellow)
- 164 (purple)
- 123 (pink)
| Route | Type | Line color |
|---|---|---|
| 184 Ligne 184 Rougnac - Angouleme | Bus | gray |
| 121 Ligne 121 St-Angeau - Angouleme | Bus | gray |
| 122 Ligne 122 Ruffec-Aigre-Angouleme | Bus | gray |
| 124 Ligne 124 Vouharte- St-Amant - Angouleme | Bus | red |
| 161 Ligne 161 Chateauneuf - Angouleme | Bus | green |
| 136 Ligne 136 Jonzac-Barbezieux-Angouleme | Bus | orange |
| 135 Ligne 135 Baignes-Barbezieux-Angouleme | Bus | orange |
| 134 Ligne 134 Chalais - Barbezieux | Bus | brown |
| 133 Ligne 133 Pereuil - Angouleme | Bus | gray |
| 132 Ligne 132 Barbezieux- Blanzac-Angouleme | Bus | teal |
| 130 Ligne 130 Aubeterre - Angouleme | Bus | pink |
| 160 Ligne 160 Cognac - Jarnac - Angouleme | Bus | teal |
| 131 Ligne 131 Gurat - Angouleme | Bus | gray |
| 162 Ligne 162 St-Jean d'Y-Verdille-Angouleme | Bus | red |
| 182 Ligne 182 Nontron - Angouleme | Bus | teal |
| 183 Ligne 183 Piégut - Montbron - Angouleme | Bus | yellow |
| 120 Ligne 120 Ruffec - Mansle - Angouleme | Bus | brown |
| 181 Ligne 181 Confolens - Angouleme | Bus | teal |
| 163 Ligne 163 Cognac - Barbezieux | Bus | yellow |
| 164 Ligne 164 Pons - Cognac | Bus | purple |
| 123 Ligne 123 - Aigre - Angouleme | Bus | pink |
List every stop
- MONTIGNAC-CHARDONNEAU cf RD15/11
- VOUILLAC RD105 Dég.
- LES NAUDINS RD37 A.Bus
- MOULIN MASSET VC A.Bus
- ARGENCE Place VC 1/2t
- MOSNAC-BLANCHEFLEUR carf RD422/VC
- MOSNAC-CHEZ FUSILLER carf RD422
- ROULLET-LES CHATELIERS carf RD425
- ROULLET-LES MERCERONS cf VC/D699
- MOSNAC-CHEZ SANDONS carf RD422/VC
- CHATEAUNEUF-LES PEYRONNETS A.Bus
- D2
- CHEZ DESMARD RD14 A.Bus
- ROULLET-FOUR A CHAUX
- ROULLET-LA FORET RD22 poteau
- L'OISELLERIE LE JONCO
- ROULLET-LA CHAUME RD910 Encoche
- CHEZ CARTIER RD731 Dég.
- LA CROIX BELET RD731 AB
- CHEZ CHAGNAUD RD128
- MAIRIE RD68
- LES OLIVIERS carf VC
- LE FAGNARD RD731 A.Bus
- LA CHATAIGNERAIE carf D46
- LE MOULIN A VENT RD7
- ECOLE RD7
- FOUR GATINE cf RD7/Impasse
- CHEZ PROMPT VC Sortie
- MOUTHIERS-LA FONT DU ROSSIGNOL
- MOUTHIERS-LES GROIES carf RD12/VC
- MOUTHIERS-LES FAYARDS VC A.Bus
- MOUTHIERS-LES NAULETS VC Place
- LA MAISON BLANCHE cf RD5
- BOIS ROND RD674 Dég.grav
- ST-CYBARD RD74 A.Bus
- ST-AMANT-DE-MON-LE POTEAU cf D709
- LARTIGE A.B n°59
- ASNIERES/NOUERE-NEUILLAC RD53 AB
- BOURRAS carf RD944/RD18
- POINTE AVOCAT carf RD14
- LA CROIX DU FILS RD41 AB
- L'HABIT carf RD14/VC
- GARDES-LE-PTX-PISCINE
- MAGNAC-LAVALETT-LA CROIX BLANCHE
- GARDES-LE-PTX-LA PETITE SARTRIE
- LA CLEF D'OR RD939 Encoche
- ST-GENIS-BOURSANDREAU carf VC AB
- ST-CYBARDEAUX-BOIS RAYMOND
- ST-GENIS-ROISSAC carf Rue Centre
- ST-CYBARDEAUX-CHAMPS(LES PETITS)
- ST-CYBARDEAUX-LES ROCHEREAUX ABus
- ST-YRIEIX-L'EBEAUPIN D939 Encoche
- ASNIERES/NOUERE-PUYRENAUD VC ABus
- ASNIERES/NOUERE-LES DORIBEAUX RD
- Rouillac Sonneville RD 939 AB
- ST-AMANT-DE-NRE-CHIZE(LA)
- ST-GERMAIN-DE-M-LA BROUSSE D33 AB
- ST-GERMAIN-DE-M-BIRAC Carf RD109
- LA CHAMBAUDIE carf RD33
- CHEZ MAILLET A.Bus n°85
- CIMETIERE 1/2t VC A.Bus
- CHEZ PAULY carf RD33/VC
- ROCHEPINE RD33 A.Bus
- LES PRATS carf RD33/VC
- LA TUILERIE RD699 AB n°87
- SALLE DES FETES VC
- GRIGNOL carf RD699/VC
- ST-SORNIN-LES PERVILLES RD415
- SAINT-PAUL RD73 Dég.
- LE MOULIN A VENT
- LES MAISONS ROUGES
- LA GAGNARDERIE RD18
- LA CHIGNOLLE RD45 AB
- LES CHAUVAUDS entrée
- LA TOUCHE D'ANAIS VC AB n°8
- CHURET RD45 A.Bus n°6
- L'ALLEMANDIE RD174
- LES RASSATS RD941 A.Bus
- ST-MARTIN RD313 ABus n°5
- GENAC-LA TOUCHE carf RD118/VC
- ST-GENIS-BASSE RD11 Encoche 1/2t
- BIGNAC-MAIRIE RD117 Dég.gravier
- LA CROIX BELET carf VC
- KLEBER arrêt STGA
- Vignes Jaunes
- CATHEDRALE (côté remparts)
- GAMBETTA (STGA)
- Carrefour de Lille
- HOTEL DE VILLE Rue du Gal Leclerc
- PONT DE VARS (STGA)
- LES FIGUIERS
- LEP LOUISE MICHEL
- CIMETIERE - RD941
- CHASSENEUIL -GARE SNCF
- DIRAC-PIERRES ROUGES cf RD104/VC
- DIRAC-LE BOISSEAU RD939 Dég.
- SERS-MAIRIE RD25 A.Bus n°101
- SOYAUX-CIMETIERE - LEP RD939
- GARAT-ECOLES VC A.Bus
- GARAT-BRAGETTE carf RD87/VC A.Bus
- BOUEX-LE CORMIER RD4 A.Bus
- SERS-PHARMACIE carf RD25/VC
- BOUEX-CHEZ GROLLIER carf RD73/VC
- VOUZAN-LES FORETS VC Entrée
- ANGOULEME-VICTOR HUGO (STGA)
- ANGOULEME-FRANQUIN
- ANGOULEME-HOTEL DE VILLE
- SOYAUX-LE GRAND LAC RD939 Encoche
- VOUZAN-VIEUX BOURG RD108
- GARAT-SAINTE-CATHERINE RD939 ABus
- CHARRAS-MAIRIE carf RD25/VC AB
- ANGOULEME-CATHEDRALE
- ROUGNAC-LE CLEDOU RD93 A.Bus 1/2t
- VOUZAN-LE MAINE GAUBRUN RD412
- ROUGNAC-ECOLE RD41 A.Bus n°94
- GRASSAC-CHENE VERT 10m cf RD34/25
- VOUZAN - BOIS DE COMBE BOUCHARD
- BOUEX-PARC MAUBRUN cf RD73/VC AB
- VOUZAN -ECOLE PARKING RD412
- GRASSAC-TENNIS RD16 A.Bus
- DIRAC-LE PICARD A.B
- ANGOULEME-GARE SNCF
- AGRIS-LES GRANGES D'AGRIS RD11
- JAULDES-SALLE DES FETES RD45
- ANGOULEME-MADELEINE (STGA)
- JAULDES-CHERVES carf RD91/113
- ST-ANGEAU-PLACE RD6 A.Bus n°111
- BRIE-MAIRIE RD91 A.Bus
- LA ROCHETTE-RD40 A.Bus
- AGRIS-LE PONT D'AGRIS RD6 Place
- MARCILLAC-PONT ROUX RD737
- MONTIGNAC-PLACE Dr FEUILLET carf
- MARCILLAC-MAIRIE RD737 A.Bus n°70
- AIGRE-COLLEGE DE L'OSME
- VARS-PLACE Mairie RD11 A.Bus
- TUSSON-PLACE Poste RD736 A.Bus
- BALZAC-LES TEXIERS RD406 maison 3
- RUFFEC-LEP LOUISE MICHEL
- ST-AMANT-DE-BXE-LOTISSEMENT RD18
- GOND-PONTOUVRE-CHALONNE RD737
- BALZAC-LES GENINS VC AB maison 49
- BALZAC-MAIRIE RD406 Place
- BALZAC-LE RENFERME RD737 AB n°23
- ST-AMANT-DE-BXE-COLLEGE
- VARS- COOPERATIVE AB RD11
- LIGNE-PLACE Mairie RD61 A.Bus
- COURCOME-PLACE RD736 Dég.goudron
- VERVANT-EGLISE VC A.Bus n°128
- VILLEJESUS-EGLISE RD739 A.B n°132
- VARS-BASCULE
- XAMBES-MAIRIE RD32 A.Bus n°135
- FOUQUEURE-MNT AUX MORTS RD739
- VERVANT-CHOUGNAT RD32 A.Bus
- LA CHAPELLE-LE FOUILLOUX RD118
- COULONGES-carf VC A.Bus
- CHARME-POSTE RD736
- LA CHAPELLE-MAIRIE carf RD737/VC
- AIGRE-PLACE des Sept Portes
- VOUHARTE-PLACE RD737 A.Bus 1/2t
- BALZAC-LES ROCHIERS VC maison 59
- AIGRE-PLACE DE LA POSTE
- ST-AMANT-DE-BXE-RUE DES ECOLES
- LA CHAPELLE -MAIRIE Mt aux MORTS
- MONTIGNAC-LE PLANTIER
- VILLEJESUS-BASLEVILLE RD739 A.Bus
- BALZAC-PLACE Liberté AB corresp.
- VILLEJESUS-LE REDOUR VC AB n°133
- MONTIGNAC-Av.Marg.Valois RD737
- BALZAC-LES ESSARDS VC maison 14
- BALZAC-LES LABBES RD737 ABus n°22
- ST-AMANT-DE-BXE-LA DOUE RD18 n°61
- VILLEJESUS-LA CHAUSSEE RD736
- RUFFEC-SALLE DES GRANDS ROCS
- VOUHARTE-PLACE AB N°134
- ST-AMANT-DE-BXE-LA STATION cf D15
- CHAMPNIERS-VOUILLAC carf VC n°195
- BALZAC-PEUSEC VC A.Bus
- VARS-LE PORTAL carf VC/RD11 A.Bus
- ST-AMANT-DE-BXE-ECOLE VC
- CHAMPNIERS-PRE DES CHAMBAUDS VC
- CHAMPMILLON-PLACE de la MAIRIE AB
- SIREUIL-CHEVILLE carf RD53/VC AB
- CHATEAUNEUF-CHATEAUNEUF HLM J.MOU
- SIREUIL-LE BRANDEAU carf RD53/VC
- SIREUIL-LES PATUREAUX cf RD53/VC
- SIREUIL-LES VIGNES DES BOIS RD53
- SIREUIL-LES TANNERIES RD7
- SIREUIL-MAIRIE RD7 Entrée parking
- TROIS-PALIS-RTE DE SIREUIL D53 AB
- TROIS-PALIS-PUYBERTIER cf VC A.B
- CHATEAUNEUF-EGLISE VC A.Bus
- TROIS-PALIS-LES ALLINS 30m cf VC
- TROIS-PALIS-BELLE VALLEE RD72 AB
- SIREUIL-BOIS DE LA ROCHE carf RD
- SIREUIL-LA MALESTRADE PARKING
- CHATEAUNEUF-POLE MULTIMODAL 1/2t
- ANGOULEME- SILLAC
- ST-SIMEUX-PLACE du Port RD84 ABus
- SIREUIL-L'ANGLE cf D699/7 maison4
- CHATEAUNEUF-LA GANACHERIE cf D699
- MOSNAC-MAIRIE RD423
- ANGOULEME-RTE DE BORDEAUX (STGA)
- SIREUIL-LA VALLADE RD7 AB n°103
- CHATEAUNEUF-CHEZ PETILLON RD14 AB
- TROIS-PALIS-MAIRIE RD72 A.B n°123
- BARBEZIEUX-PISCINE VC Encoche AB
- JONZAC - Gare SNCF
- ROULLET-LES AUBREAUX RD910 A.Bus
- JURIGNAC-PLACE VC A.Bus 1/2t
- BARBEZIEUX-LA MIRANDOLE RD917
- LE TATRE-LA TAPE carf RD14/VC
- BARBEZIEUX-CHAT PENDU RD917
- BAIGNES-CHAMP DE FOIRE
- TOUVERAC-LA LANDE carf RD14/VC
- NONAVILLE-PONT A BRAC RD916 A.Bus
- LE TATRE-LA NOVETTE carf RD14/VC
- REIGNAC-CIMETIERE RD14 Place AB
- JURIGNAC-PETIGNAC Dne Musical VC
- ROULLET-EGLISE RD210 Poteau
- ROULLET-ECOLE RD210 A.Bus n°99
- ROULLET-LE FOUR A CHAUX RD910 AB
- BARBEZIEUX-ENSEMBLE SAINTE-MARIE
- BARBEZIEUX-COLLEGE JEAN MOULIN
- BARDENAC-RD731 Encoche
- CONDEON-EGLISE RD731
- CONDEON-LA FENETRE carf VC
- REIGNAC-LE CASSIS VC maison 151
- REIGNAC-LE CHAMP DE LA VILLE D731
- CHALAIS-GARE SNCF VC Poteau
- BERNEUIL-GRANGE carf RD128/VC
- PASSIRAC-LA PETITE GARE VC A.Bus
- BROSSAC-BROSSAC GARE AB n°27
- BERNEUIL-PLACE des Tilleuls RD68
- BERNEUIL-CHEZ MOREAU carf RD68/VC
- CONDEON-Lot.LA TORTE carf VC
- ROULLET-LES GUESDONS carf VC AB
- CLAIX-LES GROIES DE CHARDY RD7 AB
- CHAMPAGNE-VIGNY-MAIRIE RD7 A.Bus
- BLANZAC-COLLEGE ALFRED DE VIGNY
- PEREUIL-PLACE des VIEUX CHAIS AB
- ANGEDUC-CALVAIRE carf VC
- VOULGEZAC-LA VIERGE carf VC/RD12
- MOUTHIERS-LE ROSIER carf VC A.Bus
- MOUTHIERS-CHENEAU VC A.Bus
- VOEUIL-EGLISE RD674 Poteau LR
- VOULGEZAC-PLACE carf VC/D436 1/2t
- MOUTHIERS-LES GRASSETS cf VC/ VC
- VOEUIL-BOURISSON RD674 A.Bus
- PEREUIL-PEREUIL Ancienne gare RD5
- VOEUIL-PETIT GIGET RD674 A.Bus
- and 688 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — up 8.1 since 2026-08-30.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 68.6 | first check |
| 2026-08-07 | 68.6 | no change |
| 2026-08-30 | 47.3 | down 21.3 |
| 2026-08-31 | 55.4 | up 8.1 |
What changed since your last check
- Correctness up 2.0
- Freshness no change
- Rider experience up 23.0
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-08-30 the grade moved from D to F. As of 2026-08-31 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-31 Score rose 8 points, rider experience rose 23 points.
- 2026-08-30 Grade went D to F, correctness fell 32 points.
Everything we checked
18 findings, ordered by severity.
Show every finding
- Error16 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 (opens the validator rules on an external site)
- Warning536 instances
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 (opens the validator rules on an external site)
- Warning228 instances
228 of 228 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 (opens the GTFS Schedule reference on an external site)
- Warning77 instances
77 of 938 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 (opens the GTFS Schedule reference on an external site)
- Warning25 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning22 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Between two distant stops, the times imply a speed no bus reaches.
A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.
Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · 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 · 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info303 instances
About 303 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info228 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)
- Info46 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 (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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 92% 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 362 days.
- Accessible Not yet
- States wheelchair access on 92% 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 361 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 16 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 38 / 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 56 / 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.
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-82324/2026-08-31.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-08-31. 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.