Feed status · checked 2026-09-06
Réseau interurbain Fluo Grand Est - Aube
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-05
Catalogued in Grand-Est, France.
Heads-up: The score rose 25 points in one step, from 24 on 2026-08-10 to 49 on 2026-09-01. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-09-01). 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 1 days ago; last changed 4 days 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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
157 of 157 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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
133 of 133 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
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
- 157 of 157 stops don't say whether a wheelchair user can board there.
- Next action
- 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.
Copy handoff text
- Feed evidence
- 133 of 133 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
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. See this feed's finding-clearance log.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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. See this feed's finding-clearance log.
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. 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 297 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
- 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 9 kinds of issue across 492 instances (6 error, 451 warning, 35 informational).
Service data covers the next 297 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
32 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("CRANCEY - ABRI RD619", "CRANCEY - ABRI RD619", "MAIZIERES-LA-GRANDE-PAROISSE - MAIZ. GDE PAR-BUREAU TABAC/RD619", 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 157 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.
- 258 (pink)
- 256 (pink)
- 257 (pink)
- 259 (white)
- 250 (pink)
- 251 (pink)
- 252 (pink)
- 253 (pink)
- 260 (pink)
- 261 (pink)
- 262 (pink)
- 254 (pink)
- 255 (pink)
| Route | Type | Line color |
|---|---|---|
| 258 BRIENNE-LE-CHATEAU / TROYES | Bus | pink |
| 256 BAR-SUR-SEINE / TROYES | Bus | pink |
| 257 CHATILLON-SUR-SEINE / BAR-SUR-SEINE | Bus | pink |
| 259 CHAOURCE-TROYES | Bus | white |
| 250 AIX-EN-OTHE / TROYES | Bus | pink |
| 251 MAILLY-LE-CAMP / TROYES | Bus | pink |
| 252 BAR-SUR-AUBE / TROYES | Bus | pink |
| 253 VILLE-SOUS-LA-FERTE / BAR-SUR-AUBE | Bus | pink |
| 260 ROMILLY-SUR-SEINE / TROYES | Bus | pink |
| 261 NOGENT-SUR-SEINE / ROMILLY-SUR-SEINE | Bus | pink |
| 262 PROVINS / NOGENT-SUR-SEINE | Bus | pink |
| 254 VENDEUVRE-SUR-BARSE / DIENVILLE | Bus | pink |
| 255 TROYES / NIGLOLAND | Bus | pink |
List every stop
- CHAOURCE - CENTRE
- BAR-SUR-SEINE - RD671 CIMETIERE
- LUSIGNY-SUR-BARSE - MAIRIE ECOLE
- VILLE-SOUS-LA-FERTE - FORGES PLACE
- PAISY-COSDON - TERRES BLANCHES
- MESNIL-SAINT-PERE - MAISON DES LACS
- LA RIVIERE-DE-CORPS - MALADIERE (TCAT)
- PONT-SAINTE-MARIE - DEBUSSY(TCAT)
- GERAUDOT - PLAGE
- DOLANCOURT - NIGLOLAND
- CHATILLON-SUR-SEINE - C. COMMERCIAL
- ROMILLY-SUR-SEINE - CENTRE COMMERCIAL
- MAILLY-LE-CAMP - GARAGE
- MERY-SUR-SEINE - HOTEL DE VILLE
- MESGRIGNY - MAIRIE
- NEUVILLE-SUR-SEINE - MAIRIE ECOLE
- PINEY - DERRIERE MAIRIE
- PLAINES-SAINT-LANGE - RD671 MAIRIE
- POLISOT - GARE SNCF
- ROMILLY-SUR-SEINE - GARE
- BAYEL - POSTE
- SAINT-HILAIRE-SOUS-ROMILLY - RD619
- SAINT-MESMIN - MONUMENT
- SAINT-PARRES-AUX-TERTRES - CENTRE COMMERCIAL
- SAINT-PARRES-LES-VAUDES - RD671 PLACE
- SAVIERES - RUE ST GILLES
- SAVIERES - ARBRE DE LA LIBERTE
- TROYES - GARE SNCF
- TROYES - THEATRE
- TROYES - EUROPE (TCAT)
- TROYES - HOPITAL H.CLOS(TCAT)
- TROYES - LYCEE DES LOMBARDS
- VALLANT-SAINT-GEORGES - MAIRIE
- VAUDES - MAIRIE/ECOLE
- AIX-VILLEMAUR-PALIS - MAIRIE RD660
- VILLE-SOUS-LA-FERTE - RUE TRAMWAY
- VIREY-SOUS-BAR - PONT RD671
- VOUE - MAIRIE
- BAR-SUR-AUBE - COL BACHELARD
- BAR-SUR-AUBE - HOTEL DE VILLE
- BAR-SUR-SEINE - COLLEGE PORTIER
- AIX-VILLEMAUR-PALIS - PLACE MAIRIE
- CHATILLON-SUR-SEINE - FORGEOTTE(CES)
- ESTISSAC - LA POSTE
- BAR-SUR-AUBE - GARE SNCF
- VENDEUVRE-SUR-BARSE - GARE SNCF
- NOGENT-SUR-SEINE - GARE
- VILLE-SOUS-LA-FERTE - CLAIRVAUX-M.ANNEXE
- CLEREY - ABRI RD671
- MUSSY-SUR-SEINE - CENTRE VILLE
- CHAOURCE - BRUYERES HAUT
- LA VILLENEUVE-AU-CHENE - MAIRIE
- LA VILLENEUVE-AU-CHENE - ABRI RD619
- BREVONNES - POSTE
- BRIENNE-LE-CHATEAU - PLACE HALLE
- CHATRES - SALLE POLYVALENTE
- ARSONVAL - MAIRIE
- CRANCEY - ABRI RD619
- FONTVANNES - PLACE DE GAULLE
- FOUCHERES - FBG DE CHAMPAGNE
- GYE-SUR-SEINE - RD971 POMPIERS
- LESMONT - HALLE
- LUSIGNY-SUR-BARSE - FACE AU CAFE
- MAGNY-FOUCHARD - PLACE
- MAGNY-FOUCHARD - RD619
- MAIZIERES-LA-GRANDE-PAROISSE - MAIZ. GDE PAR-BUREAU TABAC/RD619
- ARCIS-SUR-AUBE - RUE DE CHALONS
- TROYES - GARE ROUTIERE
- MAILLY-LE-CAMP - CAMP MILITAIRE
- ROMILLY-SUR-SEINE - HOPITAL
- SAINTE-SAVINE - BRUXELLES
- SAINTE-SAVINE - CHURCHILL
- NOGENT-SUR-SEINE - THEATRE
- PONT-SUR-SEINE - PLACE ST MARTIN
- PROVINS - GARE
- AUBETERRE - RD677
- FEUGES - RD677
- DIENVILLE - PLAGE
- PINEY - MAISON DU PARC
- Hôpital
- Gare de Provins
- BAR-SUR-SEINE - COLLEGE PORTIER
- VIREY-SOUS-BAR - PONT RD671
- MALADIERE
- CHATILLON-SUR-SEINE - FORGEOTTE(CES)
- Camp Militaire
- AIX-VILLEMAUR-PALIS - PLACE MAIRIE
- ESTISSAC - LA POSTE
- PAISY-COSDON - TERRES BLANCHES
- RUE DE CHALONS
- Magny-Fouchard
- GARAGE
- SAINT-PARRES-AUX-TERTRES - CENTRE COMMERCIAL
- ABRI RD619
- GYE-SUR-SEINE - RD971 POMPIERS
- LESMONT - HALLE
- MUSSY-SUR-SEINE - CENTRE VILLE
- NEUVILLE-SUR-SEINE - MAIRIE ECOLE
- PINEY - DERRIERE MAIRIE
- PLAINES-SAINT-LANGE - RD671 MAIRIE
- POLISOT - GARE SNCF
- CHATILLON-SUR-SEINE - C. COMMERCIAL
- Nogent-sur-Seine
- BRUXELLES
- ARSONVAL - MAIRIE
- CHURCHILL
- DOLANCOURT - NIGLOLAND
- GERAUDOT - PLAGE
- MESNIL-SAINT-PERE - MAISON DES LACS
- AIX-VILLEMAUR-PALIS - MAIRIE RD660
- AUBETERRE - RD677
- BAR-SUR-AUBE - COL BACHELARD
- BREVONNES - POSTE
- BRIENNE-LE-CHATEAU - PLACE HALLE
- CHAOURCE - BRUYERES HAUT
- CHAOURCE - CENTRE
- DIENVILLE - PLAGE
- FEUGES - RD677
- FONTVANNES - PLACE DE GAULLE
- PINEY - MAISON DU PARC
- ROMILLY-SUR-SEINE - CENTRE COMMERCIAL
- TROYES - GARE ROUTIERE
- VALLANT-SAINT-GEORGES - MAIRIE
- VAUDES - MAIRIE/ECOLE
- LA VILLENEUVE-AU-CHENE - MAIRIE
- VILLE-SOUS-LA-FERTE - FORGES PLACE
- VILLE-SOUS-LA-FERTE - RUE TRAMWAY
- HOPITAL SIMONE VEIL
- Théâtre De Champagne
- EUROPE
- DEBUSSY
- Gare de Troyes
- Gare de Bar-sur-Aube Hôtel de Ville
- BAYEL - POSTE
- FACE AU CAFE
- Bar-sur-Aube
- CHATRES - SALLE POLYVALENTE
- CRANCEY - ABRI RD619
- MAIZIERES-LA-GRANDE-PAROISSE - MAIZ. GDE PAR-BUREAU TABAC/RD619
- MERY-SUR-SEINE - HOTEL DE VILLE
- MESGRIGNY - MAIRIE
- Théâtre
- PONT-SUR-SEINE - PLACE ST MARTIN
- Gare de Romilly-sur-Seine
- Saint-Hilaire-sous-Romilly
- SAINT-MESMIN - MONUMENT
- SAVIERES - ARBRE DE LA LIBERTE
- SAVIERES - RUE ST GILLES
- BAR-SUR-SEINE - RD671 CIMETIERE
- CLEREY - ABRI RD671
- FOUCHERES - FBG DE CHAMPAGNE
- Centre
- SAINT-PARRES-LES-VAUDES - RD671 PLACE
- MARNE
- Gare de Vendeuvre-sur-Barse
- VILLE-SOUS-LA-FERTE - Clairvaux
- MAIRIE
Over time
Overall score across the last 6 checks — unchanged since 2026-09-05.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 25.2 | first check |
| 2026-08-07 | 24.7 | down 0.5 |
| 2026-08-10 | 23.5 | down 1.2 |
| 2026-09-01 | 48.8 | up 25.3 |
| 2026-09-05 | 48.8 | no change |
| 2026-09-06 | 48.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-09-05.
Same feed file as 2026-09-05; the published zip did not change.
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-08-06 this feed started at grade F. On 2026-09-01 feed renewed to a current calendar. On 2026-09-05 the check no longer reported: this feed's service calendar runs out within the next 30 days; some values have extra spaces at the start or end; some route long names repeat the route's short name inside them; route short name too long (flagged by the MobilityData validator); service data runs out in 23 day(s). As of 2026-09-06 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-09-01 Feed renewed to a current calendar.
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error6 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)
- Warning280 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)
- Warning157 instances
157 of 157 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)
- Warning133 instances
133 of 133 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)
- Warning58 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 (opens the validator rules on an external site)
- Warning55 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning40 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 (opens the validator rules on an external site)
- Warning13 instances
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 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)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · 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)
- Info142 instances
About 142 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)
- Info35 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 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 297 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 297 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 6 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 37 / 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 100 / 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 24 / 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/fluo-grand-est-aube/2026-09-06.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-06. 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.