WELL · 42-487-32097 · DISTRICT 9

Guggisburg #4

Y

Wilbarger County · Wilbarger County Regular field  · Vertical

Guggisburg #4 (API 42-487-32097) is a well in Wilbarger County operated by Thunderbird Operating L.L.C., completed April 14, 1988.

The RRC has issued one drilling permit, issued April 6, 1988, permitted to 3,400 ft.

It was permitted by Kingdom Resources Corporation and has since transferred to Thunderbird Operating L.L.C. on the wellbore schedule.

Its lease has reported 60.1K barrels of oil and 57 mcf of gas since January 1993, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Thunderbird Operating L.L.C.

Permitted by Kingdom Resources Corporation; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed May 4, 2026 · 3 permits on file · (940) 521-1016

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleThunderbird Operating L.L.C.
Production reportsThunderbird Operating, L.L.C.through Apr 2026
Latest permitKingdom Resources CorporationApr 6, 1988

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

3,400
total depth, ft
1
permits on file
Apr 6, 1988
last permit issued
Apr 14, 1988
completed
60.1K
cumulative oil, bbl
57
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 14, 1988
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Guggisburg O-13-26992Wilbarger County RegularThunderbird Operating, L.L.C.560.1K57Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 290 · prior 12 314(-8%)

0204060202420252026

Chain of custody

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

  1. 1Kingdom Resources CorporationJan 1993 → Sep 1993
  2. 2Kodiak Petroleum Corp. of Okla.Oct 1993 → Dec 1994
  3. 3Canyon Petroleum CorporationJan 1995 → Jan 2000
  4. 4AK Operating Co.Nov 1997 → Dec 1999
  5. 5Thunderbird Operating, L.L.C.Oct 2005 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
344854-99DrillKingdom Resources CorporationApr 6, 1988Apr 6, 1988—3,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-26992————

Perforations

Perforated and open-hole intervals.

FromToType
2,0052,010Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62510010.37550 S
4.52,1717.875320 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
00May 17, 1988Apr 20, 1988Yes
00May 10, 1988——

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