Feed status · checked 2026-08-01
Thousand Oaks Transit
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 67 minutes ago; last changed 2 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 3 snapshots.
- 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
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
155 of 155 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
407 of 407 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
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 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
- 155 of 155 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
- 407 of 407 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
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
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.
Remove retired stops from the export, or add them back to the trips that should serve them. · 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 is in 153 days.
- 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
- Fare information is published using GTFS Fares v1.
- Realtime information
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 80 instances (0 error, 32 warning, 48 informational).
Service data covers the next 153 days.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route 40, Route 41, Route 45, Beach Bus).
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.
140 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Teller Road west of Lawrence Dr. (W/B)", "Janss Rd. & Montgomery Rd..", "Janss Rd. at Conejo Valley High School.", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Sampled 3 times: 1 of 1 configured feed healthy.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 155 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.
- Beach Bus (teal)
- Route 40 (orange)
- Route 41 (brown)
- Route 42 (purple)
- Route 43 (red)
- Route 44 (blue)
- Route 45 (pink)
| Route | Type | Line color |
|---|---|---|
| Beach Bus Summer Beach Bus | Bus | teal |
| Route 40 Newbury Park - Borchard | Bus | orange |
| Route 41 Midtown - Flores | Bus | brown |
| Route 42 Midtown - Arboles | Bus | purple |
| Route 43 T.O.B. | Bus | red |
| Route 44 Hillcrest | Bus | blue |
| Route 45 Newbury Park - Rancho Conejo | Bus | pink |
List every stop
- Teller Road west of Lawrence Dr. (W/B)
- Janss Rd. & Montgomery Rd..
- Janss Rd. at Conejo Valley High School.
- Erbes Rd. & Ave. De Las Flores.
- Ave. De Los Arboles & Oakbrook Dr..
- Ave. De Los Arboles & Calle Olivo.
- Corporate Center Dr. west of Rancho Conejo Bl..
- Rancho Conejo Bl. & Ventu Park Rd. (S/B).
- Avenida De Los Flores & Moss Ct.
- Ave. De Las Flores at Los Cerritos MS
- Moorpark Rd & Calle Entrar
- Lynn Rd & Wildwood Ave
- Ave. de las Flores & Moorpark Rd.
- Teller Rd. & Rancho Conejo Bl.
- Hillcrest Dr. & Amgen Ct.
- Hillcrest Dr. west of Artisan Rd.
- Borchard Rd. & Carob Dr. (NP Library)
- Borchard Rd. & Theresa Dr.
- Borchard Community Park
- Reino Rd. north of Maurice Dr.
- Lynn Rd.& Knollwood Dr.
- Wendy Dr. & Corning St.
- Reino Rd. & Borchard Rd.
- Reino Rd. & Lesser Dr. (NPHS)
- Old Conejo Rd. west of Wendy Dr.
- Teller Road west of Lawrence Dr.
- Hillcrest Dr. west of Rancho Conejo Bl.
- Newbury Rd. east of Borchard Rd.
- Newbury Rd. west of Ventu Park Rd.
- Ventu Park Rd. south of Hillcrest Dr.
- Hillcrest Dr. & Lynn Rd. (E/B)
- The Oaks
- Hillcrest Dr. west of Ventu Park Rd. (W/B)
- Dos Vientos Community Center
- City Transportation Center
- Los Robles Hospital
- Lynn Rd. & Ave de los Arboles
- Olsen Rd. & Campus Dr.
- Olsen Rd. & Mountclef Bl.
- Ave. de los Arboles & Oakbrook Dr.
- Ave. de los Arboles & Calle Olivo
- Moorpark Rd. & Ave de los Arboles
- Ave. de las Flores at Waverly Park
- Ave. De Las Flores & Erbes Rd. (LCMS)
- Teen & Adult Centers
- Hillcrest Dr. & Rancho Rd. (west of Encino Vista)
- Hillcrest Dr. & Artisan Rd.
- Hillcrest Dr. & Shady Oaks Dr.
- Hillcrest Dr. & west of Ventu Park Rd. (E/B)
- Thousand Oaks Blvd. & Hodencamp Rd. (W/B)
- Thousand Oaks Bl. & Rancho Rd. (E/B)
- Civic Arts Plaza
- Thousand Oaks Bl. & Skyline Dr. (W/B)
- Thousand Oaks Bl. & Auto Mall Dr.
- Thousand Oaks Bl. & Cord Ave. (E/B)
- Agoura Rd. & Westlake Bl.
- Townsgate Rd. east of Westlake Bl.
- Westlake Bl. & Thousand Oaks Bl.
- Hillcrest Dr. across from Colina MS
- Hillcrest Dr. & Houston Dr. (W/B)
- Hillcrest Dr. & Hodencamp Rd. (E/B)
- Hillcrest Dr. east of Moorpark Rd.
- Hillcrest Dr. & Marin St. (across from The Oaks)
- Hillcrest Dr. & McCloud Av.
- Ventu Park Rd. & Hillcrest Dr.
- Newbury Rd. north of Michael Dr.
- 125 W. Thousand Oaks Bl. (VCHCA)
- Janss Marketplace
- 80 E. Hillcrest Dr.
- Hillcrest Dr. at Colina Middle School
- Hillcrest Dr. & Hilltop Way (E/B)
- Westlake Bl. north of Meadow Gate St.
- Agoura Rd. & Lakeview Canyon Rd.
- Agoura Rd. & Village Glen Av.
- Westlake Bl. & Townsgate Rd.
- Thousand Oaks Bl. & Cord Ave. (W/B)
- Thousand Oaks Blvd & Duesenberg Dr
- Thousand Oaks Bl. at Gardens of the World
- Olsen Rd. & Mountclef Bl. (NW Corner)
- Moorpark Rd. & Brazil St.
- Moorpark Rd. & Wilbur Rd.
- Janss Rd. & Montgomery Rd.
- Janss Rd. at Conejo Valley High School
- Gainsborough Rd. & Tuolumne Rd.
- Moorpark Rd. & Gainsborough Rd.
- Wilbur Rd. & Warwick Ave.
- Wilbur Rd. & Marin St.
- Wilbur Rd. & Thousand Oaks Bl.
- Borchard Community Center
- Lynn Rd. & Ave de los Arboles
- Ave. de las Flores & Moorpark Rd.
- Thousand Oaks Bl. & Baker Ave.
- Hillcrest Dr. & Houston Dr. (E/B)
- Olsen Rd. & Campus Dr.
- Thousand Oaks Bl. & Skyline Dr. (E/B)
- Hillcrest Dr. & Hodencamp Rd. (W/B)
- Newbury Rd. west of Ventu Park Rd.
- Thousand Oaks Bl. & Hodencamp Rd. (E/B)
- Borchard Rd. & Wendy Dr.
- Hillcrest Dr. & Lynn Rd. (W/B)
- W. Kimber Dr. & Wendy Dr.
- Broadbeck Rd. & Academy Dr.
- Moorpark Rd. at Conejo Valley Plaza
- Moorpark Rd. & Hillcrest Dr.
- Rolling Oaks Dr. & Moorpark Rd.
- Los Padres Dr. & Haaland Dr.
- Erbes Rd. & Ave. de las Flores
- Ave. De Los Arboles & Moorpark Rd.
- Mountclef Bl. north of Faculty Ct.
- Thousand Oaks Bl. & 23 Freeway (E/B)
- Thousand Oaks Bl. & Maegan Pl. (E/B)
- Thousand Oaks Bl. & Lakeview Cyn. Rd.
- Thousand Oaks Bl. & Maegan Pl. (W/B)
- Thousand Oaks Bl. & 23 Freeway (W/B)
- Thousand Oaks Bl. & Baker Ave. (E/B)
- Hillcrest Dr. & Rancho Rd. (east of Encino Vista)
- Hillcrest Dr. & Conejo School Rd. (E/B)
- Hillcrest Dr. & Hilltop Way (W/B)
- Hillcrest Dr. & Conejo School Rd. (W/B)
- Rancho Conejo Bl. & Ventu Park Rd. (N/B)
- Lawrence Dr. & Rancho Conejo Bl.
- Corporate Center Dr. west of Rancho Conejo Bl.
- Rancho Conejo Bl. & Ventu Park Rd. (S/B)
- Hillcrest Dr. and Marin St. (The Oaks)
- Moorpark Rd. at Conejo Valley Plaza
- Moorpark Rd. & Wilbur Rd.
- Zuma Beach Lot 8
- Hillcrest Dr. & Encino Vista (east of Rancho Rd.)
- Lynn Rd. & Gainsborough Rd.
- Olsen Rd. & Moorpark Rd.
- Thousand Oaks Bl. & Zuniga Ridge Pl.
- Hillcrest Dr. & Boardwalk Av.
- Wendy Dr. & Donald Ave.
- Hillcrest Dr. & Erbes Rd.
- Hillcrest Dr. & Duesenberg Dr.
- Old Conejo Rd. and Jenny Dr.
- Moorpark Rd. & Ave. de las Flores
- Newbury Rd. east of Kelley Rd. (CVHS)
- Ave. de las Flores & Bamboo Ct.
- Hillcrest Dr. & Westlake Bl.
- Via Merida east of Lakeview Cyn Rd.
- Wilbur Rd. & Hillcrest Dr.
- Hillcrest Dr. & Conejo School Rd.
- Thousand Oaks Bl. & Lakeview Cyn Rd.
- Moorpark Rd. & Columbia Rd.
- Pederson Rd. & Calle Almendro
- Thousand Oaks Bl. & Taylor Ct.
- Thousand Oaks Bl. & 23 Fwy.
- Erbes Rd. & Pederson Rd.
- Lynn Rd. & Camino Manzanas
- Moorpark Metrolink Station North Gate
- Hillcrest Dr. & Duesenberg Dr.
- Hillcrest Dr. & Conejo School Rd.
- Harbor Cove Beach
- Harbor Village
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 85.9 | first check |
| 2026-07-30 | 85.9 | no change |
| 2026-07-31 | 85.9 | no change |
| 2026-08-01 | 85.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality 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
8 findings, ordered by severity.
Show every finding
- Warning407 instances
407 of 407 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)
- Warning155 instances
155 of 155 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)
- Warning130 instances
130 of 407 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning32 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
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)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 153 days.
- 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) Different (allowed)
- Your feed's agency_id is 526; your National Transit Database ID is 90165. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 526 to NTD ID 90165, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 407 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. 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 Met
- Service data covers the next 153 days.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 32 of 155 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 316 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 (5 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 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 407 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 92 / 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 100 / 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 55 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/thousand-oaks-transit/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.