TEXAS · WELLS · COCHRAN COUNTY · MAGNUM LEVELLAND UNIT LEASE · API 42-079-32910 · DISTRICT 7B

Magnum Levelland Unit #6

Plugged

Cochran County · Levelland field  · Vertical

Magnum Levelland Unit #6 (API 42-079-32910) is a plugged well in Cochran County, plugged November 20, 2024, last operated by Extex Operating Company.

The RRC has issued one drilling permit, issued September 11, 1997, permitted to 5,100 ft.

It was permitted by Gruy Petroleum Management CO. and has since transferred to Extex Operating Company on the wellbore schedule.

Completion filings report one formation top, including Strawn.

Its lease has reported 183K barrels of oil and 652K mcf of gas since March 1998, last reporting volume in April 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

Extex Operating Company

Permitted by Gruy Petroleum Management Co.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Jan 7, 2026
Permits on file
117
Phone
(713) 953-0824

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExtex Operating Company
Production reportsExtex Operating Companythrough Apr 2026
Latest permitGruy Petroleum Management Co.Sep 11, 1997

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

5,100
total depth, ft
1
permits on file
Sep 11, 1997
last permit issued
Nov 14, 1997
completed
183K
cumulative oil, bbl
652K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 1998 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 14, 1997
Shut in
—
Plugged
Nov 20, 2024

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Magnum Levelland Unit O-11-67887LevellandExtex Operating Company16183K652KMar 1998 – Apr 2026

Oil, barrels lease total

Last 12 months 2,474 · prior 12 2,787(-11%)

0200400202420252026

Chain of custody

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

  1. 1Gruy Petroleum Management Co.Mar 1998 → Apr 2006
  2. 2Cimarex Energy Co. of ColoradoMay 2006 → Nov 2006
  3. 3Quantum Resources Management,llcDec 2006 → Dec 2014
  4. 4Breitburn Operating L.P.Jan 2015 → Dec 2018
  5. 5Extex Operating CompanyJan 2019 → Apr 2026
  6. 6New Horizon Resources LLCJan 2022 → Sep 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
467082-99DrillGruy Petroleum Management Co.Sep 3, 1997Sep 11, 1997Oct 15, 19975,100

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 14, 1997Magnum Levelland Unit O-11-67887LevellandExtex Operating CompanyPlugged—

Formation tops

As filed on W-2/G-1. Subsea from 3,813 ft elevation.Download CSV →

FormationMD ftSubsea
Strawn4,800-987

Perforations

Perforated and open-hole intervals.

FromToType
4,8004,980Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62542512.25350 S
5.55,0257.8751,710 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Sep 10, 2003Jul 28, 2003Yes
00Aug 18, 2003——

Well logs

2 logs loaded from the RRC's log index, the latest received Jul 20, 2006. Density, Gamma ray, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Neutron/Density PorosityPLATFORM EXPRESS THREE DETECTOR DENSITY COMPENSATED NEUTRON/GRSpans StrawnTIFF200 to 5,010Jul 20, 2006run Oct 22, 1987—
ResistivityPLATFORM EXPRESS AZIMUTHAL LATEROLOG MCFL/GAMMA RAYSpans StrawnTIFF4,000 to 5,010Jul 20, 2006run Oct 22, 1987—

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

1.37K
bbl, last 12 reported months
484K
bbl, all reported
Feb 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000087003H-1 InjectionPlugged May 12, 20251,5002,2004,750–5,050

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 1,369 · prior 12 2,193(-38%)

010020030020242025

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