StormProof → hail seasons → St. Louis → 2015
St. Louis hail season 2015
19 NWS-recorded hail reports ≥1″ within 35 miles, across 6 storm days, max 3.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2015 claim volume.
Biggest storm days (2015, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| April 7, 2015 | 5 | 1.75" | FRANKLIN, ST. CHARLES, ST. LOUIS |
| April 9, 2015 | 4 | 3.00" | ST. LOUIS, MACOUPIN, JERSEY |
| April 2, 2015 | 4 | 1.00" | JEFFERSON, MONROE, FRANKLIN, ST. LOUIS |
| June 28, 2015 | 3 | 1.50" | ST. LOUIS (C), ST. LOUIS, ST. CHARLES |
| June 25, 2015 | 2 | 1.00" | ST. CLAIR, MADISON |
“A severe thunderstorm moved east across St. Louis County. There were numerous reports of large hail between Chesterfield, Des Peres and Frontenac.”
— NWS event narrative, April 7, 2015 (NCEI Storm Events)
When it fell
Apr 13 · Jun 5 · Jul 1
Wind context: the record also holds 40 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2015 — relevant where the dispute is wind vs hail causation.
Working a St. Louis claim from 2015?
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 St. Louis 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.