WELL · 42-481-35119 · DISTRICT 3
Stegman #5
Wharton County · Boling field · Producing · Vertical
Stegman #5 (API 42-481-35119) is a well in Wharton County operated by Jrp Production LLC, completed March 23, 2010 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 10, 2010, permitted to 700 ft.
Completion filings report one formation top, including Oakville.
Its lease has reported 33.5K barrels of oil since March 2010, last reporting in July 2026. The lease carries 13 wells, so these are lease totals, not this well alone.
Operator of record
Boling, TX · P-5 Y, filed Jun 4, 2026 · 37 permits on file · (979) 533-2104
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | JRP Production LLC |
| Production reports | JRP Production, LLCthrough Apr 2026 |
| Latest permit | JRP Production, LLCFeb 10, 2010 |
- 700
- total depth, ft
- 1
- permits on file
- Feb 10, 2010
- last permit issued
- Mar 23, 2010
- completed
- 33.5K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2010 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Mar 23, 2010
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 13 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Stegman O-3-25482 | Boling | JRP Production, LLC | 13 | 33.5K | 0 | Mar 2010 – Jul 2026 |
Oil, barrels lease total
Last 12 months 1,152 · prior 12 545(+111%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1JRP Production, LLCMar 2010 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 690987-99 | Drill | JRP Production, LLC | Feb 9, 2010 | Feb 10, 2010 | Mar 13, 2010 | 700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-3-25482 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 69 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Oakville | 286 | -217 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 288 | 292 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 357 | 7.875 | 105 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 14, 2010 | Mar 29, 2010 | Yes |
| 00 | Apr 13, 2010 | — | — |
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.
- Wellbore filings for 42-481-35119 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-481-35119 → scanned completion filings
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/48135119, documented in the API reference.