← All basins

Laramie River

Division 1 · Water District 48 · As of 2026-09-24 05:17 MDT · 4 weeks ago

Who may take water from the Laramie River, who is calling for it today, and how it is running, compiled from Colorado Division of Water Resources records. Click anything on the map for its record.

Live · machine-built

Laramie River on the ground — the ditches, wells, reservoirs and gages of Water District 48 · clicktap anything for its record

Browse this district’s ditches, gages, reservoirs, wells and springs as a list.

22% of normal flow, week of 2026-09-21
0 calls the record places on it, 4 unsettled

The Laramie River is critically low for late September -- 22% of normal flow. No call that the record places on it is active right now. DWR's statements do not settle whether 4 more calls reach it.

Snow and runoff

Source Independent agency measurement · fetched 2026-10-21 · verify at NRCS report generator ↗ Source Our computation, scored against a reference · NRCS forecast, graded here against the gage record

Snow-water equivalent, WY2027

SNOTEL siteElev (ft)SWE (in)Median (in)% of medianTypical peak
Joe Wright10140 0.20.3 — May 5 (24.0 in)
Roach9710 0.10.5 — April 25 (17.5 in)

NRCS SNOTEL, daily. Sites are assigned to the district whose boundary contains them — the snow that feeds this district can also sit in a neighboring headwater district.

Two ways a snow year goes wrong (1980–2026)

A bad snow year here comes in two flavors (both called snow droughtA winter that shorts the snowpack. It happens two ways: a dry one, where the snow never comes, and a warm one, where near-normal snow falls but melts off weeks early -- and the river feels them differently.), and the river feels them differently. In 4 of the last 47 winters the snow never came — the pack peaked below 80% of its median. In 2 more, the snow came but left early — a near-normal peak melted out two weeks or more ahead of its usual date, sending the water down before the season needed it.

The snow never came: 1981, 2002, 2012, 2026. The snow left early: 1987, 1989.

Computed by this site from 2 SNOTEL sites’ full daily records (NRCS AWDB, back to 1980). Each year is measured against each site’s own multi-decade median — not the 1991–2020 normal the chart above uses — so the 1980s grade against a fair baseline. Peak and melt-out need 85% of the season’s days on the record; thin years are dropped, not guessed. Derived from snow measurements alone — it cannot tell dry-from-warm causes apart, only what the snowpack did.

Drought

Source Our computation, no independent reference · computed here from the screened DWR record Source Independent agency measurement · fetched 2026-10-13 · verify at U.S. Drought Monitor ↗

Right now

This is the 23rd-driest week 39 in 103 years of record at LARAMIE RIVER NEAR GLENDEVEY, CO. (as of 2026-09-21; this week’s flow sits at the 22nd percentileRank against the record: a river at its 5th percentile is lower than it was in 95 of the past 100 years on this same date. for the date). On this week’s US Drought Monitor, Larimer County is 26% in D4 exceptional drought (2026-10-13).

Every year since 1904, week by week

Each thin row is a year at LARAMIE RIVER NEAR GLENDEVEY, CO.; each cell is one week’s flow ranked against the same calendar week of every other year — warm means dry for the date, blue wet, so seasonality cancels and droughts appear as warm bands. Gaps are missing record, never a dry river. Click a year to reconstruct it on the Historical tab.

This year against its analogs

Over the 29 weeks recorded so far, 2026’s weekly trace most resembles 2002 (mean gap 8.8 percentile points; next closest 1966 (15.0), 1931 (15.4)). The analog’s remainder is drawn as context — its ending is what happened to it, not a forecast for this year.

The Drought Monitor’s view since 2000

Mean share of area in each class across Larimer county — the counties this district’s gages sit in, which overlap the district imperfectly. The Drought Monitor weighs soils, vegetation and local reports; it is CONTEXT beside the river’s own record above, not the water-rights picture.

This basin’s droughts, by its own record

