Feed status · checked 2026-08-01
Kitsap Transit
Based on the feed this agency publishes
Service mode Bus + Ferry
up 0.4 since 2026-07-31 · D → D
Catalogued in Washington.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 75 minutes ago; last changed 14 hours 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 9 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
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 points in its category
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
1323 of 1323 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
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
- The trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- The vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- 1323 of 1323 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
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.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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 42 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 8 routes · 602 trips
- Terminal structure
- 7 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- Unknown: none of the 7 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 602 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
- Bicycles
- 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (602 of 602). Unstated values remain unknown.
- Cars
- Unknown: none of the 602 ferry trips publish cars_allowed.
- Fares
- Whole feed: applied fare data is published using GTFS Fares v1.
- Realtime
- Whole feed: configured GTFS-Realtime endpoints are Trip Updates, Vehicle Positions, Service Alerts.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 13 instances (0 error, 7 warning, 6 informational).
Service data covers the next 42 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
15 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (500, 501, 119, 186, 219, and more).
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.
726 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Southworth & Banner", "Harper Church P&R", "Colchester & Main St", 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 9 times: 1 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 1323 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.
- 104 (brown)
- 105 (black)
- 108 (blue)
- 109 (brown)
- 119 (brown)
- 181 (teal)
- 184 (black)
- 185 (green)
- 186 (red)
- 212 (red)
- 215 (yellow)
- 217 (black)
- 219 (brown)
- 220 (brown)
- 221 (purple)
- 222 (red)
- 223 (teal)
- 224 (red)
- 225 (orange)
- 226 (purple)
- 228 (teal)
- 229 (red)
- 238 (purple)
- 265 (orange)
- 266 (brown)
- 301 (brown)
- 302 (teal)
- 307 (green)
- 331 (brown)
- 332 (purple)
- 333 (red)
- 344 (teal)
- 385 (yellow)
- 389 (green)
- 390 (brown)
- 391 (orange)
- 393 (teal)
- 394 (green)
- 395 (purple)
- 396 (brown)
- 397 (black)
- 398 (teal)
- 399 (black)
- 400 (teal)
- 401 (teal)
- 402 (teal)
- 403 (teal)
- 404 (teal)
- 405 (teal)
- 500 (orange)
- 501 (orange)
- 600 (brown)
- 602 (brown)
- 604 (brown)
- 605 (brown)
- 607 (brown)
- 608 (brown)
- 612 (brown)
- 614 (brown)
- 616 (brown)
- 618 (brown)
- 619 (brown)
- 620 (brown)
- 621 (brown)
- 623 (brown)
- 624 (brown)
- 625 (brown)
- 626 (brown)
- 627 (brown)
- 630 (brown)
- 631 (brown)
- 633 (brown)
- 635 (brown)
- 636 (brown)
- 637 (brown)
- 638 (brown)
- TA034 (white)
| Route | Type | Line color |
|---|---|---|
| 104 Tremont | Bus | brown |
| 105 Sidney | Bus | black |
| 108 Bethel | Bus | blue |
| 109 East Port Orchard | Bus | brown |
| 119 Madrona | Bus | brown |
| 181 Annapolis | Bus | teal |
| 184 Harper Shuttle | Bus | black |
| 185 Mullenix | Bus | green |
| 186 Southworth | Bus | red |
| 212 Bremerton-Silverdale West | Bus | red |
| 215 McWilliams | Bus | yellow |
| 217 Bremerton-Silverdale East | Bus | black |
| 219 Crossroads | Bus | brown |
| 220 Sunn Fjord | Bus | brown |
| 221 Perry Avenue | Bus | purple |
| 222 Gateway Express | Bus | red |
| 223 Kariotis | Bus | teal |
| 224 Olympic College | Bus | red |
| 225 Sheridan Park | Bus | orange |
| 226 Bay Vista | Bus | purple |
| 228 Marion | Bus | teal |
| 229 Trenton | Bus | red |
| 238 West Bremerton Express | Bus | purple |
| 265 Silverdale Central | Bus | orange |
| 266 Silverdale Ridgetop | Bus | brown |
| 301 North Kitsap Fast Ferry Express | Bus | brown |
| 302 Kingston/Suquamish Fast Ferry | Bus | teal |
| 307 Kingston/North Viking Fast Ferry | Bus | green |
| 331 Poulsbo/Myhre | Bus | brown |
| 332 Poulsbo/Silverdale | Bus | purple |
| 333 Silverdale/Bainbridge | Bus | red |
| 344 Poulsbo Central | Bus | teal |
| 385 BI Downtown | Bus | yellow |
| 389 Fletcher Bay | Bus | green |
| 390 Poulsbo/Bainbridge | Bus | brown |
| 391 Kingston/Bainbridge | Bus | orange |
| 393 Manzanita | Bus | teal |
| 394 Agate Point | Bus | green |
| 395 Battle Point | Bus | purple |
| 396 Sunrise | Bus | brown |
| 397 Crystal Springs | Bus | black |
| 398 Fort Ward | Bus | teal |
| 399 Bill Point | Bus | black |
| 400 Bremerton to Seattle Fast Ferry | Ferry | teal |
| 401 Kingston to Seattle Fast Ferry | Ferry | teal |
| 402 Southworth to Seattle Fast Ferry | Ferry | teal |
| 403 Seattle to Bremerton Fast Ferry | Ferry | teal |
| 404 Seattle to Kingston Fast Ferry | Ferry | teal |
| 405 Seattle to Southworth Fast Ferry | Ferry | teal |
| 500 Port Orchard Foot Ferry | Ferry | orange |
| 501 Annapolis Foot Ferry | Ferry | orange |
| 600 Burley Worker/Driver | Bus | brown |
| 602 Tracyton Worker/Driver | Bus | brown |
| 604 Horseshoe Lake Worker/Driver | Bus | brown |
| 605 Illahee Worker/Driver | Bus | brown |
| 607 Long Lake Days Worker/Driver | Bus | brown |
| 608 Manchester Worker/Driver | Bus | brown |
| 612 Phillips/Bielmeier Worker/Driver | Bus | brown |
| 614 Port Gamble Worker/Driver | Bus | brown |
| 616 Salmonberry Worker/Driver | Bus | brown |
| 618 Southworth Worker/Driver | Bus | brown |
| 619 Suquamish Worker/Driver | Bus | brown |
| 620 Winslow Worker/Driver | Bus | brown |
| 621 Woodmere Worker/Driver | Bus | brown |
| 623 Central Valley Loop Worker/Driver | Bus | brown |
| 624 Fairgrounds Worker/Driver | Bus | brown |
| 625 Sidney Woods Worker/Driver | Bus | brown |
| 626 Early North Worker/Driver | Bus | brown |
| 627 SK/Bangor Worker/Driver | Bus | brown |
| 630 Olalla Worker/Driver | Bus | brown |
| 631 Chico Worker/Driver | Bus | brown |
| 633 Viking Express Worker/Driver | Bus | brown |
| 635 Early South Worker/Driver | Bus | brown |
| 636 Parkwood-Ponderosa Worker/Driver | Bus | brown |
| 637 Sunnyslope Worker/Driver | Bus | brown |
| 638 Seabeck/Camp Union Worker/Driver | Bus | brown |
| 800 BI Ride | Bus | green (no shape in feed) |
| 801 SK Ride | Bus | green (no shape in feed) |
| 803 Kingston Ride | Bus | green (no shape in feed) |
| 807 Sunday On-Demand | Bus | green (no shape in feed) |
| TA034 Task | Bus | white |
List every stop
- Bremerton TC
- Harper Church P&R
- Old Creosote & Bill Point
- Hwy 305 at Delate
- Hwy 305 at Seminole
- Hwy 305 at Lemolo Shore
- 16300 Hwy 305
- Mountain View Middle School
- 16281 Hwy 305
- Hwy 305 at Suquamish Way
- Hwy 305 at Adas Will
- Hwy 305 at Seabold
- Hwy 305 at Hidden Cove
- Eagle Harbor & Rose
- Hwy 305 & Day Rd
- Hwy 305 at Lovgreen
- Hwy 305 at Koura
- Hwy 305 at Sportsman Club
- Hwy 305 at Madison
- Magnuson at Perry
- Hwy 305 at High School Rd
- Bainbridge Island TC
- 208 High School Road
- New Brooklyn at Northtown
- Ordway Elementary
- 253 High School Rd
- Winslow at Ericksen
- Madison at City Hall
- Madison at Knechtel
- Magnuson at Fir
- Madison & Wallace
- Madison & High School Rd
- High School at Grow
- High School at Commodore
- Tolo & Battlepoint
- High School at Capstan
- Bethany Lutheran P&R
- High School at Weaver
- High School at Commodore
- High School at Grow
- High School at Madison
- Magunson at Schley
- Madison at High School Rd
- Madison & Wallace
- Madison at Knechtel
- New Brooklyn & Madison
- Madison at Madrona
- Madison at Winslow Way
- Hwy 305 & Day Rd
- Hwy 305 at Madison
- Hwy 305 at Manitou Beach
- Winslow at T&C Market
- Wyatt at Cosgrove
- Schley at Callahan
- Wallace at Blue Herron
- American Legion P&R
- Koura at Meadowmeer Cir
- Hwy 305 & Suquamish Way
- Suquamish Way & Hwy 305
- Suquamish Way at Whale Dancer
- Suquamish Way at Division
- Suquamish P&R
- Miller Bay at Barrett
- Miller Bay at Lincoln
- Miller Bay at Sid Price
- Schley & Sheridan
- George's Corner P&R
- 11th St at Ironsides
- Hwy 104 at Barber Cutoff
- Hwy 104 at Myrtle
- Hwy 104 at Lindvog
- 10951 Hwy 104
- Hwy 104 at 2nd St
- Sheridan at Callahan
- Hwy 104 at Bannister
- 10952 Hwy 104
- Hwy 104 at Myrtle
- Miller Bay at Quail Tr
- Koura & Miller
- Miller Bay at Lincoln
- Augusta & Geneva
- Suquamish P&R
- Suquamish Way at Division
- Suquamish Way at Totten
- Sheridan & Perry
- Ridgetop at Hillsboro
- Hwy 305 at Sandy Hook
- 16300 Hwy 305
- Manzanita & Day Rd
- Hwy 305 at Creative Dr
- Hwy 305 at Seminole
- Hwy 305 at Noll
- Hwy 305 at Johnson
- Hwy 305 at Baywatch
- Warren at 6th St
- Perry at 30th St
- Fred Meyer
- Silverdale Way at Bennington Dr
- Viking Way & Hwy 308
- Hansen at Sunset
- Viking Way at Sherman Hill
- Viking Way & Hwy 308
- Poulsbo Junction P&R
- Viking Way at Hallman Rd
- Ridgetop & Pinnacle
- Viking Way at Lark Ln
- Viking Ave at Liberty
- Perry at Denny
- Gateway Fellowship P&R
- Front at Jensen
- Southworth at Olympiad
- Miller & Tolo
- Lincoln Dr at 10th Ave
- Lincoln Dr at 12th Ave
- Lincoln Rd at Caldart
- Caldart at Mesford
- Hostmark at 11th Ave
- Hostmark at Caldart
- Caldart at Mesford
- Lincoln at Caldart
- Perry at Sylvan
- Lincoln at 12th Ave
- Grand & Park
- Hostmark at Caldart
- Hostmark at 11th Ave
- Lincoln at 10th Ave
- Hwy 305 at Lincoln
- Viking Way at Anderson Ln
- Viking Way at Anderson Ln
- Jensen Way at Iverson
- 7th Ave at Liberty
- Iverson St at Library
- Sylvan at Forest
- Indianola at View Ridge
- Front at Sunset
- Lindvig Way at 3rd Ave
- Jensen Way at Iverson St
- Poulsbo Junction P&R
- Viking Ave at Edvard
- Lindvig Way at 3rd Ave
- Sylvan at Harbel
- Olhava Way & Walmart
- Madison & Manitou Beach
- Viking Ave at Edvard
- Viking Way at Sherman Hill
- Kitsap Way at Pershing
- Viking Way at Nordic Cove
- Mile Hill at Wolves Road
- Mile Hill at Jackson
- Mile Hill at Harrison
- Mile Hill & Village Ln
- Sylvan & Almira
- Mile Hill at Baby Doll
- Sunrise & Valley
- Mile Hill & Saddle Club
- Mile Hill at Woods
- Mile Hill at Nebraska
- California & Legrand
- California at Cleveland
- California at Fillmore
- California & Polk
- California at Van Buren
- California at Raintree
- Almira at Spruce
- Sunrise & Torvanger
- California at Stanley
- Chester at Madrone
- Madrone at Alaska
- Colchester & Main St
- Colchester at Puget Dr
- Colchester at Miracle Mile
- Colchester at Prichard
- Colchester at Perelli
- Colchester at Haida
- Colchester at Yukon Harbor
- Phelps & Day
- Baker Hill & Lynwood
- Wyatt & Grow
- Southworth at Cornell
- Riddell at Fred Meyer
- Riddell at Fred Meyer
- Anderson Hill at Bucklin Hill
- Silverdale Way & Spirit Ridge
- Silverdale Way at Westridge
- Silverdale Way at Vasquez
- Silverdale Way & Schold
- Kitsap Way at Pershing
- Silverdale Way & Nuthatch Way
- Silverdale Way at Woodbridge
- Sportsman Club at Business Park Ln
- Sportsman Club at Business Park Ln
- Riddell Rd at Prospector
- Silverdale TC
- St Michael Medical Center
- Greaves Way at Pacific Crest
- Greaves Way at Clear Creek
- Greaves Way & Old Frontier
- Silverdale Way at Ridgetop
- Silverdale Way at Ridgetop
- 9991 Mickelberry Rd
- Mickelberry at Ridgetop
- Nels Nelson at Fairgrounds Rd
- Nels Nelson & Fairwood
- Nels Nelson at Creekside
- Nels Nelson at Silver
- Bucklin Hill at Marissa Ln
- Bucklin Hill at Spinnaker
- Wyatt & Madison
- Bucklin Hill at Richardson
- 1st at Auto Center Way
- Silverdale Way & Randall
- Silverdale Way at Woodbridge
- Silverdale Way & Nuthatch Way
- Silverdale Way & Schold
- Silverdale Way at Westridge
- Silverdale Way at Spirit Ridge
- Silverdale Way & Randall
- PSNS Main Gate
- Charleston Gate
- Tracyton Blvd & Gillespie Way
- Central Valley Rd & San Juan
- Grand Pine Loop & McWilliams
- Old Military Rd & Foster
- PSNS Main Gate
- Tracyton Blvd & Gillespie Way
- Oddfellows & West Blakely
- Pitt at 10th St
- Madison at Wyatt
- Pitt Ave at 10th St
- Wheaton Way at Sheridan
- Luoto & Bangor Main Gate
- Luoto at Bangor Main Gate
- Miller Bay at Indianola Rd
- Burley Bible Church P&R
- Bethel Burley Rd & Oak Rd
- 10474 Bethel Burley Rd
- 10475 Bethel Burley Rd
- Silver Rd & Oneida Cir
- 7201 Tracyton Blvd
- Sylvan & Wheaton Way
- Hunter Rd & Hunter Ln
- Hunter Rd at Hunter Ln
- Paulson Rd & Central Valley
- University Point Cir & Chinook Way
- Paulson Rd & Central Valley
- New Brooklyn & Madison
- Long Lake & North St
- Ramiller & Kemp Ln
- Horizon & Emerald Dr
- Mullenix Rd & Mullenix P&R
- and 1073 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — up 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 67.8 | first check |
| 2026-07-30 | 66.1 | down 1.7 |
| 2026-07-31 | 65.8 | down 0.3 |
| 2026-08-01 | 66.2 | up 0.4 |
What changed since your last check
- Correctness up 2.0
- Freshness down 1.7
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall score rose 0.4 points since 2026-07-31.
The feed file was re-published since 2026-07-31 (-482 KB).
New since 2026-07-31 (1 finding)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
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)
Changed counts
- down 3924 of 3924 trips don't say whether the vehicle is wheelchair accessible. (7485 → 3924) (scorecard_wheelchair_accessible_unknown)
- down Some trips serve fewer than two stops. (5 → 2) (unusable_trip)
- down Some scheduled trips move faster between stops than a transit vehicle can. (6 → 4) (fast_travel_between_consecutive_stops)
- down Some trip headsigns name a stop along the way, not the final destination. (12 → 6) (trip_headsign_matches_intermediate_stop)
No longer reported since 2026-07-31 (1 finding)
- Some service calendars in the feed have already ended. (expired_calendar)
This records the later feed state. It does not establish who made a change or why.
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
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning3924 instances
3924 of 3924 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning1323 instances
1323 of 1323 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)
- Warning4 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle 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)
- Warning2 instances
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Finding code: unusable_trip · 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)
- Info6 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 42 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) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 3924 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 42 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.
- 2 of 3924 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
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 42 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.
A local transit-data support resource is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies. This resource supports agencies; it is not a scoring authority.
- Correctness 87 / 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 70 / 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 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 33 / 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/kitsap-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.