StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsRichmond → 2024

Richmond hail season 2024

13 NWS-recorded hail reports ≥1″ within 25 miles, across 4 storm days, max 2.40". Every one of those reports is a dated, located, citable official record — the context behind this market's 2024 claim volume.

Biggest storm days (2024, final record)

Date≥1″ reportsMax hailAreas named in the record
August 18, 202492.00"HENRICO
April 15, 202421.00"NEW KENT, POWHATAN
June 30, 202411.00"HENRICO
May 26, 202412.40"HENRICO

“A trained spotter reported three solar pathway lights damaged from hail with a fourth destroyed, window screen damage to a home, and hail dents in vehicles including an SUV with six dents on the top. Hail was estimated to be the size of ice cubes and lasted for around seven minutes.”

— NWS event narrative, August 18, 2024 (NCEI Storm Events)

When it fell

Apr 2 · May 1 · Jun 1 · Aug 9

Wind context: the record also holds 54 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2024 — relevant where the dispute is wind vs hail causation.

Working a Richmond claim from 2024?

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 25 miles of the Richmond 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.