Feed status · checked 2026-11-21

Orange County Transportation Authority (OCTA)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

56.5 / 100

down 0.4 since 2026-11-20

Cataloged in California.

Covers 84 daysAccessibility gaps

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Top things to fix

Fix 01

Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool

Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

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.

⏱ Usually an export-tool fix, not hand editing.worth about +24 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

5269 of 5269 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.

Fixing this covers all 5,269 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

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

7243 of 7243 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 7,243 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Riders and need behind these fixes

  • No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
  • California 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-11-02.

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
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. Fix 01

    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. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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. See this feed's finding-clearance log.

  3. Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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. See this feed's finding-clearance log.

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 84 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
Live-arrival data covered 89.6% of scheduled trips in the sampled window.

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.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Orange County Transportation Authority (OCTA)’s published feed lists 56 bus routes, 7,243 scheduled trips and 5,269 stops. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, 1 of 3 answered. The published file last changed on 2026-11-09.

Score by category

Correctness31.5 / 100

The MobilityData validator flagged 11 kinds of issue across 69413 instances (159 error, 61346 warning, 7908 informational).

Freshness85.0 / 100

Service data covers the next 84 days.

Rider experience37.5 / 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 published.

Accessibility0 / 100

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 (453, 472, 473, 480).

    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.

  • 9 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ANAHEIM-CENTER ST PROMENADE", "WEST PELTASON-@ UCI CRAWFORD HALL", "WEST PELTASON-@ UCI CRAWFORD HALL", 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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality95.7 / 100

Sampled 9 times: 1 of 1 configured feed healthy (2 not checked); 89.6% of scheduled trips had live predictions; vehicle position plausibility was not measurable; predictions ran a median of 58s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 5269 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)
  • 123 (gray)
  • 129 (gray)
  • 143 (gray)
  • 150 (gray)
  • 151 (gray)
  • 167 (gray)
  • 177 (gray)
  • 178 (gray)
  • 25 (teal)
  • 26 (teal)
  • 29 (teal)
  • 29A (teal)
  • 30 (teal)
  • 33 (teal)
  • 35 (teal)
  • 37 (teal)
  • 38 (teal)
  • 42 (teal)
  • 42A (teal)
  • 43 (teal)
  • 453 (red)
  • 46 (teal)
  • 47 (teal)
  • 472 (red)
  • 473 (red)
  • 480 (red)
  • 50 (teal)
  • 529 (teal)
  • 53 (teal)
  • 54 (teal)
  • 543 (orange)
  • 55 (teal)
  • 553 (teal)
  • 56 (teal)
  • 560 (orange)
  • 57 (teal)
  • 59 (teal)
  • 60 (teal)
  • 64 (teal)
  • 66 (teal)
  • 70 (teal)
  • 71 (teal)
  • 72 (teal)
  • 76 (teal)
  • 79 (teal)
  • 83 (teal)
  • 85 (teal)
  • 86 (teal)
  • 862 (green)
  • 89 (teal)
  • 90 (teal)
  • 91 (teal)
