Wayne @ Utah

Stop code 7349 · Greater Dayton Regional Transit Authority (Greater Dayton RTA) network

Wayne @ Utah

Next departures

America/New_York

Troy & Leo via Valley StScheduled · estimated time

38 min10:52 AM · Sat, Oct 31

Five Oaks to TrotwoodScheduled · estimated time

45 min10:58 AM · Sat, Oct 31

Troy & Leo via Valley StScheduled · estimated time

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

Five Oaks to TrotwoodScheduled · estimated time

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

Troy & Leo via Valley StScheduled · estimated time

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

Five Oaks to TrotwoodScheduled · estimated time

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

Troy & Leo via Valley StScheduled · estimated time

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

Troy & Leo via Valley StScheduled · estimated time

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

Five Oaks to TrotwoodScheduled · estimated time

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

DowntownScheduled · estimated time

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

DowntownScheduled · estimated time

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

DowntownScheduled · estimated time

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

Live data unavailableRefreshes every 30 seconds

Routes at this boarding location

Greater Dayton Regional Transit Authority (Greater Dayton RTA) · Bus

ROUTE 3

Schedules, stops & departures

↗ 12

Greater Dayton Regional Transit Authority (Greater Dayton RTA) · Bus

ROUTE 12

Schedules, stops & departures

↗

Other stops nearby

◎ANDERSON @ WAYNE↗◎STEWART @ MEDFORD↗◎STEWART @ MEDFORD↗◎STEWART @ ANDERSON↗◎STEWART @ WAYNE↗◎WAYNE @ GEBHART↗◎WAYNE @ VOLKENAND↗◎WAYNE @ ANDERSON↗◎WAYNE @ EDGAR↗◎WAYNE @ WILMINGTON↗◎WAYNE @ WILMINGTON↗◎WAYNE @ WILMINGTON↗

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

✓

Published Greater Dayton Regional Transit Authority (Greater Dayton RTA) schedule

Imported Oct 24, 2026 · 04:35 UTC · Service dates 2026-09-06 through 2027-01-02. See data status

Schedule data published by Greater Dayton Regional Transit Authority (Greater Dayton RTA). Feed discovery and cached source archives from MobilityData. Source details ↗