Anchorage Metro Schedules and Trip Planning Tools

Anchorage People Mover's fixed-route bus network operates on published timetables that define when and where service runs across the municipality. Understanding how to read those schedules and use the available planning tools is the practical foundation for any successful transit trip in Anchorage. This page explains what schedule resources exist, how the trip planning process works, what situations require specific planning approaches, and where the boundaries of automated tools end and manual judgment begins.

Definition and scope

A transit schedule is a structured document that specifies the departure and arrival times of a bus at each named stop along a route. For Anchorage People Mover — the fixed-route bus service operated under the Anchorage transit system — schedules are published per route and organized into weekday, Saturday, and Sunday/holiday service periods. The full network covers People Mover's standard fixed routes as well as the DART (Dial-A-Ride Transit) demand-responsive zones, which operate under different scheduling logic than fixed-route service.

Trip planning tools layer on top of raw schedules to answer origin-to-destination questions: which route or combination of routes connects two addresses, at what time, and with how many transfers. The Anchorage Metro home page consolidates access to the primary digital planning resources available to riders.

Scope of this page is limited to the scheduling and planning layer — the act of determining when and how to travel. Adjacent topics such as real-time tracking, fares and passes, and paratransit options interact closely with schedule planning but are covered separately.

How it works

People Mover schedules are produced through a process that ties route timetables to physical timepoints — specific named stops where buses are held to schedule rather than allowed to run ahead. Between timepoints, buses may run slightly early or late depending on traffic; they are not supposed to depart a timepoint early under standard operating policy.

The primary digital trip planning tool integrated with People Mover uses the General Transit Feed Specification (GTFS), an open data standard originally developed by Google and TriMet (Portland, Oregon) and now maintained as a public specification (MobilityData GTFS Reference). GTFS packages route geometry, stop locations, calendar service dates, and timetables into a machine-readable feed that third-party journey planners — including Google Maps and Transit App — consume automatically.

A standard trip plan is generated through 4 sequential steps:

1. Origin and destination input — the rider enters a starting address or stop and a destination address or stop.
2. Route matching — the tool identifies which route or routes serve stops within walking distance of both points.
3. Time filtering — the tool cross-references the requested departure or arrival time against active service calendars to confirm service runs that day.
4. Transfer construction — if no single route connects origin to destination, the tool identifies transfer points, calculates layover time, and builds a multi-leg itinerary.

Printed schedule booklets remain available at the Downtown Transit Center and at park-and-ride locations for riders without reliable smartphone or internet access.

Common scenarios

Standard commute planning involves a fixed origin and destination with a consistent travel time window. Riders in this scenario typically identify 1 or 2 route options and memorize a small number of departure timepoints near their origin stop.

Multi-stop or transfer trips require coordinating 2 or more route legs. Anchorage's grid-based core routes — including Routes 3, 7, 9, and 60, among others — intersect at the Downtown Transit Center, making it the most common transfer hub. A rider traveling from a midtown residential area to the University of Alaska Anchorage campus, for example, may need to transfer once, with a layover window of 5 to 15 minutes depending on the schedule cycle.

Airport and major destination trips involve routes with lower frequency. People Mover's Route 40, which connects to Ted Stevens Anchorage International Airport, operates on a schedule distinct from the high-frequency urban core routes, so trip timing is more sensitive to missed connections.

Weekend and holiday travel requires separate schedule review because Sunday and holiday service levels are reduced relative to weekday timetables. Headways (the interval between buses on the same route) extend to 60 minutes or longer on lower-service days for a portion of the network.

Winter operations affect schedule reliability. Anchorage averages roughly 75 inches of snowfall annually (National Weather Service, Anchorage Forecast Office), and service delays during active snowfall events are common.

Decision boundaries

Automated trip planners handle the majority of straightforward origin-to-destination queries accurately, but 4 categories of trips require manual verification beyond what automated tools reliably produce:

1. DART zone trips — demand-responsive service requires advance reservation and does not appear in standard fixed-route trip planners. Riders must contact People Mover directly to confirm DART availability and booking windows.
2. Service change periods — when seasonal or structural service changes take effect, GTFS feeds require an update cycle before third-party planners reflect the new timetables. Checking the official People Mover schedule page directly during transition periods reduces the risk of outdated itinerary data.
3. Trips involving reduced fare eligibility or accessibility services — these riders may have access to paratransit or complementary ADA service that operates under separate scheduling rules outside the fixed-route planner.
4. Late-night and early-morning travel — People Mover does not operate 24-hour service. The last scheduled departures on most routes fall between 9:00 PM and 11:00 PM, and the first morning departures begin between 5:30 AM and 6:30 AM depending on route, leaving gaps that fixed-route planning tools correctly report as no-service periods but may not surface alternative options for.

Understanding which scenario a trip falls into determines whether a digital planner output can be trusted directly or whether a call to People Mover customer service is warranted before travel.

References

• MobilityData — GTFS Schedule Reference
• Municipality of Anchorage — People Mover
• National Weather Service, Anchorage Forecast Office — Climate Normals
• Federal Transit Administration — Transit Data and Statistics
• MobilityData — Open Mobility Data