StormProof → hail seasons → Minneapolis–St. Paul → 1998
Minneapolis–St. Paul hail season 1998
33 NWS-recorded hail reports ≥1″ within 35 miles, across 11 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 1998 claim volume.
Biggest storm days (1998, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| May 15, 1998 | 13 | 2.00" | SCOTT, CARVER, DAKOTA, HENNEPIN |
| June 26, 1998 | 6 | 1.75" | DAKOTA, LE SUEUR, SCOTT, ANOKA |
| March 29, 1998 | 5 | 2.00" | DAKOTA, HENNEPIN, ANOKA, WASHINGTON |
| August 9, 1998 | 2 | 1.25" | RAMSEY, HENNEPIN |
| August 22, 1998 | 1 | 1.00" | SCOTT |
“Widespread damage to houses and vehicles by wind driven hail. Damage estimate for entire county.”
— NWS event narrative, May 15, 1998 (NCEI Storm Events)
When it fell
Mar 5 · May 15 · Jun 10 · Aug 3
Wind context: the record also holds 124 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 1998 — relevant where the dispute is wind vs hail causation.
Working a Minneapolis–St. Paul claim from 1998?
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.