◎

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

EB Flamingo after Palos Verdes

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

EB Flamingo after Palos Verdes

Next departures

America/Los_Angeles
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
27 min3:35 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
57 min4:05 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
4:35 AM4:35 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
5:00 AM5:00 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
5:24 AM5:24 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
5:42 AM5:42 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
6:02 AM6:02 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
6:17 AM6:17 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
6:35 AM6:35 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
6:50 AM6:50 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
7:05 AM7:05 AM · Wed, Oct 28
202
202 Flamingo EB (F1 Schedule Changes in Effect)Scheduled · estimated time
7:20 AM7:20 AM · Wed, Oct 28
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 ↗