WELL · 42-255-33017 · DISTRICT 2

Manka Unit #5H

Y

Karnes County · Eagleville (Eagle Ford-2) field · Producing  · Horizontal

Manka Unit #5H (API 42-255-33017) is a horizontal well in Karnes County operated by Murphy Expl. & Prod. CO. - USA, completed July 10, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 11, 2013, permitted to 11,278 ft.

Completion filings report 3 formation tops, including Olmos, Undifferentiated Chalk, Eagle Ford.

Its lease has reported 1.72M barrels of oil and 1.95M mcf of gas since February 2013, last reporting in July 2026. The lease carries 6 wells, so these are lease totals, not this well alone.

Operator of record

Murphy Expl. & Prod. Co. - USA

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 15, 2026
Permits on file
1,458
Phone
(281) 675-9000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMurphy Expl. & Prod. Co. - USA
Production reportsMurphy Expl. & Prod. Co. - USAthrough Apr 2026
Latest permitMurphy Expl. & Prod. Co. - USAFeb 11, 2013
11,278
total depth, ft
1
permits on file
Feb 11, 2013
last permit issued
Jul 10, 2013
completed
1.72M
cumulative oil, bbl
1.95M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 10, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Manka Unit O-2-10502Eagleville (Eagle Ford-2)Murphy Expl. & Prod. Co. - USA61.72M1.95MFeb 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 27,254 · prior 12 36,116(-25%)

02K4K202420252026

Gas, mcf lease total

Last 12 months 65,379 · prior 12 61,503(+6%)

05K10K202420252026

Chain of custody

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

  1. 1Murphy Expl. & Prod. Co. - USAJul 2013 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
756303-99DrillMurphy Expl. & Prod. Co. - USAFeb 6, 2013Feb 11, 2013May 7, 201311,278

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-10502————

Formation tops

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

FormationMD ftSubsea
Olmos9,406-9,116
Undifferentiated Chalk10,741-10,451
Eagle Ford10,982-10,692

Perforations

Perforated and open-hole intervals.

FromToType
11,25616,558Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.755,26313.51,610 S
5.516,7338.53,025 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
00Oct 21, 2013Sep 18, 2013—
00Oct 1, 2013Aug 20, 2013—
00Aug 7, 2013Jun 11, 2013Yes

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