WELL · 42-197-31290 · DISTRICT 9

Tabor H.J. #2

N

Hardeman County · Tabor (Chappell) field  · Directional

Tabor H.J. #2 (API 42-197-31290) is a well in Hardeman County operated by Corda Corporation, completed July 18, 1995.

The RRC has issued 2 drilling permits (amended once) between 1994 and 2003, permitted to 8,095 ft.

Completion filings report 6 formation tops, including Conglomerate, Barnett, Chester, Meramec Shale.

Its 2 leases have reported 244K barrels of oil and 67.5K mcf of gas since July 1995, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Corda Corporation

Wichita Falls, TX · P-5 Y, filed Sep 4, 2025 · 104 permits on file · (940) 733-1172

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCorda Corporation
Production reportsCorda Corporationthrough Apr 2026
Latest permitCorda CorporationAug 19, 2003
8,095
total depth, ft
3
permits on file
Aug 19, 2003
last permit issued
Jul 18, 1995
completed
244K
cumulative oil, bbl
67.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 1995 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 18, 1995
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Tabor, H. J. O-13-30214Tabor (Conglomerate)Corda Corporation144.8K30.2KJul 2003 – Jul 2026
Tabor, H.J. O-13-29004Tabor (Chappell)Corda Corporation1199K37.2KJul 1995 – Feb 2004

Oil, barrels lease total

Last 12 months 319 · prior 12 187(+71%)

0204060202420252026

Chain of custody

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

  1. 1Corda CorporationJul 1995 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
534980-99RecompletionCorda CorporationAug 5, 2003Aug 19, 2003Jul 9, 20038,095
424142-97DrillCorda CorporationJul 14, 1995Sep 9, 1994Feb 11, 19958,095
424142-99DrillKimbell Oil Company of TexasJun 2, 1994Sep 9, 1994—8,085

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-29004————
—— O-13-30214————

Formation tops

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

FormationMD ftSubsea
Conglomerate7,432-5,982
BarnettBARNETT SHALE7,865-6,415
Chester7,912-6,462
Meramec Shale7,958-6,508
Meramec Lime8,012-6,562
Chappel8,032-6,582

Perforations

Perforated and open-hole intervals.

FromToType
7,4327,451Perforated
8,0788,088Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62546312.25250 S
4.58,0787.875285 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
00Nov 26, 2003Aug 4, 2003Yes
00Nov 13, 2003Jul 24, 1995Yes
00Sep 20, 1995Jul 24, 1995Yes
00Aug 4, 1995——

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