Feed status · checked 2026-08-01
Jump Around Carson
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Nevada.
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 75 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 1674 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
159 of 159 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
86 of 86 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
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 1674 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
- 159 of 159 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
- 86 of 86 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. 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.
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. 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.
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. 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
- The feed's last published service date was 1674 days ago.
- 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
- 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 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 4 kinds of issue across 6 instances (0 error, 6 warning, 0 informational).
Service data ended 1674 day(s) ago. Trip planners have likely already dropped this feed.
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 not published.
0% of stops state accessibility (0% 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 (1).
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.
155 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Desatoya & Glacier", "Ormsby & Oak Ridge Westbound", "Airport & Minonee", 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 159 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.
- 2B (yellow)
- 3 (purple)
- 2A (yellow)
- 1 (red)
| Route | Type | Line color |
|---|---|---|
| 2B Route 2B - North Town (Counter Clockwise) | Bus | yellow |
| 3 Route 3 - South Carson Area | Bus | purple |
| 2A Route 2A - North Town (Clockwise) | Bus | yellow |
| 1 Route 1 - North Carson Area | Bus | red |
List every stop
- Plaza & Washington - Downtown Transfer Plaza
- Robinson & Anderson
- Roop & Washington/Community Center
- Roop & Beverly
- Beverly & Roop/Senior Center (Outbound)
- Beverly & Marian/Autumn Village I (Outbound)
- Long & Marian/Autumn Village II (Outbound)
- Long/Health & Human Services (Outbound)
- Winnie & Lone Mountain
- Carson & Hot Springs/C-A-L Ranch
- Hot Springs & Northgate/Safari Mobile Home Vil.
- Hot Springs & Pine Northbound
- Hot Springs & Retail/Walmart (Outbound)
- College Parkway & Diamond
- College Parkway & Granite
- College Parkway & Imperial
- Carson & Silver Oak/Holiday Inn Express
- Medical & Carson
- Medical Parkway/Carson Tahoe Regional Medical Center - Main Entrance
- Medical Parkway/Merrimer Cottages
- Carson Tahoe Cancer Center
- Carson Medical Group-Pediatrics
- Sierra Surgical Hospital
- Medical Parkway & Vista
- College Parkway & Carson/Burger King
- College Parkway & Northgate
- Roop & College Parkway (Outbound)
- Hot Springs/Crestview Mobile Home Park
- Hot Springs & Northgate
- Winnie & Carson Frontier Plaza
- Roop & Stewart Southbound
- Roop & Long
- Roop & Washington/Public Library
- Robinson & Walsh
- Washington & Curry
- Division & Ann
- Fleischmann & Division
- Mountain & Bath Northbound
- Mountain & Ivy
- Winnie & Mountain
- Winnie & El Rancho
- Ormsby & Oak Ridge Westbound
- Ormsby & Desert Peach Northbound
- Ormsby & Evergreen Northbound
- College Parkway & Ormsby Westbound
- College Parkway & College Westbound
- Western Nevada College
- College Parkway & College Eastbound
- College Parkway & Ormsby Eastbound
- College Parkway & GS Richards
- Research & College Parkway Northbound
- Old Hot Springs Rd. & Wedco Eastbound
- Old Hot Springs Rd. & Goni
- Goni & Research
- Research & College/Neveda Health Center
- College Parkway & Goni
- College Parkway & Lompa
- College Parkway & Airport
- Woodside & Airport/FoodMaxx
- Monte Rosa & Selby/Park Terrace Park Southbound
- Monte Rosa & Stanton/Empire Elem Sch
- Desatoya & Glacier
- Airport & Desatoya
- Airport & Minonee
- Menlo & Airport
- Lompa & U.S. 50
- Lompa & Dori
- Lompa & Carmine
- Russell & Northridge (MAC) southbound
- Russell/Foothill Garden Apartments
- Long/Carson Plaza
- Long & Rand
- Long & Molly
- Long & Saliman Eastbound
- Long & Russell
- Russell & Long
- Russell & Northridge (MAC) northbound
- Menlo & Lompa
- Airport & Menlo
- Desatoya & Airport
- Monte Rosa & Desatoya
- Monte Rosa & Selby/Park Terrace Park Northbound
- Woodside & Sharon/FoodMaxx
- Airport & U.S. 50 Northbound
- Airport & Carmine
- Airport & Sherman northbound
- Airport & Harrison
- College Parkway/Carson City Airport
- College Parkway & Carson/Save Mart
- Ormsby & College Parkway
- Ormsby & Evergreen Southbound
- Ormsby & Desert Peach Southbound
- Mountain & Winnie
- Mountain & Bath Southbound
- Fleischmann & Lane/Carson Tahoe Spec Medical Ctr
- Division & John
- Division & Washington
- Division & King
- Division & 3rd Outbound
- 10th & Nevada
- Curry & 8th Outbound
- 5th & Plaza
- Stewart & 8th
- Little & Roop
- Roop & Fairview
- California & Industrial Park Southbound
- Silver Sage & Raven
- Silver Sage & Sonoma Southbound
- Silver Sage & Stafford Southbound
- Silver Sage & Vintage
- Koontz & U.S. 395/Seven Star Mobile Home Park
- Curry @ Fandango Southbound
- Clearview & U.S. 395/Save Mart - South (Eastbound)
- Old Clear Creek/Fuji Park
- Clear Creek & U.S. 395
- Clear Creek & Center
- Clear Creek & Snyder/State of Nevada-Stewart Facility
- Silver Sage & Appion
- Silver Sage & Clearview
- Clearview & Oak/Southgate Shopping Center
- Clearview & U.S. 395/Save Mart - South (Westbound)
- Curry @ Fandango Northbound
- Koontz & U.S. 395/Eagle Station
- Silver Sage & Koontz
- Silver Sage & Pioche
- Silver Sage & Stafford Northbound
- Silver Sage & Sonoma Northbound
- Colorado & Silver Sage
- California & Industrial Park Northbound
- Roop & Evalyn
- Roop & Oregon/Governers Field
- Roop & Randell/Post Office
- Little & Stewart/NDOT
- Stewart & 5th
- 5th & Carson/State of Nevada General Assembly
- Roop & Stewart Northbound
- Hot Springs & Pine Southbound
- College Parkway & Silver Stream
- Long & Saliman Westbound
- Carmine & Lompa
- Desatoya & Cascade
- Airport & College
- College Parkway & Challenger
- Ormsby & Oak Ridge Southbound
- Mountain & Fleischmann
- Division & 7th
- Stewart & Little
- Beverly & Roop/Senior Center (Inbound)
- Beverly & Marian/Autumn Village I (Inbound)
- Long & Marian/Autumn Village II (Inbound)
- Long/Health & Human Services (Inbound)
- Hot Springs & Retail/Walmart (Inbound)
- Roop & College Parkway (Inbound)
- Carson & Musser @ City Hall
- Airport & Nye southbound
- Airport & Sherman southbound
- Airport & Nye northbound
- Musser & Roop @ Courthouse
- Airport & U.S. 50 @ CVS
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 50.8 | first check |
| 2026-07-30 | 50.8 | no change |
| 2026-07-31 | 50.8 | no change |
| 2026-08-01 | 50.8 | 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
9 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1674 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)
- Warning159 instances
159 of 159 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)
- Warning86 instances
86 of 86 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)
- 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)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · 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
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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 1674 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 1674 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 86 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 1674 days ago. 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 Not yet
- Service data expired 1674 days ago.
- 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.
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.
- Correctness 84 / 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 45 / 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/jump-around-carson/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.