Get the data

Heads up on Original: the Commission does not publish this table on its own. It publishes Oil Ledger, 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 F-MONTH group of the OLA013K field record, normalised: one row per field per month, fourteen months per field and 475,146 rows in all. It carries the statewide production factor that month, whether the field was exempt from it, and the per-well, acreage and 'other' factors the field's allocation formula multiplies.

What you can do with it

Follow the production factor and a field's allocation factors month by month, and see which fields were exempted from the factor in which cycles.

Gotchas

month_ordinal is a slot on a tape that rolls, not a date. Every cycle RRC drops the oldest month and appends a new one, so ordinal 1 means 'oldest month on this tape' and nothing else. Filter on cycle_yyyymm.

The production factor has been 1.000 in 475,092 of 475,146 rows: the factor has not curtailed Texas oil for years, and a query looking for variation will find almost none.

The manual prints the other_factor item at record position 526. It is at 528 -- the one place the OLA013K layout is wrong, found by scanning the month stamps rather than by reading.

Record layout

13 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_ledger_field_month` 13 columns

Record layout for `oil_ledger_field_month` — 13 columns, with byte positions
#	Column	Type	Bytes	RRC name	Meaning	Lookup
1	`district` key join	text	2-4	`DIST`	RRC district of the field this month belongs to, in the ledger's spelling. e.g. 01	RRC district (proration ledger spelling)
2	`field_no` key join	integer	5-12	`FIELD`	The eight-digit field number this month belongs to. e.g. 256500	—
3	`month_ordinal` key	smallint	—	—	Which of the fourteen month slots in the field record this row came from, 1 to 14, oldest first. The tape rolls: every cycle the oldest slot is dropped and a new one added at the end, so ordinal 1 means 'oldest month on this tape' and nothing more. Read cycle_yyyymm for the month it actually is. e.g. 14	—
4	`cycle_yyyymm`	integer	501-506	`FM-DATE`	The schedule month this row is for, as CCYYMM -- the only thing that makes month_ordinal mean anything. The August 2026 tape runs 202506 to 202607, and every one of the 33,939 fields carries all fourteen. e.g. 202607	—
5	`per_well`	smallint measured in bbl/d	507-508	`FM-PW`	The per-well allowable amount for this month, in barrels per day, for fields whose allocation formula has a per-well term. Zero for the fields that do not (232,764 of 475,146 rows).	—
6	`acreage_factor`	numeric	509-512	`FM-AC`	The acreage factor for this month, for fields with acres in the allocation formula. Three whole numbers and four decimals on the tape; non-zero in 95,487 rows, up to 382.	—
7	`other_factor_code`	smallint	517	`FM-OTHC`	Which factor other_factor holds when the formula uses something besides per-well or acres: 1 acre feet, 2 bottom-hole pressure, 3 potential, 4 acre pounds, 5 pressure, 6 acre foot pounds, 7 acres. Zero in 473,914 of 475,146 rows.	—
8	`month_exempt_code`	smallint	518	`FM-CHG`	Whether the field was exempt from the statewide production factor this month: 1 exempt (8,078 rows), 0 not.	—
9	`prod_factor`	numeric	519-521	`FM-PROD-FACT`	The statewide production factor set at that month's proration hearing, two whole numbers and three decimals. It has been 1.000 in 475,092 of 475,146 rows -- the factor has not curtailed Texas oil for many years. e.g. 1.000	—
10	`split_prod_factor`	numeric	522-524	`FM-SPLIT-PROD-FACT`	A second production factor for the month, where one took effect after the first of the month. Zero throughout the August 2026 tape.	—
11	`split_prod_factor_date`	smallint	525-526	`FM-SPLIT-PROD-FACT-DATE`	Day of the month the split production factor took effect. Zero throughout, matching split_prod_factor.	—
12	`change_status_code`	smallint	527	`FM-JOHN`	Six here marks an oil field that can no longer reach its maximum efficiency rate. Zero in every row of the current tape.	—
13	`other_factor`	numeric	528-535	`FM-OTH`	The amount of the factor other_factor_code names -- eight whole numbers and seven decimals on the tape. The manual prints this item at record position 526; it is actually at 528, which is the one place the OLA013K layout is wrong and was found by scanning the month stamps.	—

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 Ledger — Field Months joins to Oil Ledger on District and Field number — many rows here share a single row there.

has fourteen months of allocation factors

The F-MONTH group of the field record, one row per month. All 5,000 sampled fields have all fourteen: the group is fixed-length and the loader keeps a slot only when it carries a cycle stamp, so fourteen of fourteen means the tape filled every one.

oil-ledger.district = oil-ledger-field-months.district AND oil-ledger.field_no = oil-ledger-field-months.field_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 oil ledger.)

RRC download link

GoAnywhere MFT

Record layout manual

OLA013K — Oil Ledger — Record Layout

Our table

texas.oil_ledger_field_month

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.