Hydrohistorian
Log in

← My Water  ·  All reservoirs in this district  ·  Print / save as PDF  · 

 ·  every download of this record carries its certificate id

JASPER RES

Structure dossier · WDID 0604261 · RESERVOIR · JASPER CREEK · DWR record

Jasper Res is a reservoir on Jasper Creek in Colorado. This page is its public record: the water it has a right to, whether it may take it today, and its history, compiled from the Colorado Division of Water Resources.

Source DWR administrative record · verify at DWR structure ↗ Source DWR administrative record · verify at DWR diversion records ↗ Source Our computation, scored against a reference · scored against DWR's call analysis, see /methods

Where this page's figures come from

Generated 2026-10-16 15:33 by Hydrohistorian. Sources: DWR HydroBase snapshot HydroBase_CO_20260928 (history) + CDSS REST (current), USGS NWIS cross-checks. Engine v0.5.0 (c7f5ca1) — every figure regenerates from this named code version and data image.

Who owns it

DWR’s own records name no owner for a ditch, reservoir or well, so this comes from the source shown and can be out of date. Organisations only: a private landowner’s name is never listed.

The record and the river

In short

JASPER RES holds 1 decreed right on JASPER CREEK. A call at BOULDER WELD CTY DITCH on BOULDER CREEK (1862-09-14) currently reaches it: fully called out. 6 further calls state no district and sit outside this one, so they are counted here rather than assumed either way. That is today's position; the weeks ahead cannot be projected for it: this structure is not on the modelled flow network, so no reference gage can honestly stand in for it.

Assembled from the figures on this page — every number above is checked against them before it is shown (3 checked). The detail, with its method, is in the cards below.

Download this structure

Everything on this page as data you can work with — and a README that makes it citable: the HydroBase snapshot it was built from, the build commit, what every column means, the method behind each derived figure, and that method's stated limits.

⇩ Full record (.zip) Print / save as PDF

Or one table at a time: rights.csv · annual_use.csv · curtailment_now.csv · court_cases.csv · co_parties.csv · call_climatology.csv

What is in the bundle
  • rights.csv — every decreed right, most senior first, with admin numbers, dates, amounts, uses and case numbers.
  • annual_use.csv — recorded diversion by year, with releases accounted separately.
  • curtailment_now.csv — each right's current priority status and how often it was out across analog years.
  • court_cases.csv — the cases attached to its rights.
  • co_parties.csv — the other structures that were parties to those cases. Not available anywhere else.
  • call_climatology.csv — how often each right has been out of priority by week of season, with confidence intervals and the seasons the record could actually judge.
  • README.txt — provenance, methods, limits, disclaimer, and links back to DWR's own records for verification.

Where it sits

Location as DWR records it (storage). Faint dots are the neighbouring water; click any to open it.

Dam safety

Dam JASPER (completed 1988)
Hazard class High
Condition at last inspection Satisfactory (2026-06-16)
Storage restriction None on file
Normal storage 325 AF
Physical status Active
Emergency action plan Yes

Source: DWR Dam Safety’s jurisdictional-dam inventory (damsafety/damsafetydaminfojd), refreshed weekly. Joined on this structure’s own WDID as DWR records it on the dam. Hazard class describes the consequence of failure, not the likelihood of it. DWR’s dam record.

Current administration

● Fully called out — call at BOULDER WELD CTY DITCH (BOULDER CREEK, priority 1862-09-14).

Which of its rights are out of priority?

The outlook for the weeks ahead is not computable for this structure: this structure is not on the modelled flow network, so no reference gage can honestly stand in for it. Today’s position is a separate question, and it is answered in Current administration above — that screen reads the district’s active calls and needs no reference gage.

Where it sits in line

Priority 1896-07-25 — 178th most senior of the 1867 structures with decreed rights in this water districtDWR's administrative subdivision of a river basin; the unit calls are usually stated in..

Under prior appropriationColorado's rule for sharing water: first in time, first in right. Age decides, not proximity or need., everything ahead of it in this line is satisfied in full before it receives any water. Immediately ahead: 0604192 (1896-04-01). Immediately behind: 0600581 (1897-03-15).

Decreed rights (1)

