Richmond Metro Bus Routes and Schedules

Richmond Metro's fixed-route bus network forms the operational core of public transit service across the Richmond, Virginia metropolitan area. This page covers the structural framework of bus route classification, schedule mechanics, the factors that drive service frequency and routing decisions, and the tradeoffs inherent in network design. Riders, planners, transit advocates, and researchers can use this reference to understand how routes are built, maintained, and modified within the constraints of a regional transit authority.

Definition and scope
Core mechanics or structure
Causal relationships or drivers
Classification boundaries
Tradeoffs and tensions
Common misconceptions
Checklist or steps (non-advisory)
Reference table or matrix

Definition and scope

A bus route, in the context of fixed-route public transit, is a defined corridor along which vehicles operate according to a published schedule, stopping at designated locations to board and alight passengers. The Richmond Metropolitan Transit Authority (RMTA) administers this network as a public service, meaning routes are defined not purely by demand economics but by a mandate to provide baseline mobility across the service area, including corridors where ridership alone would not justify commercial operation.

The scope of the bus route network extends across the City of Richmond and into portions of Henrico County and Chesterfield County, reflecting the multi-jurisdictional character of the Richmond region. The service area defines the geographic outer boundary; individual routes operate within that boundary but do not cover every point uniformly. Frequency, span of service hours, and stop density vary significantly between corridors depending on land use, population density, and funding allocation.

Schedules — the published timetables that specify departure times at key timing points along each route — are the public-facing product of an underlying operational plan called a run cut. The run cut allocates vehicles, operators, and hours to meet scheduled service. What riders see on a printed timetable or mobile application is the downstream expression of that planning process.

Core mechanics or structure

Each bus route is defined by four technical components: alignment, stop locations, service span, and headway.

Alignment refers to the street path a route follows. Alignments are constrained by road geometry, turn radii compatible with transit vehicles (typically 40-foot or 60-foot buses), traffic signal timing, and lane availability. A route may operate over a single alignment in both directions or use different streets for inbound and outbound travel — the latter is called a couplet alignment and is common in downtown Richmond's one-way street grid.

Stop locations are fixed points where buses halt to serve passengers. The Federal Transit Administration (FTA) recommends stop spacing between 600 and 1,000 feet in urban environments to balance walk access against operating speed, though actual spacing reflects local conditions. Stops require ADA-compliant infrastructure under 49 CFR Part 37, which governs transportation services for individuals with disabilities.

Service span defines the hours during which a route operates — for example, 5:00 a.m. to midnight on weekdays. Span decisions affect workforce scheduling and fleet deployment because every hour of operation requires an operator and an available vehicle.

Headway is the interval between successive buses on the same route. A 15-minute headway means a bus arrives every 15 minutes at a given stop. Headways of 15 minutes or less are generally recognized in transit planning literature — including guidance from the Transit Cooperative Research Program (TCRP) — as the threshold below which passengers shift from schedule-based to frequency-based riding behavior, meaning they arrive at a stop at will rather than consulting a timetable.

Express routes operate on a distinct variant of this structure: longer stop spacing, limited service hours (typically peak periods only), and alignment optimized for speed over coverage. The paratransit service operates outside this fixed-route framework entirely, using demand-responsive scheduling.

Causal relationships or drivers

Route configuration and schedule frequency are determined by a layered set of causal factors, not by a single planner's judgment.

Land use density is the primary determinant of ridership potential. Routes through areas with residential densities above approximately 7 dwelling units per acre — a threshold frequently cited in TCRP Report 95 and FTA planning guidance — generate enough walk-up demand to justify frequent service. Low-density suburban corridors require either lower frequency or subsidy from cross-corridor revenue.

Funding levels set the total vehicle revenue hours available. Vehicle revenue hours — the hours a bus spends in service carrying or available to carry passengers — are the primary unit of transit resource allocation. Federal funding through FTA Section 5307 (Urbanized Area Formula Grants) and Section 5311 (Rural Area Formula Grants), administered under 49 USC Chapter 53, constitutes a significant share of operating and capital budgets for most mid-size transit systems. The federal and state funding structure directly limits or enables service expansion.

Transfer connectivity shapes routing decisions at the network level. A route that terminates at a major transit hub can rely on passengers completing their trip via a connecting route, allowing the system to serve more destinations with fewer direct routes. Effective transfer design requires coordinated timetabling — scheduled arrivals and departures timed to minimize passenger wait — which adds complexity to the run-cut process.

Operator and vehicle availability impose hard constraints. A route cannot operate if no qualified operator or mechanically available bus exists. Fleet size, maintenance cycles, and operator workforce directly bound what schedules are achievable. Details on fleet composition are available on the fleet and vehicles page.

Classification boundaries

Richmond Metro's bus routes fall into four functional classes, each with distinct operating characteristics.

Local routes form the coverage backbone. They operate throughout the day, 7 days a week on most corridors, with stop spacing averaging 600–800 feet and headways typically ranging from 20 to 60 minutes depending on the corridor's productivity.

Frequent routes operate on corridors with sufficient ridership to justify headways of 15 minutes or better during peak and often midday periods. These routes are the network's highest-ridership corridors and anchor transfer connectivity.

Express routes operate primarily during AM and PM peak periods, with stops limited to origin neighborhoods, key transfer points, and downtown destinations. See the dedicated express routes reference for classification details.

