◎

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

EB Flamingo after Cameron

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

EB Flamingo after Cameron

Next departures

America/Los_Angeles
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
2 min11:13 AM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
17 min11:28 AM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
32 min11:43 AM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
47 min11:58 AM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
12:13 PM12:13 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
12:28 PM12:28 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
12:42 PM12:42 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
12:56 PM12:56 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:11 PM1:11 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:26 PM1:26 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:41 PM1:41 PM · Thu, Oct 29
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
1:57 PM1:57 PM · Thu, Oct 29
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 ↗