GTFS Scorecard
← All agencies

Feed status · checked 2026-07-24

Réseau urbain évolitY

Based on the feed this agency publishes

Service mode Bus

63.7 / 100

First scorecard for this agency

Catalogued in Bourgogne-Franche-Comté, France.

Covers 322 daysRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.

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

How we measured this

Confidence in this measurement: medium.

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

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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

Fix 02

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

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

Fix 03

Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.

Some internal IDs use characters outside the basic text set. These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.

⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

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

  2. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.

    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 322 days.
Published accessibility data
Accessibility information is stated for 77.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
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

Correctness56.2 / 100

The MobilityData validator flagged 9 kinds of issue across 4482 instances (0 error, 2068 warning, 2414 informational).

Freshness85.0 / 100

Service data covers the next 322 days.

Rider experience57.0 / 100

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

Accessibility86.1 / 100

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

1 accessibility depth signal

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (A, T3, X).

    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.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

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

Skip to route and stop data

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

  • A (pink)
  • B (pink)
  • C (purple)
  • D (orange)
  • E (blue)
  • F (brown)
  • T1 (green)
  • T2 (teal)
  • T3 (red)
  • H (black)
  • N (white)
  • X (purple)
  • Z (gray)
  • T4 (yellow)
  • T5 (yellow)
  • ESTI (green)
Routes in Réseau urbain évolitY's feed
RouteTypeLine color
A BAVANS Bel Air - ETUPES La MontagneBuspink
B MONTBELIARD Le Mittan - MONTBELIARD MermozBuspink
C BETHONCOURT Champvallon - MONTBELIARD Grands JardinsBuspurple
D MONTBELIARD Acropole - MEROUX Gare TgvBusorange
E VOUJEAUCOURT Coteau de l'ane - NOMMAY/DAMBENOISBusblue
F MONTBELIARD Acropole - AUDINCOURT ArbletiersBusbrown
T1 BETHONCOURT Champvallon - VALENTIGNEY LonginesBusgreen
T2 GRAND-CHARMONT Les Fougeres - AUDINCOURT Champs MontantsBusteal
T3 SAINTE-SUZANNE St-Michel - HERIMONCOURT La BouloieBusred
H AUDINCOURT Place du Marche - PONT-DE-ROIDE PasserelleBusblack
N VALENTIGNEY Parrot - VALENTIGNEY Les BruyeresBuswhite
X MONTBELIARD Acropole - BELFORT Gare VilleBuspurple
Z MONTBELIARD Acropole - DAMBENOIS TourtelotsBusgray
T4 MONTBELIARD Acropole - AUDINCOURT BazaineBusyellow
T5 MONTBELIARD Acropole - MANDEURE Le ClosBusyellow
ESTI MONTBELIARD Acropole - BROGNARD Base NautiqueBusgreen

This feed has 666 stops.

