June 18, 2025 hail storm near Dagmar, MT. Radar-confirmed hail track and contractor lead lists available.
NWS WARNING AREA · Dagmar Metro · Jun 18, 2025
Intelligence Platform
StormSnipe Pro
Cancel anytime · No contracts
Pro renews monthly until canceled · Cancel anytime in the billing portal
What's included
Instant delivery
Every storm published within hours of NOAA confirmation.
Interactive Strike Map
Full radar-confirmed hail track on an interactive map.
Address CSV export
Every affected residential address, export-ready.
Smart alerts
Notified when a storm hits your area. Set zones once.
Nationwide coverage
All 50 states. No zone restrictions. No geographic caps.
Live pipeline
NOAA NEXRAD processed and delivered 24/7.
Address data notice
Pro coverage in California, Vermont, and Oregon includes the confirmed hail track and Strike Map only — no address lists. State data-privacy law treats compiled address lists differently in those three states, so we exclude their addresses from extraction and delivery.
This storm generated 7 NWS alert zones. Pro access covers the complete storm track and all addresses across every zone.
Dagmar, MT
55 addresses in warning area
Alert issued Wed, Jun 18 · 9:25 PM UTC
Grenora, ND
431 addresses in warning area
Alert issued Wed, Jun 18 · 9:36 PM UTC
Zahl, ND
4,901 addresses in warning area
Alert issued Wed, Jun 18 · 10:28 PM UTC
Linton, ND
804 addresses in warning area
Alert issued Wed, Jun 18 · 11:18 PM UTC
Kenmare, ND
198 addresses in warning area
Alert issued Wed, Jun 18 · 11:49 PM UTC
Almont, ND
844 addresses in warning area
Alert issued Thu, Jun 19 · 12:51 AM UTC
Newburg, ND
74 addresses in warning area
Alert issued Thu, Jun 19 · 1:11 AM UTC
A severe hail storm crossed Dagmar, MT, on June 18, 2025, with verified 1-inch hail and a later spotter report of 0.75-inch stones in the same event. The storm reached its peak in the mid-afternoon.
The National Weather Service issued a severe thunderstorm warning at 3:25 PM MDT with radar and spotter-verified confidence for 1-inch hail. A field report followed at 3:35 PM MDT, described as a Facebook report and logged as spotter-verified at 0.75 inch. The sequence points to a short-lived hail core that produced measurable stone size before easing.
The storm remained focused on the Dagmar area. The warning area covered the broader path, while the ground reports narrowed the impact to the local community. Radar and spotter input aligned closely on timing and size. The report trail stayed compact, with no extended run of escalating hail reports after the first verified event.
The field reports show a hail event that was strong enough to put verified stones on the ground in Dagmar, but not broad enough in the public reports to suggest a wide damage field. The 3:35 PM MDT observer note of 0.75-inch hail came just 10 minutes after the warning and sits below the storm’s verified peak, which points to a smaller but still notable hail swath through the area.
For surface impact, the evidence is limited to the hail reports themselves. There were no additional ground-truth notes in the available reports tied to tree damage, roof loss, siding impact, or vehicle damage. That leaves the event defined by hail size confirmation rather than a longer list of documented losses.
The timing matters for crews reviewing call volume and property claims in Dagmar. The verified report arrived in the same 10-minute window as the warning, which often means the first hail bursts reached the ground quickly after warning issuance. The local report also suggests the hail core remained intact long enough for a spotter to note it from the community, not just on radar.
For contractors, the main point is narrow but useful: a single verified hail event in Dagmar can still produce scattered roof, vent, and soft-metal issues even when the public report set is thin. The absence of extensive damage notes does not remove the need to check the usual impact points on older roofs, metal trim, and exposed vehicles.
Dagmar sits in a small, rural market. That changes the work pattern. A short hail event can translate into scattered claims rather than a large cluster, so crews should expect isolated addresses instead of a dense suburban run. The warning area was broader than the ground report footprint, so route planning should stay anchored to the verified local report rather than the full polygon.
The 3:25 PM MDT warning and 3:35 PM MDT field report put the hail window squarely in the afternoon. That means inspection calls may come in after the storm passes, not during it. Roof checks should focus on bruised shingles, granule loss on softer slopes, and impact marks on vents, gutters, and windowsills. On outbuildings, look at lightweight panels, edge metal, and any south- or west-facing exposure that took the first blast of the hail core.
See exactly what you get.
Explore the full Springdale, AR Strike Map free – hail track, address overlay, and CSV download. No account required.
Try the Free Demo →Vehicle and farm equipment checks should stay on the list. In a place like Dagmar, parked assets often sit outside the same way from one storm to the next, which leaves repeat impact patterns on hoods, mirrors, and cab glass. The reported stone size was enough to justify that inspection even without a long damage log.
The strongest signal here is not volume. It is the clean match between the warning, the spotter-verified report, and the local hail size. Crews working this event should treat the day as a targeted hail response in and around Dagmar, not a broad-area catastrophe run.
See the Strike Map for precise hail track data in Dagmar, MT.
Address data is sourced from the US National Address Database (NOAA/USDOT). Inclusion of an address does not guarantee physical damage occurred. Confidence scores are radar-derived estimates. Data Accuracy Disclaimer