The feed address on file failed at our last check (HTTP 404). Download the newest saved copy from the Mobility Database, or send us the new address.
Feed status · checked 2026-11-09
Xpress
Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified
Scored from a Mobility Database mirror copy downloaded on 2026-10-02, because the feed URL on file could not be downloaded. Service dates in that copy run 2024-01-02 to 2025-07-05. It may not match the feed the agency publishes today.
Service mode Bus
Partial: freshness not measured.
Methodology changed; trend restarts here
Cataloged in Georgia.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://gamobility.info/wp-content/uploads/2024/07/Google_Transit.zip
Failed at last check (HTTP 404) Newest saved copy
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
Check that https://gamobility.info/wp-content/uploads/2024/07/Google_Transit.zip still serves your current feed. If the feed moved, publish the new address.
The feed URL on file, https://gamobility.info/wp-content/uploads/2024/07/Google_Transit.zip, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2025-07-05, so freshness is not graded until the current feed can be downloaded.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Usually a server or hosting setting, not a change to the feed itself.
Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid input files in subfolder (flagged by the MobilityData validator). See the linked rule for what this affects.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Varies.worth about +12 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Georgia as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
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.
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.
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
- Schedule visibility is not known from this scorecard.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 100% 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 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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
Xpress’s published feed lists 30 bus routes, 197 scheduled trips and 96 stops. The published file has not changed since our first check on 2026-06-19.
Score by category
The MobilityData validator flagged 4 kinds of issue across 8 instances (7 error, 1 warning, 0 informational).
Not graded. The feed URL on file could not be downloaded, and the Mobility Database mirror copy scored instead ended its service on 2025-07-05. That date describes the copy, not the feed the agency publishes today, so it does not count against the grade.
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.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (419, 423, 426, 428, 430, and more).
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.
65 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Pryor St at Garnett St", "Central Ave at Garnett St", "Mitchell St at Peachtree St", 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 96 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.
- 400 (teal)
- 401 (teal)
- 410 (teal)
- 411 (teal)
- 412 (teal)
- 413 (teal)
- 414 (teal)
- 416 (teal)
- 417 (teal)
- 419 (green)
- 423 (green)
- 426 (green)
- 428 (green)
- 430 (orange)
- 431 (orange)
- 432 (orange)
- 440 (orange)
- 441 (orange)
- 442 (orange)
- 453 (orange)
- 463 (purple)
- 476 (purple)
- 480 (teal)
- 483 (teal)
- 484 (teal)
- 485 (teal)
- 490 (teal)
| Route | Type | Line color |
|---|---|---|
| 400 Cumming - Downtown | Bus | teal |
| 401 Cumming - Perimeter | Bus | teal |
| 410 Sugarloaf Mills - Lindbergh Cent | Bus | teal |
| 411 Hamilton Mill/Mall of GA - MT | Bus | teal |
| 412 Sugarloaf Mills - Midtown | Bus | teal |
| 413 Hamilton Mill/Mall of GA - DT | Bus | teal |
| 414 Ham Mill/Mall of GA/Sugarloaf-MT | Bus | teal |
| 416 Dacula - Downtown | Bus | teal |
| 417 Sugarloaf Mills - Perimeter | Bus | teal |
| 419 Snellville/Hewatt/Stone Mtn - DT | Bus | green |
| 423 E Conyer/W Conyer/Panola - MT | Bus | green |
| 426 E Conyer/W Conyer/Panola - DT | Bus | green |
| 428 W Conyers/Panola - Perimeter | Bus | green |
| 430 McDonough - Downtown | Bus | orange |
| 431 BrandsMart/Stockbridge - MT | Bus | orange |
| 432 BrandsMart/Stockbridge - DT | Bus | orange |
| 440 Hampton/Jonesboro - DT/MT | Bus | orange |
| 441 Jonesboro - Downtown/Midtown | Bus | orange |
| 442 Riverdale - Downtown | Bus | orange |
| 453 Newnan/Union City - DT/MT | Bus | orange |
| 463 W Douglas/Douglas MMTC - DT/MT | Bus | purple |
| 476 Hiram/Powder Springs - DT/MT | Bus | purple |
| 480 Acworth/Town Center - Downtown | Bus | teal |
| 483 Woodstock/Town Center - Midtown | Bus | teal |
| 484 Hickory Grove - Midtown | Bus | teal |
| 485 Hickory Grove - Downtown | Bus | teal |
| 490 Woodstock - Downtown | Bus | teal |
| 999 Test Route | Bus | white (no shape in feed) |
| 9999 Test Route NORTH OPS | Bus | white (no shape in feed) |
| 99999 Test Route for COBB Garage | Bus | white (no shape in feed) |
List every stop
- Pryor St at Garnett St
- Central Ave at Garnett St
- Mitchell St at Peachtree St
- Ted Turner Dr (S) at Brotherton St
- Ted Turner Dr (N) at Brotherton St
- Peachtree Center Ave at Peachtree St
- Acworth Park and Ride
- BrandsMart Park and Ride
- Cumming Park and Ride
- Dacula Park and Ride (Hebron Church)
- Douglas MMTC Park and Ride
- East Conyers Park and Ride
- Hamilton Mill Park and Ride
- Hampton Park and Ride
- Hewatt Rd Park and Ride
- Hiram Park and Ride
- Jonesboro Park and Ride
- Mall of Georgia Park and Ride
- McDonough Park and Ride
- Newnan Park and Ride
- Panola Rd Park and Ride
- Powder Springs Park and Ride
- Riverdale Park and Ride
- Snellville Park and Ride
- Stockbridge Park and Ride
- Stone Mountain Park and Ride
- Town Center/Big Shanty Park and Ride
- Union City Park and Ride
- West Conyers Park and Ride (DT)
- West Douglas Park and Ride
- Woodstock Park and Ride
- Ivan Allen at Alexander St
- John Portman Blvd at Peachtree St
- Mitchell St at Forsyth St
- Pryor St at Mitchell St
- Ted Turner Dr at Mitchell St
- Wall St at Central Ave
- Williams St at Baker St
- Baker St at Williams St
- North Ave at Peachtree St
- Spring St at 17th St
- Spring St at 5th St
- Spring St just before Linden Ave
- Arts Center Station
- Peachtree-Dunwoody Rd at Concourse Pkwy
- Peachtree-Dunwoody Rd at Concourse Pkwy
- Perimeter Center at Perimeter Center Pkwy
- Perimeter Center West at Perimeter Center Pkwy
- Perimeter Center Pkwy Office Park (N)
- Perimeter Center Pkwy Office Park (S)
- Medical Center Station
- Sandy Springs Station
- Dunwoody Station
- Thornton Rd (N) at Bankhead Hwy
- Thornton Rd (S) at Maxham Rd
- Thornton Rd (N) at Maxham Rd
- Thornton Rd (N) at North Blairs Bridge Rd
- Thornton Rd (S) at North Blairs Bridge Rd
- Thornton Rd at Oak Ridge Rd
- Thornton Rd at Skyview Dr
- Thornton Rd at Westfork Blvd
- Lindbergh Center Station
- Baker St at Peachtree St
- Central Ave at Wall St
- John Portman Blvd at Courtland St
- Peachtree Center Ave at Auburn Ave
- Civic Center Station (NB)
- Civic Center Station (SB)
- West Peachtree St at Peachtree Pl
- West Peachtree St at 5th St
- North Ave Station
- West Peachtree St after 14 St
- Sugarloaf Mills GCT Park and Ride
- Baker St at Peachtree St
- 17th St at Spring St
- 17th St at Market St
- West Conyers Park and Ride (MT/Peri)
- Ponce De Leon Ave at W Peachtree St
- Thornton Rd (S) at Bankhead Hwy
- Hickory Grove Park and Ride
- Peachtree St at Five Points Station
- Washington St at MLK Jr Dr
- Central Ave at Mitchell St
- Courtland St at Auburn Ave
- Courtland St at Ellis St
- Courtland St at Gilmer St
- Forsyth St at MLK Jr Dr
- MLK Jr Dr at Peachtree St
- Central Ave at MLK Jr Dr
- Peachtree Center Ave at Andrew Young Int'l Blvd
- Peachtree Center Ave at John Wesley Dobbs Ave
- Peachtree St at Baker St
- Peachtree St at Renaissance Pkwy
- Ted Turner Dr at West Peachtree Pl
- West Peachtree St at 12th St
- Xpress Sugarloaf Mills P&R
Over time
The producer or measurement contract changed since the prior check, so the trend restarts here. No improvement or regression is claimed across that boundary.
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-09 | 9116a4abc7d5 | not recorded | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | 9116a4abc7d5 | 2025-07-05 | F, 57.5 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-05 to 2026-10-01 (23 checks) | 9116a4abc7d5 | 2025-07-05 | F, 57.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-16 (4 checks) | 9116a4abc7d5 | not recorded | F, 26.2 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (21 checks) | 9116a4abc7d5 | not recorded | F, 26.2 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
4 findings, ordered by severity.
Show every finding
- Error5 instances
Missing required file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid input files in subfolder (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_input_files_in_subfolder · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Missing calendar and calendar date files (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_calendar_and_calendar_date_files · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
How we measured this
Checked for changes 18 hours ago; last fetch returned HTTP 404.
Measured 2 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Freshness and Realtime quality were not measured this run. They do not count against the grade.
- The configured feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead. Publisher ownership of the configured URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
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.4, validator 8.0.1.
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 3 validator errors to resolve. No service end date could be read, so currency is unknown.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 3 validator errors to resolve.
- Current Not ready
- No service end date could be read, so currency is unknown.
- 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 197 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
Two requirements remain for this feed to earn the conformance mark. 3 validator errors to resolve. No service end date could be read.
- Valid Not yet
- 3 validator errors to resolve.
- Current Not yet
- No service end date could be read.
- Accessible Met
- States wheelchair access on 100% 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.
Below the Google and Apple Maps four-week coverage bar. This feed has no service end date, so Maps cannot tell how far ahead it runs. Set a feed_info end date and a calendar that covers at least the next four weeks, then re-export. The feed also carries 7 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 60 / 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 Not yet published
- 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 100 / 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.
Part of the Georgia portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Georgia
Other scorecards in Georgia, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/xpress-2355/2026-11-09.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-11-09. 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.