WELL · 42-065-32126 · DISTRICT 10

Sanford 160 #1R

Y

Carson County · Panhandle West field · Producing  · Vertical

Sanford 160 #1R (API 42-065-32126) is a well in Carson County operated by Borger Resources 2 LLC, completed January 14, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 10, 2011, permitted to 3,000 ft.

It was permitted by Snw Operating Company and has since transferred to Borger Resources 2 LLC on the wellbore schedule.

Completion filings report one formation top, including Brown Dolomite.

No lease production has been reported under this well’s leases.

Operator of record

Borger Resources 2 LLC

Permitted by SNW Operating Company; the EWA schedule now lists a different operator.

Borger, TX · P-5 Y, filed Jan 4, 2026 · 1 permits on file · (214) 336-6692

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBorger Resources 2 LLC
Production reportsBorger Resources 2 LLCthrough Apr 2026
Latest permitSNW Operating CompanyNov 10, 2011

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

3,000
total depth, ft
1
permits on file
Nov 10, 2011
last permit issued
Jan 14, 2012
completed
0
cumulative oil, bbl
138K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 14, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sanford 160 G-14-267590Panhandle, WestBorger Resources 2 LLC10138KJan 2012 – Jul 2026

Gas, mcf lease total

Last 12 months 6,205 · prior 12 7,235(-14%)

05001K1.5K202420252026

Chain of custody

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

  1. 1SNW Operating CompanyMar 2012 → Sep 2014
  2. 2PG-M International Operating,llcOct 2014 → Jun 2019
  3. 3Bar L ProducersJul 2019 → Mar 2023
  4. 4Borger Resources 2 LLCApr 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
724037-99DrillSNW Operating CompanySep 12, 2011Nov 10, 2011Jan 9, 20123,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-267590————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite2,372903

Perforations

Perforated and open-hole intervals.

FromToType
2,3302,882Perforated
2,3302,882Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62542113.5250 S
72,3568.75200 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
00Jun 5, 2013May 8, 2013—
00May 8, 2013Apr 26, 2012Yes

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