TEXAS · WELLS · DIMMIT COUNTY · API 42-127-33693 · DISTRICT 01

Diamond H Ranch #2H

Y

Dimmit County · Briscoe Ranch (Eagleford) field · Producing  · Horizontal

Diamond H Ranch #2H (API 42-127-33693) is a horizontal well in Dimmit County operated by Javelin Energy Partners Mgmt LLC, completed February 1, 2023 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued May 26, 2010, permitted to 7,502 ft.

It was permitted by Anadarko E&P Onshore LLC and has since transferred to Javelin Energy Partners Mgmt LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Olmos, San Miguel, Eagle Ford.

Its 2 leases have reported 7.27M barrels of oil and 16.1M mcf of gas since June 2010, last reporting volume in April 2026. The leases carry 46 wells, so these are lease totals, not this well alone.

Operator of record

Javelin Energy Partners Mgmt LLC

Permitted by Anadarko E&P Onshore LLC; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 24, 2026
Permits on file
234
Phone
(469) 575-3800

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJavelin Energy Partners Mgmt LLC
Production reportsJavelin Energy Partners Mgmt LLCthrough Apr 2026
Latest permitAnadarko E&P Onshore LLCMay 26, 2010

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

7,502
total depth, ft
2
permits on file
May 26, 2010
last permit issued
Feb 1, 2023
completed
7.27M
cumulative oil, bbl
16.1M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2010 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 1, 2023
Shut in
—
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 2 leases this well is completed on; they carry 46 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Diamond H Ranch G-1-267618Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLC1110K313KMay 2012 – Apr 2026
Diamond H Ranch O-1-15205Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLC457.16M15.8MJun 2010 – Apr 2026

Oil, barrels lease total

Last 12 months 483,836 · prior 12 745,684(-35%)

050K100K202420252026

Gas, mcf lease total

Last 12 months 1,874,192 · prior 12 2,124,025(-12%)

0100K200K300K202420252026

Chain of custody

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

  1. 1Anadarko E&P Company LPJun 2010 → Dec 2012
  2. 2Anadarko E&P Onshore LLCJan 2013 → Feb 2017
  3. 3SN EF Maverick, LLCMar 2017 → Aug 2023
  4. 4Javelin Energy Partners Mgmt LLCSep 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
696542-98DrillAnadarko E&P Onshore LLCMay 15, 2013May 26, 2010Aug 14, 20108,500
696542-99DrillAnadarko E&P Company LPMay 25, 2010May 26, 2010Aug 14, 20108,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 1, 2023Diamond H Ranch G-1-267618Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLCProducing7,502
Feb 2, 2011Diamond H Ranch O-1-15205Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Olmos4,755-4,254
San Miguel5,419-4,918
Eagle FordEAGLEFORD7,337-6,836

Perforations

Perforated and open-hole intervals.

FromToType
8,04413,268Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,00012.251,385 S
5.513,3708.752,150 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
00Apr 27, 2023Apr 17, 2023—
00Jun 11, 2013Jun 28, 2012—
00May 9, 2013——
00Sep 15, 2011Mar 1, 2011—
00May 17, 2011Nov 18, 2010Yes

Well logs

1 log loaded from the RRC's log index, the latest received Sep 10, 2013. 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
RESISTIVITYSpans San Miguel, Eagle FordTIFF6,675 to 13,301Sep 10, 2013run Aug 25, 20103.81

"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.

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