TEXAS · WELLS · KLEBERG COUNTY · WARDNER, G.P. LEASE · API 42-273-32114 · DISTRICT 04

Wardner G.P. #183

Plugged

Kleberg County · Stratton (Consolidated) field  · Vertical

Wardner G.P. #183 (API 42-273-32114) is a plugged well in Kleberg County, plugged July 19, 2010, last operated by Apache Corporation.

The RRC has issued one drilling permit, issued May 18, 1988, permitted to 10,800 ft.

It was permitted by Union Pacific Resources Company and has since transferred to Apache Corporation on the wellbore schedule.

Completion filings report 2 formation tops, including K-20, K-33.

Operator of record

Apache Corporation

Permitted by Union Pacific Resources Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Dec 3, 2025
Permits on file
9,757
Phone
(713) 954-5500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleApache Corporation
Production reportsApache Corporationthrough Apr 2010
Latest permitUnion Pacific Resources CompanyMay 18, 1988

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

10,800
total depth, ft
1
permits on file
May 18, 1988
last permit issued
Jul 26, 1988
completed
0
cumulative oil, bbl
255K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 26, 1988
Shut in
—
Plugged
Jul 19, 2010

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Wardner, G.P. G-4-129339Stratton (Consolidated)Apache Corporation10255KJan 1993 – Jul 2010

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Union Pacific Resources CompanyJan 1993 → Jan 1999
  2. 2Collins & Ware, Inc.Feb 1999 → Jul 1999
  3. 3Apache CorporationSep 2005 → Apr 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
346671-99DrillUnion Pacific Resources CompanyMay 18, 1988May 18, 1988—10,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 26, 1988Wardner G.P. G-4-129339Stratton (Consolidated)Apache CorporationPlugged—

Formation tops

As filed on W-2/G-1. Subsea from 93 ft elevation.Download CSV →

FormationMD ftSubsea
K-207,808-7,715
K-338,002-7,909

Perforations

Perforated and open-hole intervals.

FromToType
7,8587,888Perforated
7,9107,932Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,33913.5540 S
7.6257,5679.875649 S
2.8758,2476.75175 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Feb 13, 1989Aug 11, 1988Yes
00Jan 7, 1989——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/27332114, documented in the API reference.