Blue River Basin

Source Our computation, no independent reference · computed here from the screened DWR record Source Our computation, no independent reference · no independent reference; see /methods

This year, in context

In the weeks around 2026-09-29 (the newest reading on file), flows at the 12 ranked gages are running at a median 68% of their own long-term norm for this window — 12 below a typical year, 0 at or above. Driest relative to its record: ELLIOTT CREEK FEEDER CANAL TO GREEN MTN RES, CO, ranking 2nd lowest of 24 years.

Gage flow trend & changepoints

Of the 46 gages with enough record, 2 are trending down and 0 up, and 3 carry a detected shift. The clearest is Blue River at Dillon, its annual mean flow changing -7.76 cfs per decade (-7.1% of its median annual flow) over 50 years (p=0.0052). The other 43 show no clear signal either way.

43 other gage(s) show no significant trend or changepoint (not shown).

3 of those show a significant trend once extended backwards from a retired neighbour's record: Blue River near Dillon (116 yr, decreasing); Tenmile Creek Bl North Tenmile Creek, at Frisco (116 yr, decreasing); Blue River below Dillon (106 yr, decreasing). Those are reconstructions, not measurements — each gage's page shows both.

How the measurement network itself changed

This basin was not always measured the way it is today — the API-era record is dense and recent, the early record sparse. 15 gage(s) and 211 structure(s) report in 2026, but structure reporting only reached half its modern level around ~1969. Every historical claim below is checked against this: long-term shifts that co-move with the growth of the network carry an explicit measurement-evolution caution, and abandonment screens whose idleness begins before the modern reporting era are flagged †.

Mass-balance (network closure) trend

Structure divrec-history backfill coverage as of the last check: 12% of 1744 schematic-relevant structures. 0 year(s) clear the 30% coverage gate so far -- the trend activates automatically once qualifying years span a full decade. No action needed; the nightly backfill keeps extending the record.

Reach gain/loss shifts (1950–2026)

Mass-balance kinks computed for every summer month back to 1950 (3195 reach-snapshots) — which reaches gain or lose water, and how that has shifted across decades. Each shift is cross-checked against the observation record above: as more diversions became metered, "unaccounted" water shrinks mechanically, which can masquerade as a hydrologic shift.