Admin noDWR's numeric encoding of a water right's seniority. Smaller is more senior; the integer part counts days from 1849-12-31 to the date that ranks the right. AppropriatedWhen water was first put to beneficial use. It sets seniority unless a prior adjudication date is later. AdjudicatedWhen the water court confirmed the right. A use decreed in 1975 was not a decreed use in 1955, however old the appropriation is. AbsoluteA right actually put to use, as opposed to conditional -- a placeholder for a use not yet made. ConditionalA right reserving a place in line for a use not yet made; it must be diligently pursued or it lapses. Alt-pointAn absolute amount decreed at another structure that may be diverted here instead -- an alternate point of diversion or an exchange. DWR calls this the APEX amount; a right showing 0.0 absolute but an alt-point amount is exercised here under another structure's decree. Decreed forWhat the court said this water may be used for -- irrigation, municipal supply, augmentation and so on.Case
20188.17008 1896-07-251907-03-13 324.4 AF 0.0 — Irrigation, Industrial 84CW0204, CA4842

Amounts marked cfs are flow rates; AF are stored volumes (storage rights are decreed in acre-feet). An absolute amount of 0.0 beside an alt-point amount is not a dead right: the water is decreed at another structure, and that row records permission to divert it here instead (an alternate point or exchange). A case listing several numbers reflects the original decree plus later change cases.

How often is it out of priority?

Across the 11 seasons whose call record is complete enough to judge this structure (2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026), week by week from April.

most senior right · admin 20188.17008 · peaks at 11 of 11 seasons
AprMayJunJulAugSep

Snow sets the clock here. In the driest third of snow years (3 seasons), the call settled in for the season around June 3; in 1 of them it never lifted at all. In the middle third (5 seasons), the call settled in for the season around June 24 (June 17 to July 8 across those years); in 1 of them it never lifted at all. In the wettest third (3 seasons), the call settled in for the season around June 24; in 2 of them it never lifted at all.

Snow years ranked by the district’s April 1 snow-water percentile across 3 SNOTEL sites; 11 seasons carry both a snow reading and a judgeable call record. How the past played out, not a forecast.

Why only 11 seasons, and what the bars mean

Each bar is one week: how many of those seasons that right was out of priority under a call this site can lawfully attribute to this structure. Green is never, red is every season on record.

The short record is a property of DWR's data, not of the river. A call only counts against a structure when we can establish it applies — by the districts named in its set comments, or by stream mile on the same source. DWR did not begin stating affected districts routinely until about 2015: fewer than one call in ten can be judged before then, against roughly two in three since. A season we cannot judge is not a season without calls, so it is dropped rather than counted as quiet — 12 seasons dropped here.

This is a frequency over past seasons, not a forecast. It says nothing about what the division engineer will do this year.

Recorded use (last 9 years on record)

Years far under the decreed amount? That gap has a name — paper water vs. wet water, explained on this structure.

This structure records both diversions and reservoir releases — they are separate water movements and are accounted separately below.

YearDiverted (AFA volume: one acre covered a foot deep, about 326,000 gallons -- roughly a suburban household's outdoor use for a year.)Compared with its own recordReleased (AF)Days recordedPeak (cfs)
2010 — no recorded volume 269 0 —
2012 — no recorded volume 115 0 —
2013 — no recorded volume 244 0 —
2014 — no recorded volume 327 0 —
2015 — no recorded volume 318 0 —
2020 — no recorded volume 251 0 —
2021 — no recorded volume 307 0 —
2024 — no recorded volume 241 0 —
2025 — no recorded volume 409 0 —

How good is our record of it?

Grade B (7/10 points) — the components below are the finding; the letter alone is not.

The rubric, component by component
CheckStateDetail
identity complete name, type, and water source all on file
decreed rights on file 1 right(s), seniority decoded
diversion record present 201 measured days; currency unknown (no data-coverage date to compare against)
record continuity sparse 6% of the irrigation seasons in 2010-2025 carry measured days
published-record stability stable no upstream revisions recorded against this structure

Advisory reading aid on public data — not an administrative or legal conclusion, not a title opinion, and not a substitute for DWR administration or an engineer's analysis. Methodology review status is disclosed at hydrohistorian's basin pages.

Hydrohistorian is free, with no ads — one server and a lot of public records. If it earns its keep, you can help keep it running.