Reader-supported. GopherTrunk is free, open-source software. Some
hardware links on this page go to Amazon with our Associates tag
(gophertrunk-20); if you buy through them we may earn a small
commission at no extra cost to you. Links to out-of-production gear may go to
eBay searches instead; we have no affiliate relationship with eBay and earn
nothing there. It never changes which gear we recommend, and
the software stays free either way. How GopherTrunk is funded →
Gunshots or Fireworks? How to Tell — and How to Find Out
By ear alone, even experienced listeners routinely get this wrong — echo, distance, and buildings smear the differences. The reliable answer isn’t in the sound; it’s in what happens next: whether a “shots heard” call goes out, and what the responding officers actually find. Here’s the honest acoustic guidance, and then the part nobody tells you — how to hear the outcome.
Key takeaways Lean gunfire: uniform sharp cracks, irregular deliberate rhythm, no whistle/crackle, nothing visible. Lean fireworks: varied bangs, whistles, crackles, clusters, flashes above rooflines. Unsure and concerned? Call 911 — that’s a legitimate call. The real answer: the “shots heard” dispatch and the officers’ findings, live on a scanner feed or your own scanner within minutes.
The by-ear checklist (and its limits)
Lean gunfire when the bangs are sharp, uniform cracks — the same sound repeated — in an irregular or deliberate rhythm, with no whistle, no crackle, and nothing lighting up the sky. Lean fireworks when reports vary shot-to-shot, whistle on the way up or crackle after, arrive in celebratory clusters, or pair with flashes above the rooflines.
Now the honest part: urban echo makes single distant fireworks sound sharp, and gunfire around a holiday hides inside the fireworks baseline. Cities deploy acoustic sensor networks (ShotSpotter) precisely because human ears — including trained ones — misclassify these sounds constantly. Treat the checklist as a lean, not a verdict.
What to do in the moment
If you suspect gunfire: stay inside, away from windows, and call 911 with what you heard, how many, and the direction. “Shots heard” is one of the most common calls dispatchers take; a fireworks false alarm costs nothing, a missed shooting costs a lot. Don’t go outside to investigate, and don’t post to Nextdoor instead of calling.
Finding out what it actually was
This is where the radio settles it. Within a few minutes of any 911 calls:
- The dispatch goes out — “shots heard, [your block]” — on the police channel, audible on a county scanner feed or your own receiver.
- The outcome follows — officers report “fireworks confirmed,” “unable to locate,” or evidence found. That closing traffic is the answer no app gives you.
- The CAD log shows the call type and disposition slightly later; the methods in police activity near me and what happened last night apply here too.
- Silence on the radio usually means nobody reported it at all — which is itself useful to know when you were the only one awake at 1 a.m.
One caveat: in cities that have encrypted police dispatch, the radio route is closed — check RadioReference for your agency, and lean on the CAD log instead.
If it was close: two checklists
What 911 actually needs from you (worth rehearsing once):
- How many bangs, over how many seconds, and the spacing (even/irregular).
- Direction and rough distance — “northeast, a block or two” beats “outside.”
- Anything paired with it: vehicles accelerating, voices, breaking glass.
- Whether you saw anything — muzzle flash low to the ground vs fireworks overhead settles it instantly for the call-taker.
If you think your home or car may have been struck: don’t touch or dig anything out — an impact mark and the round behind it are evidence. Photograph it, note the time of the bangs, and report it even a day later; a documented strike changes how the original call is classified and patrolled. And if a window or wall was hit while you were home, report immediately, not in the morning.
Why this question, more than any other, sells scanners
“Was that gunshots?” is the 1 a.m. question — exactly when nobody’s posting, no news is coming, and you want an answer before deciding whether to go back to sleep. A scanner on the nightstand shelf answers it in real time, every time. The kit below is the always-on version: it hears the call go out, and its recordings mean that even if you slept through the radio traffic, the answer is waiting for you in the morning.
The fix for next time: a scanner that never sleeps, for about $250
Every lookup method on this page depends on someone else — a feed volunteer, an app's coverage map, an agency webmaster. This kit removes the middleman: a silent little box on a shelf that decodes your county's digital dispatch directly off the air, streams it to any browser in the house, and records every call with timestamps. Next time the sirens go past, the answer is already on your phone — and free, open-source GopherTrunk is the software, so the parts below are the entire cost.
Why two receivers: one dongle stays locked to your police trunked system while the second covers fire/EMS or a neighboring system at the same time — the two channels a "what's going on?" moment actually needs. That's a trick a $500 handheld scanner can't do, and GopherTrunk drives both dongles from one Orange Pi.
Orange Pi 5
around $90
The RK3588 host that runs it all 24/7 — silent, low-power, and strong enough for both dongles with headroom to spare. GopherTrunk ships a native ARM64 Linux build for it.
Orange Pi 5 on Amazon →RTL-SDR Blog V4 kit
around $55
The dongle and the telescopic dipole antenna kit with coax and mounts in one box — this one holds your police system's control channel.
V4 + antenna kit on Amazon →RTL-SDR Blog V4 (second dongle)
around $35
Covers fire/EMS, a second trunked system, airband, or NOAA weather — simultaneously, not by giving up the first channel.
RTL-SDR V4 on Amazon →The complete parts list
| Part | Why it's in the kit | Approx $ | |
|---|---|---|---|
| Orange Pi 5 | Always-on host for both dongles | ~$90 | Amazon → |
| RTL-SDR Blog V4 + dipole antenna kit | Receiver #1, antennas, coax, mounts | ~$55 | Amazon → |
| RTL-SDR Blog V4 (second) | Receiver #2 — fire/EMS or a second system | ~$35 | Amazon → |
| Powered USB 3.0 hub | Clean, stable power for two warm dongles | ~$35 | Amazon → |
| 16-piece SMA adapter kit | Joins any antenna to any dongle, first try | ~$18 | Amazon → |
| RG316 SMA pigtail kit | Flexible jumpers between hub, dongles, antennas | ~$15 | Amazon → |
| USB-C power supply (5V/4A+) | The Orange Pi 5 needs solid power for 24/7 duty | ~$15 | Amazon → |
| microSD card (64GB, A2) | OS plus months of recorded calls | ~$12 | Amazon → |
Kit total: about $250–275. Worthwhile upgrade once it's earned a permanent shelf: an outdoor discone antenna (~$40) that hears everything from 25–3000 MHz — see the antenna guide. Prefer a Raspberry Pi 5 host instead? Same build, swap the board — Pi 5 (8GB) on Amazon and the SBC build guide.
From boxes to first decoded call
- Flash 64-bit Linux (Debian/Ubuntu image) to the microSD and boot the Orange Pi headless.
- Plug in the powered hub, both dongles, and the antennas — the adapter kit bridges any connector mismatch.
- Install GopherTrunk — one free static binary, no dependencies: download, then follow the setup guide to point it at your county's system from RadioReference.
- Open the web console from any phone or laptop in the house — live calls, talkgroup names, and a scrollable, replayable recording archive.
Two honest caveats before you spend a dime: check RadioReference that your agencies are not encrypted — no device decodes AES — and skim the legality rules for your state (listening is legal in the US; a few states restrict use in vehicles). Rather have a no-computer, pocketable option instead? That's the dedicated scanner guide.
Frequently asked questions
How can I tell gunshots from fireworks?
Rules of thumb, not guarantees: gunfire tends to be a sharp, uniform crack in a deliberate or irregular rhythm with no whistle and nothing visible; fireworks tend to vary shot-to-shot, often whistle or crackle, come in celebratory clusters, and may flash above rooflines. Echo off buildings blurs all of it — even experienced ears get it wrong, which is why acoustic gunshot-detection systems exist.
Should I call 911 if I'm not sure it was gunshots?
If you genuinely suspect gunfire — especially with screaming, screeching tires, or rapid strings — yes, call 911 and report what you heard and the direction; dispatchers triage ‘shots heard’ calls constantly and would rather take a fireworks false alarm than miss a shooting. Stay inside and away from windows while you do.
How do I find out if the bangs I heard were reported?
A live scanner feed answers within a couple of minutes: listen for a ‘shots fired’ or ‘shots heard’ call in your area and what responding officers find — very often ‘unable to locate’ or ‘fireworks confirmed.’ The agency’s active-calls page will show the same call type slightly delayed. Nothing dispatched usually means nobody reported it.
Police found nothing — does that mean it was fireworks?
Not necessarily; ‘gone on arrival’ is a common outcome for real gunfire too. But the dispatch traffic still tells you what officers observed — casings found, property struck, or nothing at all — which is far more information than a silent Nextdoor thread. Persistent problems are worth reporting to the non-emergency line so patterns get patrol attention.
What is ShotSpotter and does my city have it?
ShotSpotter (SoundThinking) is an acoustic sensor network some cities deploy to locate gunfire and dispatch police automatically — often before anyone calls 911. Coverage is limited to specific neighborhoods in subscribed cities, and alerts go to police, not the public; where it exists, you’ll hear its dispatches on the radio traffic.
Why does my neighborhood hear so many fireworks at random times?
Outside holiday weeks, sporadic single fireworks are usually leftover stock, celebrations, or teenagers; around New Year’s and July 4th the baseline is so high that genuine gunfire hides in it — the worst time to judge by ear and the best time to judge by what actually gets dispatched.