StormProof → hail seasons → Cheyenne → 2018
Cheyenne hail season 2018
63 NWS-recorded hail reports ≥1″ within 25 miles, across 17 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2018 claim volume.
Biggest storm days (2018, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| July 29, 2018 | 14 | 2.00" | LARIMER, LARAMIE |
| August 6, 2018 | 13 | 2.00" | LARIMER, LARAMIE |
| July 25, 2018 | 5 | 1.50" | LARAMIE |
| July 26, 2018 | 4 | 1.75" | LARAMIE |
| June 15, 2018 | 4 | 1.00" | LARAMIE |
“Golf ball size hail was observed at Dell Range Boulevard and Green Mountain Road. Numerous windows and sky lights were broken and siding and trees stripped in the Saddleridge and Dakota Crossing subdivisions.”
— NWS event narrative, July 29, 2018 (NCEI Storm Events)
When it fell
May 4 · Jun 13 · Jul 27 · Aug 19
Wind context: the record also holds 9 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2018 — relevant where the dispute is wind vs hail causation.
Working a Cheyenne claim from 2018?
These are aggregates. A claim file needs the per-address record: every recorded event within 1, 3 and 10 miles of the property, distances, official narratives, and citations an adjuster can check line by line. That's the report — generated in seconds, hosted on HailEvidence (the neutral evidence surface), formatted as an insurance-appeal attachment.
Unlimited reports — Pro $99/mo Single report $29
Provenance
Final counts: NCEI Storm Events Database, file vintage c20260527, hail events with recorded magnitude ≥1.00″ and point coordinates within 25 miles of the Cheyenne anchor. NWS records are point and path observations. The absence of a nearby report does NOT prove that no hail fell at this address — it means no observation was logged nearby. A report of nearby hail documents the event; it does not by itself prove damage to a specific structure. Spotted an error? Email the address on our terms page and we correct against the source.