List every stop
  • 8MAI
  • 8MAI2
  • ACROPOLE QUAI 2
  • ACROPOLE QUAI 3
  • ACROPOLE QUAI 4
  • ACROPOLE QUAI 5
  • ACROPOLE QUAI 6
  • ACROPOLE
  • AERODROME
  • AERODROME
  • ANATOLE FRANCE
  • ANATOLE FRANCE
  • AIGUILLOTTES
  • AIGUILLOTTES
  • ALLENDE
  • ALLENDE
  • ALOUETTES
  • ALOUETTES
  • ANGOULOTTE
  • ANGOULOTTE
  • ARBLETIERS
  • ARBLETIERS
  • ARBOUANS
  • ARBOUANS
  • ARCADES
  • BEL AIR
  • BEL AIR
  • BALANCE
  • BAZAINE
  • BAZAINE
  • BARRIERES BLANCHES
  • BARRIERES BLANCHES
  • BEAUCOURT
  • BEAULIEU
  • BEAULIEU
  • BERNE
  • BERNE
  • BETHONCOURT
  • BETHONCOURT
  • BIZET
  • BIZET
  • BASE NAUTIQUE
  • BOISGENETS
  • BOISGENETS
  • BOIS SUR PRES
  • BOIS SUR PRES
  • BOSSIERE
  • BOSSIERE
  • BOUDRY
  • BOUDRY
  • BOUDRY
  • BOUDRY
  • BOURGUIGNON LES FORGES
  • BOURGUIGNON LES FORGES
  • BOULLOCHE
  • BOULLOCHE
  • LES BOULOTTES
  • LES BOULOTTES
  • BOURGUIGNON
  • BOURGUIGNON
  • BOUTONNIERS
  • BOUTONNIERS
  • BRASSENS
  • BREUIL
  • BREUIL
  • BRIAND
  • BRIAND
  • BUFFON
  • BUFFON
  • CAMPUS
  • CAMPUS
  • CAMUS
  • CAMUS
  • CANAL
  • CANAL
  • CARNOT
  • CARRONS
  • CARRONS
  • CARRIERES
  • LES CARRIERES
  • CASTORS
  • CASTORS
  • CHAMP DU CERF
  • CHAMP DU CERF
  • CHEMIN DES CHARS
  • CHEMIN DES CHARS
  • COTEAU DE L'ANE
  • CERISIERS
  • CERISIERS
  • CFAI
  • CFAI
  • CHATILLON
  • CHATILLON
  • CHALETS
  • CHALETS
  • CHAMPAGNE
  • CHAMPAGNE
  • CHANOIT
  • CHANOIT
  • CHARMONTET
  • CHARMONTET
  • CHAMPS DES ILES
  • CHAMPS DES ILES
  • CHENEVIER
  • CHENEVIER
  • CHIFFOGNE
  • CHIFFOGNE
  • MAISON POUR TOUS
  • MAISON POUR TOUS
  • CIMETIERE DU HAUT
  • CIMETIERE DU HAUT
  • CIMETIERE PONT DE ROIDE
  • CIMETIERE PONT DE ROIDE
  • CITADELLE
  • CITADELLE
  • CITEDO
  • CITEDO
  • COMBE JEANNE
  • COMBE JEANNE
  • COTEAU JOUVENT
  • COTEAU JOUVENT
  • CLEMENCEAU
  • CLEMENCEAU
  • CHABAUD LATOUR
  • CHABAUD LATOUR
  • COURTES MESIERES
  • COURTES MESIERES
  • COMBE MIREY
  • COMBE MIREY
  • CHAMPS MONTANTS
  • CHAMPS MONTANTS
  • COMBE AUX BICHES
  • COMBOTTE
  • COMBOTTE
  • CONTEJEAN
  • CONTEJEAN
  • CORA
  • CORA
  • COURCELLES
  • COURCELLES
  • LA CORNETTE
  • LA CORNETTE
  • LA CORNETTE
  • LA CORNETTE
  • COURBET
  • COURBET
  • COURTS CANTONS
  • COURTS CANTONS
  • COUDROYE
  • COUDROYE
  • COURCELLE
  • COURCELLES
  • CREPON
  • CREPON
  • CHAMP SIMONIN
  • CHAMP SIMONIN
  • CUVIER
  • CUVIER
  • CHAMPVALLON
  • CHAMPVALLON
  • CHAMPVALLON
  • CHAMPVALLON
  • DAMBENOIS
  • DAMPIERRE
  • DAMPIERRE
  • DASLE
  • DASLE
  • DIDEROT
  • DIDEROT
  • DODILLET
  • DODILLET
  • DOUBS
  • DOUBS
  • DONZELOT
  • DONZELOT
  • ES BREUX
  • ES BREUX
  • ECOLE DES CHARDONNERETS
  • ECOLE DES CHARDONNERETS
  • ES COMBAS
  • ES COMBAS
  • ECUREUILS
  • ECUREUILS
  • ES EPRAUX
  • ES EPRAUX
  • EGLANTINE
  • EGLANTINE
  • EMAILLERIE
  • EMAILLERIE
  • EPINOTTES
  • EPINOTTES
  • EPOISSES
  • EPOISSES
  • ES COURES
  • ES COURES
  • ESPERANCE
  • ESPERANCE
  • ESPLANADE
  • ESPLANADE
  • ETUVE
  • ETUPES
  • ETUPES
  • ETUVE
  • FESCHES
  • FESCHES
  • FOCH
  • FOCH
  • FOILLET
  • FOILLET
  • FONDERIE
  • FONDERIE
  • FONTENOTTE
  • FONTENOTTE
  • FOURNEAU
  • FOURNEAU
  • FRAMBOISIERS
  • FRAMBOISIERS
  • FROMAGERIE
  • FROMAGERIE
  • GAMBETTA
  • GAMBETTA
  • GASCOGNE
  • GASCOGNE
  • GRANDS BOIS
  • GRAND BOIS
  • GRAND CHENOIS
  • GRAND CHENOIS
  • GARE DE BELFORT
  • GIBOULON
  • GIBOULON
  • GRANDS JARDINS
  • GARE TGV
  • GROS PIERRONS
  • GROS PIERRONS
  • GROS PIERRONS
  • GROS PIERRONS
  • GRANDJEAN
  • GRANDJEAN
  • GRAVIERS
  • GRAVIERS
  • GRANDE RUE
  • GRANDE RUE
  • GARE TGV
  • GARE TGV
  • GUYOT
  • GUYOT
  • HAUTS DES BUIS
  • HAUTS DES BUIS
  • HELVETIE
  • HELVETIE
  • and 416 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
  • Warning1667 instances

    Some internal IDs use characters outside the basic text set.

    These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.

    Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)

    Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules

  • Warning331 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

  • Warning148 instances

    148 of 666 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

  • Warning48 instances

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

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

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

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

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

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

  • Warning6 instances

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

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

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

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

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

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

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

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

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

  • Info2378 instances

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: unsorted_stop_times · See MobilityData GTFS Validator rules

  • Info662 instances

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

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

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

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

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

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

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

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

Conformance mark Not yet

This feed is close to the conformance mark. States wheelchair access on 78% 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 322 days.
Accessible Not yet
States wheelchair access on 78% of stops and 100% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Clears the Google and Apple Maps four-week coverage bar. This feed has 322 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 56 / 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 57 / 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.

Réseau urbain évolitY GTFS data quality grade: D

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-81944/2026-07-24.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-24. 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.