LEASES · O-1-7558 · OIL · DISTRICT 01

Deagen, Bill & Sons Ltd -C-

No volume since Jun 1994

Deagen, Bill & Sons, Ltd. · Wilson County · Kaye (Navarro) field

Deagen, Bill & Sons Ltd -C- is an RRC oil lease (O-1-7558) in Wilson County operated by Deagen, Bill & Sons, Ltd., with one well completed on it.

It has reported 40 barrels of oil and 6 mcf of gas since January 1993, last reporting volume in June 1994 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in June 1994.

2 operators have filed production on it, most recently Deagen, Bill & Sons, Ltd. since January 2005.

40
bbl oil, all reported
6
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
1
wells completed on it
10
peak month, bbl (Feb 1994)

PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME JUN 1994 · STATEWIDE DATA THROUGH APR 2026

Oil by month

Barrels reported on Form PR for the whole lease. The latest months are revised upward as late reports arrive.

Last 12 months 0 · prior 12 0

011996199719981999200020012002200320042005

Gas by month

Gas-well gas plus casinghead gas, mcf. On an oil lease all gas is reported as casinghead. The latest months are revised upward as late reports arrive.

Last 12 months 0 · prior 12 0

011996199719981999200020012002200320042005

Who reported it

Each run of months one operator filed the production report, oldest first.

  1. Deagen, Bill & SonsJan 1993 → Dec 2004 · 144 mo
  2. Deagen, Bill & Sons, Ltd.Jan 2005 → Dec 2005 · 12 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

NO Type on File
1

Operates them now

Newest permits

All 1 wells, searchable →

About this data

Monthly oil, gas, and casinghead from the RRC PDQ production dump, which lags the reporting month by two to three months; figures shown through Apr 2026. Wells from completion reports; operator runs from who filed each month's report.

Developers: this page as JSON is GET /v1/data/leases/tx/o-1-7558, documented in the API reference.