StormProof → hail seasons → Minneapolis–St. Paul → 2023
Minneapolis–St. Paul hail season 2023
74 NWS-recorded hail reports ≥1″ within 35 miles, across 8 storm days, max 3.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2023 claim volume.
Biggest storm days (2023, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| August 11, 2023 | 43 | 3.00" | WASHINGTON, DAKOTA, HENNEPIN, RAMSEY |
| July 24, 2023 | 9 | 1.75" | DAKOTA, ST. CROIX, ANOKA |
| July 10, 2023 | 7 | 1.50" | DAKOTA, SCOTT, ST. CROIX |
| July 3, 2023 | 6 | 1.75" | DAKOTA |
| October 24, 2023 | 3 | 1.00" | SCOTT, HENNEPIN |
“A picture was shared on social media of hail next to a baseball. The hail was slightly smaller than the baseball.”
— NWS event narrative, August 11, 2023 (NCEI Storm Events)
When it fell
Jul 28 · Aug 43 · Oct 3
Wind context: the record also holds 30 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2023 — relevant where the dispute is wind vs hail causation.
Working a Minneapolis–St. Paul claim from 2023?
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.