GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Réseau urbain Illygo

Based on the official feed source on file

Service mode Bus

72.5 / 100

First scorecard for this agency

Catalogued in Pays-de-la-Loire, France.

Covers 121 daysAccessibility gaps

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 hours ago; last changed 1 hours ago.

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 9 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

Fix 01

Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.

5 of 5 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 +41 points in its category

Fix 02

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

159 of 159 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

Fix 03

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.

Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +8 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
5 of 5 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.

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

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

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

    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 121 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 80.4% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
Live-arrival data covered 0% 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

Correctness65.0 / 100

The MobilityData validator flagged 7 kinds of issue across 1304 instances (0 error, 1299 warning, 5 informational).

Freshness100.0 / 100

Service data covers the next 121 days.

Rider experience71.9 / 100

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

Accessibility30.1 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (206GO, 208GO, 211GO).

    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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality58.8 / 100

Sampled 9 times: 3 of 3 configured feeds healthy; 0.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable.

Routes and stops

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

This feed has 159 stops.

Skip to route and stop data

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.

  • 206GO (teal)
  • 25GO (pink)
  • 2GO (pink)
  • 1GO (pink)
  • 208GO (teal)
  • 22GO (pink)
  • 211GO (teal)
  • 22GO ETE (pink)
  • 3GO (pink)
  • 23GO (pink)
