HUT Airport Shuttle

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.

   Neither feed_info.txt nor the calendars state when service ends. Nobody can tell when this feed will go stale.

   Effort: Likely a one-time export setting.

2. Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Missing calendar and calendar date files (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. 2 validator errors to resolve. No service end date could be read, so currency is unknown.

Published Ready

Published at a public URL.

Valid Needs attention

2 validator errors to resolve.

Current Not ready

No service end date could be read, so currency is unknown.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

The bar this score answers to

The state transit-data program is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS.

Key facts

Feed URL

http://oregon-gtfs.com/gtfs_data/hut-or-us/hut-or-us.zip

Last checked

2026-07-08

Service window

Expiry date not stated in the feed.

State

Oregon