Routes in Orange County Transportation Authority (OCTA)'s feed
RouteTypeLine color
1 Long Beach - San ClementeBusteal
123 Goldenwest Transportation Center - Anaheim CanyonBusgray
129 La Habra - AnaheimBusgray
143 La Habra - Brea MallBusgray
150 Santa Ana / Costa mesaBusgray
150A Santa Ana / Costa mesaBusgray (no shape in feed)
151 Santa Ana / Costa mesaBusgray
167 Orange - IrvineBusgray
177 Foothill Ranch - Laguna HillsBusgray
178 Huntington Beach - IrvineBusgray
25 Fullerton - Huntington BeachBusteal
26 Fullerton - Yorba LindaBusteal
29 La Habra - Huntington BeachBusteal
29A Buena Park - Huntington BeachBusteal
30 Cerritos - Anaheim HillsBusteal
33 Fullerton - Huntington BeachBusteal
35 Costa Mesa - FullertonBusteal
37 La Habra - Fountain ValleyBusteal
38 Lakewood - Anaheim HillsBusteal
42 Long Beach - OrangeBusteal
42A Long Beach - OrangeBusteal
43 Fullerton - Costa MesaBusteal
453 Orange Transportation Center - St Joseph HospitalBusred
46 Seal Beach - OrangeBusteal
47 Fullerton - Newport BeachBusteal
472 Tustin Station - Newport BeachBusred
473 Tustin Station - U. C. IrvineBusred
47A Fullerton - Newport BeachBusteal (no shape in feed)
480 Irvine Metrolink Station - Lake ForestBusred
50 Long Beach - OrangeBusteal
529 Rapid Fullerton - Huntington BeachBusteal
53 Anaheim - IrvineBusteal
54 Garden Grove - OrangeBusteal
543 Rapid Fullerton - Santa AnaBusorange
55 Santa Ana - Newport BeachBusteal
553 Rapid Anaheim - Costa MesaBusteal
56 Garden Grove - OrangeBusteal
560 Rapid Long Beach - Santa AnaBusorange
57 Brea - Newport BeachBusteal
59 Anaheim - IrvineBusteal
60 Long Beach - TustinBusteal
64 Huntington Beach - TustinBusteal
66 Huntington Beach - IrvineBusteal
70 Sunset Beach - Tustin StationBusteal
71 Yorba Linda - Newport BeachBusteal
72 Sunset Beach - TustinBusteal
76 Huntington Beach - IrvineBusteal
79 Tustin - Newport BeachBusteal
79A Tustin - Newport BeachBusteal (no shape in feed)
83 Fullerton - Laguna HillsBusteal
85 Mission Viejo - Laguna NiguelBusteal
86 Costa Mesa - Mission ViejoBusteal
862 Santa Ana Regional Transportation Intermodal Center - Civic CenterBusgreen
89 Mission Viejo - Laguna BeachBusteal
90 Tustin Station - Dana Point HarborBusteal
91 Laguna Hills - San ClementeBusteal
List every stop
  • HASTER-ORANGEWOOD
  • HASTER-WAKEFIELD
  • HASTER-KATELLA
  • ANAHEIM-KATELLA
  • ANAHEIM-CERRITOS
  • ANAHEIM-PALAIS
  • ANAHEIM-BALL
  • ANAHEIM-LORRAINE
  • ANAHEIM-VERMONT
  • ANAHEIM-SOUTH
  • ANAHEIM-WATER
  • ANAHEIM-SANTA ANA
  • ANAHEIM-BROADWAY
  • ANAHEIM-CENTER ST PROMENADE
  • ANAHEIM-LINCOLN
  • ANAHEIM-SYCAMORE
  • ANAHEIM-WILHELMINA
  • ANAHEIM-NORTH
  • ANAHEIM-LA VERNE
  • ANAHEIM-NORTH
  • ANAHEIM-WILHELMINA
  • ANAHEIM-SYCAMORE
  • ANAHEIM-LINCOLN
  • ANAHEIM-BROADWAY
  • ANAHEIM-SANTA ANA
  • ANAHEIM-WATER
  • ANAHEIM-SOUTH
  • ANAHEIM-VERMONT
  • ANAHEIM-LORRAINE
  • ANAHEIM-BALL
  • ANAHEIM-WINSTON
  • ANAHEIM-CERRITOS
  • HASTER-KATELLA
  • HASTER-WAKEFIELD
  • HASTER-ORANGEWOOD
  • HASTER-CLIFFWOOD
  • HASTER-TILLER
  • BALL-FREMONT
  • BALL-KNOTT
  • BALL-MASTERS
  • BALL-WESTERN
  • BALL-COURTRIGHT
  • BALL-HALLIDAY
  • BALL-BEACH
  • BALL-DALE
  • BALL-MACDUFF
  • BALL-MAGNOLIA
  • BALL-WEBSTER
  • BALL-GILBERT
  • BALL-BROOKHURST
  • BALL-EMPIRE
  • BALL-NUTWOOD
  • BALL-TRIDENT
  • BALL-EUCLID
  • BALL-LOARA
  • BALL-HAMPSTEAD
  • BALL-WALNUT
  • BALL-WEST
  • BALL-CAST
  • BALL-HARBOR
  • BALL-CLAREMONT
  • BALL-ANAHEIM
  • BALL-ALLEC
  • BALL-LEWIS
  • BALL-EAST
  • BALL-SHERMAN
  • BALL-STATE COLLEGE
  • BALL-BELHAVEN
  • BALL-SUNKIST
  • BALL-SUNKIST
  • BALL-BELHAVEN
  • BALL-STATE COLLEGE
  • BALL-EAST
  • BALL-EAST
  • BALL-LEWIS
  • BALL-ALLEC
  • BALL-ANAHEIM
  • BALL-LEMON
  • BALL-HARBOR
  • BALL-OX
  • BALL-FLORE
  • BALL-WALNUT
  • BALL-HAMPSTEAD
  • BALL-LOARA
  • BALL-EUCLID
  • BALL-TRIDENT
  • BALL-NUTWOOD
  • BALL-EMPIRE
  • BALL-BROOKHURST
  • BALL-PERDIDO
  • BALL-GILBERT
  • BALL-WEBSTER
  • BALL-MAGNOLIA
  • BALL-SHERRILL
  • BALL-DALE
  • BALL-BEACH
  • BALL-HALLIDAY
  • BALL-WESTERN
  • BALL-WESTVALE
  • BALL-KNOTT
  • BEACH-BALL
  • BEACH-ROME
  • BEACH-ORANGE
  • BEACH-YOUTH CENTER
  • BEACH-LINCOLN
  • BEACH-LINCOLN
  • BEACH-YOUTH CENTER
  • BEACH-ORANGE
  • BEACH-STONYBROOK
  • BEACH-BALL
  • BROOKHURST-KATELLA
  • BROOKHURST-CRESTWOOD
  • BROOKHURST-CERRITOS
  • BROOKHURST-PALAIS
  • BROOKHURST-BALL
  • BROOKHURST-BROOKMORE
  • BROOKHURST-NIOBE
  • BROOKHURST-ORANGE
  • BROOKHURST-BROADWAY
  • BROOKHURST-LINCOLN
  • BROOKHURST-CATALINA
  • BROOKHURST-CRESCENT
  • BROOKHURST-LA PALMA
  • BROOKHURST-LA PALMA
  • BROOKHURST-CRESCENT
  • BROOKHURST-WOODLEY
  • BROOKHURST-LINCOLN
  • BROOKHURST-ORANGE
  • BROOKHURST-STONEYBROOK
  • BROOKHURST-COLCHESTER
  • BROOKHURST-BALL
  • BROOKHURST-CERRITOS
  • BROOKHURST-CRESTWOOD
  • CHAPMAN-SOMERSET
  • DALE-LINCOLN
  • DALE-CRESCENT
  • DALE-TYLER
  • EUCLID-ORD
  • EUCLID-ORANGEWOOD
  • EUCLID-KATELLA
  • EUCLID-SALLIE
  • EUCLID-CRIS
  • EUCLID-CERRITOS
  • EUCLID-PALAIS
  • EUCLID-BALL
  • EUCLID-CRONE
  • EUCLID-ORANGE
  • EUCLID-BROADWAY
  • EUCLID-LINCOLN
  • EUCLID-CRESCENT
  • EUCLID-GLENOAKS
  • EUCLID-LA PALMA
  • EUCLID-ROMNEYA
  • EUCLID-MEDICAL CENTER
  • EUCLID-MEDICAL CENTER
  • EUCLID-ROMNEYA
  • EUCLID-LA PALMA
  • EUCLID-GLENOAKS
  • EUCLID-CRESCENT
  • EUCLID-LINCOLN
  • EUCLID-BROADWAY
  • EUCLID-ORANGE
  • EUCLID-CRONE
  • EUCLID-BALL
  • EUCLID-CHALET
  • EUCLID-CERRITOS
  • EUCLID-CRIS
  • EUCLID-SALLIE
  • HARBOR-CHAPMAN
  • HARBOR-WILKEN
  • HARBOR-ORANGEWOOD
  • HARBOR-CONVENTION
  • HARBOR-KATELLA
  • HARBOR-EAST SHUTTLE AREA
  • HARBOR-BALL
  • HARBOR-VERMONT
  • HARBOR-SOUTH
  • HARBOR-WATER
  • HARBOR-SANTA ANA
  • HARBOR-BROADWAY
  • HARBOR-LINCOLN
  • HARBOR-SYCAMORE
  • HARBOR-NORTH
  • HARBOR-LA PALMA
  • HARBOR-CARL KARCHER
  • HARBOR-ROMNEYA
  • HARBOR-LA PALMA
  • HARBOR-NORTH
  • HARBOR-SYCAMORE
  • HARBOR-LINCOLN
  • HARBOR-BROADWAY
  • HARBOR-SANTA ANA
  • HARBOR-WATER
  • HARBOR-SOUTH
  • HARBOR-VERMONT
  • HARBOR-BALL
  • HARBOR-EAST SHUTTLE AREA
  • HARBOR-KATELLA
  • HARBOR-CONVENTION
  • HARBOR-ORANGEWOOD
  • HARBOR-WILKEN
  • KATELLA-EUCLID
  • KATELLA-CARNELIAN
  • KATELLA-9TH
  • KATELLA-CASA VISTA
  • KATELLA-WEST
  • KATELLA-CONVENTION CENTER
  • KATELLA-HARBOR
  • KATELLA-CLEMENTINE
  • KATELLA-HASTER
  • KATELLA-LEWIS
  • KATELLA-MARKET
  • KATELLA-STATE COLLEGE
  • KATELLA-HOWELL
  • KATELLA-HOWELL
  • KATELLA-STATE COLLEGE
  • KATELLA-AUBURN
  • KATELLA-LEWIS
  • KATELLA-ANAHEIM
  • KATELLA-CLEMENTINE
  • KATELLA-HARBOR
  • KATELLA-CONVENTION CENTER
  • KATELLA-DISNEYLAND
  • KATELLA-WALNUT
  • KATELLA-9TH
  • KATELLA-EUCLID
  • KATELLA-HUMOR
  • KATELLA-NUTWOOD
  • KATELLA-DALLAS
  • KATELLA-BROOKHURST
  • KNOTT-THORNTON
  • KNOTT-BALL
  • KNOTT-ROME
  • KNOTT-ORANGE
  • KNOTT-DANBROOK
  • KNOTT-DEL MONTE
  • KNOTT-LINCOLN
  • KNOTT-DEL MONTE
  • KNOTT-OLINDA
  • KNOTT-ORANGE
  • KNOTT-SAVANNA
  • KNOTT-BALL
  • KNOTT-THORNTON
  • KRAEMER-FRONTERA
  • KRAEMER-LA PALMA
  • KRAEMER-CORONADO
  • KRAEMER-MIRALOMA
  • KRAEMER-LA JOLLA
  • KRAEMER-ORANGETHORPE
  • KRAEMER-ORANGETHORPE
  • and 5019 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 13 checks — down 0.4 since 2026-11-20.

