StormProof → hail seasons → Greensboro–Winston-Salem → 2015
Greensboro–Winston-Salem hail season 2015
10 NWS-recorded hail reports ≥1″ within 30 miles, across 4 storm days, max 1.25". 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 20, 2015 | 6 | 1.25" | RANDOLPH, FORSYTH, GUILFORD, ROCKINGHAM |
| September 4, 2015 | 2 | 1.00" | DAVIDSON, STOKES |
| July 13, 2015 | 1 | 1.25" | RANDOLPH |
| June 26, 2015 | 1 | 1.00" | RANDOLPH |
“Hail the size of quarters to half dollars was reported along a swath from several miles southwest of Winston Salem to a couple miles northwest of Sedge Garden.”
— NWS event narrative, April 20, 2015 (NCEI Storm Events)
When it fell
Apr 6 · Jun 1 · Jul 1 · Sep 2
Wind context: the record also holds 63 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 Greensboro–Winston-Salem 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 30 miles of the Greensboro–Winston-Salem 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.