TEXAS · WELLS · KLEBERG COUNTY · KING RANCH BORREGOS LEASE · API 42-273-31488 · DISTRICT 04

King Ranch Borregos #557

Plugged

Kleberg County · Borregos (Consolidated Gas) field  · Vertical

King Ranch Borregos #557 (API 42-273-31488) is a plugged well in Kleberg County, plugged June 9, 2026, last operated by Eog Resources Inc..

The RRC has issued one drilling permit, issued July 28, 1980, permitted to 7,300 ft.

It was permitted by Exxon Corp. and has since transferred to Eog Resources Inc. on the wellbore schedule.

Operator of record

EOG Resources Inc.

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Oct 2, 2025
Permits on file
16,354
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Jan 2015
Latest permitExxon Corp.Jul 28, 1980

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

7,300
total depth, ft
1
permits on file
Jul 28, 1980
last permit issued
Jun 24, 1999
completed
0
cumulative oil, bbl
524K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 24, 1999
Shut in
—
Plugged
Jun 9, 2026

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
King Ranch Borregos G-4-91152Borregos (Zone N-25)EOG Resources, Inc.10524KJan 1993 – Jul 2026

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. 1Exxon Corp.Jan 1993 → Mar 2000
  2. 2Exxon Mobil CorporationApr 2000 → Dec 2012
  3. 3EOG Resources, Inc.Jan 2013 → Jan 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
87890-99DrillExxon Corp.Jul 28, 1980Jul 28, 1980Aug 15, 19807,300

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 24, 1999King Ranch Borregos G-4-91152Borregos (Consolidated Gas)EOG Resources Inc.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
5,8385,848Perforated
5,8685,888Perforated
5,8985,904Perforated
5,9825,994Perforated
6,2236,240Perforated
6,2716,275Perforated
6,2716,291Perforated
6,2816,285Perforated
6,2896,291Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,532—685 S
5.56,1867.875325 S
5.56,186—325 S
2.8756,8884.75210 S
2.8756,8894.75210 S
2.8756,889—210 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
00Jul 26, 1999Jul 6, 1999—
00Jan 20, 1998Jan 5, 1998—
00Apr 4, 1996Feb 1, 1996—
00Jan 12, 1984Dec 5, 1980—

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