Methodology

Three kinds of number appear on this site, kept apart in the database and on the page:

  1. Published figures, stored exactly as RTD or the FTA published them, each tied to a logged load of a named source.
  2. Derived figures, calculated from published ones by the formulas below and rebuilt from scratch on every refresh.
  3. User-contributed observations, always labelled, never used in any published or derived figure.

System cost rates

For each NTD report year and mode (bus, light rail, commuter rail, demand response), RTD-operated and contractor-operated rows are added together, then:

Fully-burdened cost

Operating expense leaves out what the vehicles, track and buildings cost. Fully-burdened cost adds depreciation and interest expense from RTD's Annual Comprehensive Financial Report, allocated to each mode by its share of operating expense. Only ACFR figures marked verified against the page are used. Until they are loaded, fully-burdened columns show "n/a" rather than an estimate. NTD capital spending is shown separately. It is not used here because it is cash spent in a year, which jumps around.

Route cost

RTD does not publish cost by route. It does publish each route's annual boardings and service hours, compiled for 2018–2024 by Greater Denver Transit.

What this misses. Every route is charged the system-average rate. In reality, peak-only routes cost more per hour (split shifts, buses idle midday), and contracted routes have different unit costs from RTD-operated ones. Route years without a matching NTD year are not costed. The calibration table shows how much of RTD's total service the matched routes cover.

Scheduled service (GTFS)

From the current GTFS feed: each trip's revenue miles = the length of its shape, measured in PostGIS on the WGS84 ellipsoid. Its hours = last arrival − first departure. Annual totals = Σ trips × days the trip runs in the feed window × 365 ÷ window length. A route is peak-only if it has weekday trips, none starting between 10:00 and 14:59, and no weekend trips. Route type (local / limited / express / regional / airport) comes from RTD's naming conventions and can be corrected in the admin.

Security and fare evasion

NTD security events are federally reportable events only, shown per million boardings. Fare-check figures come from RTD news releases and dashboards, cited row by row. Estimated lost fares = non-payment rate × the mode's annual boardings × average fare. This is an upper bound, because some riders who didn't pay would not otherwise have ridden.

Robotaxi scenario

Every input is set by you. Vehicle-miles = boardings × trip length × (1 + empty-mile share) ÷ riders per vehicle trip. Operator cost = vehicle-miles × cost per vehicle-mile. Compared on net public cost: (bus cost − bus fares) against (robotaxi cost − rider fares).

Conclusion page

The Conclusion page is an argument; its numbers come from the sources on this site, combined as follows.