WELL · 42-105-33618 · DISTRICT 7

University 2 B #7G

Plugged

Crockett County · Farmer (San Andres) field  · Vertical

University 2 B #7G (API 42-105-33618) is a plugged well in Crockett County, plugged September 9, 2003, last operated by R2q Operating LLC.

The RRC has issued one drilling permit, issued August 25, 1981, permitted to 2,750 ft.

It was permitted by Wilson Energy, Inc. and has since transferred to R2q Operating LLC on the wellbore schedule.

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

Operator of record

R2Q Operating LLC

Permitted by Wilson Energy, Inc.; the EWA schedule now lists a different operator.

Based in
Iowa Park, TX
P-5 status
Active – Extension (X)
P-5 last filed
Sep 12, 2025
Permits on file
38
Phone
(940) 228-1500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExtex Operating Company
Production reportsExtex Operating Companythrough Nov 2023
Latest permitWilson Energy, Inc.Aug 25, 1981

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

2,750
total depth, ft
1
permits on file
Aug 25, 1981
last permit issued
Jan 11, 1982
completed
39.6K
cumulative oil, bbl
108K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 11, 1982
Shut in
—
Plugged
Sep 9, 2003

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 12 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
University 2 "B" O-9-8641Farmer (San Andres)Extex Operating Company1239.6K108KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 0 · prior 12 0

0102030202420252026

Chain of custody

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

  1. 1JMW Resources, Inc.Jan 1993 → Aug 1998
  2. 2Larron Energy CorporationSep 1998 → May 2006
  3. 3Legacy Reserves Operating LPJun 2006 → Oct 2019
  4. 4Extex Operating CompanyOct 2021 → Nov 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
131023-99DrillWilson Energy, Inc.Aug 25, 1981Aug 25, 1981Dec 21, 19812,750

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 11, 1982University 2 B O-9-8641Farmer (San Andres)R2Q Operating LLCPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
2,1932,296Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62584411450 S
2.3752,108——
4.52,7507.875300 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
00Jan 12, 1984Jan 21, 1982—

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