RogataEvery bill, laid before the people.

HB26-1200 · Bill · 2026 Regular Session · Colorado

Armed Services Member Motor Vehicle Taxes & Fees

Concerning required payments upon registration of a vehicle for a member of the United States armed forces serving outside the state.

Official status: Became Law

1 proposed amendment

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

Colorado law exempts the owner of a motor vehicle who is a member of the United States armed forces (member) from motor vehicle registration fees and sets the specific ownership tax at $1 while the member is serving outside the United States. This applies to personal motor vehicles and intrastate trucks, truck tractors, trailers, and semitrailers used to transport property. To qualify, the member must show the military order or evidence acceptable to the department of revenue (department) demonstrating that the member served outside the United States. The act repeals a requirement that the member sign an affidavit to qualify for the $1 specific ownership fee or to be exempt from the motor vehicle fee. Colorado law exempts members from paying late fees for failing to renew a registration for a vehicle if the member was serving outside the state when the registration period expired. The act sets the requirement to qualify for a late fee exception by requiring the member to show the military order or evidence acceptable to the department demonstrating that the member served outside of the state. The department will notify the member that the vehicle or motor vehicle must not be driven during deployment. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1200, oldest first
DateLocationAction
02/11/2026HouseIntroduced In House - Assigned to Finance
03/05/2026HouseHouse Committee on Finance Refer Unamended to House Committee of the Whole
03/10/2026HouseHouse Second Reading Laid Over Daily - No Amendments
03/11/2026HouseHouse Second Reading Special Order - Passed with Amendments - Floor
03/12/2026HouseHouse Third Reading Passed - No Amendments
03/17/2026SenateIntroduced In Senate - Assigned to Finance
03/24/2026SenateSenate Committee on Finance Refer Unamended to Senate Committee of the Whole
03/27/2026SenateSenate Second Reading Passed - No Amendments
03/30/2026SenateSenate Third Reading Passed - No Amendments
04/16/2026HouseSigned by the Speaker of the House
04/16/2026SenateSigned by the President of the Senate
04/16/2026GovernorSent to the Governor
04/20/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (1 proposed amendment)

Amendments proposed to HB26-1200, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.005
Sponsor: Representative Garcia Sander		Floor amendment — Second Reading (House)03/11/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

View HB26-1200 on leg.colorado.gov

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

254c9b7acf5273df5992cdd6471a5dc0f1f0c63900b3d0609f3b5ba3d75c258a

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-11-06 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.