WELL · 42-105-42560 · DISTRICT 7

University Lands 224 #N274H

Y

Crockett County · Lin (Wolfcamp) field · Producing  · Horizontal

University Lands 224 #N274H (API 42-105-42560) is a horizontal well in Crockett County operated by Triple Crown Resources LLC, completed October 9, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 8, 2025, permitted to 9,000 ft.

Completion filings report 8 formation tops, including Queen, San Andres, Leonard, Wolfcamp.

Its lease has reported 715K barrels of oil and 3.08M mcf of gas since January 2023, last reporting in July 2026. The lease carries 13 wells, so these are lease totals, not this well alone.

Operator of record

Triple Crown Resources LLC

Dallas, TX · P-5 Y, filed Nov 4, 2025 · 345 permits on file · (214) 306-0606

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTriple Crown Resources LLC
Production reportsTriple Crown Resources, LLCthrough Mar 2026
Latest permitTriple Crown Resources, LLCMay 8, 2025
9,000
total depth, ft
1
permits on file
May 8, 2025
last permit issued
Oct 9, 2025
completed
715K
cumulative oil, bbl
3.08M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2023 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 9, 2025
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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
University Lands 224 O-9-21912Lin (Wolfcamp)Triple Crown Resources, LLC13715K3.08MJan 2023 – Jul 2026

Oil, barrels lease total

Last 12 months 269,458 · prior 12 126,271(+113%)

050K100K202420252026

Gas, mcf lease total

Last 12 months 1,298,675 · prior 12 860,369(+51%)

0100K200K202420252026

Chain of custody

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

  1. 1Triple Crown Resources, LLCJun 2023 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
907838-99DrillTriple Crown Resources, LLCMay 8, 2025May 8, 2025May 13, 20259,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-21912————

Formation tops

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

FormationMD ftSubsea
Queen1,0431,578
San Andres1,717904
San Andres1,742879
Leonard4,912-2,291
Wolfcamp5,647-3,026
Canyon——
Devonian——
Ellenburger——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
6,68114,556Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62592412.25385 S
5.514,6528.751,880 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
00Feb 2, 2026Jan 16, 2026—
00Oct 15, 2025Sep 19, 2025Yes

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) and the University Lands library. 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/10542560, documented in the API reference.