Feed status · checked 2026-07-18
Réseau Stan (Nancy)
Based on the feed this agency publishes
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.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
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
1464 of 1465 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
75487 of 75487 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 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
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.
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 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.
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 166 days.
- Published accessibility data
- Accessibility information is stated for 0.1% 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 62400 instances (0 error, 62384 warning, 16 informational).
Service data covers the next 166 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (14exp, 16, T3, 22, 55, 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- T1 (red)
- 11 (orange)
- 12 (yellow)
- 13 (green)
- 15 (gray)
- 16 (teal)
- 17 (teal)
- T2 (teal)
- 20 (purple)
- 21 (purple)
- 22 (pink)
- T3 (green)
- 30 (pink)
- 32 (yellow)
- 33 (yellow)
- 39 (pink)
- T4 (yellow)
- CITADINE 1 (teal)
- CITADINE 2 (teal)
- PLEINE LUNE (yellow)
- 50 (blue)
- 51 (teal)
- 52 (green)
- 53 (yellow)
- 54 (pink)
- 55 (red)
- 56 (gray)
- 57 (green)
- 58 (teal)
- 59 (black)
- 60 (teal)
- 61 (purple)
- 62 (pink)
- 63 (yellow)
- 64 (orange)
- 66 (green)
- 67 (pink)
- Corol (brown)
| Route | Type | Line color |
|---|---|---|
| T1 Tempo 1 | Bus | red |
| 11 Artem <> Saulxures Lorraine | Bus | orange |
| 12 Heillecourt <> Malzéville Savlons | Bus | yellow |
| 13 Maxéville EcoParc <> Dommartemont | Bus | green |
| 14exp Express - Ludres <> Nancy Gare | Bus | green (no shape in feed) |
| 15 Seichamps Ecoquartier<> Nancy Gare | Bus | gray |
| 16 Villers Clairlieu <> Malzéville | Bus | teal |
| 17 Villers Campus <> Ludres | Bus | teal |
| T2 Tempo 2 - Laxou Sapiniere <> Laneuveville Centre | Bus | teal |
| 20 Art-sur-Meurthe <> Nancy Gare | Bus | purple |
| 21 Ludres/Fléville <> Nancy Gare | Bus | purple |
| 22 Saint Max Gérard Barrois <> Porte Verte | Bus | pink |
| T3 Tempo 3 - Villers Campus <> Seichamps Haie Cerlin | Bus | green |
| 30 Laneuveville Gare <> Villers Campus | Bus | pink |
| 32 Nancy Jean Lamour <>Gérard Barrois | Bus | yellow |
| 33 Vandoeuvre Parc des Exposition <> Nancy Gare | Bus | yellow |
| 39 Navette Foire Exposition | Bus | pink |
| T4 Tempo 4 - Laxou CLB <> Houdemont Porte Sud | Bus | yellow |
| CITADINE 1 Citadine 1 - Citadine Nancy | Bus | teal |
| CITADINE 2 Citadine 2 - Citadine Vandoeuvre | Bus | teal |
| PLEINE LUNE Ligne Pleine Lune | Bus | yellow |
| T5 Maxeville Meurthe Canal - Vandoeuvre Roberval | Bus | purple (no shape in feed) |
| 50 Jarville Sion <> Ludres | Bus | blue |
| 51 Villers Clairlieu <> Villers Lycée Stanislas | Bus | teal |
| 52 Villers G. Chepfer <> Villers Lycée Stanislas | Bus | green |
| 53 Malzéville le Nid <> Malzéville Paul Verlaine | Bus | yellow |
| 54 Dommartemont Nickles <> Malzéville Verlaine | Bus | pink |
| 55 Jarville Léon Songeur <> Heillecourt Montaigu | Bus | red |
| 56 Fléville <> Jarville Sion | Bus | gray |
| 57 Vandoeuvre Simone de Beauvoir <> Vélodrome | Bus | green |
| 58 Dommartemont Nickles <> Tomblaine Grp ScolR | Bus | teal |
| 59 Tomblaine Groupe Scolaire <> Saulxures Foret | Bus | black |
| 60 Tomblaine Groupe Scolaire <> Art-sur-Meurthe | Bus | teal |
| 61 Nancy Gare <> Art-sur-Meurthe - Bosserville | Bus | purple |
| 62 Nancy Gare <> Malzéville Pixerécourt | Bus | pink |
| 63 Laxou Jet d'eau <> Laxou V. Prouvé | Bus | yellow |
| 64 Nancy Tilleul Argenté <> Georges de la Tour | Bus | orange |
| 65 Malzéville Margeville <>Nancy Division de Fer | Bus | purple (no shape in feed) |
| 66 Villers Lycée Stanislas <> Fléville | Bus | green |
| 67 Ludres J. Monod <> Fléville l'Orée du Bois | Bus | pink |
| Corol Corol - Lx Plateau de Haye<>Lx Plateau de haye | Bus | brown |
This feed has 1465 stops.
List every stop
- Gare de Laneuveville-devant-Nancy
- Belle Croix
- Le Royal - Jean XXIII
- Château de Montaigu
- Saint-Julien
- Europeen
- Sadi Carnot
- Giron
- Charles Gide
- Didelot
- Bois Châtel
- Chanoine Laurent
- Edith Piaf
- Emile Gallé
- Essey La Fallée
- Essey Mairie
- Oppidum
- Tronc qui fume
- Château
- Fléville
- L'Orée du Bois
- Port Cros
- Temps Libre
- Les Egrez
- Houdemont Porte Sud
- Sion
- le Féru des sciences
- Gérardcourt
- Les Aulnois
- Croix Saint-Claude
- Heubach
- Jet d'eau
- Madine
- Ader
- Curie
- Freres Lumiere
- Genobois
- J. Monod
- Saint-Blaine
- Driant
- Ecole Paul Bert
- Grosses Terres
- Malzéville Mairie
- Orme
- Passerelle
- André Vautrin
- Bon Repos
- Zénith
- Beauregard Sainte-Anne
- Brice
- Chevert
- Citadelle
- Colline
- Exelmans
- Gentilly
- Gridel
- Musée Lorrain
- Oudinot
- Place des Justes
- Place Stanislas
- Sainte-Catherine
- Collège Goncourt
- Lebrun
- Pont de Pierre
- Saulxures Lorraine
- Ecoquartier
- Seichamps Haie Cerlin
- Les Bijoins
- Renoir
- Crévic
- Doyen Roubault
- Fribourg
- Hôtel de Ville
- Myosotis
- Rotterdam
- Sud Europe
- Vandoeuvre Palissy
- Asnée
- Castelnau
- Haut de la Taye
- Joseph Laurent
- Lycée Stanislas
- Monument
- Villers Stade
- Amsterdam
- Sainte-Valdrée
- Jean Moulin
- Bosserville
- Courbet
- Cimetière du Sud
- Jarville Gabriel Fauré
- Essey Emile Gallé
- ARTEM
- Patton
- Villers Campus Sciences
- Mere Teresa
- Vandoeuvre Brabois - H.
- Porte Verte
- Bergé
- Cyfflé
- Gérard Barrois
- Art-sur-Meurthe
- Cartonneries
- Flaubert
- Laneuveville Centre
- Brasseries
- Lavoir
- Grande Corvée
- Gare de Ludres
- Saint-Georges
- Place Stanislas - Cathédrale
- Point Central
- Achille Lévy
- VILLERS-LES-NANCY - VILLERS-LES-NANCY STAN ESIAL Mutualité
- Ludres Marvingt
- JARVILLE-LA-MALGRANGE - Atelier
- MALZEVILLE - Pixérécourt
- NANCY - Place des Vosges
- Villemin
- Ravel
- Cristalleries
- Gambetta
- Lobau
- Kehl
- Ludres
- Place Charles III - Point Central
- Jolimont
- Résidences Vertes
- Saint-André - Jardin Botanique
- Garenne - Rose Wild
- Jean Jaures
- Mon Désert - Thermal
- Fléville Mairie
- Tourtel
- Laxou V. Prouvé
- Maréville
- Fresnel
- Ecole Pasteur
- Salengro
- ARTEM - Blandan - Thermal
- Montet Octroi
- Parc de Brabois
- Amerval
- Carsat
- Désilles
- Saint-Fiacre
- Brabois hôpitaux
- Technopole
- Laneuveville Piscine
- La Malgrange
- Maison des Vignes
- François Jacob
- Libération
- 18 juin
- Art-sur-Meurthe Château
- Baudricourt
- Laxou Champ-le-Boeuf
- Mouzon
- Saône
- Zola
- Baraques de Ludres
- LUDRES - Cinéma
- Pascal
- Douëra
- Gustave Nordon
- Les Savlons
- Lion d'Or
- Malzéville Stade
- Alfred Kastler
- Maxéville ZA Saint-Jacques
- Pont Fleuri
- Charlemagne
- Georges de la Tour
- Maréchal Juin
- MJC 3 Maisons
- NANCY - Pierson
- Victor
- Viray
- Saulxures Jardins Fleuris
- La Paix
- Pottier
- Rive Droite - Méchelle
- Tomblaine Groupe Scolaire
- Tomblaine Mairie
- Tuilerie
- Nations
- France Lanord
- Général Mangin
- Villers Mairie
- Saint-Exupéry
- Boufflers
- Austrasie
- Boufflers
- Cours Léopold
- Esplanade
- Rond-Point des Familles
- Saint-Sébastien
- Les Rosiers
- Biancamaria
- La Malgrange
- Vélodrome - Callot
- Ecole
- Charles de Foucauld
- Pichon
- College George Chepfer
- Beaupré
- Jarville Californie
- Foch
- Faiencerie
- Mac Mahon
- Parc de la Pépiniere
- Parc des Sports - Nations
- Pôle Technologique
- Valtriche
- Villers Eglise
- Essey Porte Verte
- Heillecourt La Rotonde
- Maxéville Meurthe-Canal
- Crépin
- Sion Badinter
- Dommartemont
- Laxou Plateau de Haye
- Vezouze
- Bisiaux
- Majorelle
- Vandoeuvre Roberval
- Villers Clairlieu
- Place Carnot
- Cinéma
- UFR Staps
- Mairie
- Leclerc
- Transformateur
- Hôpital Central-Maternité
- Vic
- Chartreuse
- Napoléon
- Repentir
- Colonies
- Essey Centre
- ESSEY-LES-NANCY - Quartier Kléber
- Croix du Soldat
- Ducret
- Fleurychamp
- Besançon
- Chateaubriand
- Heillecourt
- Husson
- Morlaix
- Pré de la Dame
- and 1215 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
- Warning75487 instances
75487 of 75487 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning60436 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 (opens the validator rules on an external site)
- Warning1868 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 (opens the validator rules on an external site)
- Warning1464 instances
1464 of 1465 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 (opens the GTFS Schedule reference on an external site)
- Warning45 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 (opens the validator rules on an external site)
- Warning23 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 (opens the validator rules on an external site)
- Warning7 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- Warning1 instance
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.)
Validator rule: stop_too_far_from_shape · 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.)
Validator rule: 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 connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info16 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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).
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 (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 166 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 166 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 38 / 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/stan-nancy/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.