cd /news/structured-data/only-16-of-u-s-fast-charging-station… · home › topics › structured-data › article
[ARTICLE · art-165498] src=chargingnear.me ↗ pub= topic=structured-data verified=true sentiment=· neutral

Only 16% of U.S. fast-charging stations meet federal NEVI standards (open data)

Only 2,547 of 15,927 open public DC fast-charging stations in the 50 states and DC — about 16% — meet the federal NEVI station minimums, according to the US EV Charging Open Data catalog published by ChargingNear.me as of November 6, 2026. The same dataset, rebuilt daily from the company's live database of 58,164 charging locations and 273,246 ports, lists 881 stretches of U.S. highway where open public DC fast chargers are more than 50 miles apart, 22 of them in Colorado. The 20 free CSV and JSON files are released under CC BY 4.0, with station facts drawn from the U.S. Department of Energy's Alternative Fuels Data Center, and the 50-mile spacing benchmark traces to FHWA's NEVI guidance of February 10, 2022, which Colorado's 2025 NEVI plan retains even after FHWA's August 11, 2025 guidance left spacing to each state.

read68 min views1 publishedNov 6, 2026
Only 16% of U.S. fast-charging stations meet federal NEVI standards (open data)
Image: source

Free · Sourced · Citable

Where public EV charging falls short along U.S. highways and in which counties, which DC fast stations meet the federal NEVI minimums or take a NACS plug, how chargers hold up, and how the network grows, county by county in Colorado and state by state. Every figure comes from our database or a named, dated, linked source.

The catalog today: 58,164 charging locations with 273,246 ports across all 50 states and DC. A charging location is one physical charging site: every charger at one address counts once. A port is one plug that can charge one car at a time.

Last updated . Rebuilt daily from our live database.

Catalog for harvesters: /data.json (DCAT-US 1.1). Questions: reserve@winsparking.com. Also on Zenodo (DOI 10.5281/zenodo.23984554) and Hugging Face (NEVI check and highway gaps, public charging stations and charging by state).

Quick answer ·

What free EV charging data can I download here? #

As of November 6, 2026, this page publishes 20 free files on U.S. public EV charging, rebuilt daily. 881 stretches of U.S. highway have open public DC fast chargers more than 50 miles apart, 22 of them in Colorado. 2,547 of 15,927 open public DC fast stations in the 50 states and DC meet the federal NEVI station minimums. Our own files are CC BY 4.0, and station facts from the Alternative Fuels Data Center are U.S. public domain.

Which files can I download? #

20 files, each as CSV and JSON.

a. Where are the gaps between fast chargers on U.S. highways? #

The 50-mile line comes from FHWA’s NEVI guidance of February 10, 2022, which counted a state’s Interstates as fully built out with a charger every 50 miles. FHWA’s guidance of August 11, 2025 leaves spacing to each state. Colorado’s 2025 NEVI plan keeps 50 miles. 23 CFR part 680 sets station minimums, not spacing.

U.S. highway charging gaps over 50 miles

Every stretch of Interstate and U.S. highway in the 50 states and DC, and of every other road FHWA designates as an EV Alternative Fuel Corridor, where open public DC fast chargers are more than 50 miles apart along the road. State, mile markers, coordinates, gap length and corridor designation.

  • Rows
  • 881
  • Version
  • v6
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “U.S. highway charging gaps over 50 miles.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#us-highway-charging-gaps. CC BY 4.0.

Column dictionary 21 columns #

Column Meaning
gap_id Stable ID: state, highway, start mile marker, end mile marker.
state Two-letter code of the state the stretch is in. A highway that crosses a state line is split there.
highway Highway as signed: I-70, US-40. Other designated roads keep FHWA’s name: CO-82, Bluegrass Parkway.
direction Always “both”: a charger counts for both directions of travel.
start_mile_marker Mile marker where the gap starts (one decimal). See mile_marker_basis.
end_mile_marker Mile marker where the gap ends.
mile_marker_basis state_route_measure: the route measure the state reports to FHWA in HPMS (often, not always, the posted milepost). from_south_or_west_end: miles from the south or west end of this line in the state.
gap_miles Miles along the highway between the two ends (one decimal).
start_type What starts the gap: charger, state_line, national_border (Canada or Mexico), or highway_end (the highway ends, or its line stops where it shares road with another highway).
start_description The charger’s name and city, the state line or border, or the junction.
start_afdc_station_id AFDC ID of the charger that starts the gap; empty for a state line, border or highway end.
start_latitude Latitude of the point on the highway where the gap starts (WGS 84).
start_longitude Longitude of that point.
end_type As start_type, for the end of the gap.
end_description As start_description, for the end.
end_afdc_station_id AFDC ID of the charger that ends the gap.
end_latitude Latitude of the point on the highway where the gap ends.
end_longitude Longitude of that point.
designated_corridor_miles Miles of the gap on an FHWA-designated EV Alternative Fuel Corridor.
corridor_status FHWA status of those miles: ready, pending, both, partly, or not designated.
fhwa_corridor FHWA corridor name(s) for the designated miles.

Methodology #

Highway lines and mile markers come from FHWA’s Highway Performance Monitoring System (HPMS, 2024 data year): every mainline section a state signed as Interstate or U.S. highway. Several states leave that signing blank in HPMS (Texas, California, Maryland and Delaware among them), so a section’s signing also comes from FHWA’s National Highway System dataset, which records the posted route for the same HPMS route IDs. Sections of one highway in one state are joined end to end; a second carriageway or couplet drawn beside the first is dropped. Roads FHWA designates that are not Interstate or U.S. highways (state routes, parkways, turnpikes) use FHWA’s own corridor lines.

Mile markers come from the route measure each state reports to FHWA in HPMS, where it runs continuously along the line (state_route_measure). It often matches the posted mileposts (it does for I-70 in Colorado) but not always: some states measure from a different starting point or by section. Where the measure does not run continuously, such as one that restarts by county, the markers are miles from the south or west end of the line within the state (from_south_or_west_end).

Chargers are AFDC stations listed as open and public with at least one DC fast port, any network and any plug, including Tesla. A charger serves a highway when it is within 1 mile of it in a straight line. Chargers just across a state line count.

We walk each highway from end to end and record every stretch longer than 50 miles between consecutive chargers, or between a charger and a state line, the Canada or Mexico border, or the end of the highway. Gap length is measured along the highway.

Why 50 miles: FHWA’s February 10, 2022 NEVI guidance treated a state’s corridors as fully built out when chargers were installed every 50 miles along its Interstates. FHWA’s August 11, 2025 interim final guidance superseded it and leaves spacing to each state; Colorado’s NEVI plan (CDOT and the Colorado Energy Office, 2025 update) keeps a 50-mile target. 23 CFR part 680 itself sets no spacing. We use 50 miles everywhere so states can be compared.

Corridor designation comes from FHWA’s Alternative Fuel Corridors map (Round 8), matched to the highway lines within 0.1 mile. A corridor named for another road counts only where that road has no line of its own there.

Known limits

  • Straight-line distance to the highway, not driving distance to the exit.
  • Where two highways share the road, the line is drawn once, under one of them, so the shared miles appear once.
  • Chargers in Canada and Mexico are not in AFDC’s U.S. listing, so a gap ending at a border may be shorter in practice.
  • A charger listed as open in AFDC may be down on a given day; the gaps assume it works.

Sources 10 #

Changelog 6 versions #

  1. v6: Rows 878 → 881.
  2. v5: Values updated in existing rows (878 rows).
  3. v4: Rows 883 → 878.
  4. v3: Rows 881 → 883.
  5. v2: Rows 880 → 881.
6. v1: First release: 880 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

b. Which DC fast stations meet the federal NEVI minimums? #

Today 2,547 of 15,927 open public DC fast stations in the 50 states and DC pass all three NEVI minimums. In Colorado, 84 of 499 pass.

U.S. DC fast stations checked against NEVI minimums

Pass or fail for every open public DC fast station in the 50 states and DC against the federal NEVI minimums: four CCS ports, 150 kW each, within 1 mile of a designated corridor, with the reason for each fail.

  • Rows
  • 15,927
  • Version
  • v6
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “U.S. DC fast stations checked against NEVI minimums.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#us-nevi-station-check. CC BY 4.0.