Crosstown routes connect major activity centers without routing through downtown Richmond. These routes serve riders making lateral trips — between employment centers, medical facilities, or educational campuses — that would otherwise require two transfers through downtown.

The boundary between local and frequent classification is not administrative; it reflects a threshold of demonstrated ridership productivity, typically measured in passengers per vehicle revenue hour. Routes falling below a minimum productivity standard — commonly 10–15 boardings per vehicle revenue hour in peer system benchmarks — are candidates for service reduction or restructuring.

Tradeoffs and tensions

Transit network design involves genuine conflicts between competing values, and Richmond Metro's bus network is no exception.

Coverage versus frequency is the central tradeoff in fixed-route network design. A coverage-oriented network distributes service broadly, ensuring many neighborhoods have at least one route, but results in infrequent service everywhere. A frequency-oriented network concentrates vehicles on high-demand corridors, producing fast and reliable service for the largest number of trips but leaving lower-density areas without direct service. Most transit agencies, including mid-size systems comparable to Richmond Metro, operate hybrid networks with explicit policy decisions about how much of the budget is allocated to coverage versus frequency — a framework formalized by transit consultant Jarrett Walker in Human Transit (Island Press, 2012) and adopted in planning processes by agencies including TriMet (Portland) and Houston Metro.

Span versus frequency presents a second tension. Extending a route's operating hours to serve early morning or late night riders requires additional vehicle revenue hours. If the total budget is fixed, adding span to one route typically means reducing frequency on another. Riders who depend on late-night service face a different mobility constraint than peak-hour commuters, and neither group's need is inherently more legitimate.

Reliability versus efficiency emerges in schedule padding. Operators pad schedules with recovery time at the end of each trip to allow late-running buses to reset before their next departure. Insufficient recovery time causes schedule adherence to deteriorate throughout the day — a bus running 5 minutes late compounds into 15 minutes late by midday. Excessive recovery time wastes vehicle revenue hours that could serve more trips.

Common misconceptions

Misconception: Bus routes follow the most direct path between two points.
Route alignments are shaped by street geometry, turn constraints for large vehicles, need to serve intermediate destinations, and ADA stop infrastructure. A route may travel a longer path specifically to serve a hospital, school, or transfer hub that lies off the straight-line corridor.

Misconception: A route that exists will always run on time.
Schedule adherence is a performance metric, not a guarantee. Factors including traffic signal timing, passenger boarding volumes at high-activity stops, and road construction independently affect on-time performance. The service alerts and delays page publishes real-time and planned disruption notices.

Misconception: Reducing headways is simply a matter of adding more buses.
Headway reduction requires additional vehicle revenue hours, which requires additional operators, additional vehicles, and the maintenance capacity to support a larger active fleet. Each of these has lead times measured in months to years. Operator hiring and training cycles, vehicle procurement timelines under FTA procurement rules, and facility capacity all constrain how quickly headways can be improved.

Misconception: Express routes serve more destinations than local routes.
Express routes serve fewer stops than local routes by design. Their purpose is to reduce travel time for riders making long-distance trips along a corridor, not to maximize the number of intermediate destinations served.

Checklist or steps

The following sequence describes the steps in a standard route or schedule modification process as practiced by transit agencies operating under FTA oversight:

Service need identification — Ridership data, passenger complaints, land use changes, or budget adjustments trigger an assessment of whether a route's current configuration meets performance standards.
Productivity analysis — Boardings per vehicle revenue hour, farebox recovery, and passenger load factors are calculated for the route segment under review.
Alternatives development — Planners develop 2–4 candidate modifications: alignment changes, headway adjustments, span modifications, or route consolidation.
Title VI equity analysis — Under FTA Circular 4702.1B, changes meeting the threshold of a "major service change" require analysis of disparate impact on minority populations and disproportionate burden on low-income populations. Most transit agencies define "major service change" as a modification affecting 25% or more of a route's mileage or a headway change exceeding a defined percentage.
Public engagement — The agency conducts public meetings, comment periods, or both. For major service changes, FTA civil rights requirements mandate documented outreach to affected communities.
Governing board approval — Significant service changes are presented to the governing board for approval. Administrative schedule adjustments may fall within operator authority without board action.
Run cut development — Once a change is approved, schedulers develop the operator run cut — the specific block assignments and operator duties — needed to implement the new service pattern.
Publication and implementation — Updated schedules are published in print and digital formats. GTFS (General Transit Feed Specification) data is updated to propagate changes to third-party trip planning applications.

For questions about specific schedule changes or how to navigate route information, the how to get help for Richmond Metro page describes available support channels.

Reference table or matrix

The table below summarizes the distinguishing characteristics of each bus route class within a fixed-route transit network of Richmond Metro's type.

Route Class	Typical Headway	Service Days	Stop Spacing	Primary Purpose
Local	20–60 min	7 days	600–800 ft	Geographic coverage
Frequent	10–15 min	7 days	600–800 ft	High-demand corridors
Express	15–30 min (peak only)	Weekdays	1–3 mi	CBD commuter trips
Crosstown	30–60 min	Varies	600–1,000 ft	Lateral connectivity

The fares and passes structure applies uniformly across local and crosstown routes; express routes may carry a fare premium depending on agency policy. Riders using reduced fare programs retain eligibility across all fixed-route classes subject to program terms. The broader Richmond Metro overview provides context on how bus service integrates with rail, paratransit, and regional transportation planning.