Routes in Réseau urbain Illygo's feed
RouteTypeLine color
206GO La-Suze-sur-Sarthe - Fillé - Allonnes Les Hautes Métairies T3Busteal
25GO Saint-Ouen-en-Belin - Marigné-Laillé via Gare d'EcommoyBuspink
2GO Challes - Saint-Mars-d'Outillé - Le Mans Espal T2Buspink
1GO Changé - Le Mans Espal T2Buspink
208GO La-Suze-sur-Sarthe - Chemiré-le-Gaudin - Allonnes Stade Georges Garnier T3Busteal
22GO Saint-Rémy-de-Sillé - Sillé-le-Guillaume via Gare de SilléBuspink
211GO Ballon-Saint-Mars - Le Mans Maillets-Zamenhof T2Busteal
22GO ETE Sillé-le-Guillaume, Gare SNCF - Sillé-PlageBuspink
3GO Challes - Saint Mars d'OutilléBuspink
23GO Monfort le Gesnois - Connerré - ThorignéBuspink
List every stop
  • MARIGNÉ LAILLÉ Salle des fêtes
  • CHANGÉ Maison de retraite
  • MONTFORT LE GESNOIS Honoré Broutelle
  • NEUVILLE SUR SARTHE La Trugalle-route du Mans
  • NEUVILLE SUR SARTHE La Trugalle-route du Mans
  • ROËZÉ SUR SARTHE Route de Fillé
  • SAINT BIEZ EN BELIN Place Vénus
  • CHALLES École
  • SAINT-MARS-D'OUTILLÉ Place Victor Hugo
  • SAINT OUEN EN BELIN Mairie
  • SPAY Emmanuel Baërt
  • SPAY Place du 11 Novembre
  • SOULIGNÉ SOUS BALLON Grande Rue
  • SOULIGNÉ SOUS BALLON Grande Rue
  • LA SUZE SUR SARTHE Pape Carpentier
  • LA SUZE SUR SARTHE Pape Carpentier
  • ÉTIVAL LÈS LE MANS Place Albertine Leffray
  • FILLÉ Groupe scolaire
  • SILLÉ LE GUILLAUME Place du Marché aux bestiaux
  • MARIGNÉ LAILLÉ Salle des fêtes
  • SILLÉ LE GUILLAUME Groupe scolaire Paul Scarron
  • MARIGNÉ LAILLÉ Salle des fêtes
  • MONTFORT LE GESNOIS Honoré Broutelle
  • NEUVILLE SUR SARTHE La Trugalle-route du Mans
  • BALLON-SAINT MARS Saint Laurent
  • MONTFORT LE GESNOIS Libération
  • ROËZÉ SUR SARTHE route de Fillé
  • ÉCOMMOY La Providence
  • ÉCOMMOY La Providence
  • ÉCOMMOY La Providence
  • MONTFORT LE GESNOIS Libération
  • SAINT BIEZ EN BELIN Place Vénus
  • BEILLÉ Gare
  • PARIGNÉ-L'ÉVÊQUE Trois Puits
  • PARIGNÉ-L'ÉVÊQUE Trois Puits
  • PARIGNÉ-L'ÉVÊQUE Trois Puits
  • THORIGNÉ SUR DUÉ IME Épione
  • THORIGNÉ SUR DUÉ IME Épione
  • THORIGNÉ SUR DUÉ IME Épione
  • SAINT-MARS-D'OUTILLÉ Place Victor Hugo
  • SAINT OUEN EN BELIN Mairie
  • SPAY Emmanuel Baërt
  • SPAY Place du 11 Novembre
  • LA SUZE SUR SARTHE Pape Carpentier
  • SILLÉ LE GUILLAUME Groupe scolaire Paul Scarron
  • SILLÉ LE GUILLAUME Place du marché aux bestiaux
  • CHANGÉ Route de L'Epau
  • CONNERRÉ avenue de Verdun
  • SOULIGNÉ SOUS BALLON Grande Rue
  • CHANGÉ Blanchardière
  • CHANGÉ Blanchardière
  • CHANGÉ Blanchardière
  • CHANGÉ Route de L'Epau
  • CHANGÉ Route de L'Epau
  • LE MANS Zamenhof
  • LE MANS Zamenhof
  • JOUÉ L'ABBÉ ZA les petites forges
  • NEUVILLE SUR SARTHE ZA du Chapeau
  • NEUVILLE SUR SARTHE ZA du Chapeau
  • CHANGÉ ZA Les Ravalières
  • CHANGÉ ZA Les Ravalières
  • CHANGÉ ZA Les Ravalières
  • BRETTE-LES-PINS Mairie
  • BRETTE-LES-PINS Mairie
  • BEILLÉ Gare
  • CONNERRÉ Avenue de Verdun
  • CONNERRÉ Avenue de Verdun
  • CONNERRÉ Rue du Petit Train
  • CONNERRÉ Rue Du Petit Train
  • CONNERRÉ Rue du petit train
  • SILLÉ LE GUILLAUME gare sncf
  • SILLÉ LE GUILLAUME gare SNCF
  • LE MANS Arche de la Nature
  • LE MANS Arche de la Nature
  • CHANGÉ Allée du Perquoi
  • CHANGÉ Allée du Perquoi
  • PARIGNÉ-L'ÉVÊQUE Zone du Ruisseau
  • PARIGNÉ-L'ÉVÊQUE Zone du Ruisseau
  • ROËZÉ SUR SARTHE Route de Fillé
  • ALLONNES Stade Georges Garnier
  • ALLONNES Stade Georges Garnier
  • SAINT REMY DE SILLE Rue des Epinettes
  • SAINT REMY DE SILLE Rue des Epinettes
  • SILLÉ LE GUILLAUME Lac de Sillé
  • SILLÉ LE GUILLAUME Lac de Sillé
  • CONNERRÉ La belle Inutile
  • CONNERRÉ La belle Inutile
  • CONNERRÉ La belle Inutile
  • ÉCOMMOY Gare
  • ÉCOMMOY Gare
  • ÉCOMMOY Boissière
  • ÉCOMMOY Boissière
  • ÉCOMMOY ZAC les Truberdières
  • ÉCOMMOY ZAC les Truberdières
  • MARIGNÉ LAILLÉ Fimurex
  • MARIGNÉ LAILLÉ Fimurex
  • ÉCOMMOY Soleil
  • ÉCOMMOY Soleil
  • ROËZÉ SUR SARTHE Route du Mans
  • ROËZÉ SUR SARTHE Route du Mans
  • ROËZÉ SUR SARTHE Route du Mans
  • ROËZÉ SUR SARTHE ZA du Val de l'Aune
  • ROËZÉ SUR SARTHE ZA du Val de l'Aune
  • SPAY LTR Industries
  • SPAY LTR Industries
  • SPAY Parc des Noës
  • SPAY Parc des Noës
  • SPAY Parc des noës
  • SAINT REMY DE SILLE Rue des Epinettes
  • SILLÉ LE GUILLAUME ZA du Champ d’Esse
  • SILLÉ LE GUILLAUME ZA du Champ d’Esse
  • SILLÉ LE GUILLAUME ZA du Bois des Cours
  • SILLÉ LE GUILLAUME ZA du Bois des Cours
  • SILLÉ LE GUILLAUME Place du Marché aux bestiaux
  • JOUÉ L'ABBÉ ZA les petites forges
  • BALLON-SAINT MARS Saint Laurent
  • JOUÉ L'ABBÉ Les Quatre Routes
  • JOUÉ L'ABBÉ Les Quatre Routes
  • SILLÉ LE GUILLAUME Groupe scolaire Paul Scarron
  • LOUPLANDE Stade
  • LOUPLANDE Stade
  • LOUPLANDE Stade
  • LA SUZE SUR SARTHE Route de Chemiré
  • LA SUZE SUR SARTHE Route de Chemiré
  • CHEMIRÉ LE GAUDIN Mairie
  • CHEMIRÉ LE GAUDIN Mairie
  • CHEMIRÉ LE GAUDIN Mairie
  • VOIVRES LÈS LE MANS ZA Actival Les Clottées
  • VOIVRES LÈS LE MANS ZA Actival Les Clottées
  • LA SUZE SUR SARTHE Route de Chemiré
  • JOUÉ L'ABBÉ Les Quatre Routes
  • ALLONNES Hautes Métairies T3
  • ALLONNES Hautes Métairies T3
  • ALLONNES Hautes Métairies T3
  • LE MANS ESPAL Rue de Hongrie
  • LE MANS ESPAL Rue de Hongrie
  • SILLÉ LE GUILLAUME ZA du Champs d'Esse 2
  • SILLÉ LE GUILLAUME ZA du Champs d'Esse 2
  • SILLÉ LE GUILLAUME Chemin des Petits Cours
  • SILLÉ LE GUILLAUME Chemin des Petits Cours
  • SILLÉ LE GUILLAUME LEGRAND
  • SILLÉ LE GUILLAUME LEGRAND
  • THORIGNÉ SUR DUÉ Salle des fêtes
  • THORIGNÉ SUR DUÉ Salle des fêtes
  • MONTFORT LE GESNOIS ZA la Pécardière
  • MONTFORT LE GESNOIS ZA la Pécardière
  • CONNERRÉ ZA les Terrasses de Challans
  • CONNERRÉ ZA les Terrasses de Challans
  • LE MANS ESPAL T2 Rue de l'Esterel
  • LE MANS ESPAL T2 Rue de l'Esterel
  • LE MANS ESPAL T2 Rue de l'Esterel
  • CHANGÉ Maison de retraite
  • CHANGÉ Maison de retraite
  • CHALLES École
  • CHALLES École
  • ÉTIVAL LÈS LE MANS Place Albertine Leffray
  • ÉTIVAL LÈS LE MANS Place Albertine Leffray
  • FILLÉ Groupe scolaire
  • FILLÉ Groupe scolaire

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

11 findings, ordered by severity.

Show every finding
  • Warning973 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

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

  • Warning159 instances

    159 of 159 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

  • Warning88 instances

    88 of 448 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

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

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

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

  • Warning5 instances

    5 of 5 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

  • 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

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

  • Info1 instance

    Feed valid beyond total service window (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 80% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 121 days.
Accessible Not yet
States wheelchair access on 0% of stops and 80% 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 5 checks over the last 1 day, with 7s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Clears the Google and Apple Maps four-week coverage bar. This feed has 121 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 65 / 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 72 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 59 / 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.

Réseau urbain Illygo GTFS data quality grade: C

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-80586/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.