WELL · 42-199-31258 · DISTRICT 3
Paraffine Oil Corporation #6
Hardin County · Batson New field · Vertical
Paraffine Oil Corporation #6 (API 42-199-31258) is a plugged well in Hardin County, plugged January 11, 1996, last operated by Tandem Energy Corporation.
The RRC has issued one drilling permit, issued July 24, 1978, permitted to 3,500 ft.
It was permitted by Marwood Oil Company and has since transferred to Tandem Energy Corporation on the wellbore schedule.
Its lease has reported 94.8K barrels of oil and 8 mcf of gas since January 1993, last reporting in July 2026. The lease carries 10 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Marwood Oil Company; the EWA schedule now lists a different operator.
Houston, TX · P-5 Y, filed May 4, 2026 · 138 permits on file · (281) 351-5840
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Tandem Energy Corporation |
| Production reports | Tandem Energy Corporationthrough Apr 2026 |
| Latest permit | Marwood Oil CompanyJul 24, 1978 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 3,500
- total depth, ft
- 1
- permits on file
- Jul 24, 1978
- last permit issued
- —
- completed
- 94.8K
- cumulative oil, bbl
- 8
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Jan 11, 1996
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 10 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Paraffine Oil Corporation O-3-5198 | Batson New | Tandem Energy Corporation | 10 | 94.8K | 8 | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 498 · prior 12 227(+119%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Nostar Inc.Jan 1993 → Feb 1993
- 2Magic Oil & GasAug 1994 → Nov 1994
- 3Magic Oil & Gas Inc.Dec 1994 → Jan 2001
- 4F.I.G. Energy, LLCFeb 2001 → Apr 2014
- 5Tandem Energy CorporationJun 2014 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 28999-99 | Drill | Marwood Oil Company | Jul 24, 1978 | Jul 24, 1978 | — | 3,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-3-5198 | — | — | — | — |
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 | Dec 9, 1988 | — | — |
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-199-31258 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-199-31258 → 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/19931258, documented in the API reference.