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
unchanged since 2026-07-08
Ahead of 32% of all tracked agencies and 30% 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 10 hours ago.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1531 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
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
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 +8 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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.
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.
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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 11 kinds of issue across 258 instances (0 error, 108 warning, 150 informational).
Service data ended 1531 day(s) ago. Trip planners have likely already dropped this feed.
90% of stops state wheelchair accessibility (0% marked accessible, 90% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
90% of stops state accessibility (0% marked accessible). Reflects what the feed states, 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.
- BB (pink)
- BRK (green)
- CN (green)
- CS (white)
- CSX (pink)
- DD (blue)
- MX (orange)
- NE (green)
- NW (orange)
- NX (white)
- OS (brown)
- WS (purple)
- WX (pink)
| Route | Type | Line color |
|---|---|---|
| 99995 Commencement Charters | Bus | white (no shape in feed) |
| 99996 NTI 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 | pink |
| BBL Bursley-Baits Loop | Bus | green (no shape in feed) |
| BRK On Break | Bus | green |
| CC Campus Connector | Bus | green (no shape in feed) |
| CN Commuter North | Bus | green |
| CS Commuter South | Bus | white |
| CSX Crisler Express | Bus | pink |
| DD Diag-to-Diag Express | Bus | blue |
| GNW Green Rd-NW5 Loop | Bus | green (no shape in feed) |
| GX Glazier Express | Bus | green (no shape in feed) |
| MX Med Express | Bus | orange |
| NE North-East Shuttle | Bus | green |
| NW Northwood | Bus | orange |
| NWL Northwood Loop | Bus | green (no shape in feed) |
| NX Northwood Express | Bus | white |
| OS Oxford Shuttle | Bus | brown |
| OXM Oxford-Markley Loop | Bus | green (no shape in feed) |
| SD Stadium-Diag Loop | Bus | green (no shape in feed) |
| WBNW Winter Break Northwood | Bus | green (no shape in feed) |
| WS Wall Street-NIB | Bus | purple |
| WX Wall Street Express | Bus | pink |
This feed has 135 stops.
List every stop
- FIFTH AVE SW
- VA Hospital Fuller Rd
- Biomedical Engineering Bldg
- Ford Presidential Library
- Cooley Lab Inbound
- Oxford Housing
- Cooley Lab Outbound
- FXB Inbound
- FXB Outbound
- Bursley Hall Inbound
- Bursley Hall Outbound
- CARROLL STREET
- Baits II Inbound
- Baits II Outbound
- Baits I
- Murfin/Northwood III
- Northwood III Inbound
- Angell Elementary School
- Northwood III Outbound
- Northwood I Inbound
- Northwood I Outbound
- Cram Circle Inbound
- THIRD AVE SW
- Cram Circle Outbound
- Northwood II Inbound
- Northwood II Outbound
- Fire Station Inbound
- Plymouth Rd Crosswalk
- Kraus Building
- Northwood IV
- Northwood Community Center
- Hayward/Hubbard Hubbard Inbound
- Hayward/Hubbard Hubbard Outbound
- BRUCE STREET
- Huron/Hubbard Hubbard Inbound
- Hayward/Hubbard Hayward Outbound
- NCAC Hubbard Inbound
- Huron/Hubbard Huron Outbound
- Northwood V (1)
- Northwood V (2)
- NCAC, Hubbard Outbound
- Fire Station Outbound
- TEST STOP 1
- TEST STOP 2
- Hill Street at Tappan Avenue
- Revelli Hall Inbound
- Kipke Tunnel
- Hill at Oakland
- GNW Break Node
- CC Break Node
- Simpson Drive
- Kipke and Stadium
- Fuller Rd at Lot NC-78 Mitchell Field (2)
- Michigan League
- Stadium and Main
- Gate 9
- Keech and Kipke
- Upper Yard Fence
- Michigan Union S. State
- Northwood V (3)
- 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
- Fuller Rd at Lot NC-78 Mitchell Field (1)
- Power Center
- Fuller Rd at Lot NC-78 Mitchell Field (3)
- Glazier Way Lot NC-51 West
- Glazier Way Lot NC-51 North
- 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
- Rackham Bldg
- Transportation Gate
- Facilities Services Building
- Institute for Continuing Legal Education
- Greene/Hoover
- Intramural Building Outbound
- Intramural Building Inbound
- Crisler Center Lot SC-5
- Law Quad
- South Quad
- W Medical Ctr Dr at Catherine
- NCRC South
- NCRC North Inbound
- Michigan Union - South University
- Central Campus Transit Center: Chemistry
- Central Campus Transit Center: Ruthven Museum
- Green Rd Park & Ride Inbound
- Green Rd Park & Ride Outbound
- Shapiro Library
- 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
- East Quad Willard
- 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
- East Quad Church
- North Ingalls Building
- Medical Science Research Bldg II
- Markley Hall
- Mott Hospital
- Taubman Outbound
- Taubman Inbound
- Cancer Center Inbound
- WATERTOWER DRIVEWAY
- Cancer Center Outbound
- Maiden Lane
- Wall St Structure
- Henderson House
- VA Hospital Circle Drive
- Fuller Rd at Mitchell Field Lot M-75
- Lot M-75 Mitchell Field Outbound (2)
- Lot M-75 Mitchell Field Inbound (1)
- Lot M-75 Mitchell Field Inbound (2)
- Lot M-75 Mitchell Field Outbound
Over time
Overall score across the last 15 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-25 | 48.6 | first check |
| 2026-06-26 | 48.6 | no change |
| 2026-06-27 | 48.6 | no change |
| 2026-06-28 | 48.6 | no change |
| 2026-06-29 | 48.6 | no change |
| 2026-06-30 | 48.6 | no change |
| 2026-07-01 | 48.6 | no change |
| 2026-07-02 | 48.6 | no change |
| 2026-07-03 | 48.6 | no change |
| 2026-07-04 | 48.6 | no change |
| 2026-07-05 | 48.6 | no change |
| 2026-07-06 | 48.6 | no change |
| 2026-07-07 | 48.6 | no change |
| 2026-07-08 | 48.6 | no change |
| 2026-07-09 | 48.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady 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
- Error1 instance
Service data ended 1531 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning68 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)
- Warning23 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)
- Warning13 instances
13 of 135 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)
- 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)
- Warning5 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
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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · 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
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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · 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)
- Info147 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 (opens the validator rules on an external site)
- Info8 instances
About 8 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 (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' 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: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · 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.
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (DD, NE, WS).
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.
27 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.
Trimmed surrounding whitespace 2 changes
For example: 'stop_code': 'STOP 2 ' -> 'STOP 2'
Recased shouting stop names 8 changes
For example: NCRC -> Ncrc
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1531 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1531 days ago, so FTA would find the link out of date.
- 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. Service data expired 1531 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1531 days ago.
- Accessible Met
- States wheelchair access on 90% of stops and 100% of trips.
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.
- 23 of 135 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 58 / 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 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 74 / 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/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.