Explore/Auburn/Stop ID 22730

◎

King County Metro / BOARDING STOP

35th Ave SW & SW Raymond St

Stop code 22730 · King County Metro network

35th Ave SW & SW Raymond St

Next departures

America/Los_Angeles

21

Downtown Seattle Via 35th Ave SWLive · estimated time

26 min10:46 AM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWLive · estimated time

45 min11:05 AM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

11:25 AM11:25 AM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

11:45 AM11:45 AM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

12:05 PM12:05 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

12:25 PM12:25 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

12:45 PM12:45 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

1:05 PM1:05 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

1:25 PM1:25 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

1:45 PM1:45 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

2:05 PM2:05 PM · Sat, Oct 31

21

Downtown Seattle Via 35th Ave SWScheduled · estimated time

2:25 PM2:25 PM · Sat, Oct 31

Live predictions availableRefreshes every 30 seconds

Routes at this boarding location

King County Metro · Bus

21

Schedules, stops & departures

Other stops nearby

◎35th Ave SW & SW Morgan St↗◎SW Morgan St & 35th Ave SW↗◎SW Morgan St & Lanham Pl SW↗◎SW Morgan St & 38th Ave SW↗◎SW Morgan St & Lanham Pl SW↗◎SW Morgan St & 35th Ave SW↗◎35th Ave SW & SW Morgan St↗◎35th Ave SW & SW Findlay St↗

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

✓

Published King County Metro schedule

Imported Oct 24, 2026 · 04:37 UTC · Service dates 2026-08-29 through 2027-12-31. See data status

Schedule data published by King County Metro. Feed discovery and cached source archives from MobilityData. Source details ↗

Privacy Policy Contact