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