Natural hazards · Lynn

Lynn, ND natural hazards

Most of the natural-hazard damage FEMA expects in Lynn comes from cold waves, and overall the risk is low for a U.S. community.

FEMA National Risk Index, December 2025 · OpenFEMA claims, aid & declarations
Expected damage

How exposed is Lynn?

36
Low
vs. U.S. communities

FEMA expects yearly storm and flood damage to homes and buildings in Lynn to be higher than in 36% of U.S. communities, mostly from cold waves and inland flooding.

Cold waves57%Inland flooding15%Hail9%Tornadoes6%Everything else12%
By hazard

What Lynn faces

Each hazard’s share of the damage FEMA expects here, and how that compares with the rest of the country.

Cold waves

57% of expected damage
Above average · higher than 69% of U.S. places
Recorded about 21 times a year in the area

Inland flooding

15% of expected damage
Well below average · higher than 23% of U.S. places
Recorded about once every 2 years in the area

Hail

9% of expected damage
Well above average · higher than 96% of U.S. places
Recorded about 2 times a year in the area

Tornadoes

6% of expected damage
Above average · higher than 73% of U.S. places
Recorded about once every 2 years in the area

Lower here

Ice stormsWinter weatherHeat wavesWildfireEarthquakesLandslidesStrong windLightningDrought

Not a risk here

Coastal floodingHurricanesAvalanchesTsunamisVolcanic activity
Flood risk changes street by street. Check a specific address on FEMA’s flood map, and ask about flood insurance before you buy.
Flood insurance claims

Does Lynn flood?

FEMA's records show no paid flood insurance claims in Lynn.

Disasters that hit Lynn

Federal disasters declared here

None of the disasters declared for Wells County shows FEMA aid or repair money reaching Lynn itself in FEMA’s records.

Brought FEMA money into LynnDeclared for Wells County only
Wells County has had 25 natural disasters declared since 1953, most often floods and severe storms.
Around Lynn

Lynn and the towns around it

Silver Lake: Low, mostly cold wavesBull Moose: Low, mostly cold wavesMauch: Very low, mostly hailStewart: High, mostly cold wavesChaseley: Low, mostly cold wavesProgress: Low, mostly cold wavesCrystal Lake: Low, mostly cold wavesSperry/Goodrich: Very low, mostly hailHazel Grove: High, mostly inland floodingNorthwest: High, mostly cold wavesAtwood: High, mostly cold wavesMerkel: High, mostly cold wavesLynn: Low, mostly cold waves LynnSilver LakeBull MooseMauchStewart
Very lowLowModerateHighVery high
Stewartmostly cold wavesHigh
Lynnmostly cold wavesLow
Silver Lakemostly cold wavesLow
Bull Moosemostly cold wavesLow
Mauchmostly hailVery low
About these numbers

How to read this page

An average, not a forecastFEMA’s National Risk Index estimates the damage 18 kinds of natural hazards cause in a typical year, from decades of records and models. A quiet decade can follow a bad year.
Compared by rate“Higher than N%” compares yearly damage as a share of what’s here, so a big city isn’t rated riskier just for having more buildings. Lynn is smaller than a census tract, so it shares the figures of the tract around its center.
Money that reached townFlood claims are matched to Lynn’s own flood-insurance community; household aid to the registrant’s city; repair grants to the Township of Lynn. FEMA’s model follows property values, so a place that recently lost many homes can rate lower than it feels.

Sources: FEMA National Risk Index (December 2025); OpenFEMA: NFIP redacted claims, multiple-loss properties, community status book and residential penetration rates, housing assistance (owners and renters), public assistance funded projects, hazard mitigation properties and disaster declarations. Census tracts: U.S. Census Bureau.

You’re browsing

Lynn

North Dakota · ND · Wells County
View town boundary →
Township / city / CDP overlaps possible.
Loading boundary…

Lynn is your selected town. The feed includes posts assigned to this town, not a distance radius or ZIP code.

Neighborhoods narrow the feed further, while townwide announcements, events, and issues remain visible.

Boundary source: https://tigerweb.geo.census.gov/arcgis/rest/services/TIGERweb/Places_CouSub_ConCity_SubMCD/MapServer/15 · 2025-01-01