◎

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

WB Flamingo after Cimarron

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

WB Flamingo after Cimarron

Next departures

America/Los_Angeles
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
3 min10:27 PM · Thu, Oct 29
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
22 min10:46 PM · Thu, Oct 29
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
41 min11:05 PM · Thu, Oct 29
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
11:25 PM11:25 PM · Thu, Oct 29
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
11:45 PM11:45 PM · Thu, Oct 29
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
12:05 AM12:05 AM · Fri, Oct 30
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
12:35 AM12:35 AM · Fri, Oct 30
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:05 AM1:05 AM · Fri, Oct 30
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:33 AM1:33 AM · Fri, Oct 30
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:58 AM1:58 AM · Fri, Oct 30
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
2:28 AM2:28 AM · Fri, Oct 30
202
202 Flamingo WB (F1 Schedule Changes in Effect)Scheduled · estimated time
2:58 AM2:58 AM · Fri, Oct 30
Live data unavailableRefreshes every 30 seconds

Routes at this boarding location

Other stops nearby

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 ↗