2026-11-09: 57.02026-11-10: 56.92026-11-11: 57.12026-11-12: 56.82026-11-13: 56.92026-11-14: 56.52026-11-15: 56.32026-11-16: 56.82026-11-17: 56.92026-11-18: 57.12026-11-19: 56.92026-11-20: 56.92026-11-21: 56.5
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0957.0 first check
2026-11-1056.9 down 0.1
2026-11-1157.1 up 0.2
2026-11-1256.8 down 0.3
2026-11-1356.9 up 0.1
2026-11-1456.5 down 0.4
2026-11-1556.3 down 0.2
2026-11-1656.8 up 0.5
2026-11-1756.9 up 0.1
2026-11-1857.1 up 0.2
2026-11-1956.9 down 0.2
2026-11-2056.9 no change
2026-11-2156.5 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality down 1.6

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.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-09 to 2026-11-21 (13 checks)818336f10e752027-02-13Current rubric: see the trend above
2026-10-02 to 2026-11-06 (36 checks)4351011846ab2026-11-07F, 43.6 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-08-14 to 2026-10-01 (45 checks)4351011846ab2026-11-07F, 48.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-09 to 2026-08-13 (5 checks)aff842daf9882026-11-07F, 56.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-08-08 (15 checks)9dad723b248c2026-08-08F, 39.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-14 to 2026-07-24 (8 checks)9dad723b248c2026-08-08F, 41.8 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-13 (25 checks)9dad723b248c2026-08-08F, 45.4 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

