LEASES · O-13-29374 · OIL · DISTRICT 09
Pipkin #2
No volume since Apr 2016American Operating Company (A) · Montague County · Eanes (Caddo) field
Pipkin #2 is an RRC oil lease (O-13-29374) in Montague County operated by American Operating Company (A), with one well completed on it.
It has reported 4.16K barrels of oil and 91 mcf of gas since June 1997, last reporting volume in April 2016 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in April 2016.
6 operators have filed production on it, most recently American Operating Company (A) since January 2018.
- 4.16K
- bbl oil, all reported
- 91
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- 178
- peak month, bbl (Apr 2003)
PDQ LEASE REPORTS · FIRST JUN 1997 · LAST VOLUME APR 2016 · 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
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
Who reported it
Each run of months one operator filed the production report, oldest first.
- Rocking, R, Drilling & Prod Co.Jun 1997 → Sep 2013 · 196 mo
- Big Rock Oil LLCOct 2013 → Oct 2014 · 13 mo
- MSM EnergyNov 2014 → May 2016 · 19 mo
- Harvest Petroleum Inc.Jun 2016 → Jan 2017 · 8 mo
- Innovo Resources Group, Inc.Feb 2017 → Dec 2017 · 11 mo
- American Operating Company (A)Jan 2018 → Jul 2026 · 103 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
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-13-29374, documented in the API reference.