LEASES · G-14-185619 · GAS · DISTRICT 10

Tarbox, Waldo

No volume since Jan 2014

4P Energy Texas, LLC · Ochiltree County · Haywood (Atoka) field

Tarbox, Waldo is an RRC gas lease (G-14-185619) in Ochiltree County operated by 4p Energy Texas, LLC, with one well completed on it.

It has reported 120K mcf of gas and 1.8K barrels of condensate since September 2001, last reporting volume in January 2014 (statewide data runs through April 2026).

No volume was reported in the 12 months through April 2026; the last was in January 2014.

4 operators have filed production on it, most recently 4p Energy Texas, LLC since July 2016.

120K
mcf gas, all reported
1.8K
bbl condensate, all reported
0
mcf gas, 12 months through Apr 2026
—
vs the 12 before
1
wells completed on it
—
peak month, bbl

PDQ LEASE REPORTS · FIRST SEP 2001 · LAST VOLUME JAN 2014 · STATEWIDE DATA THROUGH APR 2026

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.

12 months through Apr 2026 0 · prior 12 0

02K4K2002200320042005200620072008200920102011201220132014201520162017201820192020202120222023202420252026

Who reported it

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

  1. Apache CorporationSep 2001 → Oct 2001 · 2 mo
  2. Chesapeake Operating, Inc.Nov 2001 → Oct 2014 · 156 mo
  3. Chesapeake Operating, L.L.C.Nov 2014 → Jun 2016 · 20 mo
  4. 4P Energy Texas, LLCJul 2016 → Feb 2017 · 8 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

Plugged
1

Operates them now

Newest permits

  • — #1—

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/g-14-185619, documented in the API reference.