Feed status · checked 2026-08-01
Montgomery Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Alabama.
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 days ago; last changed 38 days ago.
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
1841 of 1841 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
666 of 666 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
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 +8 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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
- 1841 of 1841 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 666 of 666 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 152 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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
- 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 1220 instances (0 error, 1175 warning, 45 informational).
Service data covers the next 152 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
1676 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("South Blvd and Mobile Hwy", "South Blvd Wendys", "South Blvd Comfort Inn", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
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.
This feed has 1841 stops.
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.
- 6 (pink)
- 7 (white)
- 9 (orange)
- 10 (gray)
- 11 (gray)
- 12 (white)
- 16 (red)
- 1 (blue)
- 2 (green)
- 3 (brown)
- 4 (green)
- 5 (pink)
- 8 (purple)
- 17 (purple)
| Route | Type | Line color |
|---|---|---|
| 6 Southlawn Twingates | Bus | pink |
| 7 Maxwell AFB | Bus | white |
| 9 Virginia Loop | Bus | orange |
| 10 Court St. | Bus | gray |
| 11 Rosa Parks / South Blvd. | Bus | gray |
| 12 Smiley Court/Gibbs Village | Bus | white |
| 16 East/West Connector | Bus | red |
| 1 AUM Eastchase | Bus | blue |
| 2 Eastdale Mall | Bus | green |
| 3 Montgomery Commons | Bus | brown |
| 4 Boylston | Bus | green |
| 5 McGehee Road | Bus | pink |
| 8 Gunter Annex | Bus | purple |
| 17 Boulevard | Bus | purple |
List every stop
- South Blvd and Mobile Hwy
- South Blvd Wendys
- South Blvd Comfort Inn
- South Blvd Waffle House
- South Blvd Pizza Hut
- South Blvd Davenport Dr
- South Blvd Rosa Parks
- South Blvd & Court St
- E South Blvd Norman Bridge
- South Blvd
- South Blvd Sunshine Dr
- South Blvd Narrow Lane
- Eastern Blvd and Christine Elizabeth Curve
- Eastern Blvd. and Calmar Dr.
- Eastern Blvd and Buckboard Rd
- Eastern Blvd and Carriage Hills
- Eastern Blvd and Monticello
- Eastern Blvd at Zolen Rd
- Eastern Blvd at E Shirley Ln
- Eastern Blvd at Eddins Rd.
- Eastdale Circle Entrance
- Eastdale Circle and Dunbarton (Eastdale Mall)
- Eastdale Mall Circle and Atlanta Hwy
- E Blvd Service Rd and Dalphon Rd.
- Eastern Blvd at E Shirley ln
- Eastern Blvd at Monticello Dr.
- Eastern Blvd at Woodmere
- Eastern Blvd at Hitching Post Ln
- Eastern Blvd at Carriage Hills
- Lagoon Park Dr & Shadey Grove Dr
- Lagoon Park Dr & Shadey Grove Dr
- Lagoon Park Dr. & Plantation Way
- Lagoon Park Dr. & Plantation Way
- Lagoon Park Dr. & Eastern Blvd.
- Eastern Blvd. & Twain Curve
- Twain Curve and Oliver Rd.
- Twain Curve and Wares Ferry Rd.
- Wares Ferry Rd & Dunbarton Rd
- Wares Ferry Rd & Oakwild Dr
- Wares Ferry & Dunbarton Rd
- Wares Ferry & Twain Curve
- Twain Curve & Oliver Rd.
- Twain Curve & Eastern Blvd.
- Lagoon Park Dr. & Gunter Park Dr. E.
- 2739 Lagoon Park Dr. E.
- Gunter Park Dr. E & Midpark Rd
- Gunter Park Dr. @ Rheem Water Heating
- Gunter Park Dr E. & Gunter Park Dr W.
- EastChase Pkwy & Eastchase Ln
- EastChase Pkwy & Eastchase Ln
- EastChase Pkwy at Costco
- EastChase Pkwy at Costco
- EastChase Pkwy & Boyd Cooper Pkwy.
- EastChase Pkwy & Boyd Cooper Pkwy.
- EastChase Pkwy & Minnie Brown Rd
- EastChase Pkwy & Minnie Brown Rd
- Chantilly Pkwy & EastChase Pkwy.
- Chantilly Pkwy & EastChase Pkwy.
- Chantilly Pkwy at WalMart
- Chantilly Pkwy & Chantilly Dr.
- Chantilly Dr & Service Rd
- Service Rd & Chantilly Pkwy.
- Chantilly Pkwy. & Ryan Rd.
- Chantilly Pkwy. & Ryan Rd.
- VA Hospital
- Baptist Hospital @ Morrow Dr
- Brewer Rd
- Schley St. & Rice St.
- Rice St. & May St.
- Lee St. & Court St.
- S. Court St. & Flemming Rd.
- Fleming Rd. & Rosa Parks
- Rosa Parks & South Blvd.
- S. Court St. & Fairview Ave.
- Clay St. & Goldthwaite St.
- Clay St & Dickerson
- Dickerson St. & Clay St.
- Mobile Rd. & Terminal Rd.
- Airbase Blvd. & Mobile Hwy.
- N Holt St. & Clay St.
- Crossway St. & Mobile Rd.
- Perry Hill Rd. & Carmichael Rd.
- Fairview Ave. & Norman Bridge Rd.
- Decatur St. & Carter Hill. Rd.
- Adams Ave. & Jackson St.
- Washington Ave. & Jackson St.
- Lee St. & Church St.
- Montgomery St. & Lee St.
- Eastchase Pkwy. @ Five Guys
- Berryhill Rd.
- Fairview and Norman Bridge
- Norman Bridge & E. Edgemont Ave.
- Morrow Dr & Normandie Dr.
- Tremont St & Vandy Dr.
- Park Blvd. & Eastern Blvd.
- McGhee Rd & McGhee Place Dr. North
- McGhee Rd. & Fieldcrest Dr.
- McGhee Rd. & Carter Hill Rd.
- McGhee Rd @ Dannelly Elementry School
- McLemore @ WalMart Shopping Center
- AUM School of Nursing
- Troy Hwy & Jack Pine Dr.
- Jack Pine Dr. @ Troy Hwy.
- Perry Hill & Cairnbrook
- Perry Hill & Cairnbrook (w)
- Dickerson St. & Day St.
- Day St. & Dickerson St.
- Fairview Transfer Center
- W. Jeff Davis Ave. & Rosa Parks Ave.
- Rosa Parks Ave. & Fairview Ave.
- Delano Ave. & Norman Bridge Rd.
- Intermodal Transfer Center
- Highland Ave. & Ann St.
- Vaughn Rd. & East Blvd.
- Vaughn Rd. & Taylor Rd.
- The Shoppes at Eastchase
- AUM Campus
- Wal-Mart (On Atlanta Highway)
- Atlanta Hwy. & Ann St.
- Perry Hill Rd. & Atlanta Hwy. (East)
- Pinebrook Dr. & Wares Ferry Rd.
- Eastdale Mall
- Baptist Medical Center South
- One Center
- Wal-Mart (On Christine Elizabeth Curv)
- Sadler St. & N. Decatur
- Alabama River Pkwy. & Coliseum Blvd.
- Jackson Hospital
- Carter Hill @ Zelda Rd.
- Mobile Hwy. & Hwy 80
- Woodcrest & Yorkshire
- Gateway Dr. & Piedmont
- Richardson Rd. & Hwy 80
- Montgomery Regional Airport
- Greenleaf Dr. & Mobile Hwy.
- Maxwell Blvd. & Eugene St.
- Hunter Station
- Old Selma Rd. & Trinity Rd.
- Crestview & Federal Dr.
- Troy Hwy. & Cherry Hill Rd.
- Woodley Rd. & Eagerton Rd.
- Woodley Rd. & South Blvd.
- Highland Ave. & Ann St.
- Vaughn Rd. & East Blvd.
- Vaughn Rd. & Taylor Rd.
- VA Hospital
- Perry Hill Rd. & Atlanta Hwy.
- Madison Ave. & Ann St.
- Rosa Parks & Patton Ave.
- Sadler St. & N. Decatur
- Jackson Hospital
- Carter Hill & Zelda Rd.
- Mobile Hwy. & Hwy 80
- Maxwell Blvd. & Eugene St.
- Crestview & Federal Dr.
- Gaston Ave. & Patton Ave.
- South Court St. & Flemming Rd.
- Catholic Social Services
- South Blvd. & Davenport Dr.
- Mobile Dr. & Edgemont Ave.
- South Blvd. & Mobile Hwy.
- Otis Ln. & East Smiley Ct.
- Airbase Blvd. & Day St.
- Day Street Rd. & Terminal Rd.
- Oak St. & W. Jeff Davis
- Cloverdale Rd & Norman Bridge Rd
- Old Farm & Pinehurst
- Cloverdale & Decatur
- Perry Hill Rd & Carmichael Rd.
- Eastern Blvd. & Vaughn Rd.
- Troy Hwy. & Cherry Hill Rd.
- McKee Junior High School
- Molton & Bibb
- Bibb & Lee
- Bibb & Commerce
- Bibb & Coosa
- Madison & Perry
- Madison & Lawrence
- Madison & McDonough
- Madison & Hull
- Madison & Decatur
- Madison & Bainbridge
- Bainbridge & Monroe
- Bainbridge & Dexter
- Bainbridge & Washington
- Bainbridge & Adams
- Adams & Union
- Adams & Ripley
- Adams & Jackson
- Adams & Brassell
- Adams & Yougene
- Adams & Hall
- Mt. Meigs & Chase
- Mt. Meigs & Hopper
- Mt. Meigs & Cory
- Mt. Meigs & Lewis
- Mt. Meigs & Capitol
- Capitol & Miriam
- Capitol & Yougene
- Capitol & Palmetto
- Capitol & Highland
- Putnam & Highland
- Putnam & Plum
- Putnam & Cherry
- Cherry & Boyce
- Cherry & Arthur
- Arthur & Plum
- Plum & Boyce
- Plumb & Highland
- Highland & Arthur
- Highland & Buford
- Highland & Polk
- Highland & Ryan
- Highland & Charles
- Highland & Panama
- Highland & Grace
- Ann & Plum
- Ann & Cherry
- Ann & Locust
- Ann & Poplar
- Ann & Chesnut
- Zelda & Ann
- Zelda & F Scott
- Zelda & Gatsby Dr.
- Zelda & Gatsby Ln. North
- Zelda & Gatsby Ln. South
- Zelda & Malone
- Zelda & Fitzgerald
- Zelda North of Vaughn
- Carter Hill @ Vaughn
- Vaughn at Montgomery Academy
- Vaughn & Wentworth
- Vaughn & Croom
- Vaughn & Hillwood
- Vaughn & Vaughn Ln
- Vaughn & Fairforest
- Vaughn & Radcliffe
- Vaughn & Shoreham
- Vaughn & Perry Hill
- Vaughn & Green Acres
- Vaughn & Talbot
- Vaughn & Worley
- Vaughn & Kingsbury
- Vaughn & Cottingham
- Fairlane & Vaughn
- Vaughn & Young Farm
- Vaughn & Central
- Vaughn & US 80 Service
- Vaughn & Vaughn Plaza
- Vaughn & Carriage Brook
- and 1591 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 78.5 | first check |
| 2026-07-30 | 78.5 | no change |
| 2026-07-31 | 78.5 | no change |
| 2026-08-01 | 78.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning1841 instances
1841 of 1841 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 (opens the GTFS Schedule reference on an external site)
- Warning1161 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning666 instances
666 of 666 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 (opens the GTFS Schedule reference on an external site)
- Warning12 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 (opens the validator rules on an external site)
- Warning2 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 (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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 (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.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make 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 152 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 666 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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 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 152 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 1161 of 1841 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 151 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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 80 / 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. FTA NTD readiness also checks that the published feed is valid.
- 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. FTA NTD readiness also checks that the published feed is current.
- Rider experience 60 / 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/montgomery-transit/2026-08-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-08-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.