← All agencies

Feed status · checked 2026-08-01

Victor Valley Transit Authority (VVTA)

Based on the feed this agency publishes

Service mode Bus

43.7 / 100

unchanged since 2026-07-31

Catalogued in California.

Feed expiredAccessibility gapsRealtime not yet published

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 65 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

Fix 01

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 490 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

Fix 02

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

1065 of 1065 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

Fix 03

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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.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 490 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
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.

  1. 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.

  2. 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.

  3. 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. · 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 490 days ago.
Published accessibility data
Accessibility information is stated for 0% of stops and 15.4% 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

Correctness71.5 / 100

The MobilityData validator flagged 7 kinds of issue across 48 instances (0 error, 47 warning, 1 informational).

Freshness0.0 / 100

Service data ended 490 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience39.8 / 100

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.

Accessibility5.8 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 1028 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("E Mountain View St & EB Belinda Ave", "N 2nd Ave NB & Cozy Ave", "Hutchinson St WB & N 1st Ave", 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.

Realtime qualityNot yet measured

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 1065 stops.

Skip to route and stop data

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.

  • 1 (teal)
  • 111 (yellow)
  • 114 (white)
  • 115 (teal)
  • 118 (green)
  • 15 (red)
  • 2 (yellow)
  • 20 (teal)
  • 21 (pink)
  • 22 (green)
  • 23 (teal)
  • 27 (pink)
  • 28 (yellow)
  • 29 (white)
  • 3 (orange)
  • 31 (yellow)
  • 32 (purple)
  • 33 (yellow)
  • 40 (orange)
  • 41 (white)
  • 42 (teal)
  • 43 (yellow)
  • 47 (orange)
  • 49 (yellow)
  • 50 (yellow)
  • 52 (orange)
  • 53 (white)
  • 55 (pink)
  • 56 (teal)
  • 6 (yellow)
  • 64 (yellow)
  • 66 (teal)
  • 68 (white)
Routes in Victor Valley Transit Authority (VVTA)'s feed
RouteTypeLine color
1 Barstow City Hall - Armory + ChateauBusteal
111 Fort Irwin - BarstowBusyellow
114 Fort Irwin - HesperiaBuswhite
115 Fort Irwin - HelendaleBusteal
118 Fort Irwin - Hesperia via BarstowBusgreen
15 Barstow - Victorville - San BenrardinoBusred
2 Barstow City Hall - Barstow CollegeBusyellow
20 Hesperia Super Target - Pinon HillsBusteal
21 Hesperia Super Target - WrightwoodBuspink
22 Victorville - HelendaleBusgreen
23 Apple Valley - Lucerne ValleyBusteal
27 Barstow - HinkleyBuspink
28 Barstow - HelendaleBusyellow
29 Barstow - Newberry SpringsBuswhite
3 Barstow City Hall - LenwoodBusorange
31 Victorville - Highway 395 + CrossroadsBusyellow
32 Victorville - North AdelantoBuspurple
33 Hwy 395 + Crossroads - Bartlett + GreeningBusyellow
40 Apple Valley Post Office - WalmartBusorange
41 Apple Valley - VictorvilleBuswhite
42 Victor Valley College - Public Safety Training CenterBusteal
43 Apple Valley Post Office - Victor Valley CollegeBusyellow
47 Apple Valley Post Office - Bear Valley + NavajoBusorange
49 Apple Valley - Victor Valley MallBusyellow
50 Victorville - HesperiaBusyellow
52 Victor Valley Transportation Center - Mall of Victor ValleyBusorange
53 Victor Valley College - Mall of Victor ValleyBuswhite
55 Victor Valley Transportation Center - Victor Valley CollegeBuspink
56 Victor Valley Transportation Center - Lorene + 7thBusteal
6 Barstow City Hall - Rimrock + N StBusyellow
64 Hesperia Post Office - Super TargetBusyellow
66 Hesperia East DeviationBusteal
68 Hesperia Post Office - Super TargetBuswhite
List every stop
  • Armory Rd EB & Chateau Way NS
  • Arbor Way NB & Sierra Linda Dr FS
  • Arbor Way NB & Guaco Ave FS
  • Victor St SB & E Main Street
  • Arbor Way SB & Guaco Ave NS
  • Arbor Way SB & Sierra Linda Dr Ns
  • Armory Rd WB & Barstow Rd FS
  • Agarita Ave SB & Armory Rd FS
  • Agarita Ave SB & Cypress Dr NS
  • Rimrock Rd EB & Agarita Ave FS
  • Rimrock Rd EB & Barstow Rd NS
  • H Ave SB & Rimrock Rd
  • Brucite Rd WB & H St
  • Brucite Rd WB & K St FS
  • Rimrock Rd WB & Barstow Rd FS
  • Rimrock Rd WB & Agarita Ave
  • Agarita Rd NB & Cypress Dr FS
  • Armory Rd EB & Agarita Rd
  • Armory Rd EB & Wisteria Ave
  • Rimrock Rd EB & N St FS
  • Rimrock Rd EB & H Ave
  • Rimrock Rd EB & Agarita Ave
  • Rimrock Rd EB & K Ave FS
  • Hwy 18 EB & Trade Post Rd
  • Baldy Mesa Rd NB & Yucca Terrace Dr
  • Baldy Mesa Rd NB & 7th St
  • Duncan Rd EB & Baldy Mesa Rd
  • Bear Valley Rd EB & Hwy 395
  • Bear Valley Rd EB & Marina Ln
  • Bear Valley Rd EB & Jade Rd NS
  • Anacapa Rd SB & Park Ave E
  • Park Ave SB & Bonanza Rd
  • Amargosa Rd SB & Dos Palmas Rd
  • Phelan Rd WB & Lilac Rd
  • Phelan Rd WB & Braceo St
  • Pahute Ave WB & Tonikma Rd
  • Pahute Ave WB & Quinnault Rd
  • Pahute Ave WB & Pawnee Rd
  • Pahute Ave WB & Navajo Rd
  • Pahute Ave WB & Algonguin Rd
  • Pahute Ave WB & Tamiani
  • Kiowa Rd EB & Pahute Rd
  • Pahute Ave EB & Tamiani
  • Pahute Ave EB & Algonguin Rd
  • Community Blvd EB & Mountain View
  • Community Blvd EB & Lenwood Rd
  • Community Blvd EB & Rifle Rd
  • Old Hwy 58 EB & Ramirez Rd
  • Old Hwy 58 EB & Gladys Dr
  • Irwin Rd NB & Old Hwy 58
  • Old Hwy 58 EB & Camarillo Ave
  • Old Hwy 58 EB & Muriel Dr
  • Old Hwy 58 EB & Leona Rd
  • Old Hwy 58 EB & Hawthorne Dr
  • Yucca Ave NB & Suncrest Apts
  • Riverview Dr EB & Carmen Dr
  • Yucca Ave SB & Riverview Apts
  • Yucca Ave SB & Mountain View St NS
  • Yucca Ave NB & Mountain View St
  • Old Hwy 58 WB & Hawthorne Dr
  • Old Hwy 58 WB & Muriel Dr
  • Old Hwy 58 WB & Camarillo Ave
  • Irwin Rd SB & Old Hwy 58
  • Old Hwy 58 WB & Vernon Dr
  • Old Hwy 58 WB & Ramirez Rd
  • Amargosa Rd SB & Luna Rd
  • Mariposa Rd NB & Nisqualli Rd
  • Yucca Loma Rd WB & Kiowa Rd
  • Yucca Loma Rd WB & Seminole Rd
  • Yates Rd WB & Park Rd
  • Hesperia Rd SB & Winona St
  • W Main St WB & Lenwood Rd
  • W Main St EB & Lenwood Rd
  • Cobalt Rd NB & Dos Palmas Rd
  • Cobalt Rd NB & Palmdale Rd
  • Seneca Rd EB & Cobalt Rd
  • Nisqualli Rd EB & Mariposa Rd
  • Nisqualli Rd EB & Arrowhead Dr
  • 7th St NB & Lorene Dr
  • Hesperia Rd NB & Comanche St
  • Yates Rd EB & Park Rd
  • Yucca Loma Rd EB & Havasu Rd
  • Yucca Loma Rd EB & Apple Valley Rd
  • Yucca Loma Rd EB & Seminole Rd
  • Seneca Rd WB & Amargosa Rd
  • Cobalt Rd SB & Seneca Rd
  • Cobalt Rd SB & Palmdale Rd
  • Cobalt Rd SB & Dos Palmas Rd
  • Dos Palmas Rd WB & Topaz Rd
  • Dos Palmas Rd WB & Mesa Linda Ave
  • Bellflower St SB & Shanandoah St
  • Outer Hwy 18 North NB & Thunderbird Rd
  • Bass Hill Rd EB & Westlund Way
  • Dale Evans Pkwy SB & Westlund Way
  • Outer Hwy 18 North WB & Jicarilla Rd
  • Zuni Rd EB & Serrano Rd
  • Zuni Rd EB & Witchita Rd
  • Dale Evans Pkwy NB & Otoe Rd
  • Dale Evans Pkwy NB & Waalew Rd
  • Navajo Rd NB & Lafayette St
  • Navajo Rd SB & Lafayette St
  • Dale Evans Pkwy SB & Waalew Rd
  • Dale Evans Pkwwy SB & Otoe Rd
  • Zuni Rd WB & Witchita Rd
  • Zuni Rd WB & Serrano Rd
  • Kiowa Rd SB & Pahute Ave
  • Hesperia Rd NB & Nisqualli Rd
  • Yucca Loma Rd EB & Choco Rd
  • Yucca Loma Rd WB & Choco Rd
  • Quinnault Rd NB & PO Driveway
  • Yucca Loma Rd WB & Havasu Rd
  • N St NB & Brucite Rd
  • Navajo Rd NB & Pahute Ave
  • Montara Rd NB & Armory Rd (DO)
  • Williams Park & Ride (DO)
  • L St Park & Ride (DO)
  • VVTC - Dock 3 (DO)
  • Bear Valley Park & Ride (DO)
  • Child Development Center (DO)
  • Mates & South Depot Loop (DO)
  • Inner Loop & Burger King (DO)
  • Inner Loop & Langford Lake Rd (DO)
  • Inner Loop & 4th St (DO)
  • Weed Army Hospital (DO)
  • 5th St & D Ave (DO)
  • Fort Irwin Bus Lot (DO)
  • Vista Rd EB & Helendale Rd (DO)
  • Quinnault Rd NB & PO Driveway
  • Pinon Hills Community Center
  • Phelan Rd EB & Sheep Creek Rd
  • Phelan Rd EB & Sierra Vista Rd
  • Phelan Rd EB & Johnson Rd
  • Phelan Rd EB & Eaby Rd
  • Phelan Rd EB & Wilson Ranch Rd
  • Phelan Rd EB & Sonora Rd
  • Phelan Rd EB & Buttemere Rd
  • Phelan Rd EB & Caughlin Rd
  • Phelan Rd EB & Arrowhead Rd
  • Phelan Rd EB & Braceo St
  • Phelan Rd EB & Lilac Rd
  • Main St EB & Cataba Rd
  • Key Pointe Ave NB & Main St
  • Amargosa Rd NB & Bear Valley Rd
  • Victor Valley Mall
  • Bear Valley Rd WB & Mall Blvd
  • Bear Valley Rd WB & Pacoima Rd
  • Bear Valley Rd WB & Amethyst Rd
  • Bear Valley Rd WB & Cobalt Rd FS
  • Bear Valley Rd WB & Topaz Rd
  • Bear Valley Rd WB & Eagle Ranch Pkwy
  • Bear Valley Rd WB & Hwy 395
  • Baldy Mesa Rd SB & Duncan Rd
  • Baldy Mesa Rd SB & 7th St
  • Baldy Mesa Rd SB & Yucca Terrace Dr
  • Phelan Rd WB & Arrowhead Rd
  • Phelan Rd WB & Caughlin Rd
  • Phelan Rd WB & Buttemere Rd
  • Phelan Rd WB & Sonora Rd
  • Phelan Rd WB & Wilson Ranch
  • Phelan Rd WB & Eaby Rd
  • Phelan Rd WB & Johnson Rd
  • Phelan Rd WB & Sheep Creek Rd
  • I Ave NB & Main St
  • I Ave NB & Live Oak St
  • I Ave NB & Hercules St
  • I Ave NB & Mojave St
  • I Ave NB & Mauna Loa St
  • I Ave NB & Lemon St
  • I Ave NB & Valencia St
  • I Ave NB & E Ave
  • I Ave NB & Eucalyptus St
  • I Ave NB & Catalpa St
  • VVC - Dock 2
  • Bear Valley Rd WB & Tamarisk Rd
  • Bear Valley Rd WB & Apatite Ave
  • Bear Valley Rd WB & Hesperia Rd
  • Hesperia Rd NB & Bear Valley Rd
  • Hesperia Rd NB & Jasmine St
  • Hesperia Rd NB & Silica Dr
  • Nisqualli Rd WB & Hesperia Rd
  • Nisqualli WB & Cypress Ave
  • Nisqualli Rd WB & 9th Ave
  • Nisqualli Rd WB & 11th Ave
  • Nisqualli Rd WB & Mariposa Rd
  • Mariposa Rd NB & Talpa St
  • Mariposa Rd NB & 7th St
  • 7th St NB & E Sage St
  • Valley Center Dr SB & 7th St
  • Nisqualli Rd EB & 11th Ave
  • Nisqualli Rd EB & 9th Ave
  • Nisqualli Rd EB & Cypress Ave
  • Nisqualli Rd EB & 3rd Ave
  • Nisqualli Rd EB & 2nd Ave
  • Nisqualli Rd EB & 1st Ave
  • Hesperia Rd SB & Nisqualli Rd
  • Hesperia Rd SB & Comanche St
  • Hesperia Rd SB & Silica Dr
  • Hesperia Rd SB & Jasmine St
  • Bear Valley Rd EB & Hesperia Rd
  • Bear Valley Rd EB & Industrial Blvd
  • VVC - Dock 4
  • Fish Hatchery
  • Farmers Market
  • I Ave SB & Catalpa St
  • I Ave SB & Eucalyptus St
  • I Ave SB & E Ave
  • I Ave SB & Valencia St
  • I Ave SB & Lemon St
  • I Ave SB & Mauna Loa St
  • I Ave SB & Mojave St
  • I Ave SB & Live Oak St
  • I Ave SB & Main St
  • Main St WB & I Ave
  • 7th St NB & La Paz Dr
  • 7th St NB & Desert Knoll Dr
  • 7th St NB & Circle Dr
  • 7th St NB & Lacy St
  • 7th St NB & Mojave Dr
  • 7th St NB & Center St NS
  • 7th St NB & Forrest Ave FS
  • Stoddard Wells Rd NB & 15 Fwy
  • Dante St EB & Venus Ave
  • Emerson St WB & Mars Ave
  • Dante St WB & Jupiter Ave
  • Stoddard Wells Rd SB & Dante St
  • Stoddard Wells Rd SB & Abbey Ln
  • Stoddard Wells Rd SB & 15 Fwy
  • Stoddard Wells Rd SB FS Overpass
  • Stoddard Wells Rd SB & River Ranch MHP
  • National Trails Hwy NB FS Air Expressway
  • Portland St EB & 1st St
  • 3rd St NB & State St
  • Olive St WB & 3rd St
  • National Trails Hwy NB & Oro Grande Market
  • National Trails Hwy NB & Polish Ln
  • National Trails Hwy NB & Iron Hog Restaurant
  • National Trails Hwy NB & Robinson Ranch Rd
  • National Trails Hwy NB & N Bryman Rd
  • National Trails Hwy SB & Bryman Rd
  • National Trails Hwy NB & Cardigan Rd NS
  • National Trails Hwy NB & Chatsworth Rd
  • National Trails Hwy NB & Hillside Dr
  • Vista Rd NB & Jordan Rd (Comm Services)
  • Vista Rd WB & Helendale Rd
  • Silver Lakes Pkwy & Nautical Ln
  • Vista Rd EB & Helendale Rd
  • National Trails Hwy SB & Darghty Rd
  • National Trails Hwy SB & Chatsworth Rd
  • National Trails Hwy SB & Citation St
  • National Trails Hwy SB & Bryman Rd
  • and 815 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 43.72026-07-30: 43.72026-07-31: 43.72026-08-01: 43.7
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2543.7 first check
2026-07-3043.7 no change
2026-07-3143.7 no change
2026-08-0143.7 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

12 findings, ordered by severity.

Show every finding
  • Error1 instance

    Service data ended 490 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)

  • Warning1626 instances

    1626 of 1921 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)

  • Warning1065 instances

    1065 of 1065 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)

  • Warning34 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)

  • Warning7 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3 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

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · 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)

  • Info1 instance

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • 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 · 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. Service data expired 490 days ago, so FTA would find the link out of date. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Not ready
Service data expired 490 days ago, so FTA would find the link out of date.
agency_id provided Not ready
agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
shapes.txt covers your trips Ready
All 1921 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 490 days ago. States wheelchair access on 0% of stops and 15% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Not yet
Service data expired 490 days ago.
Accessible Not yet
States wheelchair access on 0% of stops and 15% 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 (3 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.

  • Gap Designate a technical contact in feed_info.txt's feed_contact_email

    feed_info.txt has no feed_contact_email or feed_contact_url.

  • Gap wheelchair_boarding stated on stops and trips

    States wheelchair access on 0% of stops and 15% of trips.

  • Meets shapes.txt with a shape for every trip

    All 1921 trips have a shape in shapes.txt.

  • Gap Fare data published, or the service marked fare-free

    No fare data is published.

Correctness 72 / 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 40 / 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.

Victor Valley Transit Authority (VVTA) GTFS data quality grade: F

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/victor-valley-transit-authority-vvta/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.