TEXAS · WELLS · ANGELINA COUNTY · SABER GAS UNIT LEASE · API 42-005-30409 · DISTRICT 06
Saber Gas Unit #1H
Angelina County · Carthage (Haynesville Shale) field · Producing · Horizontal
Saber Gas Unit #1H (API 42-005-30409) is a horizontal well in Angelina County operated by Bpx Operating Company, completed December 14, 2017 and listed as producing on the RRC schedule, shut in November 1, 2026.
The RRC has issued one drilling permit, issued February 22, 2017, permitted to 16,299 ft.
It was permitted by BP America Production Company and has since transferred to Bpx Operating Company on the wellbore schedule.
Completion filings report 5 formation tops, including Nacatoch, Glen Rose, Pettit, Travis Peak.
Its lease has reported 15.8M mcf of gas since December 2017, last reporting volume in March 2026.
Operator of record
Permitted by BP America Production Company; the EWA schedule now lists a different operator.
- Based in
- Denver, CO
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Jun 24, 2026
- Permits on file
- 1,576
- Phone
- (720) 439-5104
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | BPX Operating Company |
| Production reports | BPX Operating Companythrough Mar 2026 |
| Latest permit | BP America Production CompanyFeb 22, 2017 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 16,299
- total depth, ft
- 1
- permits on file
- Feb 22, 2017
- last permit issued
- Dec 14, 2017
- completed
- 0
- cumulative oil, bbl
- 15.8M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2017 THROUGH Mar 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 14, 2017
- Shut in
- Nov 1, 2026
- 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 lease this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Saber Gas Unit G-6-284011 | Carthage (Haynesville Shale) | BPX Operating Company | 1 | 0 | 15.8M | Dec 2017 – Mar 2026 |
Gas, mcf lease total
Last 12 months 372,361 · prior 12 1,030,650(-64%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1BP America Production CompanyDec 2017 → Feb 2022
- 2BPX Operating CompanyMar 2022 → Mar 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 822561-99 | Drill | BP America Production Company | Jan 27, 2017 | Feb 22, 2017 | Mar 19, 2017 | 19,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Dec 14, 2017 | Saber Gas Unit G-6-284011 | Carthage (Haynesville Shale) | BPX Operating Company | Producing · shut in Nov 1, 2026 | 16,299 |
Formation tops
As filed on W-2/G-1. Subsea from 307 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Nacatoch | 3,920 | -3,613 |
| Glen Rose | 7,537 | -7,230 |
| PettitPETTET | 9,894 | -9,587 |
| Travis Peak | 10,814 | -10,507 |
| HaynesvilleHAYNESVILLE SHALE | 14,623 | -14,316 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 15,915 | 23,223 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 4,296 | 17.5 | 2,440 S |
| 5.5 | 12,173 | 8.5 | 1,264 S |
| 9.625 | 12,994 | 12.25 | 1,510 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | May 31, 2018 | Feb 14, 2018 | Yes |
Well logs
2 logs loaded from the RRC's log index, 1 of them with a digital LAS file, the latest received Dec 1, 2020. Gamma ray. 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| Gamma RaySpans Haynesville | TIFF | 14,700 to 23,295 | Dec 1, 2020 | 4.37 |
| Gamma RaySpans Haynesville | LAS + TIFF | 14,700 to 23,295 | Jun 19, 2018 | 1.61 + 4.37 |
"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.
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-005-30409 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-005-30409 → scanned completion filings
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/00530409, documented in the API reference.