Everything we checked

19 findings, ordered by severity.

Show every finding
  • Error159 instances

    Some trips have stop times whose distances along the route go backwards.

    Apps can show buses jumping backwards or mis-order stops.

    Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)

    Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning48672 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 for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning12475 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

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

  • Warning7243 instances

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

  • Warning5269 instances

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

  • Warning189 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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning7 instances

    7 of 67 trips scheduled during the sampling window had no live predictions.

    Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.

    Fix: Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. (A vendor data-mapping question.)

    Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

  • Warning6 instances

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning2 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules 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

    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 for trip_coverage_not_active_for_next7_days · 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)

  • Info7243 instances

    Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info5267 instances

    About 5267 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info664 instances

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    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)

  • Info1 instance

    We could not check your vehicle positions feed on this run.

    The fetch failed on our side. That is a gap in our check, not a fault in your feed.

    Fix: Nothing to do. The feed is left out of this score rather than counted as an outage. (None.)

    Finding code: scorecard_rt_vehicle_positions_not_checked

  • Info1 instance

    We could not check your service alerts feed on this run.

    The fetch failed on our side. That is a gap in our check, not a fault in your feed.

    Fix: Nothing to do. The feed is left out of this score rather than counted as an outage. (None.)

    Finding code: scorecard_rt_service_alerts_not_checked

