Everett Transit

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 88 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 2196 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 100% 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 88 days.

Accessible Not yet

States wheelchair access on 100% 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.

• 4 of 500 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 17s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Live predictions vs schedule

Arrival predictions ran right on the schedule, and stayed within 0s nine times in ten. They were on time (about a minute early to five late) 100.0% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.

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.

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 80 / 100

GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.

Freshness 100 / 100

GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.

Rider experience 35 / 100

GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.

Realtime quality 100 / 100

GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.