GOLDKING PROD. CO · TRINITY COUNTY

Goldking Prod. Co in Trinity County

One operator, one county: its permits, wells of record, formations, and leases here, with the rest of the county and the rest of the operator one click away.

Goldking Prod. Co has 7 drilling permits on file in Trinity County, the first issued in 1980 and the latest on December 14, 1994.

None were issued in the last twelve months.

It is operator of record on 4 wells in the county: 0 producing, 0 shut in, 0 injection.

Its completed wells here most often report Sparta, Queen City, Carrizo.

0
permits, 12 months
7
permits, all time since 1980
—
horizontal, 12 months
—
ft average depth, 12 months
4
wells of record
0
producing · 0 shut in · 0 injection

Latest permits here

IssuedLease / wellTypeDepth
Dec 14, 1994Gaston, M. H. #2 430910Drill2,000
Oct 25, 1994McLane #1 428529Drill2,000
Nov 1, 1991Walton/Koonce #2 393511Recompletion1,748
Nov 1, 1991Walton/Koonce #2 393511Recompletion1,748
Sep 28, 1990Walton/Koonce #2 378542Drill1,950
Aug 21, 1990Temple-Inland #1A 376598Recompletion1,215
Jan 11, 1989Kee/Fondren #1 355098Drill1,200
Oct 18, 1988Pam/Temple-Eastex #1A 352432Drill1,850
Mar 3, 1988Pam Petroleum/Bounds #1 343449Drill1,800
Dec 17, 1984Usnma 19754 #1 261662Drill8,800

All 7 permits in Trinity County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 7

12 MONTHS / ALL TIME

Formations reported

Leases it reports here

LeaseWellsOil, bblLast reported
Bounds10Aug 1996
Kee/Fondren10Aug 1996
Temple-Inland10Aug 1996
Temple-Inland10Aug 1996
Simms10Jul 1994
Walton/Koonce10Jul 1994

All leases it reports → ·  Other operators in Trinity County →

About this data

Permits from the RRC OGA049M master and daily daf420 files; wells of record and status from the EWA wellbore schedule, weekly; formations from the dbf900 wellbore file; leases from PDQ lease reports, placed in the county by the wells completed on them.

Developers: this page as JSON is GET /v1/data/operators/tx/313165/counties/trinity, documented in the API reference.