TRANSIT
ATLAS
Explore/Clark County/Stop ID 5117
◎

Regional Transportation Commission of Southern Nevada (RTC) / BOARDING STOP

SB Fort Apache after Charleston

Stop code 5117 · Regional Transportation Commission of Southern Nevada (RTC) network

SB Fort Apache after Charleston

Next departures

America/Los_Angeles
120
120 Rampart / Fort Apache SouthboundScheduled
47 min9:13 PM · Thu, Oct 29
120
120 Rampart / Fort Apache SouthboundScheduled
10:13 PM10:13 PM · Thu, Oct 29
120
120 Rampart / Fort Apache SouthboundScheduled
11:13 PM11:13 PM · Thu, Oct 29
120
120 Rampart / Fort Apache SouthboundScheduled
12:10 AM12:10 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
1:09 AM1:09 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
4:43 AM4:43 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
5:36 AM5:36 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
6:24 AM6:24 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
6:54 AM6:54 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
7:24 AM7:24 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
7:54 AM7:54 AM · Fri, Oct 30
120
120 Rampart / Fort Apache SouthboundScheduled
8:24 AM8:24 AM · Fri, Oct 30
Live data unavailableRefreshes every 30 seconds

Routes at this boarding location

120
Regional Transportation Commission of Southern Nevada (RTC) · Bus

Fort Apache/Rampart

Schedules, stops & departures
↗

Other stops nearby

◎EB Charleston before Fort Apache↗◎EB Charleston after Fort Apache↗◎WB Charleston after Rampart↗◎WB Charleston after Odette↗◎NB Rampart after Charleston↗

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

✓
Published Regional Transportation Commission of Southern Nevada (RTC) schedule

Imported Oct 24, 2026 · 04:52 UTC · Service dates 2026-08-23 through 2027-08-21. See data status

Schedule data published by Regional Transportation Commission of Southern Nevada (RTC). Feed discovery and cached source archives from MobilityData. Source details ↗