Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
University of Michigan Transit Services
Based on the feed this agency publishes
down 0.4 since 2026-07-08
Ahead of 64% of all tracked agencies and 63% of mid-size agencies. Operates in Michigan.
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.1, validator 8.0.1.
Checked for changes 7 hours ago; last changed 18 days ago.
Top things to fix
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
1245 of 1245 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 points
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Enable 'remove unused shapes' (or similar) in your export tool.Likely your export tool
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
⏱ One setting.worth about +6 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Enable 'remove unused shapes' (or similar) in your export tool. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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 7 kinds of issue across 45 instances (0 error, 45 warning, 0 informational).
Service data covers the next 44 days.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
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.
- CN (purple)
- CS (teal)
- CSX (gray)
- MX (red)
- NES (gray)
- NW (orange)
- WS (white)
- WX (white)
| Route | Type | Line color |
|---|---|---|
| 99995 Commencement Charters | Bus | white (no shape in feed) |
| 99997 Training route | Bus | white (no shape in feed) |
| 99998 Charter Route | Bus | white (no shape in feed) |
| 99999 Test Route | Bus | white (no shape in feed) |
| BB Bursley Baits | Bus | gray (no shape in feed) |
| CN Commuter North | Bus | purple |
| CS Commuter South | Bus | teal |
| CSX Crisler Express | Bus | gray |
| DD Diag-to-Diag Express | Bus | yellow (no shape in feed) |
| MX Med Express | Bus | red |
| NES North-East Shuttle | Bus | gray |
| NW Northwood | Bus | orange |
| NX Northwood Express | Bus | red (no shape in feed) |
| OS Oxford Shuttle | Bus | gray (no shape in feed) |
| WS Wall Street-NIB | Bus | white |
| WX Wall Street Express | Bus | white |
This feed has 112 stops.
List every stop
- Michigan Union S. State
- Michigan Union S. Univ
- Shapiro Library
- East Quad Willard
- East Quad Church
- Henderson House
- Oxford Housing
- Angell Elementary School
- School of Kinesiology Building
- Power Center
- Rackham Bldg
- Central Campus Transit Center: Chemistry
- Central Campus Transit Center: Ruthven Museum
- Green Rd Park & Ride Inbound
- Green Rd Park & Ride Outbound
- Michigan House
- 2101 Commonwealth
- Rachel Upjohn Building
- East Ann Arbor Health & Geriatrics Center
- Arbor Lakes
- Domino's Farms Lobby A
- Domino's Farms Lobby C
- Domino's Farms Lobby M
- Domino's Farms Lobby H
- Plymouth Park-and-Ride
- Stockwell Hall Outbound
- Stockwell Hall Inbound
- Cardiovascular Center
- Lloyd/Observatory
- Couzens Hall
- Biomedical Science Research Bldg
- Glen/Catherine Outbound
- Glen/Catherine Inbound
- North Ingalls Bldg
- Medical Science Research Bldg II
- Markley Hall
- Mott Hospital
- Taubman Outbound
- Taubman Inbound
- Cancer Center Inbound
- Cancer Center Outbound
- Maiden Lane
- W Medical Ctr Dr at Catherine
- Wall St Structure
- VA Hospital Circle Drive
- Fuller Rd at Mitchell Field Lot M-75
- VA Hospital Fuller Rd
- Biomedical Engineering Bldg
- Ford Presidential Library
- Cooley Lab Inbound
- Cooley Lab Outbound
- FXB Inbound
- FXB Outbound
- Bursley Hall Inbound
- Bursley Hall Outbound
- Baits II Inbound
- Baits II Outbound
- Baits I
- Murfin/Northwood III
- Northwood III Inbound
- Northwood III Outbound
- Northwood I Inbound
- Northwood I Outbound
- Cram Circle Inbound
- Cram Circle Outbound
- Northwood II Inbound
- Northwood II Outbound
- Fire Station Inbound
- Fire Station Outbound
- Plymouth Rd Crosswalk
- Northwood IV
- Northwood Community Center
- Hayward/Hubbard Hubbard Inbound
- Hayward/Hubbard Hubbard Outbound
- Huron/Hubbard Hubbard Inbound
- Hayward/Hubbard Hayward Outbound
- NCAC Hubbard Inbound
- Huron/Hubbard Huron Outbound
- Northwood V (1)
- Northwood V (2)
- Northwood V (3)
- NCAC%% Hubbard Outbound
- NCRC SB Huron Pkwy
- NCRC NB Huron Pkwy
- NCAC Inbound
- NCAC Outbound
- North Campus Facilities Services Bldg Outbound
- North Campus Facilities Services Bldg Inbound
- NCRC
- NCRC South
- Fuller Rd at Lot NC-78 Mitchell Field (1)
- Fuller Rd at Lot NC-78 Mitchell Field (2)
- Fuller Rd at Lot NC-78 Mitchell Field (3)
- Glazier Way Lot NC-51 West
- Glazier Way Lot NC-51 North
- North Campus Facilities Services Bldg Outbound
- Glazier Way Lot NC-51 East
- Pierpont Commons Murfin Outbound
- Pierpont Commons Murfin Inbound
- Art & Architecture
- Pierpont Commons Bonisteel Inbound
- Crisler Center/Lot SC-7
- Crisler Center Lot SC-5
- Transportation Gate
- Facilities Services Building
- Institute for Continuing Legal Education
- Greene/Hoover
- Intramural Building Outbound
- Intramural Building Inbound
- Law Quad
- South Quad
- Zina Pitcher
Over time
Overall score across the last 21 checks — down 0.4 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 78.9 | first check |
| 2026-06-20 | 78.9 | no change |
| 2026-06-21 | 78.9 | no change |
| 2026-06-22 | 78.9 | no change |
| 2026-06-23 | 78.9 | no change |
| 2026-06-24 | 78.5 | down 0.4 |
| 2026-06-25 | 78.1 | down 0.4 |
| 2026-06-26 | 77.7 | down 0.4 |
| 2026-06-27 | 77.3 | down 0.4 |
| 2026-06-28 | 76.8 | down 0.5 |
| 2026-06-29 | 76.4 | down 0.4 |
| 2026-06-30 | 76.0 | down 0.4 |
| 2026-07-01 | 75.6 | down 0.4 |
| 2026-07-02 | 75.2 | down 0.4 |
| 2026-07-03 | 74.8 | down 0.4 |
| 2026-07-04 | 74.4 | down 0.4 |
| 2026-07-05 | 73.9 | down 0.5 |
| 2026-07-06 | 73.5 | down 0.4 |
| 2026-07-07 | 73.1 | down 0.4 |
| 2026-07-08 | 72.7 | down 0.4 |
| 2026-07-09 | 72.3 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning1245 instances
1245 of 1245 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning20 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Enable 'remove unused shapes' (or similar) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some service calendars in the feed have already expired.
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
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)
- 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.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
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 files are missing recommended (not required) fields.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges become unreadable, especially for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (CN, MX).
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.
25 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Green Rd Park & Ride Inbound", "Green Rd Park & Ride Outbound", "East Ann Arbor Health & Geriatrics Center", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Recased shouting stop names 1 change
For example: NCRC -> Ncrc
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 44 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 100% 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 44 days.
- Accessible Not yet
- States wheelchair access on 100% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 20 of 112 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 44 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
Your state runs a transit-data program that can help: Michigan Public Transit Open Data Program. MDOT's program helping agencies produce and maintain GTFS and GTFS-Flex. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 68 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 73 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 77 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/university-of-michigan-transit-services-2072/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.