StormProof → hail seasons → Minneapolis–St. Paul → 2017
Minneapolis–St. Paul hail season 2017
41 NWS-recorded hail reports ≥1″ within 35 miles, across 4 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2017 claim volume.
Biggest storm days (2017, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| June 11, 2017 | 22 | 2.00" | SCOTT, HENNEPIN, RAMSEY, WASHINGTON |
| July 9, 2017 | 13 | 1.50" | DAKOTA, SCOTT, RAMSEY |
| May 16, 2017 | 5 | 1.75" | DAKOTA, WASHINGTON, RAMSEY, ANOKA |
| July 25, 2017 | 1 | 1.75" | HENNEPIN |
When it fell
May 5 · Jun 22 · Jul 14
Wind context: the record also holds 50 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2017 — relevant where the dispute is wind vs hail causation.
Working a Minneapolis–St. Paul claim from 2017?
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 35 miles of the Minneapolis–St. Paul 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.