WELL · 42-235-34593 · DISTRICT 7

Williams G #1

N

Irion County · Wildcat field  · Vertical

Williams G #1 (API 42-235-34593) is a well in Irion County operated by Petrodata Resources Inc., completed November 21, 2010.

The RRC has issued 2 drilling permits between 2010 and 2012, permitted to 6,000 ft.

Completion filings report 4 formation tops, including San Angelo, Clearafork, Clear Fork, Wolfcamp.

Its 2 leases have reported 1.59K barrels of oil and 163K mcf of gas since November 2010, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Petrodata Resources Inc.

Midland, TX · P-5 Y, filed Oct 4, 2019 · 20 permits on file · (432) 687-2910

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetrodata Resources Inc.
Production reportsTHP Operating LLCthrough Apr 2026
Latest permitPetrodata Resources, Inc.May 19, 2012

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

6,000
total depth, ft
2
permits on file
May 19, 2012
last permit issued
Nov 21, 2010
completed
1.59K
cumulative oil, bbl
163K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 21, 2010
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Williams 'G' O-9-17768Tankersley (5200)THP Operating LLC11.59K163KJun 2011 – Jul 2026
Williams "G" O-9-17464WildcatPetrodata Resources, Inc.100Nov 2010 – Apr 2013

Oil, barrels lease total

Last 12 months 7 · prior 12 5(+40%)

01202420252026

Chain of custody

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

  1. 1Petrodata Resources, Inc.Jun 2011 → Jun 2019
  2. 2THP Operating LLCAug 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
738770-99RecompletionPetrodata Resources, Inc.Apr 20, 2012May 19, 2012Nov 12, 20105,830
703303-99DrillPetrodata Resources, Inc.Oct 5, 2010Oct 14, 2010Nov 12, 20106,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-17464————
—— O-9-17768————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
San Angelo835
Clearafork4,055
Clear Fork4,055
Wolfcamp4,935

Perforations

Perforated and open-hole intervals.

FromToType
5,2105,250Perforated
5,5655,575Perforated
5,6125,622Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62551311225 S
5.55,8137.875705 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
00Mar 20, 2013May 22, 2012—
00Mar 26, 2012Apr 26, 2011Yes

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) and the University Lands library. 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/23534593, documented in the API reference.