Feed status · checked 2026-10-07
JAUNT Inc
Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-06
Cataloged in Virginia.
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 39 minutes ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
JAUNT Inc’s published feed lists 7 bus routes, 145 scheduled trips and 46 stops. The published file has not changed since our first check on 2026-06-19.
Top things to fix
Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool
Service data ended 1376 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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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.
- Virginia 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-10-05.
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.
Fix 01 · Read the fix guide for scorecard_feed_expired
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
- The feed's last published service date was 1376 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 8 instances (7 error, 1 warning, 0 informational).
Service data ended 1376 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
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (BUCK-E, BUCK-N, LOVE).
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.
31 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Emmet St @ Central Grounds Garage", "Emmet St @ Ridley Hall", "Freedom Blvd @ Edmond Dr", 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 46 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.
- 29N (blue)
- BUCK-E (blue)
- BUCK-N (purple)
- CROZ-E (teal)
- CROZ-L (white)
- CROZ-W (teal)
- LOVE (red)
| Route | Type | Line color |
|---|---|---|
| 29N 29 North CONNECT | Bus | blue |
| BUCK-E Buckingham East CONNECT | Bus | blue |
| BUCK-N Buckingham North CONNECT | Bus | purple |
| CROZ-E Crozet East CONNECT | Bus | teal |
| CROZ-L Crozet CONNECT Loop | Bus | white |
| CROZ-W Crozet West CONNECT | Bus | teal |
| LOVE Lovingston CONNECT | Bus | red |
List every stop
- Barracks Road McDonalds (North)
- Barracks Road McDonalds (South)
- Dillwyn Food Lion
- Duck's Corner Store
- Emmet St @ Central Grounds Garage
- Emmet St @ Ridley Hall
- Fontaine Research Park
- Food Lion Hollymead
- Freedom Blvd @ Edmond Dr
- Hydraulic Ridge Rd
- Jarman Lake Rd @ Grayrock Rd
- Jarmans Gap Rd @ Old Trail Rd
- Jefferson Park Ave @ Brandon Ave
- Jefferson Park Ave @ Cabell Hall
- Jefferson Park Ave @ Pinn Hall
- Jefferson Park Ave @ West Complex
- Lee St @ UVA Cancer Center
- Lee St @ UVA Health System
- Lockwood Dr @ Abington Place Plaza
- Martha Jefferson Hospital
- Mechums River Rd @ Amber Ridge Rd
- Midway Market
- Nelson Center
- Old Trail Rd @ Jarmans Gap Rd
- Old Trail Rd @ Old Trail Village Center
- Old Trail Rd @ Old Trail Village Center
- Our Lady of Peace
- PVCC Stultz Center
- Park Ridge Dr @ Cardinal Crest Ct
- Park Ridge Dr @ Eastern Dr
- Park Ridge Dr @ Stonegate Ln
- Re-Store 'N Station
- Scottsville Farmer's Market Pavilion
- Summerford Ln @ Welbourne Ln (East)
- Summerford Ln @ Welbourne Ln (West)
- Thomas Nelson Hwy @ River Rd
- Three Notchd Rd @ East Downtown Crozet
- Three Notchd Rd @ Starr Hill Brewery
- Towncenter Dr @ Community St
- UVA Medical Center Loading Dock (Lane Rd)
- Virginia Institute for the Blind
- Water St @ Omni Hotel
- Westminster Canterbury
- Whitehead Rd @ Rice Hall
- Whitehead Rd @ Rice Hall
- Wickham Pond Dr @ Clubhouse
Over time
Overall score across the last 4 checks — unchanged since 2026-10-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 38.0 | first check |
| 2026-08-07 | 38.0 | no change |
| 2026-10-06 | 38.0 | no change |
| 2026-10-07 | 38.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
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-08-06 to 2026-10-07 (4 checks) | d1f6ff161e0d | 2022-12-31 | Current rubric: see the trend above |
| 2026-06-19 to 2026-07-10 (16 checks) | d1f6ff161e0d | not recorded | F, 26.2 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-06.
Same feed file as 2026-10-06; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
10 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)
- Error1 instance
Service data ended 1376 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. Set feed_end_date in feed_info.txt 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 for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning145 instances
145 of 145 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning46 instances
46 of 46 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference 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)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
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 for scorecard_missing_feed_info_dates · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 3 validator errors to resolve. Service data expired 1376 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 3 validator errors to resolve.
- Current Not ready
- Service data expired 1376 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 145 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 does not meet the conformance requirements yet. Here is what the mark needs: 3 validator errors to resolve. Service data expired 1376 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 3 validator errors to resolve.
- Current Not yet
- Service data expired 1376 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. 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 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 38 / 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 Virginia portfolio: the same scorecards for every feed we track in that group, on one free page.
For programs that support several agencies
This scorecard and the board one-pager for JAUNT Inc are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for JAUNT Inc uses the same numbers as this page: grade F (38.0 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.3 and MobilityData gtfs-validator 8.0.1. Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
Similar feeds in Virginia
Other scorecards in Virginia, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/jaunt-inc/2026-10-07.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-10-07. 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.