How we measured this

Checked for changes 18 hours ago; last changed 13 days ago.

Measured 4 of 4 score categories from the feed URL on file (publisher not verified).

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 9 snapshots.
  • The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

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.5, validator 8.0.1.

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 84 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 1; your National Transit Database ID is 90036. 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 1 to NTD ID 90036, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 7243 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

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 84 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.

  • 189 of 5269 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 in the 25 days to 2026-11-22, with 0s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.

Live predictions vs schedule

Arrival predictions ran a median 58s late versus the schedule, and stayed within 216s nine times in ten. They were on time (about a minute early to five late) 92.3% of the time.

From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.

Clears the Google and Apple Maps four-week coverage bar. This feed has 83 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 159 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.

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.

  • Gap Produce no critical errors in the MobilityData GTFS Validator

    1 validator error to resolve.

  • 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 0% of trips.

  • Meets shapes.txt with a shape for every trip

    All 7243 trips have a shape in shapes.txt.

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

    Fare data is published.

Correctness 32 / 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 85 / 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 96 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in California

Other scorecards in California, 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.

Orange County Transportation Authority (OCTA): GTFS feed quality grade F, 56.5 of 100, checked 2026-11-21. GTFS 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/orange-county-transportation-authority-octa/2026-11-21.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-11-21. 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.