The feed address on file failed at our last check (HTTP 403). Download the newest saved copy from the Mobility Database, or send us the new address.
Feed status · checked 2026-11-09
RIDE Sitka
Based on a Mobility Database mirror copy of an archived feed listing
Scored from a Mobility Database mirror copy downloaded on 2026-10-19, because the feed URL on file could not be downloaded. Service dates in that copy end 2021-12-31. It may not match the feed the agency publishes today.
Service mode Bus
Partial: freshness not measured.
Methodology changed; trend restarts here
Cataloged in Alaska.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://transitfeeds.com/p/ride-sitka/713/latest/download
Failed at last check (HTTP 403) Newest saved copy
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
Check that https://transitfeeds.com/p/ride-sitka/713/latest/download still serves your current feed. If the feed moved, publish the new address.
The feed URL on file, https://transitfeeds.com/p/ride-sitka/713/latest/download, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2021-12-31, so freshness is not graded until the current feed can be downloaded.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Usually a server or hosting setting, not a change to the feed itself.
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
52 of 52 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 52 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Alaska 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.
This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Fix 03 · Read the fix guide for scorecard_no_fare_data
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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
- Schedule visibility is not known from this scorecard.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names 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.
RIDE Sitka’s published feed lists 3 bus routes, 3 scheduled trips and 52 stops. The published file has not changed since our first check on 2026-06-19.
Score by category
The MobilityData validator flagged 5 kinds of issue across 8 instances (0 error, 7 warning, 1 informational).
Not graded. The feed URL on file could not be downloaded, and the Mobility Database mirror copy scored instead ended its service on 2021-12-31. That date describes the copy, not the feed the agency publishes today, so it does not count against the grade.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
19 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Price St / Burkhart Dr", "Arrowhead St / Monastery St", "Verstovia St / A 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.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 52 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.
- Blue Line (blue)
- Green Line (green)
- Red Line (pink)
| Route | Type | Line color |
|---|---|---|
| Blue Line | Bus | blue |
| Green Line | Bus | green |
| Red Line | Bus | pink |
List every stop
- Alder Wy / Halibut Point Rd
- Anna Drive / Sawmill Creek Rd
- Arrowhead St / Monastery St
- Arrowhead Transfer
- Baranof St / Sawmill Creek Rd
- Biorka St / Sawmill Creek Rd
- Blue Apartments
- Cascade Laundry
- Cascade Creek Bridge - Inbound
- Cascade Creek Bridge - Outbound
- Channel Club
- Charteris St / Edgecumbe Dr
- Sitka Community Hospital
- Community House
- Crescent Harbor
- Center For Community
- Eagles Roost
- Ferry Terminal
- Gary Paxton Industrial Park
- Grace Harbor Church
- Horizon Way / Halibut Point Rd
- Kaasdaa Heen Cr / Indian River Rd
- Kashevaroff St / Edgecumbe Dr
- Lakeside Grocery
- McDonalds
- Mills St / Edgecumbe Dr
- Sitka National Historical Park Main Entrance
- Sitka National Historical Park Sawmill Creek Rd Entrance
- Peter Simpson Rd / Indian River Rd
- Pirates Wy / Halibut Point Rd
- Price St / Burkhart Dr
- HPR Rec - Inbound
- HPR Rec - Outbound
- Random House
- Sandy Beach
- Sand Dollar Dr / Halibut Point Rd
- Sealing Cove
- SEARHC - Mt Edgecumbe Hospital
- Sea Mart
- Swan Lake Senior Center
- Sharon Dr / Halibut Point Rd
- Sitka High School
- Sitka Tribe
- SJ Campus
- Sollars Ct / Halibut Point Rd - Inbound
- Sollars Ct / Halibut Point Rd - Outbound
- Thimbleberry Lake
- UAS
- US Coast Guard
- Verstovia St / A St
- Whale Park
- Wildlife Troopers
Over time
The producer or measurement contract changed since the prior check, so the trend restarts here. No improvement or regression is claimed across that boundary.
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-09 | 6cbca8d91092 | not recorded | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | 6cbca8d91092 | 2021-12-31 | F, 52.9 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | 6cbca8d91092 | 2021-12-31 | F, 52.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (9 checks) | 6cbca8d91092 | 2021-12-31 | F, 52.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (24 checks) | 6cbca8d91092 | 2021-12-31 | F, 52.9 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning52 instances
52 of 52 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)
- Warning4 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · 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
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
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 for unknown_column · 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)
How we measured this
Checked for changes 13 days ago; last fetch returned HTTP 403.
The latest run did not download this feed: the host's robots.txt could not be read, and this scorecard does not request a feed until it can. The grade shown was measured on 2026-11-09.
Measured 2 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Freshness and Realtime quality were not measured this run. They do not count against the grade.
- The archived feed URL on file was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
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.4, validator 8.0.1.
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. No service end date could be read, so currency is unknown. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- No service end date could be read, so currency is unknown.
- agency_id provided Not ready
- agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- shapes.txt covers your trips Ready
- All 3 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. No service end date could be read. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- No service end date could be read.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Below the Google and Apple Maps four-week coverage bar. This feed has no service end date, so Maps cannot tell how far ahead it runs. Set a feed_info end date and a calendar that covers at least the next four weeks, then re-export.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 84 / 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 Not yet published
- 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 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Alaska portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Alaska
Other scorecards in Alaska, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/ride-sitka/2026-11-09.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-09. 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.