Feed status · checked 2026-08-01
City Coach
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
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 80 minutes ago; last changed 41 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
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 32 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 in its category
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
168 of 190 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 +22 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
262 of 262 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
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
- Service data ended 32 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- 168 of 190 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
- 262 of 262 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
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.
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. 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_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.
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 was 32 days ago.
- Published accessibility data
- Accessibility information is stated for 11.6% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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.
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 3 kinds of issue across 4 instances (0 error, 4 warning, 0 informational).
Service data ended 32 day(s) ago. Trip planners have likely already dropped this feed.
12% of stops state wheelchair accessibility (12% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
12% of stops state accessibility (12% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (5).
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.
177 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Mason St. at Merchant St.", "Mason St. at Wilson St. (Sutter Health)", "Markham Ave. at Little Caesars Pizza", 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.
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 190 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.
- 2 (orange)
- 3 (pink)
- 4 (green)
- 5 (teal)
- 6 (brown)
| Route | Type | Line color |
|---|---|---|
| 2 Route 2 | Bus | orange |
| 3 Route 3 | Bus | pink |
| 4 Route 4 | Bus | green |
| 5 Route 5 | Bus | teal |
| 6 Route 6 | Bus | brown |
List every stop
- Vacaville Transportation Center
- Vacaville Transit Plaza
- Orange Tree Cir at Orange Dr
- Orange Dr at Harly Davidson
- Burton Dr.
- Burton Dr. at Nut Tree Rd.
- Nut Tree Rd. at Burton Dr.
- Leisure Town Rd. at Quick Quack Car Wash
- Orange Dr. at Leisure Town Rd.
- Burton Dr. at Nut Tree Rd. (Outlets)
- Burton Dr. at Helen Power Dr. (Sam's Club)
- Orange Dr at Leisure Town
- Lawrence Dr at Vacaville Senior Manor
- Orange Dr. at I-505 N
- Orange Tree Cir at Diamond Grove
- Elmira Rd. at Allison Dr.
- Mason St. at Hawaiian Building
- Merchant St. at Cernon St.
- Merchant St. at City Hall
- Merchant St. at Orchard Ave.
- N. Orchard Ave. at Anita Ct. (Recycle)
- Buck Ave. at Eldridge Ave.
- Buck Ave. at Buck Mansion
- Monte Vista at Boost Mobile
- Brown St. at E. Monte Vista Ave.
- Brown St. at Hazel St.
- Brown St. at Mobile Home Park
- Brown St. at Bennett Hill Dr.
- Brown St. at School Bus Yard
- Brown St. at Markham Ave. (Church)
- Brown St. at Woodcrest Dr.
- Browns Valley Rd. at Shannon Dr.
- Tipperary Dr. at Longford Ln.
- Tipperary Dr. at Wexford Ln.
- Tipperary Dr. at Waterford Dr.
- Tipperary Dr. at Roscommon Pl.
- Tipperary Dr. at Bantry Dr.
- Tipperary Dr. at Browns Valley Rd.
- Browns Valley Rd. at In-Shape
- Glen Eagle Way at Browns Valley Rd.
- Glen Eagle Way at Silver Eagle
- Glen Eagle Way at Wrentham Dr.
- Wrentham Dr. at Graylyn Ct.
- Wrentham Dr. at Harwinton Ct.
- Wrentham Dr. at Wethersfield Dr.
- Wrentham Dr. at Rollingwood Ct.
- Wrentham Dr. at Browns Valley Rd.
- Brown St. at Markham Ave.
- Eldridge Ave. at Buck Ave.
- Hemlock St. at N. Orchard Ave. (Ball Field)
- N. Orchard Ave. at Acacia St.
- Elder St. at Jepson School
- N. Orchard Ave. at FoodFair
- Hume Way at Costco
- Peabody Rd. at 99 Cent Store
- Solano Community College
- Kaiser Hospital
- Orange Dr. at Gilley Way (Dodge)
- Lawrence Dr at Motel 6
- Harbison Dr. at Nut Tree Pkwy. (Burlington Coat Fa
- Orange Dr. at Nut Tree Rd.
- Crescent Dr. at Stratton Ranch Rd.
- Crescent Dr. at Parkside Dr.
- Crescent Dr. at Quinn Rd.
- Orange Dr. at Orange Tree Cir. (DMV)
- Orange Tree Cir. at Amethyst Dr. (Diamond Grove)
- Nut Tree Pkwy. at Grocery Outlet
- Harbison Dr. at Safeway
- Helen Power Dr. at Baskin Robins
- Helen Power Dr. at Burton Dr. (Walmart)
- Nut Tree Rd. at Arcadia Dr.
- Nut Tree Rd. at Ulatis Dr.
- Nut Tree Rd. at North Bay Way
- Nut Tree Rd. at Elmira Rd.
- Nut Tree Rd. at Vaca Pena Middle School
- Nut Tree Rd. at Marshall Rd.
- Nut Tree Rd. at Bel Air Dr.
- Nut Tree Rd. at Alamo Dr.
- Alamo Dr. at Nut Tree Rd.
- Alamo Dr. at Bel Air Dr.
- Alamo Dr. at Peabody Rd. (Lucky Store)
- Alamo Dr. at Peabody Rd. (Chevron)
- Alamo Dr. at Rosewood Ln.
- Alamo Dr. at Mariposa Ave.
- Alamo Dr. at Alamo Ln.
- Alamo Dr. at Davis St.
- Alamo Dr. at Whitehall Way
- Alamo Dr. at La Cruz Ln.
- Alamo Dr. at Marshall Rd.
- Alamo Dr. at Butcher Rd.
- Merchant St. at Alamo Dr.
- Merchant St. at Elm St.
- Merchant St. at Stevenson St.
- Dobbins St. at McBride Senior Center
- Alamo Dr. at Butcher Rd.
- Alamo Dr. at Marshall Rd. (3 Oaks)
- Alamo Dr. at Beythe Ln.
- Alamo Dr. at Alamo Ct.
- Alamo Dr. at Alamo Ln.
- Alamo Dr. at Mariposa Ave.
- Alamo Dr. at Fire House
- Alamo Dr. at Wildwood Ln. (Rose Garden Apartments)
- Alamo Dr. at Peabody Rd. (Walgreens)
- Alamo Dr. at Marna Dr.
- Alamo Dr. at Farmington Dr.
- Alamo Dr. at Needham Dr.
- Nut Tree Rd. at Alamo Dr. (Autumn Leaves)
- Nut Tree Rd. at Woodridge Dr.
- Nut Tree Rd. at Bel Air Dr.
- Nut Tree Rd. at Marshall Rd.
- Nut Tree Rd. at Vaca Pena Middle School
- Nut Tree Rd. at Elmira Rd.
- Nut Tree Rd. at North Bay Way
- Nut Tree Rd. at Yellowstone Dr.
- Burton Dr. at Helen Power Dr.
- E. Monte Vista Ave. at Amici's Pizza
- E. Monte Vista Ave. at Best Buy
- E. Monte Vista Ave. at Browns Valley Pkwy. (Taco B
- E. Monte Vista Ave. at Allison Dr. (Goodwill)
- E. Monte Vista Ave. at Brown St.
- Rocky Hill Rd. at Lomita Ave.
- Rocky Hill Rd. at Novato Dr.
- Meadows Dr. at Rocky Hill Rd..
- Markham Ave. at Meadows Dr.
- Markham Ave. at Wesley Ave.
- Markham Ave. at E. Monte Vista Ave. (Lucky Store)
- Mason St. at Merchant St.
- Mason St. at Wilson St. (Sutter Health)
- Markham Ave. at Little Caesars Pizza
- Markham Ave. at Rocky Hill Rd.
- Markham Ave. at Meadows Dr.
- Meadows Dr. at Rocky Hill Rd.
- Rocky Hill Rd. at Novato Dr.
- Rocky Hill Rd. at Manzanita Dr.
- Markham Ave. at Markham Elementry School
- Brown St. at Markham Elementry School
- Brown St. at Bennett Hill Dr.
- Brown St. at Rocky Hill Trail
- Brown St. at Hazel St. (Church)
- Brown St. at E. Monte Vista Ave.
- E. Monte Vista Ave. at Mexico Meat Market
- E. Monte Vista Ave. at Allison Dr.
- E. Monte Vista Ave. at Browns Valley Pkwy.
- E. Monte Vista Ave. at Bodin SF
- Nut Tree Pkwy. at Outlets
- Aegean Way at Meadowood Apartments
- Aegean Way
- Aegean Way at Mobile Home Park
- Peabody Rd. at Elmira Rd. (Carl's Jr.)
- Peabody Rd. at Hume Way
- Peabody Rd. at Marshall Rd.
- Beelard Dr. at Peabody Rd.
- Beelard Dr. at Tulare Dr.
- Beelard Dr. at Beelard Park
- Marshall Rd. at Hidden Creek Apartments
- Marshall Rd. at Nut Tree Rd. (Nelson Park)
- Marshall Rd. at Dumbarton Dr.
- Vanden Rd. at Bluebird Dr.
- Vanden Rd. at Harvest Dr.
- Alamo Dr. at Nut Tree Rd. (7 Flags)
- Nut Tree Rd. at Alamo Dr.
- Nut Tree Rd. at Needham Dr.
- Youngsdale Dr. at Nut Tree Rd.
- Youngsdale Dr. at Ruby Dr.
- Youngsdale Dr. at Marna Dr.
- Youngsdale Dr. at Morning Glory Dr.
- Morning Glory Rd. at Peabody Rd.
- Peabody Rd. at California Dr.
- Peabody Rd. at Alamo Dr.
- Peabody Rd. at Alamo Dr. (Lucky Store)
- Peabody Rd. at Beelard Dr.
- Will C. Wood High School
- Marshall Rd. at Dowline Dr.
- Marshall Rd. at Aberdeen Way
- Marshall Rd. at Davis St.
- Davis St. at Winco
- Davis St. at Brenden Theaters
- Davis St. at Stevenson St.
- Davis St. Park & Ride
- Davis St. Park and Ride
- Davis St. at Self Storage
- Davis St. at Kingman Dr.
- Marshall Rd. at Davis St.
- Marshall Rd. at Padan Park
- Marshall Rd. at Bowline Dr.
- Will C. Wood High School
- Peabody Rd. at Prairie Ct. (Shell Station)
- Elmira Rd. at Shasta Dr.
- Allison Dr. at Elmira Rd.
- Vanden Rd. at Marshall Rd.
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 53.5 | first check |
| 2026-07-30 | 53.5 | no change |
| 2026-07-31 | 53.5 | no change |
| 2026-08-01 | 53.5 | 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-31.
Same feed file as 2026-07-31; 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
7 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 32 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.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning262 instances
262 of 262 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)
- Warning168 instances
168 of 190 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)
- 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'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.)
Finding code: feed_expiration_date7_days · 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.)
Finding code: 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.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 32 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 32 days ago, so FTA would find the link out of date.
- 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 262 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. Service data expired 32 days ago. States wheelchair access on 12% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 32 days ago.
- Accessible Not yet
- States wheelchair access on 12% 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.
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
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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (4 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 12% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 262 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 88 / 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 0 / 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 48 / 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.
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/city-coach/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.