Column dictionary 22 columns #

Column Meaning
afdc_station_id The station’s ID in the AFDC Station Locator. Join on it.
chargingnear_station_id The station’s ID on ChargingNear.me (the same number for AFDC stations).
station_name Station name as AFDC lists it.
address Street address.
city City.
state Two-letter state code.
zip ZIP code. 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| network | Charging network, named as in AFDC. | | dc_fast_ports | DC fast ports AFDC lists, any plug. | | ccs_ports | DC fast ports with a CCS (J1772COMBO) plug, from AFDC’s port-by-port listing. Empty when AFDC has no port detail. | | ccs_ports_150kw | Of those, ports whose CCS plug AFDC lists at 150 kW or more. | | max_ccs_kw | Highest power AFDC lists for any CCS plug at the station, in kW. | | nearest_corridor | Nearest FHWA-designated EV corridor (ready or pending) within 25 miles. | | corridor_state | State that stretch of corridor is in (it can differ from the station’s near a state line). | | corridor_status | FHWA status of that corridor stretch: ready or pending. | | corridor_mile_marker | Mile marker on that corridor nearest the station (basis as in the gap file). | | miles_from_corridor | Straight-line miles from the station to that corridor. | | nevi_grade | pass or fail. | | failing_reasons | Why it fails, separated by semicolons. Empty on a pass. | | last_nrel_sync | When our daily sync last read the station from AFDC (UTC). |

Methodology #

Every station in the 50 states and DC that AFDC lists as open and public with at least one DC fast port is tested against three NEVI minimums. Two are in 23 CFR 680.106 (FHWA final rule, February 28, 2023) for stations along designated Alternative Fuel Corridors: at least four ports with a CCS connector (680.106(b)(1) and (c)), each able to deliver at least 150 kW (680.106(d)(1)). The third, a location within 1 mile of a designated corridor, is the “within 1 travel mile” distance in FHWA’s February 10, 2022 NEVI guidance; part 680 itself sets no distance.

Ports and power come from AFDC’s port-by-port listing. A port counts as CCS when it has a J1772COMBO connector, including Tesla ports with a CCS adapter that AFDC lists that way. A port counts at 150 kW when AFDC lists its CCS connector at 150 kW or more; a port with no listed power does not count.

Corridor distance is the straight line from the station to the nearest designated corridor stretch (ready or pending) on the highway lines described for the gap file.

Known limits

  • AFDC lists each plug’s top power, not what every port delivers while all four charge at once, so a pass here does not prove 680.106(d)(1)’s simultaneous 150 kW.
  • The test does not check the other parts of 23 CFR 680, such as 24-hour access, payment methods, uptime or networking.
  • “Within 1 mile” is a straight line, not travel miles from the exit.

Sources 6 #