• BLUE RIVER BELOW GREEN MOUNTAIN RESERVOIR, CO: reach shifted from +268 cfs to +587 cfs summer mean (more gaining, p=0.043, 77 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
• TENMILE CREEK BELOW WEST TENMILE CREEK, CO: reach shifted from -55 cfs to -48 cfs summer mean (more gaining, p=0.043, 11 yr) [mountain crystalline canyon: minimal groundwater storage -- large or shifting unaccounted losses here are more consistent with data/measurement issues or unmodeled plumbing than with aquifer exchange]
• BLUE RIVER BELOW DILLON, CO.: reach shifted from +207 cfs to -52 cfs summer mean (more losing, p=0.001, 67 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records] [5 alluvial wells within 2 mi of the gage; pooled water table -2.0 ft (1973–2011, no_trend)]
• BOULDER CREEK AT UPPER STATION, NEAR DILLON, CO.: reach shifted from -15 cfs to -5 cfs summer mean (more gaining, p=0.049, 27 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]

Groundwater now has its own tab: 29 monitored well(s), water-table trends, stream corridors, and the advisory depletion screen.

Reservoirs now has its own tab: 64 reservoir(s), end-of-year storage back to 1964, click-to-chart histories.

Cross-gage pattern fingerprint

Over the 69-year window with full coverage (1958–2026), the dominant shared pattern across 4 gage(s) explains 84% of year-to-year variance (almost certainly a basin-wide climate/snowpack driver).

All gages in this window move with the shared pattern -- no localized outlier.

Structures most implicated by reconciliation (as of 2026-09-01)

Which structures' data absorbed the most correction when the current mass-balance snapshot was reconciled -- see the Historical tab for the full picture on any date.

• COUNTRY BOY MINE SPRING (return): +2.3 cfs (14% of that reach's correction)
• BRECKENRIDGE PIPELINE - AP (diversion): +2.3 cfs (14% of that reach's correction)
• BRECKENRIDGE SKI AREA PUMP PLANT & PIPEL (diversion): +2.3 cfs (14% of that reach's correction)
• CHRISTIE HEIGHTS D NO 1 (diversion): +2.3 cfs (14% of that reach's correction)
• ELYRIA DITCH (diversion): +2.3 cfs (14% of that reach's correction)
• ATKINS DITCH (diversion): +2.3 cfs (14% of that reach's correction)
• BRADDOCK DITCH (diversion): +2.3 cfs (14% of that reach's correction)
• TIGER RUN - BLUE RIVER DIVERSION (diversion): +2.1 cfs (25% of that reach's correction)
• GETZ POND (diversion): +2.1 cfs (25% of that reach's correction)
• VER PLOEG SPRING (return): +2.1 cfs (25% of that reach's correction)

Source DWR administrative record · verify at DWR groundwater wells ↗ Source DWR administrative record · verify at DWR well permits ↗

104 water-level measurements across 29 monitored well(s) — 27 alluvial, 0 bedrock — plus 25 administered well(s) reporting metered pumping.

Well map

3D aquifer x-ray

Every aquifer unit as its own head surface, animated through time.

Water-table trends

Of 0 well(s) with enough record for a trend test: 0 declining, 0 rising.

Stream corridors — the surface connection

Where a reach's gain or loss has shifted, the wells within two miles of its anchoring gage and what their water table did over the same era.

TENMILE CREEK BELOW WEST TENMILE CREEK, CO: 0 alluvial well(s) nearby. Glover screen: 0.7 cfs of nearby metered alluvial pumping → est. lagged depletion 0.6–0.7 cfs (uncalibrated T/S ranges; flagged for SPDSS calibration, AWAS cross-check, and expert review — DWR's AWAS is the authority).

BLUE RIVER BELOW DILLON, CO.: 5 alluvial well(s) nearby; pooled water table -2.0 ft (1973–2011, no_trend, p=0.9641)

Wells labeled by administrative world before anything else is said about them: tributary alluvium participates in the priority system; designated-basin and Denver Basin bedrock aquifers are governed differently and are excluded from stream-connection reasoning. Read bedrock declines differently too: deep bedrock aquifers recharge negligibly on human timescales, so a falling bedrock level is storage mining — effectively permanent — not a drought response that a wet year undoes. All screens advisory.

Source DWR administrative record · verify at DWR structure records ↗

64 reservoir(s) with 6,955 storage measurement(s), 1964–2025. Basin storage as of 2024-10-31 (the record's own end — reservoir records publish ~annually): 295,455 AF across 4 reservoir(s).

Reservoir map — how full is each vessel?

Basin storage, end of each water year

End-of-water-year totals; per-year reservoir counts shown because reporting coverage varies -- a total is only comparable to years with similar counts.

Largest reservoirs on record

Click a row to chart its full storage history, or open its dossier for rights, documents and dam-safety facts.

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

Snow-water equivalent, WY2027

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 (1979–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 8 of the last 48 winters the snow never came — the pack peaked below 80% of its median. In 0 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, 1987, 1991, 2002, 2004, 2012, 2021, 2026.

Computed by this site from 6 SNOTEL sites’ full daily records (NRCS AWDB, back to 1979). 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.

Runoff outlook — Dillon Reservoir Inflow

NRCS's final issue (2026-06-01) calls it even odds that at least 25 kAF arrives over 06-01 to 07-31 — 25% of a normal season; almost certainly at least 12, probably not more than 46. Our own record at this gage shows 7 kAF actually delivered. New forecasts begin in January. How to read these numbers →

The record-adjusted April benchmark

NRCS’s April issue (2026-04-01) called even odds at 54 kAF over 04-01 to 07-31. Re-anchoring that number on this river’s own history — how its April issues have verified, the winter’s baseflow, and the district’s April 1 snowpack — moves it to 24 kAF. The river delivered 14 kAF.

Computed by this site — not an NRCS number, and shown only because it earned it: replayed over 58 past seasons here (1974–2025), never seeing the year it predicts, the adjustment cut the typical April miss from 85% to 44%. At points where it does not beat NRCS, no adjusted number appears. Coefficients are frozen each August; the model never changes mid-season. Method and honest limits →

How good are these forecasts here? (1973–2026)

Grading every April issue against what the river then delivered, measured at this gage’s own record — 53 seasons: the median miss of the 50% forecast is 86%, with a high bias of 86%, and the observed volume landed inside the stated 10–90% band 24% of the time (a calibrated forecast would say 80%).

Computed by this site: NRCS's archived April issues (their period as issued each year) against the observed volume in DWR’s published record; years with under 90% daily coverage are dropped, not summed. A grade of the forecast, never of the forecasters — these are hard rivers. How this point ranks among every graded Colorado forecast point →

What April snow has meant for this river (1979–2026)

Across 48 measured years, the season’s water has closely followed the April snowpack: a year opening April with 80% of median snow has typically gone on to deliver about 60% of a normal season (a snow-to-runoff elasticityHow strongly one number moves with another. A snow-to-runoff elasticity of 1.5 means a 10% shortfall in April snowpack has typically become a 15% shortfall in the season's water. of 2.5).

Computed by this site: the district’s April 1 SWE (% of each SNOTEL site’s own-record median) against the observed April–July volume at this gage (% of its median season) — a fixed window every year, unlike the forecast grades above, which use each issue’s own period. The slope is fit so single wild years can’t steer it (Theil–Sen, log space); years missing 10% of their days are dropped.

Runoff outlook — Green Mountain Reservoir Inflow

NRCS's final issue (2026-06-01) calls it even odds that at least 44 kAF arrives over 06-01 to 07-31 — 27% of a normal season; almost certainly at least 25, probably not more than 70. Our own record at this gage shows 56 kAF actually delivered. New forecasts begin in January. How to read these numbers →

The record-adjusted April benchmark

NRCS’s April issue (2026-04-01) called even odds at 98 kAF over 04-01 to 07-31. Re-anchoring that number on this river’s own history — how its April issues have verified, the winter’s baseflow, and the district’s April 1 snowpack — moves it to 39 kAF. The river delivered 85 kAF.

Computed by this site — not an NRCS number, and shown only because it earned it: replayed over 63 past seasons here (1962–2025), never seeing the year it predicts, the adjustment cut the typical April miss from 91% to 39%. At points where it does not beat NRCS, no adjusted number appears. Coefficients are frozen each August; the model never changes mid-season. Method and honest limits →

How good are these forecasts here? (1950–2026)

Grading every April issue against what the river then delivered, measured at this gage’s own record — 76 seasons: the median miss of the 50% forecast is 73%, with a high bias of 73%, and the observed volume landed inside the stated 10–90% band 12% of the time (a calibrated forecast would say 80%).

Computed by this site: NRCS's archived April issues (their period as issued each year) against the observed volume in DWR’s published record; years with under 90% daily coverage are dropped, not summed. A grade of the forecast, never of the forecasters — these are hard rivers. How this point ranks among every graded Colorado forecast point →

What April snow has meant for this river (1979–2026)

Across 48 measured years, the season’s water has closely followed the April snowpack: a year opening April with 80% of median snow has typically gone on to deliver about 49% of a normal season (a snow-to-runoff elasticityHow strongly one number moves with another. A snow-to-runoff elasticity of 1.5 means a 10% shortfall in April snowpack has typically become a 15% shortfall in the season's water. of 2.3).

Computed by this site: the district’s April 1 SWE (% of each SNOTEL site’s own-record median) against the observed April–July volume at this gage (% of its median season) — a fixed window every year, unlike the forecast grades above, which use each issue’s own period. The slope is fit so single wild years can’t steer it (Theil–Sen, log space); years missing 10% of their days are dropped.

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 9th-driest week 39 in 89 years of record at BLUE RIVER BELOW GREEN MOUNTAIN RESERVOIR, CO (as of 2026-09-21; this week’s flow sits at the 10th 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, Summit County is 88% in D4 exceptional drought (2026-10-13). The law agrees: the most senior active call leaves 0% of this district’s decreed flow rights junior to the calling right this week.

Every year since 1937, week by week

Each thin row is a year at BLUE RIVER BELOW GREEN MOUNTAIN RESERVOIR, 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 39 weeks recorded so far, 2026’s weekly trace most resembles 2002 (mean gap 15.2 percentile points; next closest 1991 (17.9), 1964 (18.7)). 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 Grand, Summit counties — 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.

The law’s own drought gauge

When water runs short, administration answers: calls reach further back in time, and more decreed rights go junior to the calling right. This is that response, weekly since 2002 — the share of this district’s decreed flow rights junior to the most senior active call. Watch it spike in the named droughts below, and linger after the river recovers.

Computed from DWR’s call record (137 calls touching this district) against the district’s rights index. Scoping is deliberately coarse — a call’s own district, or districts named in its comments — and this is administration’s RESPONSE, not a per-structure verdict (each dossier’s curtailment card does that, with stream miles). A deepening call can also reflect growing demand, not only shrinking supply.

This basin’s droughts, by its own record

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.

When this basin claimed its water

Every bar is a year’s new appropriations (1,696 rights across 90 years of shared record), colored by that year’s wetness from the barcode above. Here the correlation is +0.09 — 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.

The water itself, in this district

Four registers, each on its own schedule: what USGS sensors read right now, where samples have been taken, which stretches the state lists as impaired, and how the tap water of the systems here stands with EPA. None is a DWR record; each links its own page.

Right now

Source Provisional telemetry · fetched 2026-10-16 · verify at USGS current conditions ↗

2 USGS sensors report temperature, conductance, dissolved oxygen or turbidity from inside this district; provisional readings, never merged into the verified record.

Where water has been sampled

Source Register of another agency · fetched 2026-10-08 · verify at Water Quality Portal ↗

The portal lists 835 sampling stations in this district's watershed (Blue 14010002), of which 57 reported a sample in the last 5 years on the state and tribal side (USGS activity is in the station count, not in that figure). Most active: Colorado Dept. of Public Health & Environment-WQCD (46), Colorado River Watch (8), USGS Colorado Water Science Center (3). Most-sampled groups: Nutrient, Physical, Inorganics, Major, Metals, Inorganics, Minor, Non-metals. Every station as a file ↗

Results themselves are not fetched here; USGS samples added after March 2024 may not be in the portal's legacy profiles yet.

Drinking water

Source Register of another agency · fetched 2026-10-07 · verify at EPA SDWIS ↗

19 community systems touch this district. None carries an open health-based violation on EPA's record. EPA sampled 5 of them for PFAS in 2023–25; 1 had PFOA or PFOS at or above the 2024 limit.

and 9 more; the full directory filters by district.

EPA's record carries violations and lead/copper percentiles; nitrate and disinfection by-product results are not in it. UCMR 5 samples are monitoring, not compliance, and the 2024 PFOA/PFOS limits equal its reporting limit, so any detection of those two is at or above them.

Impaired waters

Source Register of another agency · verify at EPA ATTAINS ↗

The state's 303(d) impaired-waters list has not been joined to this basin's own watershed boundary yet, so nothing is shown rather than a guess; the basins with a join carry the full list here. Why the join is geometry, not a name match.