TRANSIT
ATLAS
Explore/King County/Stop ID 73420
◎

Sound Transit, Metro Transit, City of Seattle - King County Metro / BOARDING STOP

NE Redmond Way & 148th Ave NE

Stop code 73420 · Sound Transit, Metro Transit, City of Seattle - King County Metro network

NE Redmond Way & 148th Ave NE

Next departures

America/Los_Angeles
250
Avondale Bear Creek P&RScheduled · estimated time
17 min5:49 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
45 min6:17 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
6:47 PM6:47 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
7:17 PM7:17 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
7:45 PM7:45 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
8:15 PM8:15 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
8:45 PM8:45 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
9:15 PM9:15 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
9:45 PM9:45 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
10:14 PM10:14 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
10:44 PM10:44 PM · Sat, Oct 31
250
Avondale Bear Creek P&RScheduled · estimated time
11:43 PM11:43 PM · Sat, Oct 31
Live data unavailableRefreshes every 30 seconds

Routes at this boarding location

250
Sound Transit, Metro Transit, City of Seattle - King County Metro · Bus

250

Schedules, stops & departures
↗

Other stops nearby

◎148th Ave NE & NE Redmond Way↗◎148th Ave NE & NE Redmond Way↗◎NE Redmond Way & 149th Pl NE↗

Nearby locations are based on coordinates; walking connections have not been verified.

✓
Published Sound Transit, Metro Transit, City of Seattle - King County Metro schedule

Imported Oct 30, 2026 · 09:32 UTC · Service dates 2026-08-29 through 2027-12-31. See data status

Schedule data published by Sound Transit, Metro Transit, City of Seattle - King County Metro. Feed discovery and cached source archives from MobilityData. Source details ↗

Privacy PolicyContact