- [FHWA Alternative Fuel Corridors, Round 8 (USDOT/BTS National Transportation Atlas Database, Jan 16, 2025)](https://data-usdot.opendata.arcgis.com/datasets/usdot::alternative-fuel-corridors)
- [FHWA Highway Performance Monitoring System (HPMS), 2024 data year, public geospatial release (USDOT/BTS)](https://www.fhwa.dot.gov/policyinformation/hpms/shapefiles.cfm)

Changelog 6 versions #

  1. v6: Rows 15,926 → 15,927.
  2. v5: Rows 15,925 → 15,926.
  3. v4: Rows 15,890 → 15,925.
  4. v3: Rows 15,908 → 15,890.
  5. v2: Rows 15,918 → 15,908.
6. v1: First release: 15,918 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

Corridor miles meeting 50-mile NEVI spacing, by state

For each designated EV corridor highway in each state: how many miles meet 50-mile spacing between NEVI-grade stations today, as miles and as a share.

  • Rows
  • 710
  • Version
  • v6
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “Corridor miles meeting 50-mile NEVI spacing, by state.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#us-nevi-corridor-coverage. CC BY 4.0.

Column dictionary 11 columns #

Column Meaning
state Two-letter state code.
highway Highway as signed (or FHWA’s name for another designated road).
fhwa_corridor FHWA corridor name(s).
designated_miles Miles of this highway in this state designated as an EV corridor (ready plus pending).
corridor_ready_miles Of those, miles FHWA lists as corridor-ready.
corridor_pending_miles Miles FHWA lists as corridor-pending.
nevi_grade_stations Stations that pass the NEVI check and sit within 1 mile of the designated stretch.
miles_meeting_50_mile_rule Designated miles in stretches that meet 50-mile spacing.
share_meeting_50_mile_rule That as a percentage of designated miles.
stretches_not_meeting Stretches that do not meet it.
longest_stretch_not_meeting_miles Designated miles in the longest stretch that does not meet it.

Methodology #

Each designated highway is split at its NEVI-grade stations (those that pass the station check in this section). A stretch between two NEVI-grade stations meets the spacing when it is 50 miles or less. A stretch from a NEVI-grade station to a state line, a border or the end of the highway meets it when it is 25 miles or less, so a station within 25 more miles past that point would keep the 50. A highway with no NEVI-grade station on it does not meet it.

The 50-mile figure comes from FHWA’s February 10, 2022 NEVI guidance (“every 50 miles” along a state’s Interstates for a fully built-out corridor). FHWA’s August 11, 2025 interim final guidance superseded that and leaves spacing to states; Colorado’s plan (CDOT and the Colorado Energy Office, 2025 update) keeps a 50-mile target. 23 CFR part 680 does not set a spacing. Other states’ own targets may differ.

Known limits

  • Stations on a crossing highway count only when they are within 1 mile of this one.
  • A stretch that is partly designated counts only its designated miles.
  • Rows are per state: a highway that crosses several states has one row in each.

Sources 8 #

- [FHWA Alternative Fuel Corridors, Round 8 (USDOT/BTS National Transportation Atlas Database, Jan 16, 2025)](https://data-usdot.opendata.arcgis.com/datasets/usdot::alternative-fuel-corridors)
- [FHWA Highway Performance Monitoring System (HPMS), 2024 data year, public geospatial release (USDOT/BTS)](https://www.fhwa.dot.gov/policyinformation/hpms/shapefiles.cfm)

Changelog 6 versions #

1. v6: Values updated in existing rows (710 rows).
2. v5: Values updated in existing rows (710 rows).
3. v4: Values updated in existing rows (710 rows).
4. v3: Values updated in existing rows (710 rows).
5. v2: Values updated in existing rows (710 rows).
6. v1: First release: 710 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

c. How reliable are public chargers, by network, county and corridor? #

No network, county or corridor has reached 10 driver reports in the last 30 days yet (1 reports across all stations), so the file has no rows today. Groups appear as soon as they reach 10.

Working-Now Score roll-up by network, Colorado county and corridor

The average Working-Now Score of open public stations by network (U.S.), Colorado county and Colorado corridor. A group is published only once drivers have sent at least 10 reports about its stations in the last 30 days.

  • Rows
  • 0
  • Version
  • v1
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “Working-Now Score roll-up by network, Colorado county and corridor.” US EV Charging Open Data, version 1, October 31, 2026. https://chargingnear.me/data#reliability-rollup. CC BY 4.0.

Column dictionary 12 columns #

Column Meaning
group_type network, county or corridor.
group_name Network as named in AFDC, county name, or highway.
area United States for networks; Colorado for counties and corridors.
stations_scored Open public AFDC stations in the group.
reports_30d Driver check-ins and “did it work?” answers about those stations in the last 30 days, approved by moderation, plus in-person field checks by our team.
stations_with_reports_30d Stations with at least one such report.
average_working_now_score Mean Working-Now Score (0–100) across the group.
median_working_now_score Median score.
stations_85_to_100 Stations scoring 85 to 100.
stations_70_to_84 Stations scoring 70 to 84.
stations_40_to_69 Stations scoring 40 to 69.
stations_0_to_39 Stations scoring 0 to 39.

Methodology #

The Working-Now Score (0–100) starts at 70 for a station listed as open. It adds 10 when the listing was confirmed in the last 30 days (5 within 90 days) and subtracts 10 when the last confirmation is over a year old. Driver reports from the last 30 days move it up to +20 or down to −40, with failures weighing 1.5 times successes. A failure in the last 48 hours caps it at 40; a success in that window lifts it to at least 85.

Confirmation dates come from AFDC’s date_last_confirmed and our own verification passes. Driver reports are check-ins and one-tap answers sent on ChargingNear.me, including field checks by our team.

A group is published only when its stations have at least 10 reports in the last 30 days. Until then, scores mostly reflect how recently listings were confirmed, not whether chargers worked.

Known limits

  • Station-by-station scores and their history are not in this file; they stay under the API Terms.
  • Reports come from drivers who chose to send them, not from a random sample.

Changelog 1 version #

1. v1: First release: 0 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

d. Where is every public charging station? #

Public charging stations (NREL fields)

Every public charging station we list from NREL's AFDC Station Locator: location, network, plugs, Level 2 and DC fast port counts, max power, access and hours. Station facts as of our AFDC sync on .

  • Rows
  • 83,886
  • Version
  • v6
  • Last changed
  • Area
  • United States

Public domain + CC BY 4.0 · Rebuilt daily Cite as

ChargingNear.me. “Public charging stations (NREL fields).” US EV Charging Open Data, version 6, November 6, 2026. https://chargingnear.me/data#public-charging-stations. CC BY 4.0.

Column dictionary 17 columns #

Column Meaning
afdc_station_id The station’s ID in the AFDC Station Locator. Join on it.
chargingnear_station_id The station’s ID on ChargingNear.me (the same number for AFDC stations).
station_name Station name as AFDC lists it.
address Street address.
city City.
state Two-letter state code.
zip ZIP code.
latitude Latitude (WGS 84, decimal degrees).
longitude Longitude (WGS 84, decimal degrees).
network Charging network, named as in AFDC.
connector_types AFDC connector codes, separated by spaces: J1772, J1772COMBO (CCS), CHADEMO, TESLA (NACS).
level2_ports Level 2 ports.
dc_fast_ports DC fast ports.
max_kw Highest per-plug power AFDC lists for the station, in kW. Empty when AFDC lists none.
access public or private.
hours Hours as AFDC lists them.
last_nrel_sync When our daily sync last read the station from AFDC (UTC, ISO 8601).

Methodology #

One row per station we list from AFDC, read by our daily sync. Stations we know only from other sources, such as Google Maps or Open Charge Map, are left out: they are not NREL facts and have no AFDC ID.

Known limits

  • Facts are as AFDC publishes them; a correction sent to us appears in the corrections layer, not here.

Changelog 6 versions #

  1. v6: Rows 83,797 → 83,886.

  2. v5: Rows 83,764 → 83,797.

  3. v4: Rows 83,655 → 83,764.

  4. v3: Rows 83,675 → 83,655.

  5. v2: Rows 83,699 → 83,675.

  6. v1: First release: 83,699 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

e. What are drivers reporting about stations? #

Driver-report layers fill as reports come in; updated daily.

Outages and repairs

Chargers drivers found broken, blocked or locked off, with the report date and, once fixed, the repair date; drivers' reports that a charger was working; and in-person checks by our own team with a dated photo.

  • Rows
  • 0
  • Version
  • v1
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “Outages and repairs.” US EV Charging Open Data, version 1, October 31, 2026. https://chargingnear.me/data#outages-and-repairs. CC BY 4.0.

Column dictionary 18 columns #

Column Meaning
afdc_station_id The station’s ID in the AFDC Station Locator. Join on it.
chargingnear_station_id The station’s ID on ChargingNear.me (the same number for AFDC stations).
station_name The station as listed when the file was built.
address Street address.
city City.
state Two-letter state code.
network Charging network, named as in AFDC.
report_type What was reported. Outages: broken, blocked, access_restricted, working (a driver found the charger working), or field_check (our own team checked the charger in person). Corrections: hours, access, pricing. Removed or relocated: closed, wrong_location.
reported_at When the report, correction or field check was made (UTC, ISO 8601).
verified_status verified: a ChargingNear.me reviewer approved or resolved it, or staff applied the correction. unverified: sent by a driver and not yet reviewed, or a correction applied automatically from a driver. field-verified by ChargingNear.me: our own team checked the charger in person.
details A short description of the report type, written by ChargingNear.me. Never the driver’s own words.
resolved_at When a reviewer marked the report resolved. Empty while it is open.
ports_working Field checks only: how many of the station’s ports our team found working.
ports_total Field checks only: how many ports the station had when checked.
payment_worked Field checks only: yes or no when our team tried to pay; empty when payment was not tried.
price_shown Field checks only: the price the charger or its app showed, as written; empty when none was shown.
photo_url Field checks only: the photo our team took at the station during the check.
record_id A stable ID for the row, such as report-123, correction-45 or field-check-7.

Methodology #

Rows are reports drivers send on ChargingNear.me about stations in AFDC, and checks our own team makes in person. Reports a reviewer rejected or dismissed are left out; reports not yet reviewed are included and marked unverified.

Every row is a station in AFDC; reports about stations we found through other sources have no AFDC ID and are left out.

Known limits

  • Reports come from drivers who chose to send them, not from a random sample, so a station with no row is not proof it works.
  • No personal data: no reporter names, emails, phone numbers, user IDs or IP addresses, and nothing a driver typed in their own words.

Changelog 1 version #

1. v1: First release: 0 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

Hours, access and pricing corrections

Changes drivers made to a station's hours, access or price, with the old value, the new value and the date, and drivers' reports that the listed hours or price are wrong.

  • Rows
  • 1
  • Version
  • v1
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “Hours, access and pricing corrections.” US EV Charging Open Data, version 1, October 31, 2026. https://chargingnear.me/data#hours-access-pricing-corrections. CC BY 4.0.

Column dictionary 16 columns #

Column Meaning
afdc_station_id The station’s ID in the AFDC Station Locator. Join on it.
chargingnear_station_id The station’s ID on ChargingNear.me (the same number for AFDC stations).
station_name The station as listed when the file was built.
address Street address.
city City.
state Two-letter state code.
network Charging network, named as in AFDC.
report_type What was reported. Outages: broken, blocked, access_restricted, working (a driver found the charger working), or field_check (our own team checked the charger in person). Corrections: hours, access, pricing. Removed or relocated: closed, wrong_location.
reported_at When the report, correction or field check was made (UTC, ISO 8601).
verified_status verified: a ChargingNear.me reviewer approved or resolved it, or staff applied the correction. unverified: sent by a driver and not yet reviewed, or a correction applied automatically from a driver. field-verified by ChargingNear.me: our own team checked the charger in person.
details A short description of the report type, written by ChargingNear.me. Never the driver’s own words.
field The listing field that changed: hours, access or pricing.
old_value Its value before. Empty on a driver’s report that the listed hours or price are wrong.
new_value Its value after. Empty on a driver’s report that the listed hours or price are wrong.
applied_at When the change went live on the listing. Empty on a driver’s report, which changes nothing by itself.
record_id A stable ID for the row, such as report-123, correction-45 or field-check-7.

Methodology #

Rows are reports drivers send on ChargingNear.me about stations in AFDC, and checks our own team makes in person. Reports a reviewer rejected or dismissed are left out; reports not yet reviewed are included and marked unverified.

Every row is a station in AFDC; reports about stations we found through other sources have no AFDC ID and are left out.

Known limits

  • Reports come from drivers who chose to send them, not from a random sample, so a station with no row is not proof it works.
  • No personal data: no reporter names, emails, phone numbers, user IDs or IP addresses, and nothing a driver typed in their own words.

Changelog 1 version #

1. v1: First release: 1 row.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

Removed or relocated stations

Stations drivers report as closed, removed or not at the listed location, with the report date.

  • Rows
  • 0
  • Version
  • v1
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “Removed or relocated stations.” US EV Charging Open Data, version 1, October 31, 2026. https://chargingnear.me/data#removed-or-relocated-stations. CC BY 4.0.

Column dictionary 13 columns #

Column Meaning
afdc_station_id The station’s ID in the AFDC Station Locator. Join on it.
chargingnear_station_id The station’s ID on ChargingNear.me (the same number for AFDC stations).
station_name The station as listed when the file was built.
address Street address.
city City.
state Two-letter state code.
network Charging network, named as in AFDC.
report_type What was reported. Outages: broken, blocked, access_restricted, working (a driver found the charger working), or field_check (our own team checked the charger in person). Corrections: hours, access, pricing. Removed or relocated: closed, wrong_location.
reported_at When the report, correction or field check was made (UTC, ISO 8601).
verified_status verified: a ChargingNear.me reviewer approved or resolved it, or staff applied the correction. unverified: sent by a driver and not yet reviewed, or a correction applied automatically from a driver. field-verified by ChargingNear.me: our own team checked the charger in person.
details A short description of the report type, written by ChargingNear.me. Never the driver’s own words.
resolved_at When a reviewer marked the report resolved. Empty while it is open.
record_id A stable ID for the row, such as report-123, correction-45 or field-check-7.

Methodology #

Rows are reports drivers send on ChargingNear.me about stations in AFDC, and checks our own team makes in person. Reports a reviewer rejected or dismissed are left out; reports not yet reviewed are included and marked unverified.

Every row is a station in AFDC; reports about stations we found through other sources have no AFDC ID and are left out.

Known limits

  • Reports come from drivers who chose to send them, not from a random sample, so a station with no row is not proof it works.
  • No personal data: no reporter names, emails, phone numbers, user IDs or IP addresses, and nothing a driver typed in their own words.

Changelog 1 version #

1. v1: First release: 0 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

f. How much charging does each Colorado county have, and how fast is it growing? #

Monthly growth starts in September 2026, the first month of our daily sync history. We could not confirm a dated, citable county-level EV registration release from the Colorado Energy Office, so county rates are per resident only.

Colorado public charging by county

All 64 Colorado counties: open public stations, ports and DC fast ports, per 100,000 residents.

  • Rows
  • 64
  • Version
  • v6
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “Colorado public charging by county.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#colorado-counties. CC BY 4.0.

Column dictionary 11 columns #

Column Meaning
county_fips Five-digit county FIPS code.
county County name.
population_2025 Residents, July 1, 2025 (Census Bureau Vintage 2025 estimates).
stations Open public AFDC stations in the county.
ports Level 1, Level 2 and DC fast ports at those stations.
level2_ports Level 2 ports.
dc_fast_ports DC fast ports.
dc_fast_stations Stations with at least one DC fast port.
stations_per_100k_residents Stations per 100,000 residents.
ports_per_100k_residents Ports per 100,000 residents.
dc_fast_ports_per_100k_residents DC fast ports per 100,000 residents.

Methodology #

Stations are AFDC stations listed as open and public. Each is placed in a county by its coordinates, using Census county boundaries.

Rates use the Census Bureau’s July 1, 2025 county population estimates.

Per-EV rates are not shown for counties: we could not confirm a dated, published county-level EV registration source from the Colorado Energy Office, so the file ships population-based rates only.

Known limits

  • Boundaries are simplified to about 150 meters, so a station right on a county line can land in the neighboring county.

Sources 3 #

Changelog 6 versions #

1. v6: Values updated in existing rows (64 rows).
2. v5: Values updated in existing rows (64 rows).
3. v4: Values updated in existing rows (64 rows).
4. v3: Values updated in existing rows (64 rows).
5. v2: Values updated in existing rows (64 rows).
6. v1: First release: 64 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

Monthly new public charging by state

New public stations, ports and DC fast ports per month for the 50 states and DC, from our daily AFDC sync history.

  • Rows
  • 153
  • Version
  • v7
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “Monthly new public charging by state.” US EV Charging Open Data, version 7, November 5, 2026. https://chargingnear.me/data#monthly-growth-by-state. CC BY 4.0.

Column dictionary 8 columns #

| Column | Meaning |

|---|---|
| `month` | Calendar month (UTC), YYYY-MM. |

| state | Two-letter state code. | | state_name | State name. | | new_stations | Open public AFDC stations first seen by our sync that month. | | new_ports | Their Level 1, Level 2 and DC fast ports. | | new_dc_fast_ports | Their DC fast ports. | | complete_month | yes for a finished month; no for the month in progress. | | note | Anything that affects the month’s count. |

Methodology #

A station is new in the month our daily sync first added it from AFDC. Only stations still listed as open and public count, so a station that opened and later closed drops out.

The series starts in 2026-09, the first full month of our daily AFDC sync history. September 2026 also includes stations AFDC added from June 13 to September 5, 2026, which the sync picked up on September 7.

Known limits

  • The month a station appears in AFDC can lag the day it opened.

Changelog 7 versions #

1. v7: Values updated in existing rows (153 rows).
2. v6: Values updated in existing rows (153 rows).
3. v5: Values updated in existing rows (153 rows).
4. v4: Values updated in existing rows (153 rows).
5. v3: Values updated in existing rows (153 rows).
  1. v2: Rows 102 → 153.
7. v1: First release: 102 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

Monthly new public charging by Colorado county

New public stations, ports and DC fast ports per month for every Colorado county, from our daily AFDC sync history.

  • Rows
  • 192
  • Version
  • v6
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “Monthly new public charging by Colorado county.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#monthly-growth-colorado-counties. CC BY 4.0.

Column dictionary 8 columns #

| Column | Meaning |

|---|---|
| `month` | Calendar month (UTC), YYYY-MM. |

| county_fips | Five-digit county FIPS code. | | county | County name. | | new_stations | Open public AFDC stations first seen by our sync that month. | | new_ports | Their Level 1, Level 2 and DC fast ports. | | new_dc_fast_ports | Their DC fast ports. | | complete_month | yes for a finished month; no for the month in progress. | | note | Anything that affects the month’s count. |

Methodology #

A station is new in the month our daily sync first added it from AFDC. Only stations still listed as open and public count, so a station that opened and later closed drops out.

The series starts in 2026-09, the first full month of our daily AFDC sync history. September 2026 also includes stations AFDC added from June 13 to September 5, 2026, which the sync picked up on September 7.

Known limits

  • The month a station appears in AFDC can lag the day it opened.

Sources 2 #

Changelog 6 versions #

1. v6: Values updated in existing rows (192 rows).
2. v5: Values updated in existing rows (192 rows).
3. v4: Values updated in existing rows (192 rows).
4. v3: Values updated in existing rows (192 rows).
  1. v2: Rows 128 → 192.
6. v1: First release: 128 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

g. How do states compare on public charging? #

State public charging per resident and per EV

The 50 states and DC: open public stations, ports and DC fast ports, per 100,000 residents and per 1,000 registered EVs.

  • Rows
  • 51
  • Version
  • v6
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “State public charging per resident and per EV.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#state-charging-rankings. CC BY 4.0.

Column dictionary 13 columns #

Column Meaning
state Two-letter state code.
state_name State name.
stations Open public AFDC stations.
ports Level 1, Level 2 and DC fast ports at those stations.
dc_fast_ports DC fast ports.
population_2025 Residents, July 1, 2025 (Census Bureau Vintage 2025 estimates).
ev_registrations_2025 Light-duty battery-electric plus plug-in hybrid registrations, 2025 (AFDC).
stations_per_100k_residents Stations per 100,000 residents.
ports_per_100k_residents Ports per 100,000 residents.
dc_fast_ports_per_100k_residents DC fast ports per 100,000 residents.
stations_per_1000_evs Stations per 1,000 registered EVs.
ports_per_1000_evs Ports per 1,000 registered EVs.
dc_fast_ports_per_1000_evs DC fast ports per 1,000 registered EVs.

Methodology #

Stations and ports are AFDC stations listed as open and public, counted by the state in their address.

Population is the Census Bureau’s July 1, 2025 estimate. EVs are AFDC’s 2025 light-duty registration counts by state, battery-electric plus plug-in hybrid, rounded by AFDC to the nearest 100.

Known limits

  • Registration counts are for 2025; station counts are today’s.

Sources 3 #

- [U.S. Census Bureau, Vintage 2025 Population Estimates (July 1, 2025)](https://www2.census.gov/programs-surveys/popest/datasets/2020-2025/state/totals/NST-EST2025-ALLDATA.csv) , January 2026
- [U.S. DOE Alternative Fuels Data Center, Vehicle Registration Counts by State (2025)](https://afdc.energy.gov/vehicle-registration?year=2025) , retrieved 2026-10-30

Changelog 6 versions #

1. v6: Values updated in existing rows (51 rows).
2. v5: Values updated in existing rows (51 rows).
3. v4: Values updated in existing rows (51 rows).
4. v3: Values updated in existing rows (51 rows).
5. v2: Values updated in existing rows (51 rows).
6. v1: First release: 51 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

h. Where are the fast chargers on Colorado's highway corridors? #

The tables from our Colorado corridor pages, I-70, I-25, I-76, US-285, CO-82 and US-40, with CDOT mile points.

I-70 fast chargers, Denver to Grand Junction

Every DC fast charging location within 2 miles of I-70 from I-25 in Denver (exit 274) to the west side of Grand Junction (exit 26), in the order you reach them driving west: CDOT mile point, miles from the previous fast charger, ports and power. The table on the I-70 corridor page.

  • Rows
  • 53
  • Version
  • v3
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “I-70 fast chargers, Denver to Grand Junction.” US EV Charging Open Data, version 3, November 5, 2026. https://chargingnear.me/data#i-70-corridor-denver-to-grand-junction. CC BY 4.0.

Column dictionary 18 columns #

Column Meaning
order_east_to_west Position in driving order heading west, starting at 1 nearest Denver.
location_name The location’s name on ChargingNear.me.
street_address Street address.
city City.
state Two-letter state code (always CO).
network Charging network as listed by the source.
connector_types Connector codes, semicolon-separated, in AFDC’s vocabulary: J1772COMBO (CCS), TESLA (NACS/J3400), CHADEMO, J1772.
dc_fast_ports DC fast ports at the location.
max_power_kw Highest power listed for the location, in kW; empty when the listed figure is not a plausible DC fast value (under 20 or over 1,500). 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| cdot_mile_point | CDOT mile point on I-70 where the location is closest to the highway (one decimal). Colorado numbers I-70’s exits by mile point. | | miles_west_of_i25 | Miles along I-70 from the I-25 interchange in Denver. | | miles_from_previous_fast_charger | Miles along I-70 from the previous row’s location; empty for the first row. | | miles_off_i70 | Straight-line miles from the location to I-70 (2 or less). | | source | AFDC, or Open Charge Map for a location AFDC does not list. | | afdc_station_id | The main station’s ID in the AFDC Station Locator; empty for Open Charge Map rows. | | station_url | The location’s page on ChargingNear.me. |

Methodology #

We read every public DC fast charging location in our live station data and keep those within 2 miles of I-70 between the I-25 interchange in Denver (exit 274) and the US 6/50 interchange on the west side of Grand Junction (exit 26). A location without its own page is never listed.

The highway is CDOT’s line for I-70 (route 070A in CDOT’s Highways open data); mile points are CDOT’s mile points on it. Distances are measured along I-70 between the points where each location is closest to the highway.

The file is rebuilt from the same data as the I-70 corridor page once a day, with the other files. The page updates as stations change, so it can be up to a day ahead of the file.

Known limits

  • Each location can be up to 2 miles off I-70, so allow for the drive to and from the exit.
  • A location with several stations is one row; its ports are the sum of its stations’ DC fast ports.
  • Rows whose source is Open Charge Map come from Open Charge Map contributors under CC BY 4.0; credit them as well when you reuse those rows.

Sources 3 #

- [Colorado Department of Transportation, Highways (CDOT open data)](https://data-cdot.opendata.arcgis.com/datasets/cdot::highways)
- [Open Charge Map (openchargemap.org), user-contributed data under CC BY 4.0, for the few locations AFDC does not list](https://www.openchargemap.org/about/terms)

Changelog 3 versions #

  1. v3: Values updated in existing rows (53 rows).

  2. v2: Rows 54 → 53.

  3. v1: First release: 54 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

I-25 fast chargers in Colorado, Wyoming line to New Mexico line

Every DC fast charging location in Colorado within 2 miles of I-25 from the Wyoming line to the New Mexico line, in the order you reach them: CDOT mile point, miles from the previous fast charger, ports and power. The table on the I-25 corridor page.

  • Rows
  • 99
  • Version
  • v5
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “I-25 fast chargers in Colorado, Wyoming line to New Mexico line.” US EV Charging Open Data, version 5, November 5, 2026. https://chargingnear.me/data#i-25-corridor-colorado. CC BY 4.0.

Column dictionary 19 columns #

Column Meaning
driving_order Position in driving order from the Wyoming line to the New Mexico line, starting at 1.
location_name The location’s name on ChargingNear.me.
street_address Street address.
city City.
state Two-letter state code (always CO).
network Charging network as listed by the source.
connector_types Connector codes, semicolon-separated, in AFDC’s vocabulary: J1772COMBO (CCS), TESLA (NACS/J3400), CHADEMO, J1772.
dc_fast_ports DC fast ports at the location.
max_power_kw Highest power listed for the location, in kW; empty when the listed figure is not a plausible DC fast value (under 20 or over 1,500). 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| highway | The highway the location is closest to: I-25. | | cdot_mile_point | CDOT mile point on that highway where the location is closest to it (one decimal). Colorado numbers I-25’s exits by mile point. | | miles_from_start | Miles along the highway from the Wyoming line. | | miles_from_previous_fast_charger | Miles along the highway from the previous row’s location; empty for the first row. | | miles_off_highway | Straight-line miles from the location to the highway (2 or less). | | source | AFDC, or Open Charge Map for a location AFDC does not list. | | afdc_station_id | The main station’s ID in the AFDC Station Locator; empty for Open Charge Map rows. | | station_url | The location’s page on ChargingNear.me. |

Methodology #

We read every public DC fast charging location in our live station data and keep those in Colorado within 2 miles of I-25 between the Wyoming line (CDOT mile point 299) and the New Mexico line (mile point 0), plus half a mile past either end. A location without its own page is never listed.

The highway is CDOT’s line for I-25 (route 025A in CDOT’s Highways open data); mile points are CDOT’s mile points on it. Distances are measured along the highway between the points where each location is closest to it.

The file is rebuilt from the same data as the I-25 corridor page once a day, with the other files. The page updates as stations change, so it can be up to a day ahead of the file.

Known limits

  • Each location can be up to 2 miles off I-25, so allow for the drive to and from the highway.
  • A location with several stations is one row; its ports are the sum of its stations’ DC fast ports.
  • Rows whose source is Open Charge Map come from Open Charge Map contributors under CC BY 4.0; credit them as well when you reuse those rows.

Sources 3 #

- [Colorado Department of Transportation, Highways (CDOT open data)](https://data-cdot.opendata.arcgis.com/datasets/cdot::highways)
- [Open Charge Map (openchargemap.org), user-contributed data under CC BY 4.0, for the few locations AFDC does not list](https://www.openchargemap.org/about/terms)

Changelog 5 versions #

  1. v5: Rows 98 → 99.

  2. v4: Values updated in existing rows (98 rows).

  3. v3: Rows 97 → 98.

  4. v2: Rows 96 → 97.

  5. v1: First release: 96 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

I-76 fast chargers, Denver to the Nebraska line

Every DC fast charging location in Colorado within 2 miles of I-76 from I-70 in Arvada to the Nebraska line, in the order you reach them: CDOT mile point, miles from the previous fast charger, ports and power. The table on the I-76 corridor page.

  • Rows
  • 14
  • Version
  • v3
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “I-76 fast chargers, Denver to the Nebraska line.” US EV Charging Open Data, version 3, November 5, 2026. https://chargingnear.me/data#i-76-corridor-denver-to-nebraska. CC BY 4.0.

Column dictionary 19 columns #

Column Meaning
driving_order Position in driving order from I-70 in Arvada to the Nebraska line, starting at 1.
location_name The location’s name on ChargingNear.me.
street_address Street address.
city City.
state Two-letter state code (always CO).
network Charging network as listed by the source.
connector_types Connector codes, semicolon-separated, in AFDC’s vocabulary: J1772COMBO (CCS), TESLA (NACS/J3400), CHADEMO, J1772.
dc_fast_ports DC fast ports at the location.
max_power_kw Highest power listed for the location, in kW; empty when the listed figure is not a plausible DC fast value (under 20 or over 1,500). 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| highway | The highway the location is closest to: I-76. | | cdot_mile_point | CDOT mile point on that highway where the location is closest to it (one decimal). Colorado numbers I-76’s exits by mile point. | | miles_from_start | Miles along the highway from I-70 in Arvada. | | miles_from_previous_fast_charger | Miles along the highway from the previous row’s location; empty for the first row. | | miles_off_highway | Straight-line miles from the location to the highway (2 or less). | | source | AFDC, or Open Charge Map for a location AFDC does not list. | | afdc_station_id | The main station’s ID in the AFDC Station Locator; empty for Open Charge Map rows. | | station_url | The location’s page on ChargingNear.me. |

Methodology #

We read every public DC fast charging location in our live station data and keep those in Colorado within 2 miles of I-76 between I-70 in Arvada (CDOT mile point 0) and the Nebraska line (mile point 184), plus half a mile past either end. A location without its own page is never listed.

The highway is CDOT’s line for I-76 (route 076A in CDOT’s Highways open data); mile points are CDOT’s mile points on it. Distances are measured along the highway between the points where each location is closest to it.

The file is rebuilt from the same data as the I-76 corridor page once a day, with the other files. The page updates as stations change, so it can be up to a day ahead of the file.

Known limits

  • Each location can be up to 2 miles off I-76, so allow for the drive to and from the highway.
  • A location with several stations is one row; its ports are the sum of its stations’ DC fast ports.
  • Rows whose source is Open Charge Map come from Open Charge Map contributors under CC BY 4.0; credit them as well when you reuse those rows.

Sources 3 #

- [Colorado Department of Transportation, Highways (CDOT open data)](https://data-cdot.opendata.arcgis.com/datasets/cdot::highways)
- [Open Charge Map (openchargemap.org), user-contributed data under CC BY 4.0, for the few locations AFDC does not list](https://www.openchargemap.org/about/terms)

Changelog 3 versions #

  1. v3: Rows 15 → 14.

  2. v2: Rows 14 → 15.

  3. v1: First release: 14 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

US-285 fast chargers, Denver to the New Mexico line

Every DC fast charging location in Colorado within 2 miles of US-285 from I-25 in Denver to the New Mexico line, in the order you reach them: CDOT mile point, miles from the previous fast charger, ports and power. The table on the US-285 corridor page.

  • Rows
  • 15
  • Version
  • v3
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “US-285 fast chargers, Denver to the New Mexico line.” US EV Charging Open Data, version 3, November 5, 2026. https://chargingnear.me/data#us-285-corridor-denver-to-new-mexico. CC BY 4.0.

Column dictionary 19 columns #

Column Meaning
driving_order Position in driving order from I-25 in Denver to the New Mexico line, starting at 1.
location_name The location’s name on ChargingNear.me.
street_address Street address.
city City.
state Two-letter state code (always CO).
network Charging network as listed by the source.
connector_types Connector codes, semicolon-separated, in AFDC’s vocabulary: J1772COMBO (CCS), TESLA (NACS/J3400), CHADEMO, J1772.
dc_fast_ports DC fast ports at the location.
max_power_kw Highest power listed for the location, in kW; empty when the listed figure is not a plausible DC fast value (under 20 or over 1,500). 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| highway | The highway the location is closest to: US-285, or US-24 or US-160 where US-285 shares its road. | | cdot_mile_point | CDOT mile point on that highway where the location is closest to it (one decimal). | | miles_from_start | Miles along the highway from I-25 in Denver. | | miles_from_previous_fast_charger | Miles along the highway from the previous row’s location; empty for the first row. | | miles_off_highway | Straight-line miles from the location to the highway (2 or less). | | source | AFDC, or Open Charge Map for a location AFDC does not list. | | afdc_station_id | The main station’s ID in the AFDC Station Locator; empty for Open Charge Map rows. | | station_url | The location’s page on ChargingNear.me. |

Methodology #

We read every public DC fast charging location in our live station data and keep those in Colorado within 2 miles of US-285 between I-25 in Denver (CDOT mile point 264) and the New Mexico line (mile point 0), plus half a mile past either end. A location without its own page is never listed.

The highway is CDOT’s line for US-285 (routes 285D, 024A, 285B, 160A and 285A in CDOT’s Highways open data); mile points are CDOT’s mile points on it. Where US-285 shares the road with US-24 and US-160, the line there is the other highway’s, and so are its mile points; the highway column says which. Distances are measured along the highway between the points where each location is closest to it.

The file is rebuilt from the same data as the US-285 corridor page once a day, with the other files. The page updates as stations change, so it can be up to a day ahead of the file.

Known limits

  • Each location can be up to 2 miles off US-285, so allow for the drive to and from the highway.
  • A location with several stations is one row; its ports are the sum of its stations’ DC fast ports.
  • Rows whose source is Open Charge Map come from Open Charge Map contributors under CC BY 4.0; credit them as well when you reuse those rows.

Sources 3 #

- [Colorado Department of Transportation, Highways (CDOT open data)](https://data-cdot.opendata.arcgis.com/datasets/cdot::highways)
- [Open Charge Map (openchargemap.org), user-contributed data under CC BY 4.0, for the few locations AFDC does not list](https://www.openchargemap.org/about/terms)

Changelog 3 versions #

  1. v3: Values updated in existing rows (15 rows).

  2. v2: Rows 14 → 15.

  3. v1: First release: 14 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

CO-82 fast chargers, Glenwood Springs to Aspen

Every DC fast charging location in Colorado within 2 miles of CO-82 from I-70 in Glenwood Springs to Aspen, in the order you reach them: CDOT mile point, miles from the previous fast charger, ports and power. The table on the CO-82 corridor page.

  • Rows
  • 8
  • Version
  • v1
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “CO-82 fast chargers, Glenwood Springs to Aspen.” US EV Charging Open Data, version 1, October 31, 2026. https://chargingnear.me/data#co-82-corridor-glenwood-springs-to-aspen. CC BY 4.0.

Column dictionary 19 columns #

Column Meaning
driving_order Position in driving order from I-70 in Glenwood Springs to Aspen, starting at 1.
location_name The location’s name on ChargingNear.me.
street_address Street address.
city City.
state Two-letter state code (always CO).
network Charging network as listed by the source.
connector_types Connector codes, semicolon-separated, in AFDC’s vocabulary: J1772COMBO (CCS), TESLA (NACS/J3400), CHADEMO, J1772.
dc_fast_ports DC fast ports at the location.
max_power_kw Highest power listed for the location, in kW; empty when the listed figure is not a plausible DC fast value (under 20 or over 1,500). 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| highway | The highway the location is closest to: CO-82. | | cdot_mile_point | CDOT mile point on that highway where the location is closest to it (one decimal). | | miles_from_start | Miles along the highway from I-70 in Glenwood Springs. | | miles_from_previous_fast_charger | Miles along the highway from the previous row’s location; empty for the first row. | | miles_off_highway | Straight-line miles from the location to the highway (2 or less). | | source | AFDC, or Open Charge Map for a location AFDC does not list. | | afdc_station_id | The main station’s ID in the AFDC Station Locator; empty for Open Charge Map rows. | | station_url | The location’s page on ChargingNear.me. |

Methodology #

We read every public DC fast charging location in our live station data and keep those in Colorado within 2 miles of CO-82 between I-70 in Glenwood Springs (CDOT mile point 0) and Aspen (mile point 42), plus half a mile past either end. A location without its own page is never listed.

The highway is CDOT’s line for CO-82 (route 082A in CDOT’s Highways open data); mile points are CDOT’s mile points on it. Distances are measured along the highway between the points where each location is closest to it.

The file is rebuilt from the same data as the CO-82 corridor page once a day, with the other files. The page updates as stations change, so it can be up to a day ahead of the file.

Known limits

  • Each location can be up to 2 miles off CO-82, so allow for the drive to and from the highway.
  • A location with several stations is one row; its ports are the sum of its stations’ DC fast ports.
  • Rows whose source is Open Charge Map come from Open Charge Map contributors under CC BY 4.0; credit them as well when you reuse those rows.

Sources 3 #

- [Colorado Department of Transportation, Highways (CDOT open data)](https://data-cdot.opendata.arcgis.com/datasets/cdot::highways)
- [Open Charge Map (openchargemap.org), user-contributed data under CC BY 4.0, for the few locations AFDC does not list](https://www.openchargemap.org/about/terms)

Changelog 1 version #

  1. v1: First release: 8 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

US-40 fast chargers, I-70 to Steamboat Springs

Every DC fast charging location in Colorado within 2 miles of US-40 from I-70 near Empire to the west side of Steamboat Springs, in the order you reach them: CDOT mile point, miles from the previous fast charger, ports and power. The table on the US-40 corridor page.

  • Rows
  • 7
  • Version
  • v1
  • Last changed
  • Area
  • Colorado

Cite as

ChargingNear.me. “US-40 fast chargers, I-70 to Steamboat Springs.” US EV Charging Open Data, version 1, October 31, 2026. https://chargingnear.me/data#us-40-corridor-i-70-to-steamboat-springs. CC BY 4.0.

Column dictionary 19 columns #

Column Meaning
driving_order Position in driving order from I-70 near Empire to the west side of Steamboat Springs, starting at 1.
location_name The location’s name on ChargingNear.me.
street_address Street address.
city City.
state Two-letter state code (always CO).
network Charging network as listed by the source.
connector_types Connector codes, semicolon-separated, in AFDC’s vocabulary: J1772COMBO (CCS), TESLA (NACS/J3400), CHADEMO, J1772.
dc_fast_ports DC fast ports at the location.
max_power_kw Highest power listed for the location, in kW; empty when the listed figure is not a plausible DC fast value (under 20 or over 1,500). 
| `latitude` | Latitude (WGS 84). | 
| `longitude` | Longitude (WGS 84). |

| highway | The highway the location is closest to: US-40. | | cdot_mile_point | CDOT mile point on that highway where the location is closest to it (one decimal). | | miles_from_start | Miles along the highway from I-70 near Empire. | | miles_from_previous_fast_charger | Miles along the highway from the previous row’s location; empty for the first row. | | miles_off_highway | Straight-line miles from the location to the highway (2 or less). | | source | AFDC, or Open Charge Map for a location AFDC does not list. | | afdc_station_id | The main station’s ID in the AFDC Station Locator; empty for Open Charge Map rows. | | station_url | The location’s page on ChargingNear.me. |

Methodology #

We read every public DC fast charging location in our live station data and keep those in Colorado within 2 miles of US-40 between I-70 near Empire (CDOT mile point 258) and the west side of Steamboat Springs (mile point 129), plus half a mile past either end. A location without its own page is never listed.

The highway is CDOT’s line for US-40 (route 040A in CDOT’s Highways open data); mile points are CDOT’s mile points on it. Distances are measured along the highway between the points where each location is closest to it.

The file is rebuilt from the same data as the US-40 corridor page once a day, with the other files. The page updates as stations change, so it can be up to a day ahead of the file.

Known limits

  • Each location can be up to 2 miles off US-40, so allow for the drive to and from the highway.
  • A location with several stations is one row; its ports are the sum of its stations’ DC fast ports.
  • Rows whose source is Open Charge Map come from Open Charge Map contributors under CC BY 4.0; credit them as well when you reuse those rows.

Sources 3 #

- [Colorado Department of Transportation, Highways (CDOT open data)](https://data-cdot.opendata.arcgis.com/datasets/cdot::highways)
- [Open Charge Map (openchargemap.org), user-contributed data under CC BY 4.0, for the few locations AFDC does not list](https://www.openchargemap.org/about/terms)

Changelog 1 version #

  1. v1: First release: 7 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

i. Which U.S. counties are charging deserts? #

Today 1,308 of 3,144 counties are charging deserts, with no DC fast port or fewer than 1 public port per 10,000 residents. They are home to 6.8% of U.S. residents. Population is the Census Bureau’s CO-EST2025-POP table (July 1, 2025).

EV charging access by U.S. county

Every county and county-equivalent in the 50 states and DC, by 5-digit FIPS: public charging locations, ports, DC fast and Level 2 ports, ports per 10,000 residents, miles from the county’s center to the nearest DC fast charger, and whether it is a charging desert.

  • Rows
  • 3,144
  • Version
  • v1
  • Last changed
  • Area
  • United States

Cite as

ChargingNear.me. “EV charging access by U.S. county.” US EV Charging Open Data, version 1, November 5, 2026. https://chargingnear.me/data#us-county-charging-access. CC BY 4.0.

Column dictionary 12 columns #

Column Meaning
county County or county-equivalent name, as the Census Bureau writes it (parishes, boroughs, independent cities and Connecticut’s planning regions included).
state Two-letter state code.
fips Five-digit county FIPS code (2 digits state, 3 digits county). Join on it.
population Residents, July 1, 2025 (Census Bureau Vintage 2025 estimates, table CO-EST2025-POP).
public_charging_locations Public charging locations in the county: each site counts once however many AFDC stations it holds, and a station in no site counts on its own.
public_ports Level 1, Level 2 and DC fast ports at the county’s open public AFDC stations.
dc_fast_ports DC fast ports.
level2_ports Level 2 ports.
ports_per_10k_residents public_ports per 10,000 residents, to two decimals.
dc_fast_ports_per_10k_residents dc_fast_ports per 10,000 residents, to two decimals.
nearest_dc_fast_miles_from_county_centroid Straight-line (great-circle) miles from the county’s center point (the Census internal point) to the nearest open public DC fast station in the 50 states and DC, any network including Tesla, in or out of the county. Not driving distance.
desert_flag yes when the county has no DC fast port, or fewer than 1 public port per 10,000 residents; otherwise no.

Methodology #

Stations are AFDC stations listed as open and public in the 50 states and DC, read by our daily sync. Each is placed in a county by its coordinates, using Census TIGERweb county boundaries; ports are summed from those stations.

Locations follow the site-wide rule ChargingNear.me uses everywhere: stations at the same place form one site, so a site counts once; a station not yet in a site counts on its own.

Population is the Census Bureau’s Vintage 2025 estimate for July 1, 2025, from the table “Annual Estimates of the Resident Population for Counties: April 1, 2020 to July 1, 2025” (CO-EST2025-POP, released March 2026), read from its machine-readable twin co-est2025-alldata.csv, column POPESTIMATE2025.

The county’s center point is the internal point the Census Bureau publishes for it in TIGERweb (INTPTLAT, INTPTLON): a point inside the county near its center. We use it rather than the plain geometric centroid (CENTLAT, CENTLON), which for counties with large water areas falls in open water; Honolulu County’s lies in the Pacific, hundreds of miles from Oahu. Distances are great-circle miles to the nearest open public DC fast station, rounded to a tenth of a mile.

A county is a charging desert (desert_flag = yes) when it has no DC fast port, or fewer than 1 public port per 10,000 residents.

No EV registration column: no official source publishes EV registrations for every U.S. county, so the file ships population-based rates only.

Known limits

  • Boundaries are simplified to about 200 meters, so a station right on a county line can land in the neighboring county.
  • A county’s center point can sit in open country or a national forest; the distance is from that point, not from where people live.
  • Puerto Rico and the other territories are not included.

Sources 3 #

Changelog 1 version #

1. v1: First release: 3,144 rows.

License: Creative Commons Attribution 4.0 International (CC BY 4.0). Credit ChargingNear.me. [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)

j. Which non-Tesla fast chargers have NACS plugs? #

Today 1,924 of 12,617 open public DC fast stations off Tesla’s network have a NACS (J3400) plug, on 47 networks in 50 states.

Non-Tesla DC fast chargers with NACS (J3400) plugs

Every open public DC fast station in the 50 states and DC that is not on Tesla’s network and has a NACS (SAE J3400) plug: its network, location, NACS, CCS and CHAdeMO ports, top power and the date AFDC last confirmed it.

  • Rows
  • 1,924
  • Version
  • v1
  • Last changed
  • Area
  • United States

By network 48

Network Stations NACS ports
ChargePoint 743 809
IONNA 216 634
EVgo 123 282
Walmart 110 452
Rivian Adventure Network 98 451
Mercedes-Benz High-Power Charging 74 691
Red E Charge 69 137
Applegreen Electric 49 176
bp pulse 38 244
7Charge 37 38
Blink Network 34 68
EVCS 34 66
FPL EVolution 27 77
Non-Networked 25 57
Kwik Charge 23 92
Electric Era 19 56
ViaLynk 18 53
Electrify America 17 71
Francis Energy 15 62
EV Connect 15 29
Shell Recharge 14 49
Graviti Energy 14 23
RaceTrac 13 19
Jule 11 32
EvGateway 9 15
Chaevi 8 9
ChargeNet 7 32
Revel 6 81
InCharge 6 22
PowerPump 6 13
Nayax Energy 5 34
SWTCH Energy 5 19
OnPoint EV Solutions 5 14
OpConnect 5 7
Noodoe 5 6
ChargeLab 4 5
Jojo Superfast 3 24
EV Range 2 5
Autel 2 4
Ford Charge 2 2
Gravity Charging Center 1 24
EVOLV Charging 1 8
GO TO-U 1 6
Circle K Charge 1 4
PowerUp 1 4
Rove 1 4
FLO 1 2
synergEV 1 1

By state 50

State Stations NACS ports
California 415 872
Florida 165 433
Texas 161 541
Georgia 105 254
Washington 83 184
New York 80 278
Colorado 69 152
Michigan 69 149
Pennsylvania 66 166
Massachusetts 61 143
Illinois 56 138
Tennessee 44 71
Wisconsin 40 114
Alabama 40 76
Ohio 36 103
New Jersey 35 95
North Carolina 31 92
Minnesota 29 74
Kentucky 27 67
Arizona 25 88
Utah 23 101
Oregon 23 74
Maine 20 80
Missouri 20 61
Maryland 17 38
Indiana 16 62
Virginia 15 58
South Carolina 14 47
Connecticut 13 57
Oklahoma 13 44
Arkansas 11 32
Kansas 10 27
Nevada 10 19
Mississippi 10 11
Vermont 9 28
New Mexico 8 20
Hawaii 8 13
New Hampshire 7 33
Idaho 7 15
Rhode Island 6 19
Nebraska 5 20
Louisiana 3 11
Montana 3 11
Iowa 3 3
North Dakota 3 3
Delaware 2 13
Wyoming 2 11
West Virginia 2 6
Alaska 2 4
South Dakota 2 2

NACS ports are DC fast ports with a NACS plug.

Cite as

ChargingNear.me. “Non-Tesla DC fast chargers with NACS (J3400) plugs.” US EV Charging Open Data, version 1, November 5, 2026. https://chargingnear.me/data#us-nacs-fast-chargers. CC BY 4.0.

Column dictionary 12 columns #

Column Meaning
station_id The station’s ID in the AFDC Station Locator and on ChargingNear.me (the same number). Join on it.
name Station name as AFDC lists it.
network Charging network, named as in AFDC. Never Tesla or Tesla Destination.
city City.
state Two-letter state code.
lat Latitude (WGS 84, decimal degrees).
lon Longitude (WGS 84, decimal degrees).
nacs_ports DC fast ports with a NACS (J3400) plug. Empty when AFDC lists no per-port detail for the station.
ccs_ports DC fast ports with a CCS (J1772 Combo) plug. Empty when AFDC lists no per-port detail.
chademo_ports DC fast ports with a CHAdeMO plug. Empty when AFDC lists no per-port detail.
max_kw Highest power AFDC lists for any DC fast plug at the station, in kW. Empty when unknown.
date_last_confirmed The date AFDC last confirmed the station’s details (YYYY-MM-DD). Empty when AFDC gives none.

Methodology #

Rows are AFDC stations listed as open and public with at least one DC fast port, in the 50 states and DC, read by our daily sync. Stations on AFDC’s Tesla and Tesla Destination networks are left out; every other network, and non-networked stations, stay in.

AFDC writes the NACS (SAE J3400) connector as TESLA. Where AFDC itemizes a station’s ports, a station is in the file only if a DC fast port has that plug (a Level 2 NACS plug alone does not count). Where it does not, the station’s connector list decides, and the three port columns are left empty rather than guessed.

Port columns count DC fast ports by the plugs each has. A port with two cables, such as NACS and CCS, counts under both, so the three columns can add up to more than the station’s DC fast ports.

The by-network and by-state tables on this card are built from the same rows on the same day.

Known limits

  • A NACS plug on a non-Tesla charger is often a NACS cable fitted to a CCS charger; AFDC does not say whether a Tesla can start a session without an app or adapter.
  • Facts are as AFDC publishes them; a network adding NACS cables shows up here once AFDC lists them.

Changelog 1 version #

  1. v1: First release: 1,924 rows. License: Station facts from AFDC (NREL) are U.S. public domain; ChargingNear.me’s selection and IDs are CC BY 4.0. Credit ChargingNear.me. CC BY 4.0

What is the license? #

Our own files and layers are licensed Creative Commons Attribution 4.0 International (CC BY 4.0): use them for anything, with credit to ChargingNear.me. Station facts from AFDC are U.S. public domain. Each file shows its “Cite as” line.

Station-by-station reliability history, availability history and the Demand Graph are not in these files; they stay paid, under our API Terms. The files never include reporter names, emails, phone numbers, user IDs or IP addresses, or anything a driver typed in their own words.

How can agencies and researchers get help? #

A weekly file is available on request, in any format your team prefers. To report an error in a file, or ask how a figure was built, write to reserve@winsparking.com. Our guide for agencies covers citation, the API and corrections; the methodology page explains how every file is built.

Questions about this data #

Where are the biggest gaps between EV fast chargers on U.S. highways?

As of November 6, 2026, the longest stretch in our highway gap file is 376.6 miles of US-2 in Montana, from Idaho state line to Tilleman Motors, Havre. The file lists 881 highway stretches where open public DC fast chargers are more than 50 miles apart. Colorado has 22 of them; its longest is 152.6 miles of US-160, from where US-160 meets I-25 to Kansas state line.

What does NEVI-compliant mean?

A NEVI-compliant station has at least four CCS ports that can each deliver 150 kW at the same time, under 23 CFR 680.106 (FHWA final rule, February 28, 2023). FHWA’s February 10, 2022 guidance put stations within 1 travel mile of a designated corridor and every 50 miles; its August 11, 2025 guidance leaves spacing to states. As of November 6, 2026, 2,547 of 15,927 open public DC fast stations in the 50 states and DC meet the port, power and distance minimums in our NEVI station check.

Is there open data on EV charger reliability?

Yes. Our reliability roll-up file gives the average and median Working-Now Score for each network, Colorado county and Colorado corridor whose stations have at least 10 driver reports in the last 30 days. As of November 6, 2026, no group has reached 10 reports, so the file has no rows yet. Drivers sent 1 report about public stations in the 30 days to that date.

Which Colorado counties have the most EV chargers per person?

As of November 6, 2026, Gilpin County has the most public charging ports per person of Colorado’s 64 counties: 1,630.2 per 100,000 residents, in our county file. Summit County (799.6) and Pitkin County (745.9) come next. Among counties of more than 100,000 people, Boulder County leads with 250.5; resident counts are Census Bureau estimates (January 2026).

Can I use this EV charging data for free?

Yes. Our own files are CC BY 4.0: use them for anything, with credit to ChargingNear.me. Station facts from the Alternative Fuels Data Center are U.S. public domain.

How do I cite this data?

Each file shows a “Cite as” line with its version and date. Today the highway gap file’s line reads: ChargingNear.me. “U.S. highway charging gaps over 50 miles.” US EV Charging Open Data, version 6, November 5, 2026. https://chargingnear.me/data#us-highway-charging-gaps. CC BY 4.0.

How often is this data updated?

Every file is rebuilt daily from our live database. A file’s version number goes up only when its rows change. The latest build ran on November 6, 2026.

Can AI assistants and apps query this data directly?

Yes. Three read-only endpoints serve the gap, corridor and NEVI files: /api/v1/open-data/charging-gaps, /api/v1/open-data/corridors/{corridor}/chargers (for example /api/v1/open-data/corridors/i-25-ev-charging/chargers, one for each of our 6 Colorado corridors) and /api/v1/open-data/nevi-status. Our MCP server at https://chargingnear.me/api/mcp offers the same as get_charging_gaps, get_corridor_chargers and get_nevi_status, and /data.json is the DCAT-US catalog.

source & further reading
chargingnear.me — original article
── more in #structured-data 4 stories · sorted by recency
── more on @chargingnear.me 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/only-16-of-u-s-fast-…] indexed:0 read:68min 2026-11-06 · —