TEXAS · WELLS · MARTIN COUNTY · HOLT RANCH NORTH LEASE · API 42-317-39211 · DISTRICT 7B

Holt Ranch North #1504

Shut in

Martin County · Spraberry (Trend Area) field · Shut In  · Vertical

Holt Ranch North #1504 (API 42-317-39211) is a well in Martin County operated by Ovintiv USA Inc., completed June 10, 2014 and listed as shut in on the RRC schedule, shut in April 1, 2024.

The RRC has issued one drilling permit, issued March 10, 2014, permitted to 12,078 ft.

It was permitted by Athlon Holdings LP and has since transferred to Ovintiv USA Inc. on the wellbore schedule.

Completion filings report 10 formation tops, including Yates, Grayburg, San Andres, Spraberry.

Its lease has reported 2.97M barrels of oil and 9.31M mcf of gas since December 2000, last reporting volume in April 2026. The lease carries 37 wells, so these are lease totals, not this well alone.

Operator of record

Ovintiv USA Inc.

Permitted by Athlon Holdings LP; the EWA schedule now lists a different operator.

Based in
Denver, CO
P-5 status
Active (A)
P-5 last filed
Dec 12, 2025
Permits on file
1,391
Phone
(720) 876-5176

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOvintiv USA Inc.
Production reportsOvintiv USA Inc.through Apr 2026
Latest permitAthlon Holdings LPMar 10, 2014

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

12,078
total depth, ft
1
permits on file
Mar 10, 2014
last permit issued
Jun 10, 2014
completed
2.97M
cumulative oil, bbl
9.31M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2000 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 10, 2014
Shut in
Apr 1, 2024
Plugged
—

Operator's P-5 on the schedule: Active (A)

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Holt Ranch North O-10-36524Spraberry (Trend Area)Ovintiv USA Inc.372.97M9.31MDec 2000 – Apr 2026

Gas, mcf lease total

Last 12 months 354,570 · prior 12 254,068(+40%)

050K100K202420252026

Oil, barrels lease total

Last 12 months 43,926 · prior 12 40,577(+8%)

05K10K202420252026

Chain of custody

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

  1. 1Arco PermianDec 2000 → Dec 2001
  2. 2BP America Production CompanyJan 2002 → Jun 2003
  3. 3OXY USA WTP LPJul 2003 → Jul 2003
  4. 4Forest Oil CorporationAug 2003 → Dec 2009
  5. 5Sandridge Expl. and Prod., LLCJan 2010 → Sep 2010
  6. 6Athlon Energy Operating LLCOct 2010 → Dec 2013
  7. 7Athlon Holdings LPJan 2014 → Jan 2015
  8. 8Encana Oil & Gas(usa) Inc.Feb 2015 → Jan 2020
  9. 9Ovintiv USA Inc.Feb 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
777761-99DrillAthlon Holdings LPJan 21, 2014Mar 10, 2014Apr 25, 201412,300

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 10, 2014Holt Ranch North O-10-36524Spraberry (Trend Area)Ovintiv USA Inc.Shut In · shut in Apr 1, 202412,078

Formation tops

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

FormationMD ftSubsea
Yates2,978-74
Grayburg4,493-1,589
San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H4,977-2,073
Spraberry8,226-5,322
Dean9,552-6,648
Wolfcamp9,757-6,853
Cisco——
Pennsylvanian——
Queen——
Santa Rosa——

Perforations

Perforated and open-hole intervals.

FromToType
8,21010,961Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37540617.5450 S
8.6255,31011620 S
5.512,0787.875900 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
00Aug 28, 2014Aug 4, 2014Yes

Well logs

1 log loaded from the RRC's log index, 1 of it with a digital LAS file, the latest received May 3, 2017. Gamma ray. 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
Gamma RaySpans San Andres, Spraberry, Dean, WolfcampLAS + TIFF5,450 to 12,028May 3, 20170.77 + 16.1

"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. The University Lands library has no per-well link: then paste it into its 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/31739211, documented in the API reference.