WELL · 42-473-31099 · DISTRICT 3

Weido #13

Y

Waller County · Brookshire field · Shut IN  · Vertical

Weido #13 (API 42-473-31099) is a well in Waller County operated by 84 Energy LLC, completed March 30, 2007 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued March 15, 2007, permitted to 3,500 ft.

It was permitted by Gen-Nan Resources & Equip., L.P. and has since transferred to 84 Energy LLC on the wellbore schedule.

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

Operator of record

84 Energy LLC

Permitted by Gen-Nan Resources & Equip., L.P.; the EWA schedule now lists a different operator.

Sugar Land, TX · P-5 Y, filed Oct 4, 2025 · 1 permits on file · (832) 653-9480

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedule84 Energy LLC
Production reports84 Energy LLCthrough Mar 2023
Latest permitGen-Nan Resources & Equip., L.P.Mar 15, 2007

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

3,500
total depth, ft
1
permits on file
Mar 15, 2007
last permit issued
Mar 30, 2007
completed
80.4K
cumulative oil, bbl
42.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 30, 2007
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
Weido O-3-23787Brookshire84 Energy LLC580.4K42.9KJan 2000 – 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. 1Gen-Nan Resources & Equip., Inc.Feb 2000 → Dec 2002
  2. 2Gen-Nan Resources & Equip., L.P.Jan 2003 → Jan 2008
  3. 3Layline Petroleum I, LLCFeb 2008 → May 2013
  4. 4Wapiti Operating, LLCJun 2013 → Mar 2015
  5. 5Clearly Petroleum, LLCApr 2015 → Apr 2020
  6. 6GTG Operating, LLCJun 2020 → Aug 2022
  7. 784 Energy LLCSep 2022 → Mar 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
634937-99DrillGen-Nan Resources & Equip., L.P.Mar 9, 2007Mar 15, 2007Mar 27, 20073,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-23787————

Perforations

Perforated and open-hole intervals.

FromToType
2,4202,426Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62560012.25225 S
5.52,7507.875386 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
00Oct 4, 2007Aug 9, 2007Yes
00Sep 27, 2007——

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