Fire Department Partially Encrypted

Deer Mountain Fire Department

Fremont, Colorado

How we verified this

DTRS (sid 329), 'Fremont County': Deer Mountain Fire Dispatch and Tac are D Enc. County page 'Deer Mountain Fire Protection District' lists 154.235 FM 'Fire (Cotopaxi, Coaldale)' Fire Dispatch in the clear; which is primary isn't stated. RR name is Fire Protection District. Checked ctid 262/trs. As of October 2026.

Checked against a primary source on 2026-10-14: radioreference.com . Status changes without notice: confirm on the live RadioReference database.

What you can do right now

Encryption Details

Encryption type Algorithm not published
Scope Some talkgroups encrypted; others remain in the clear.

Talkgroup Data Under Review

Our October 2026 audit removed 2 talkgroups because it could not tie them to Deer Mountain Fire Department by RadioReference category (2 naming another agency or town). Those found on RadioReference are filed under Jefferson County (2). Totals and percentages computed from that list are withheld.

2 talkgroups remain, filed under RadioReference category Fremont County:

View 2 talkgroups
DEC Alpha tag Description RadioReference category Status
4435 DeerMtn FD 1 Deer Mountain Fire Dispatch Fremont County Encrypted
4436 DeerMtn FD 2 Deer Mountain Fire Tac Fremont County Encrypted

Current list: RadioReference, Fremont County.

Shared Radio System

This page is one of 6 built from the same underlying radio record: fire department here shares State of Colorado DTRS with 5 other departments in Fremont County; encryption is set per talkgroup, so what a scanner hears can differ from one of those pages to the next.

Fremont County Context

Fremont County is a mixed picture: 5 of 12 agencies we track here are fully encrypted (42%), which means some neighboring departments are still audible on a scanner.

What This Means

Some of this agency's traffic is encrypted and some is not. What you can hear depends on the channel and on what the department is doing at the time.

See encryption status nationwide Interactive map showing which US police departments have encrypted their radios. Open the encryption map →

Frequently Asked Questions

Is Deer Mountain Fire Department radio encrypted?

Only in part — Deer Mountain Fire Department encrypts some of its talkgroups while leaving others open (algorithm not published). Some of this agency's traffic is encrypted and some is not. What you can hear depends on the channel and on what the department is doing at the time.

Can I listen to Deer Mountain Fire Department on a police scanner?

Partially. Deer Mountain Fire Department encrypts some of its talkgroups while leaving others open, so some channels may still be accessible. Check RadioReference for specific talkgroup status.

Why did Deer Mountain Fire Department encrypt their radio?

Departments typically point to officer safety and operational security. Neither claim tends to come with evidence specific to Fremont County; what's verifiable is what's lost — journalists can't monitor the encrypted share of fire department activity in real time, and coordination with agencies that stay unencrypted gets harder.

Can Deer Mountain Fire Department's encryption decision be reversed?

Yes. Encryption is a policy choice made by department leadership or elected officials, not a technical requirement, so it can be reversed the same way. Public pressure, city council advocacy, and organized local coalitions have reversed encryption decisions elsewhere.

What can I do about Deer Mountain Fire Department encryption?

Start local: show up when local officials discuss the budget for Deer Mountain Fire Department, and ask specifically why encryption was chosen over a delayed feed. File a FOIA request for recordings or policy documents, and connect with others nearby who want the same information — a coordinated ask carries more weight than an individual one.

Data source: RadioReference Wiki + checked against RadioReference database

Checked against a primary source on 2026-10-14 — see "How we verified this" above. Encryption status changes; confirm at RadioReference before relying on it.