Get the data

Heads up on Original: the Commission does not publish this table on its own. It publishes Oil Detail Well, which this was parsed out of — so Original gets you that whole file, not just this table. Every other format is this table alone.

Free. You will be asked to confirm an email address before the files are built — that is the only gate, and it is there so we can tell you when a large export is ready.

Preview the first 100 rows

What this is

The DW-TST-INFO group of OLA028K normalised: 171,948 rows, two for each of the 85,974 wells on the detail-well tape. test_ordinal 1 is the previous test and 2 the most recent, in the order the manual gives them.

The same values are also flattened onto the well row as test1_ and test2_ columns in Oil Detail Well. This shape exists because 'the tested potential of every well in this unit over time' is a query, and against two columns per row it is a UNION.

What you can do with it

Chart a well's tested potential between its last two tests, or aggregate potential and water across the wells of a unit without unpivoting anything.

Gotchas

Every well has both rows even when a test is empty, which is why 171,948 is exactly twice 85,974. test_date is null on 690 of the previous tests and 663 of the most recent ones.

oil_bbl is the well's working POTENTIAL in barrels per calendar day, not production. It is the only number here that carries a decimal place: the tape wrote four digits and a fifth after an implied point.

Record layout

12 columns. Byte positions are 1-based and come from the RRC record layout, so you can check our decoding against the original file yourself.

`oil_detail_well_test` 12 columns

Record layout for `oil_detail_well_test` — 12 columns, with byte positions
#	Column	Type	Bytes	RRC name	Meaning	Lookup
1	`district` key join	text	1-3	`DW-DST`	RRC district the well is in, in the ledger's spelling. e.g. 01	RRC district (proration ledger spelling)
2	`field_no` key join	integer	4-11	`DW-FIELD-NUMBER`	The eight-digit RRC field number.	—
3	`operator_no` key join	integer	12-17	`DW-OPERATOR-NUMBER`	P-5 organization number of the lease operator.	—
4	`lease_no` key join	integer	18-22	`DW-LSE`	The five-digit RRC oil lease number. e.g. 31	—
5	`rec_no` key	text	23	`DW-RECNO`	Identifier of the multi-well group, one character. e.g. 1	—
6	`well_no` key	text	24-29	`DW-WELLNO`	The operator's well number, right-justified in six bytes as the tape wrote it. e.g. ' 2'	—
7	`test_ordinal` key	smallint	—	—	Which of the record's two W-10 tests this row is: 1 the previous test, 2 the most recent. The tape's OCCURS 2 group in the order the manual gives it -- the first 24 bytes are the previous test and the next 24 the most recent. Every well has both rows even when a test is empty, which is why 171,948 rows sit behind 85,974 wells. e.g. 2	—
8	`test_date`	date	43-50	`DW-TST-DT`	Date the test was filed. Null where the tape held zeros -- 690 of the previous tests and 663 of the most recent ones. e.g. 2025-03-08	—
9	`oil_bbl`	numeric measured in bbl/d	51-55	`DW-OIL`	The well's working potential on this test, in barrels per calendar day, to one decimal place. A potential, not production. e.g. 1.0	—
10	`prd_method`	smallint	56	`DW-PRD-METHOD`	Producing method on the test: 0 flowing, 1 pumping, 2 gas lift, 3 gas lift with a 10,000:1 exception, 4 vacuum, 5 casing leak, 6 designate well, 7 receiving well, 8 water well shut down. e.g. 1	—
11	`water_bbl`	integer measured in bbl	57-60	`DW-WATER`	Barrels of water produced with the oil on the test, generally over 24 hours.	—
12	`gor`	integer measured in cf/bbl	61-65	`DW-GOR`	Gas-oil ratio on the test, in cubic feet per barrel. Zero where it was not reported.	—

Code lookups used here

Every coded column in this dataset resolves to a real lookup table, so a well code of G can be read as what it actually means.

RRC district (proration ledger spelling) 14 values

Read by district

The district as the oil and gas proration ledger tapes write it, which is NOT how the rest of the corpus writes it. The ledger pads the lettered districts to three bytes -- 06E, 07B, 07C, 08A -- where the W-10, the G-10 and PDQ's district_name write 6E, 7B, 7C and 8A. That difference is worth a code set of its own because it is invisible in a join: a query matching ledger.district against w10.district returns rows for the ten numeric districts and silently drops the four lettered ones, which are 24% of the oil ledger's wells. Strip the leading zero before joining, or add it coming the other way. `canonical_value` is the internal district number, the same convention rrc.district uses, so a ledger district resolves to the same district in either numbering.

RRC district (proration ledger spelling) — 14 codes and their meanings
Code	Means
`01`	District 01 — San Antonio Written 01 here and 01 elsewhere.
`02`	District 02 — San Antonio Written 02 here and 02 elsewhere.
`03`	District 03 — Houston Written 03 here and 03 elsewhere.
`04`	District 04 — Corpus Christi Written 04 here and 04 elsewhere.
`05`	District 05 — Kilgore Written 05 here and 05 elsewhere.
`06`	District 06 — Kilgore Written 06 here and 06 elsewhere.
`06E`	District 6E — Kilgore The ledger writes 06E; the W-10 and PDQ write 6E.
`07B`	District 7B — Abilene The ledger writes 07B; the W-10 and PDQ write 7B.
`07C`	District 7C — San Angelo The ledger writes 07C; the W-10 and PDQ write 7C.
`08`	District 08 — Midland Written 08 here and 08 elsewhere.
`08A`	District 8A — Midland The ledger writes 08A; the W-10 and PDQ write 8A.
`08B`	District 8B — reserved The manuals list 08B as reserved for future use. No record of any ledger tape has ever carried it.
`09`	District 09 — Wichita Falls Written 09 here and 09 elsewhere.
`10`	District 10 — Pampa Written 10 here and 10 elsewhere.

Source: RRC manuals OLA013K, GSA020K and OLA028K (DIST/DIST-NO items); the thirteen spellings in use confirmed as the complete distinct set in texas.oil_ledger_field, texas.oil_ledger_well and texas.oil_detail_well on 2026-08-21

What this joins to

The Railroad Commission never states these keys anywhere in the files. They are the reason the data is hard to use, so here they are with the exact columns on both sides.

Oil Detail Well — W-10 Tests joins to Oil Detail Well on District and Field number and Operator number and Lease number and Rec number and Well number — many rows here share a single row there.

has its two W-10 tests

The same two tests the well row carries as test1_ and test2_, one row each. All 5,000 sampled wells have both rows, because the tape's OCCURS 2 group is always two occurrences even when a test is empty.

oil-detail-well.district = oil-detail-well-tests.district AND oil-detail-well.field_no = oil-detail-well-tests.field_no AND oil-detail-well.operator_no = oil-detail-well-tests.operator_no AND oil-detail-well.lease_no = oil-detail-well-tests.lease_no AND oil-detail-well.rec_no = oil-detail-well-tests.rec_no AND oil-detail-well.well_no = oil-detail-well-tests.well_no

Where this comes from

Published by

Texas Railroad Commission — the original page

Original format

EBCDIC IBM mainframe encoding (cp037). Opening it as text gives you nonsense; it has to be transcoded first.

RRC publishes

Updated once a month (Monthly, with the detail-well tape.)

RRC download link

GoAnywhere MFT

Record layout manual

OLA028K — Oil Detail Well — Record Layout

Our table

texas.oil_detail_well_test

EZRRC is an independent mirror of public-domain data published by the Texas Railroad Commission. It is not affiliated with or endorsed by the RRC. For any legal or regulatory purpose, verify against the official RRC release.