DroughtSpanWeeks Trough percentileFlows recovered Water table back
the 2018 drought 2019-02-04 → 2019-09-02 30 4th (2019-04-22) 0 weeks —
the 2018 drought 2017-12-25 → 2018-09-17 38 4th (2018-04-02) 1 week —
unnamed dry spell 2015-12-07 → 2017-09-04 91 4th (2016-06-06) 4 weeks —
unnamed dry spell 2015-02-23 → 2015-08-17 25 4th (2015-04-20) 111 weeks —
the 2012-13 drought 2014-02-10 → 2014-08-18 27 4th (2014-03-31) 0 weeks —
the 2012-13 drought 2012-10-29 → 2013-10-07 49 4th (2013-04-29) 0 weeks —
the 2002 drought 2001-08-27 → 2003-09-08 106 5th (2002-10-28) 0 weeks —
the 1981 drought 1981-07-27 → 1982-01-25 26 22nd (1981-09-28) 2 weeks —
the 1977 drought 1977-03-07 → 1978-03-06 52 13th (1977-10-31) 4 weeks —
unnamed dry spell 1966-09-26 → 1967-03-06 23 21st (1966-11-14) 18 weeks —
the 1950s drought 1954-09-06 → 1955-02-14 23 24th (1954-11-15) 40 weeks —
unnamed dry spell 1943-12-06 → 1944-09-25 42 20th (1944-06-26) 45 weeks —
unnamed dry spell 1942-05-11 → 1943-03-29 46 24th (1942-05-18) 4 weeks —
the 1930s Dust Bowl drought 1939-09-25 → 1940-09-02 49 14th (1939-12-18) 5 weeks —

Detected mechanically: the 26-week smoothed percentile below the 30th for at least 20 weeks; recovered on regaining the 50th. The water-table clock compares each monitoring well against its own pre-drought median (the 3 years before onset) and dates the year the median well got back — the aquifer remembers longest, and “still below” is a finding, not a gap. The knobs are stated because the episode list depends on them — a different reasonable choice merges or splits episodes at the edges. Names are attached where an episode overlaps a drought Colorado already talks about.

What drought has cost here

Since 1991, federal crop insurance has paid $194,432 in drought-caused claims across Larimer county — 0.8% of all insured crop losses there. The worst year was 2017 ($39,168).

USDA crop-insurance indemnities where the recorded cause of loss is drought, summed over the counties this district's gages sit in. Counties overlap water districts imperfectly, and insured-crop claims are a floor on drought damage, not a total. Source: USDA RMA cause-of-loss files.

When this basin claimed its water

Every bar is a year’s new appropriations (62 rights across 107 years of shared record), colored by that year’s wetness from the barcode above. Here the correlation is +0.02 — essentially no wet-dry pattern; here, law and settlement set the pace, not the weather. Across the state both behaviors exist: ephemeral southwest basins file after wet demonstrations, transbasin-source basins under drought — and the biggest statewide filing waves sat in the 1950s drought and after 2002, not in the wet 1980s–90s.

Appropriation dates are the CLAIMED initiation of a right, not the courthouse filing date; the record is survivor-biased (abandoned claims are absent, so failed dry-era scrambles are undercounted); and the big 1960s and 2000s spikes sit on legal events — the pre-1969-Act adjudication era and 2000s legislation — not on weather. A correlation here is a description, never a cause.

New to how a dry winter becomes a call on the river? Anatomy of a drought walks the chain in four minutes — snow to rivers to reservoirs to calls to the water table.

Snowpack — 2 SNOTEL sites report here. Full snow & runoff picture — charts, forecast history and how the forecasts have verified →

Sites, exceedance bands and sources
SNOTEL siteElev (ft)SWE (in)Median (in)% of medianTypical peak
Joe Wright10140 0.20.3 — May 5 (24.0 in)
Roach9710 0.10.5 — April 25 (17.5 in)

Snow-water equivalent and medians (1991–2020) from NRCS SNOTEL; seasonal volume forecasts from the NRCS National Water and Climate Center. Sites and forecast points are assigned to the district whose boundary contains them — snowpack that feeds this district can also sit in a neighboring headwater district. Toggle the Snow chip on the map above to see the sites.

Topology cross-check: 0 parent disagreements, 10 sizable streams not on this network (vs DWR's route framework — under review)

This flow network was built mechanically; DWR's Source Water Route Framework disagrees with it in the places below. Each row is a question a human reviewer has not yet answered — not an error verdict. Checked 8 streams, 8 agree. Know this water? Tell us →

Sizable streams DWR maps here that this network does not carry:

Stuck Creek (12 mi) · Nunn Creek (11 mi) · Jimmy Creek (10 mi) · La Garde Creek (9 mi) · Stub Creek (7 mi) · Link Creek (6 mi) · Porter Creek (5 mi) · Drink Creek (4 mi)

Something wrong on this page? Tell us →