Sources and data freshness
Every official figure on this site comes from one of these sources. Each load is logged with the URL fetched, the publisher's version or date, a checksum and a row count. Rider observations are stored separately and listed under Rider observations.
- News releases and reporting (FreeRide figures, Zoox fares), 2026-11-19 10:59: ValueError: Invalid isoformat string: '2026-08'
RTD GTFS static feed
Regional Transportation District (RTD) · updates: Each service change (roughly 3 times a year: January, May, August/September)
Routes, stops, shapes, trips, stop times and service calendars. Used for route length, stop lists, scheduled frequency, peak-only detection and scheduled revenue miles and hours.
Limitations. Scheduled service only: no deadhead, cancellations or detours. Annual totals are the feed window scaled to 365 days, so seasonal changes outside the window are not captured.
- Fetched from
- https://www.rtd-denver.com/files/gtfs/google_transit.zip
- About the data
- https://www.rtd-denver.com/open-records/open-spatial-information
- Source version
- Sep26-37381-22-23-20261113-122950
- Rows
- 844,989
- SHA-256
- a80cf0a40b2d282811d7ce9417395a01bdebc052e03791bf5058541f5acb2867
- Refresh
python manage.py load_gtfs
NTD Annual Data - Metrics (agency 80006)
Federal Transit Administration, National Transit Database · updates: Annual; a report year is published roughly 10 months after it ends
Operating expense, fare revenue, unlinked passenger trips, passenger miles, vehicle revenue miles and hours by mode and type of service. These are the system-average cost rates applied to routes.
Limitations. Mode level only. Purchased-transportation rows are contractor costs and exclude some RTD overhead that sits in the directly-operated rows.
- Fetched from
- https://data.transportation.gov/resource/ekg5-frzt.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2026-10-14
- Rows
- 24
- Refresh
python manage.py load_ntd
NTD Operating Expenses by Function (agency 80006)
Federal Transit Administration, National Transit Database · updates: Annual
Splits each mode's operating cost into vehicle operations, vehicle maintenance, facility maintenance and general administration. Answers 'why does this cost exist?'.
Limitations. Security / transit police is inside these functions (mostly general administration), not a separate line. Its size comes from RTD's budget (see Financial documents).
- Fetched from
- https://data.transportation.gov/resource/dkxx-zjd6.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2026-10-14
- Rows
- 24
- Refresh
python manage.py load_ntd
NTD Capital Expenses by Mode (agency 80006)
Federal Transit Administration, National Transit Database · updates: Annual
Capital spending by mode and asset type (vehicles, guideway, stations, facilities).
Limitations. Cash spent in the year, which is lumpy. Fully-burdened cost uses ACFR depreciation instead.
- Fetched from
- https://data.transportation.gov/resource/2667-vitc.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2026-10-14
- Rows
- 23
- Refresh
python manage.py load_ntd
NTD Complete Monthly Ridership (agency 80006)
Federal Transit Administration, National Transit Database · updates: Monthly, about two months in arrears
Monthly boardings, revenue miles and revenue hours by mode since 2002.
Limitations. Recent months can be revised.
- Fetched from
- https://data.transportation.gov/resource/8bui-9xvu.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/data-product/monthly-module-adjusted-data-release
- Source version
- 2026-11-03
- Rows
- 1,639
- Refresh
python manage.py load_ntd
NTD Safety & Security Agency Profile (agency 80006)
Federal Transit Administration, National Transit Database · updates: Monthly
Monthly major security events, assaults, injuries and fatalities for bus and rail, with ridership for rates.
Limitations. Only events that meet NTD reportable thresholds; minor incidents and calls for service are not included.
- Fetched from
- https://data.transportation.gov/resource/pgwk-wjqa.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2026-11-06
- Rows
- 1,290
- Refresh
python manage.py load_ntd
NTD Annual Data - Metrics, comparison agencies (RTC Southern Nevada 90045)
Federal Transit Administration, National Transit Database · updates: Annual
Las Vegas bus system cost, ridership and service, for the FreeRide page's Las Vegas comparison. Same dataset and definitions as RTD's NTD rows.
Limitations. Mode level only: NTD has no route data, so the Strip's Deuce route cannot be separated from the rest of the RTC bus network. RTC contracts out its bus service (purchased transportation).
- Fetched from
- https://data.transportation.gov/resource/ekg5-frzt.json?ntd_id=90045
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2026-10-14
- Rows
- 8
- Refresh
python manage.py load_ntd --only peers
NTD Annual Data - Fuel and Energy, 2022-2025 (agency 80006)
Federal Transit Administration, National Transit Database · updates: Annual
Diesel, gasoline and electricity used by each mode, and the miles run on each, for the fuel and carbon figures on the Conclusion page.
Limitations. Commuter rail DO and PT rows repeat the same miles, so miles are taken once. NTD flags some values as questionable (shown with the figure). Tank-to-wheel only: no upstream fuel or power plant losses.
- Fetched from
- https://data.transportation.gov/resource/8ehq-7his.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2026-10-14
- Rows
- 24
- Refresh
python manage.py load_ntd --only energy
NTD Facility Inventory, 2025 (agency 80006)
Federal Transit Administration, National Transit Database · updates: Annual
Every RTD station, garage, office and parking facility RTD reports to the FTA: type, year built or rebuilt, condition rating (1 poor to 5 excellent), square feet and location.
Limitations. Condition ratings are RTD's own assessments on the FTA TERM scale, made on the date shown. No values or occupancy. Parking lots and structures report no space counts here.
- Fetched from
- https://data.transportation.gov/resource/mbm2-ck6q.json?ntd_id=80006
- About the data
- https://www.transit.dot.gov/ntd/ntd-data
- Source version
- 2025 inventory, updated 2026-10-05
- Rows
- 219
- Refresh
python manage.py load_estate --only facilities
Colorado Public Parcels (statewide composite), owner = RTD
Colorado Governor's Office of Information Technology (OIT), from county assessors · updates: Periodic (county data received April 2026)
Land whose owner of record is RTD (or the RTD Asset Acquisition Authority), with boundaries, acres, land use and the county's appraised and assessed value.
Limitations. Owner names are matched by text, so a parcel recorded under an unusual name can be missed. Values are county appraisals for tax purposes (RTD land is exempt), not market prices, and some counties publish none. Totals only: land and improvements are not split.
- Fetched from
- https://gis.colorado.gov/public/rest/services/Address_and_Parcel/Colorado_Public_Parcels/FeatureServer/0
- About the data
- https://gis.colorado.gov/
- Source version
- county data received 3/27/2026, 4/21/2026, 4/23/2026
- Rows
- 613
- Refresh
python manage.py load_estate --only parcels
Load history
| 2026-11-19 03:33 | ok | 613 | county data received 3/27/2026, 4/21/2026, 4/23/2026 |
| 2026-11-19 03:32 | ok | 616 | county data received 3/27/2026, 4/1/2026, 4/21/2026, 4/23/2026 |
RTD park-n-ride facilities (RTD GIS, current runboard)
Regional Transportation District (RTD) · updates: Each service change
Each park-n-ride: spaces, fees, bike racks, location.
Limitations. Capacity only. RTD does not publish current occupancy online.
- Fetched from
- https://services5.arcgis.com/1fZoXlzLW6FCIUcE/arcgis/rest/services/RTD_GIS_Current_Runboard/FeatureServer/0
- About the data
- https://www.rtd-denver.com/open-records/open-spatial-information
- Source version
- 2026-11-19 snapshot
- Rows
- 131
- Refresh
python manage.py load_estate --only parknride
Park-n-ride average daily counts 2019-2023 (RTD and SP+ counts, compiled by CPR News)
Colorado Public Radio (CPR News), data credited to RTD · updates: One-off compilation (2024)
Average daily cars parked per lot per year, against capacity: how much of each lot is used.
Limitations. A news organisation's compilation, not an RTD publication. Count method changes by year (RTD staff vs SP+). Ends in 2023. Lot names are matched to RTD's list by name.
- Fetched from
- https://docs.google.com/spreadsheets/d/1mX66Dp_1UIaA8H7ugV5_C1vyvZ2RIzeT-0_CQMsBDgI
- About the data
- https://www.cpr.org/2024/06/21/housing-development-rtd-park-and-ride-parking-lots/
- Source version
- years 2019-2023
- Rows
- 351
- SHA-256
- fb8cb26adf0111a6f1c6f304ef8d24914eb8d56f40bc70654e7777e67fcaefc8
- Refresh
python manage.py load_estate --only parknride-use
Load history
| 2026-11-19 03:34 | ok | 351 | years 2019-2023 |
| 2026-11-19 03:33 | ok | 351 | years 2019-2023 |
Greater Denver Transit: RTD route boardings and service hours, 2018-2024
Greater Denver Transit (compiled from RTD service performance reports) · updates: Annual (compiled after RTD publishes the year)
Annual boardings, service hours and trips for every RTD route and rail line. This is the ridership and hours behind every route-level cost.
Limitations. Third-party compilation of RTD figures; route names are the public route label, matched to GTFS by short name. Routes renamed or discontinued since do not match a current GTFS route.
- Fetched from
- https://www.greaterdenvertransit.com/wp-content/uploads/2018_2024_RTD_BoardingsServiceHour.csv
- About the data
- https://www.greaterdenvertransit.com/rtd-ridership/
- Source version
- 2018_2024_RTD_BoardingsServiceHour.csv + 2018_2024_RTD_BoardingsTrip.csv
- Rows
- 971
- SHA-256
- 7c42fdc329c65377c9b558204c76fa4b9102cfb40954ae358e193236ad969244
- Notes
- Labels with no current GTFS route: 104, 104X, 120E, 120W, 122X, 125, 128, 131, 157, 16L, 1W, 205T, 206F, 206S, 208F, 209, 225E, 228, 236, 26, 27, 29, 30L, 31L, 33A, 33B, 34, 36L, 39L, 401, 403, 50, 55, 55L, 62, 67, 72L, 72W, 77, 80L, 85, 87L, 99L, AA, AB, CS, CX, DTC, ES, EX, F, FF6, FF7, H, J, L, LD2, LD3, LX1, NB, NB3, P, RC, STMP, Y
- Refresh
python manage.py load_gdt
Load history
| 2026-11-18 19:02 | ok | 971 | 2018_2024_RTD_BoardingsServiceHour.csv + 2018_2024_RTD_BoardingsTrip.csv |
| 2026-11-18 18:55 | ok | 971 | 2018_2024_RTD_BoardingsServiceHour.csv + 2018_2024_RTD_BoardingsTrip.csv |
| 2026-11-18 18:51 | ok | 971 | 2018_2024_RTD_BoardingsServiceHour.csv + 2018_2024_RTD_BoardingsTrip.csv |
RTD Public Information Dashboards (ridership, safety & security)
Regional Transportation District (RTD) · updates: Monthly
Security and fare-enforcement figures (calls for service, fare checks, non-payment) from the rider & driver safety dashboard and RTD news releases. Related dashboards: ridership, boardings, farebox recovery, workforce statistics.
Limitations. Dashboards are interactive (not a download). Figures are copied into data/manual/security_metrics.csv by hand with the period and page cited, until a scraper exists.
- Fetched from
- https://www.rtd-denver.com/public-information-dashboards/rider-driver-safety
- About the data
- https://www.rtd-denver.com/public-information-dashboards
- Source version
- security_metrics.csv
- Rows
- 5
- Refresh
python manage.py load_manual
Load history
| 2026-11-19 12:06 | ok | 5 | security_metrics.csv |
| 2026-11-19 11:45 | ok | 5 | security_metrics.csv |
| 2026-11-19 11:45 | ok | 5 | security_metrics.csv |
| 2026-11-19 11:18 | ok | 5 | security_metrics.csv |
| 2026-11-19 11:04 | ok | 5 | security_metrics.csv |
RTD financial documents: ACFR, adopted budget, monthly financial statements, audits
Regional Transportation District (RTD); Colorado Office of the State Auditor · updates: ACFR annual (mid-year); budget annual (December); statements monthly
Depreciation and interest (fully-burdened cost), transit police / security spending, workforce and turnover figures. One row per number in data/manual/financial_facts.csv, each citing its document URL and page.
Limitations. PDF tables are transcribed by hand and marked verified only once checked against the page. Unverified rows are shown with a warning and never used in fully-burdened cost.
- Fetched from
- https://www.rtd-denver.com/open-records/financial-information
- About the data
- https://www.rtd-denver.com/performance-dashboard/financial-performance
- Source version
- financial_facts.csv
- Rows
- 21
- Refresh
python manage.py load_manual
Load history
| 2026-11-19 12:06 | ok | 21 | financial_facts.csv |
| 2026-11-19 11:45 | ok | 21 | financial_facts.csv |
| 2026-11-19 11:45 | ok | 21 | financial_facts.csv |
| 2026-11-19 11:18 | ok | 21 | financial_facts.csv |
| 2026-11-19 11:04 | ok | 21 | financial_facts.csv |
News releases and reporting (FreeRide figures, Zoox fares)
RTD news releases; Denverite; Las Vegas Review-Journal · updates: As published
Figures that are not in any dataset: FreeRide ridership and running cost as RTD states them, fleet size, and robotaxi fares observed by reporters. Each row quotes its sentence.
Limitations. Hand-transcribed into data/manual/external_facts.csv. News figures are rounded and sometimes a one-day sample (Zoox fares); the page shows them as reported, not as measurements.
- Fetched from
- https://www.rtd-denver.com/community/news
- About the data
- https://www.rtd-denver.com/community/news
- Source version
- external_facts.csv
- Rows
- 175
- Refresh
python manage.py load_manual
Load history
| 2026-11-19 12:06 | ok | 175 | external_facts.csv |
| 2026-11-19 11:45 | ok | 161 | external_facts.csv |
| 2026-11-19 11:45 | ok | 152 | external_facts.csv |
| 2026-11-19 11:18 | ok | 108 | external_facts.csv |
| 2026-11-19 11:04 | ok | 106 | external_facts.csv |
RTD district boundary (RTD GIS)
Regional Transportation District · updates: Rarely
The area RTD taxes and serves; limits the census blocks used for stop coverage.
Limitations. One polygon (BND = IN).
- Fetched from
- https://services5.arcgis.com/1fZoXlzLW6FCIUcE/arcgis/rest/services/RTD_GIS_Boundaries/FeatureServer/0
- About the data
- https://www.rtd-denver.com/open-records/open-spatial-information
- Source version
- —
- Rows
- 1
- Refresh
python manage.py load_census
Load history
| 2026-11-19 11:39 | ok | 1 | |
| 2026-11-19 11:39 | ok | 1 | |
| 2026-11-19 10:44 | ok | 1 |
2020 Census blocks, population (Census TIGERweb)
U.S. Census Bureau · updates: Every 10 years
Where people live: population of each block in the RTD district, used to measure how many people live within a quarter mile of a stop.
Limitations. 2020 population, placed at each block's internal point; straight-line distance to the stop, not walking distance, so coverage is overstated where streets don't connect.
- Fetched from
- https://tigerweb.geo.census.gov/arcgis/rest/services/TIGERweb/Tracts_Blocks/MapServer/2
- About the data
- https://tigerweb.geo.census.gov/
- Source version
- —
- Rows
- 35,250
- Refresh
python manage.py load_census
Load history
| 2026-11-19 11:39 | ok | 35,250 | |
| 2026-11-19 11:39 | ok | 35,250 | |
| 2026-11-19 10:44 | ok | 35,250 |
American Community Survey 5-year, census tracts: age and disability (Esri Living Atlas)
U.S. Census Bureau, via Esri Living Atlas · updates: Annual (5-year estimates)
Share of each tract's residents who are 65+, 5-17 or living with a disability; applied to each block's 2020 population to estimate how many older, school-age and disabled residents live near a stop.
Limitations. Survey estimates with margins of error, applied evenly across a tract's blocks. Esri republishes the Census tables; the vintage is recorded with each load.
- Fetched from
- https://P3ePLMYs2RVChkJx.svcs.arcgis.com/P3ePLMYs2RVChkJx/arcgis/rest/services/ACS_Population_View_Boundaries/FeatureServer/2
- About the data
- https://www.arcgis.com/home/item.html?id=60c98f20a162416ea1725b94d7297f83
- Source version
- —
- Rows
- 849
- Refresh
python manage.py load_census
Load history
| 2026-11-19 11:40 | ok | 849 | |
| 2026-11-19 11:39 | ok | 849 |
Calibration: do the route figures add up to RTD's totals?
RTD's route reports count hours differently from NTD. Rail reports train-hours, while NTD counts every car, so a three-car train is three vehicle-hours. Bus reports leave out layover time, which NTD counts. The hours factor (NTD vehicle revenue hours ÷ all reported route hours, discontinued routes included) converts one to the other. Route costs should then add up to close to NTD's total. The shortfall is the cost of routes since discontinued or renamed, which this site can't attach to a current route.
| Year | Mode | NTD revenue hours | Sum of matched route hours | Ratio | NTD boardings | Sum of matched route boardings | Ratio | Hours factor | Route costs as share of NTD cost | GTFS scheduled hours (current feed, annualised) |
|---|---|---|---|---|---|---|---|---|---|---|
| 2025 | CR | 267,925 | — | — | 8,644,691 | — | — | — | — | 70,219 |
| 2025 | LR | 424,586 | — | — | 10,568,743 | — | — | — | — | 170,626 |
| 2025 | MB | 2,355,786 | — | — | 44,014,803 | — | — | — | — | 1,898,622 |
| 2024 | CR | 284,384 | 64,232 | 23% | 8,331,378 | 8,580,144 | 103% | ×4.43 | 100% | 70,219 |
| 2024 | LR | 524,860 | 118,901 | 23% | 11,161,755 | 9,713,623 | 87% | ×3.57 | 81% | 170,626 |
| 2024 | MB | 2,126,336 | 1,685,737 | 79% | 44,041,734 | 44,822,448 | 102% | ×1.25 | 99% | 1,898,622 |
| 2023 | CR | 283,983 | 61,737 | 22% | 8,578,271 | 8,613,983 | 100% | ×4.60 | 100% | 70,219 |
| 2023 | LR | 489,089 | 117,864 | 24% | 12,740,358 | 10,228,843 | 80% | ×3.13 | 76% | 170,626 |
| 2023 | MB | 2,071,320 | 1,571,521 | 76% | 42,438,505 | 41,222,421 | 97% | ×1.30 | 99% | 1,898,622 |
| 2022 | CR | 279,373 | 61,377 | 22% | 7,935,811 | 8,048,713 | 101% | ×4.55 | 100% | 70,219 |
| 2022 | LR | 562,126 | 125,201 | 22% | 13,604,641 | 10,922,881 | 80% | ×3.28 | 73% | 170,626 |
| 2022 | MB | 2,007,671 | 1,518,808 | 76% | 39,006,884 | 35,691,603 | 92% | ×1.29 | 98% | 1,898,622 |
Route labels in ridership data with no current GTFS route (mostly discontinued; current ones can be matched in official/management/commands/load_gdt.py ALIASES): 104, 104X, 120E, 120W, 122X, 125, 128, 131, 157, 16L, 1W, 205T, 206F, 206S, 208F, 209, 225E, 228, 236, 26, 27, 29, 30L, 31L, 33A, 33B, 34, 36L, 39L, 401, 403, 50, 55, 55L, 62, 67, 72L, 72W, 77, 80L, 85, 87L, 99L, AA, AB, CS, CX, ES, EX, F, FF6, FF7, H, J, L, LD2, LD3, LX1, NB, NB3, P, RC, STMP, Y