Feed status · checked 2026-09-01
Réseau urbain TeMo'b
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Grand-Est, France.
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
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
1551 of 1579 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
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
Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.
13 of 49 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 +11 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
- 1551 of 1579 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
- The feed contains no fare information.
- Next action
- 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.
- 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
- 13 of 49 trips scheduled during the sampling window had no live predictions.
- Next action
- Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.
- 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.
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. Self-check a feed before you publish.
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.
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.
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 1.8% 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
- Live-arrival data covered 73.5% 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
The MobilityData validator flagged 9 kinds of issue across 6241 instances (0 error, 6228 warning, 13 informational).
Service data covers the next 362 days.
2% of stops state wheelchair accessibility (2% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
2% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
44 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (33, 52, 53, 34, 35, 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.
142 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("CHAPELLE ST HUBERT", "Chapelle St Laurent", "Chapelle St Hubert", 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.
Sampled 3 times: 1 of 1 configured feed healthy; 73.5% of scheduled trips had live predictions; predictions ran a median of 214s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 1579 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.
- 106 (red)
- 108 (green)
- 110 (teal)
- 30 (teal)
- 31 (blue)
- 33 (teal)
- 34 (gray)
- 35 (white)
- 36 (white)
- 38 (white)
- 40 (green)
- 41 (green)
- 42 (green)
- 43 (gray)
- 44 (gray)
- 45A (white)
- 45B (white)
- 46 (white)
- 47 (white)
- 48 (white)
- 49 (green)
- 51 (orange)
- 52 (orange)
- 53 (yellow)
- 54 (yellow)
- 60 (yellow)
- 61 (white)
- 62 (yellow)
- 70 (gray)
- 71 (gray)
- D25 (teal)
- D26 (gray)
- N60 (yellow)
- N90 (red)
- N91 (teal)
- S01 (pink)
- S02 (gray)
- S03 (teal)
- S04 (brown)
- S05 (pink)
- S06 (yellow)
- S07 (purple)
- S08 (white)
- S09 (white)
- S10 (gray)
- S11 (white)
- S12 (blue)
- S13 (pink)
- S14 (teal)
- S20 (pink)
- S22 (yellow)
- S23 (yellow)
- S24 (brown)
| Route | Type | Line color |
|---|---|---|
| 106 BEYREN LES SIERCK <-> THIONVILLE | Bus | red |
| 108 BASSE RENTGEN <-> THIONVILLE | Bus | green |
| 110 MONDORFF <-> THIONVILLE | Bus | teal |
| 30 KUNTZIG Gare <-> THIONVILLE Foch | Bus | teal |
| 31 LOMMERANGE Cimetiere <-> FONTOY Super U | Bus | blue |
| 33 ANGEVILLERS Place <-> FONTOY College | Bus | teal |
| 34 ROCHONVILLERS Centre <-> HAYANGE Hurlevent | Bus | gray |
| 35 OEUTRANGE St Luc <-> THIONVILLE Galiéni | Bus | white |
| 36 MANOM Place <-> HAYANGE L.E.P Maryse Bastié | Bus | white |
| 38 BASSE HAM Golf <-> YUTZ Arc en Ciel | Bus | white |
| 40 BOULANGE Silo <-> THIONVILLE Foch | Bus | green |
| 41 HAYANGE Esplanade <-> THIONVILLE Maillet | Bus | green |
| 42 HAYANGE Esplanade <-> FAMECK Zone Artisanale | Bus | green |
| 43 BERTRANGE Carrefour <-> HAYANGE Maryse Bastié | Bus | gray |
| 44 NEUFCHEF Pharmacie <-> FAMECK Zone Artisanale | Bus | gray |
| 45A HAYANGE Esplanade <-> KONACKER College via Marspic | Bus | white |
| 45B HAYANGE Esplanade <-> KONACKER College via Marspic | Bus | white |
| 46 NILVANGE Aristide Briand <-> KONACKER College | Bus | white |
| 47 ALGRANGE - THIONVILLE Foch | Bus | white |
| 48 FONTOY College -> FAMECK Lycée | Bus | white |
| 49 KONACKER Stand <-> FAMECK Lycée | Bus | green |
| 51 THIONVILLE Foch <-> OTTANGE Cité St Paul | Bus | orange |
| 52 BOULANGE Cité du Bois <-> HAYANGE Hurlevent | Bus | orange |
| 53 OTTANGE Cité St Paul - FONTOY College | Bus | yellow |
| 54 BOULANGE Croix <-> FAMECK Lycée St exupéry | Bus | yellow |
| 60 UCKANGE Rue d'Hayange Gare <-> THIONVILLE Bel Air | Bus | yellow |
| 61 FAMECK Mermoz <-> THIONVILLE Sécurité Sociale | Bus | white |
| 62 UCKANGE Gare <-> THIONVILLE Foch | Bus | yellow |
| 70 FAMECK Budange <-> FLORANGE Moulin Daspich | Bus | gray |
| 71 FAMECK Budange<-> ANGEVILLERS Place | Bus | gray |
| D25 HAYANGE Esplanade <-> YUTZ Aéroparc | Bus | teal |
| D26 METZANGE P+R <-> YUTZ Arc en Ciel | Bus | gray |
| N60 Uckange Rue d'Hayange <-> Bertrange Transformateur | Bus | yellow |
| N90 HAYANGE Esplanade <-> St Nicolas en foret | Bus | red |
| N91 HAYANGE Esplanade <-> NEUFCHEF Terminal | Bus | teal |
| S01 THIONVILLE Linkling 3 - YUTZ Aéroparc | Bus | pink |
| S02 THIONVILLE Gare <-> THIONVILLE Bel Air | Bus | gray |
| S03 UCKANGE Gare SNCF <-> FLORANGE Moulin Daspich | Bus | teal |
| S04 ALGRANGE Terminus <-> FAMECK Feltiere | Bus | brown |
| S05 FONTOY Super U <-> HAYANGE Hôpital | Bus | pink |
| S06 THIONVILLE Foch <-> STUCKANGE Liberté | Bus | yellow |
| S07 UCKANGE Rte de Metz <-> FLORANGE Vieilles Vignes | Bus | purple |
| S08 CATTENOM Sentzich <-> ELANGE Ruisseau | Bus | white |
| S09 THIONVILLE Foch <-> GUENANGE Village | Bus | white |
| S10 VOLMERANGE Douane <-> THIONVILLE Foch | Bus | gray |
| S11 OEUTRANGE St Luc <-> THIONVILLE Foch | Bus | white |
| S12 THIONVILLE Foch <-> MANOM Pommiers | Bus | blue |
| S13 THIONVILLE Foch <-> TERVILLE St Jean | Bus | pink |
| S14 FLORANGE Moulin Daspich <-> THIONVILLE Bel Air | Bus | teal |
| S20 HAYANGE Esplanade <-> THIONVILLE Gare SNCF | Bus | pink |
| S22 HAYANGE Esplanade - THIONVILLE Foch (via KONACKER) | Bus | yellow |
| S23 HAYANGE Esplanade <-> THIONVILLE Foch | Bus | yellow |
| S24 YUTZ Aéroparc <-> THIONVILLE Foch | Bus | brown |
List every stop
- Beauregard
- Luxembourg
- Gallieni
- Banque de France
- Beauregard
- Château d'eau - Thionville
- Cité Jeanne d'Arc
- Rue Basse - Terville
- Cimetiere - Terville
- Acacias
- Moulin Daspich
- Daspich
- Charlemagne
- Bétange
- Eglise Ste Agathe
- Grand rue - Florange
- Centrale
- Verdun - Florange
- Ponts
- Suzange
- Fenderie
- Bureau Central
- Hôpital - Hayange
- Station Foch
- Ste Berthe
- St Jacques
- Route de Nilvange
- Eglise St Charles
- Place des Fetes
- Viaduc
- Mine d'Havange
- Stade Ste Genevieve
- Bâtiment Y
- Carl Lueg
- Haut Pont
- Moulin Brulé
- Brasserie - Fontoy
- Rue de Moulin
- Place des fetes
- Eglise - Fontoy
- College Marie Curie
- Pont SNCF
- Portier Bas
- Portier Haut
- Poincaré
- Eglise St jean Baptiste
- Centre - Algrange
- Mairie - ALgrange
- Hôpital - Algrange
- Mine d'Angevillers
- CIté des mines
- Stade du Batzenthal
- Abeilles
- Pyramides
- Piscine - Thionville
- Pic-Vert
- Bossuet
- Bel Air
- Creve Coeur
- Guentrange Ecole
- Sécurité Sociale
- Epis d'Or
- Pharmacie - Thionville
- Clémenceau - Thionville
- Porte Saarlouis
- Jean Jaures
- Emile Zola
- Aragon
- St Vitus
- Beethoven - Yutz
- Henri Dunant
- Rocade
- Ancien Cimetiere
- Rue du 13 Novembre
- Cité - Yutz
- Nations 143
- Place Schuman
- Nieppe
- Résidences du Golf
- Pinsons
- Fauvettes
- Rue du Fort
- Foret N°19
- Château d'eau - Basse Ham
- St Louis
- Gabriel Lippmann
- Ecluse Sud
- Paul Albert
- Clinique Notre Dame
- Roosevelt
- Pasteur - Yutz
- Vieux Bourg
- Pépiniere
- Route de Kuntzig
- Chalets
- Printemps
- Maginot
- Foyer Amli
- Cité St Paul
- Bouleau
- Le Kem
- St Jean - Terville
- Romains - Florange
- Ebange Eglise
- Ebange rue d'Uckange
- Moulin St Pierre
- Route d'Ebange
- Brasserie - Uckange
- Berry
- Pont de Pierre
- Weimerskirch
- Lucie Aubrac
- Afrique
- Fabert
- Gare SNCF - Florange
- Rue de la Gare
- Lorraine - Florange
- Place d'Harling
- Oury Nord
- Oury Sud
- 4 Routes
- Place du marché
- Château
- Strasbourg
- Nancy
- Metz
- Leclerc - Fameck
- Zone Artisnale - Fameck
- Bouvreuils
- Cimetiere - Fameck
- Centre - Fameck
- Edange
- 3 Vallées
- Funiculaire
- Budange
- Mermoz
- Sous Préfecture
- Centre - Kuntzig
- Lobélies
- Rue du Stade
- Cézanne
- Europe
- Square Schwartz
- Comte de Bertier
- La Malgrange
- Maison Rouge
- Tilleuls - Hettange Grande
- Cité des Jardins
- Carrefour d'Oeutrange
- Michelet
- De Gaulle - Hettange Grande
- Cité Soetrich
- Juge de Paix
- Sud
- Centre - Entrange
- Cité - Entrange
- De Gaulle - Kanfen
- Rue de Volmerange
- Stade de Basse Ham
- Liberté - Volmerange
- Route de Molvange
- Molvange
- Mine - Volmerange
- Place Roland
- Laminoirs
- Tilleuls - Manom
- Boulangerie
- Cimetiere - Marspich
- Meilbourg
- La Biche
- Kiesel
- Prieur
- Route de Mondorff
- Chenaie
- Rue Basse - Koeking
- Ambroise Paré
- Route de Guentrange
- Rue du Canal
- Domaine de la foret
- Grand Chenes
- St Martin
- Stade du Buchel
- Ferme
- Metzange Ferme
- St Jean Baptiste
- Seigneurie
- Castors - Volkrange
- Route de Volkrange
- Miniere
- Lavoir
- Mendes France
- Pompiers
- Zone Artisanale - Hayange
- Gare SNCF - Hayange
- Parc Public
- Godron
- Syracus
- Mine d'Hayange
- Cité Gargan
- Ste Neige
- Pharmacie - Neufchef
- Rue d'Hayange
- Eglise St Denis
- De Gaulle (Provisoire)
- Temple - Nilvange
- Pharmacie - Nilvange
- Place des fetes - Nilvange
- Places des fetes - Konacker
- St Jean - Konacker
- Yves Farges
- Stand
- St Fiacre
- Jules Ferry
- Clemenceau - Hayange
- Théophile Maire
- Cité des Grans Bois
- Lot. Grands Bois
- Toul
- Seine
- Mairie - St Nicolas
- Place Ranguevaux
- Métropole
- Terrasse
- Médiatheque
- Rue d'Hayange Gare
- Petite Fontaine
- St Hubert
- St Nicolas
- Cimetiere - Serémange
- Le réveil
- Jeanne d'Arc
- Droguerie
- Pelerin
- Breckels
- Morlange Lavoir
- Morlange 66
- Morlange 34
- République - Ranguevaux
- Lerclerc - Nilvange
- Lyautez
- Lorraine - Nilvange
- Hôtel de ville
- Jean Burger
- Stade Lucien Noirot
- Clemenceau - Nilvange
- Café des Pecheurs
- Gassion
- Maisons Neuves
- U4
- Route de Metz
- and 1329 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
15 findings, ordered by severity.
Show every finding
- Warning4212 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)
- Warning1692 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)
- Warning1551 instances
1551 of 1579 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)
- Warning239 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)
- Warning60 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)
- Warning21 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)
- Warning13 instances
13 of 49 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 (opens the GTFS-Realtime reference on an external site)
- Warning3 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.)
Finding code: expired_calendar · 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)
- Info377 instances
About 377 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)
- Info12 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
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 2% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 362 days.
- Accessible Not yet
- States wheelchair access on 2% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Realtime reliability
The realtime feed responded on 100.0% of 4 checks over the last 1 day, with 60s 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 214s late versus the schedule, and stayed within 560s nine times in ten. They were on time (about a minute early to five late) 66.6% 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 362 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 53 / 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 49 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 89 / 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.
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-80459/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.