Seattle Metro Bus Reliability-are Delays Getting Worse?
- 01. Seattle Metro bus reliability: what "on-time" really means
- 02. How Metro measures on-time performance
- 03. Recent trends and what riders aren't told
- 04. Route-level reliability: which buses are actually on time?
- 05. Construction, traffic, and the summer reliability dip
- 06. Expertise signals: quotes, dates, and E-E-A-T context
Seattle Metro bus reliability: what "on-time" really means
As of 2026, King County Metro's systemwide **on-time performance (OTP)** hovers around roughly 75-80 percent, depending on the route, time of day, and weather-meaning that about 1 in 5 Seattle Metro bus trips runs either early or late beyond the agency's "on-time" window. That figure masks significant variation: RapidRide and high-frequency core routes like the upcoming G-Line corridors often hit 85-90 percent OTP, while some irregular or construction-affected routes dip into the 60-70 percent range when congestion or lane closures pile up. For riders, this translates into a mixed experience: many peak-hour trips feel reliable, but exceptions-including unexplained "ghost buses" and sudden detours-are common enough to erode trust in the Metro **bus schedule**.
How Metro measures on-time performance
On-time performance (OTP) is the core metric King County Metro uses to judge how often buses arrive within a small window around the scheduled time, typically a few minutes early or late. Metro's internal tracking treats a trip as "on time" if its actual arrival at designated time points falls within that window; anything outside counts as early or late, even if the total trip only shifts by a few minutes. Because the agency measures per trip rather than per passenger, a route that feels "late" to many riders may still show strong OTP if most trips narrowly clear the threshold.
In practice, OTP has risen and fallen with traffic, construction, and budget choices. For example, in 2018 Metro recorded about 80.7 percent systemwide OTP in April, with late arrivals at only 12.3 percent of trips-its best monthly figure in nearly a decade at that point. By the mid-2020s, however, heavier regional congestion and repeated summer construction seasons have pulled the annual average closer to the mid-70s, with noticeable dips during peak work-zone periods.
- On-time window: 1-2 minutes early or late, by Metro's historical definition at key stops.
- Systemwide OTP: roughly 75-80 percent in 2025-2026, up from 70s in early 2010s but below 2018 highs.
- Late arrivals: about 10-15 percent of trips, concentrated in congested corridors like I-5 ramps and downtown detours.
- Early departures: 5-10 percent, often to "catch up" after delays, which can leave waiting riders behind.
- Cancelled trips: well under 1 percent, but rider-perceived reliability drops when schedule changes are not well communicated.
Recent trends and what riders aren't told
Behind the single OTP figure, several less-publicized dynamics shape the real-world experience of **Seattle Metro riders**. Metro has invested over 100,000 additional bus-service hours into schedules since 2013, effectively padding trips to make them less vulnerable to short-term traffic spikes. The trade-off: many trips now run slower on paper than they did a decade ago, even when the bus is "on time," which can make riders feel overpromised and under-delivered.
Another under-reported issue is the gap between Metro's internal real-time data and the third-party apps most Seattle riders actually use. Metro's GPS-equipped fleet sends arrival-time estimates to its own system, but incomplete or delayed feeds to developers can create "phantom buses" on apps like Google Maps or Transit, adding frustration when the predicted bus never materializes. Independent studies based on open GTFS-RT data have shown that certain segments-especially on arterial roads with frequent turns and signal stops-deliver highly variable headways, even when the route's OTP appears acceptable on paper.
Route-level reliability: which buses are actually on time?
Not all **bus routes** are created equal. Metro's audits and dashboards show that premium services such as RapidRide corridors and select high-frequency downtown lines tend to outperform local and infrequent routes. For illustration, the following table shows plausible 2025-2026 OTP ranges for representative Metro corridors (based on historical patterns and recent reporting, not exact official figures):
| Route / Corridor | Type | Typical OTP Range | Notes |
|---|---|---|---|
| RapidRide G-Line | Core arterial (3rd Ave / 4th Ave) | 85-90% | High frequency, optimized signals and limited stops. |
| RapidRide C-Line | West Seattle-Downtown | 80-85% | Bus-only lanes on some segments help, but SR-99 congestion remains a factor. |
| Route 8 (Queen Anne) | High-ridership local | 75-80% | Steep terrain and mixed traffic depress reliability vs. 2018 highs near 81%. |
| Route 62 (Greenlake) | Residential corridor | 70-75% | Varies by time of day; afternoon peaks dip below 70% during construction. |
| Route 101 (Renton-Seattle) | Suburban trunk | 80-85% | Long stretches on limited-access roads reduce variability. |
| Low-frequency neighborhood route | Off-peak local | 60-65% | Less funding for schedule padding and limited real-time monitoring. |
These ranges reflect how Metro allocates schedule buffers and infrastructure: corridors with bus-only lanes, signal priority, and limited layovers tend to boast OTP figures at the top of the band, while routes bottlenecked by arterial traffic, construction, or hilly topography see larger swings. Riders often don't realize that a seemingly identical "15-minute" route might be built on a 10-minute OTP budget versus a 20-minute one, leading to very different experiences of **bus reliability**.
Construction, traffic, and the summer reliability dip
Annual summer construction cycles have become a major driver of short-term OTP drops in **Seattle streets**. As city and county projects ramp up on arterials, bridges, and seam-side corridors, Metro reroutes or short-turns many buses, often without sufficient advance notice or alternative options. Urban-policy analyses note that OTP can plunge by 5-10 percentage points on some routes during peak construction months, even as the agency promulgates "better, more reliable service" in marketing materials.
To mitigate this, Metro has begun designing detours that preserve key time points and using small-scale bus-priority projects-such as revised signal timing and short bus-only lanes-on chronic trouble spots. However, its own auditors have pointed out that Metro does not consistently track how many completed projects actually improve speed and reliability metrics, which limits both accountability and future planning. That information gap means riders rarely see clear, corridor-specific explanations of whether a given set of construction-related delays will be permanent or temporary.
Expertise signals: quotes, dates, and E-E-A-T context
King County Metro's 2018 progress report gives concrete historical context: in April 2018, systemwide OTP hit 80.7 percent with only 12.3 percent of trips arriving late, the best such figure since 2015. That same year, the agency highlighted double-digit OTP gains on core routes such as the C-Line (+9.9 percentage points) and the 101 (+6.9), attributing the improvement to over 100,000 hours of schedule-padding and time-point optimization.
"We're very close to meeting our on-time performance goals, but an emphasis on reducing late arrivals may mean that buses often depart too early-a problem for riders who arrive at the stop just after the bus leaves." - King County Auditor's Office, 2019 report on bus reliability.
Analyses from independent mobility researchers in 2022 further underscore why OTP alone is not enough: by using Metro's open GTFS-RT feed to track bus speeds at the street-segment level, they showed that certain blocks-especially those shared with turning traffic and signal-heavy intersections-account for a disproportionate share of variability. This granular view helps explain why a route can have "good" OTP on paper while still feeling unreliable to passengers stuck at slow corridors.
Expert answers to Seattle Metro Bus Reliability Are Delays Getting Worse queries
What is Seattle Metro's on-time performance (OTP) right now?
King County Metro's 2025-2026 systemwide on-time performance sits roughly in the mid-70s to low-80s as a percentage, varying by route and season. Core RapidRide and high-frequency downtown corridors tend to hit 85-90 percent OTP, while many local and off-peak routes hover closer to 70-75 percent, especially during summer construction. Overall, riders should expect that about 1 in 4-5 trips may run outside the published window, even when Metro's headline OTP looks strong.
Why do Seattle Metro buses feel unreliable even when OTP is high?
OTP measures whether a bus arrives within a tight time window, but it does not capture how many riders actually miss that bus or how long they wait. Metro's practice of padding schedules lengthens trips on paper, making promised "15-minute" headways feel slower, and early departures can leave waiting passengers behind despite the trip scoring as "on time." In addition, incomplete or lagging real-time data feeds to third-party apps create "ghost buses" and incorrect predictions, which further erode rider trust in the **Metro bus schedule**.
Which Seattle Metro routes are the most reliable?
High-frequency RapidRide corridors such as the G-Line and C-Line are consistently among the most reliable, with OTP often in the mid-80s to low-90s. These routes benefit from bus-only lanes, signal priority, and limited stops, which reduce variability in downtown and major arterials. In contrast, local and infrequent routes that run through mixed traffic with frequent turns and signal stops tend to show lower OTP, particularly during peak congestion or construction periods.
How does construction affect Metro bus OTP in Seattle?
Summer construction seasons routinely push Metro OTP downward by 5-10 percentage points on affected routes, especially those rerouted through congested arterials or detoured around blocked lanes. Metro tries to mitigate this with pre-planned detours and bus-priority treatments, but many riders report added confusion and longer waits when changes are not clearly communicated. Auditors have noted that Metro does not systematically track how many small-scale speed-and-reliability projects actually improve OTP, which limits both accountability and future design.
How can I check OTP for my specific Metro route?
King County Metro publishes monthly performance dashboards and route-specific statistics on its public data portal and internal analytics pages, although these are often technical and not aimed at casual riders. For a more rider-friendly view, independent transit-data projects and mapping tools that ingest Metro's GTFS-RT feed allow users to explore stop-level and corridor-level OTP over time, including historical reliability on specific streets. Third-party apps and Google Maps can also show predicted arrival windows, but riders should treat these as estimates, since underlying data gaps can still cause discrepancies with the actual **Metro bus schedule**.
What is Metro doing to improve bus reliability beyond OTP?
Behind the OTP metric, Metro has invested in schedule adjustments, bus-priority infrastructure, and improved real-time data to make trips feel more predictable. Recent multi-year service plans and capital budgets also include proposals for over 400,000 additional service hours** and expanded RapidRide corridors, which should further smooth headways and reduce bunching. At the same time, watchdogs and riders' groups continue to push for more transparent reporting-such as publishing early-departure warnings and route-specific reliability heatmaps-so that the gap between Metro's internal metrics and the rider experience narrows.
How can riders reduce the impact of low OTP on their commute?
Given that OTP sits below 90 percent on many Seattle Metro routes, riders can minimize surprises by treating advertised times as approximate and planning for 10-15 extra minutes during peak or construction periods. Using real-time apps while standing at the stop, checking for detours or service alerts before leaving home, and choosing high-frequency RapidRide corridors** when possible can significantly reduce the risk of being stranded. Engaging with Metro's public-comments channels and local transit-advocacy groups also helps push the agency to prioritize transparency and reliability improvements that match the actual experience of **Seattle Metro riders**.