WELL · 42-329-36342 · DISTRICT 8

Robbie #2404

Plugged

Midland County · Spraberry (Trend Area) field  · Vertical

Robbie #2404 (API 42-329-36342) is a plugged well in Midland County, plugged October 23, 2019, last operated by Xto Energy Inc..

The RRC has issued 2 drilling permits between 2009 and 2016, permitted to 11,300 ft.

Completion filings report 7 formation tops, including Sndr Est, Glorieta, Clear Fork, Spraberry.

Its lease has reported 1.35M barrels of oil and 2.67M mcf of gas since April 2010, last reporting in July 2026. The lease carries 23 wells, so these are lease totals, not this well alone.

Operator of record

XTO Energy Inc.

Spring, TX · P-5 Y, filed Feb 4, 2026 · 16,153 permits on file · (832) 625-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsXTO Energy Inc.through Apr 2026
Latest permitXTO Energy Inc.Jan 29, 2016
11,300
total depth, ft
2
permits on file
Jan 29, 2016
last permit issued
Apr 21, 2011
completed
1.35M
cumulative oil, bbl
2.67M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 21, 2011
Shut in
—
Plugged
Oct 23, 2019

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Robbie O-10-40191Spraberry (Trend Area)XTO Energy Inc.231.35M2.67MApr 2010 – Jul 2026

Oil, barrels lease total

Last 12 months 23,743 · prior 12 27,314(-13%)

02K4K202420252026

Gas, mcf lease total

Last 12 months 61,968 · prior 12 67,937(-9%)

05K10K202420252026

Chain of custody

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

  1. 1Barron Operating LLCApr 2010 → Jun 2011
  2. 2Linn Operating, Inc.Jul 2011 → Oct 2014
  3. 3XTO Energy Inc.Nov 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
813314-99RecompletionXTO Energy Inc.Jan 19, 2016Jan 29, 2016Mar 7, 201111,300
683353-99DrillBarron Operating LLCJul 22, 2009Jul 23, 2009Mar 7, 201111,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-40191————

Formation tops

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

FormationMD ftSubsea
Sndr Est4,840-2,336
GlorietaGLORIETA SAND5,853-3,349
Clear ForkCLEARFORK7,155-4,651
Spraberry8,007-5,503
Dean9,267-6,763
Wolfcamp9,488-6,984
WolfcampLOWER WOLFCAMP9,937-7,433
Strawn10,631-8,127

Perforations

Perforated and open-hole intervals.

FromToType
8,06010,695Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,22012.75635 S
5.510,8057.875865 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
00Apr 4, 2018Feb 27, 2018—
00Jan 31, 2012May 24, 2011Yes

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