Get the data

Heads up on Original: the Commission does not publish this table on its own. It publishes Production Data Query Dump, 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

One of the sixteen delimited tables inside the monthly Production Data Query dump. RRC publishes the dump as a single archive; EZRRC publishes each table inside it separately so you can take the one you need instead of a 3.6 GB zip.

Production summed to the P-5 operator and month: 3.4 million rows of who produced what.

What you can do with it

Rank Texas operators by monthly oil or gas production, watch an operator's output through an acquisition, and size a company against its peers.

Gotchas

The operator is whoever reported the production that month. An acquisition shows up as one operator's volume stopping and another's starting, with no link between them.

A lease number is only unique with the oil/gas code and the district in it. Oil lease 027587 in District 08 and gas lease 027587 in District 08 are different leases; so is oil lease 027587 in District 09.

district_no here is RRC's INTERNAL district numbering (01-14, 20), not the designation the industry prints. Internal 07 is District 6E, 08 is 7B, 09 is 7C, 10 is District 08, 11 is 8A, 13 is 09 and 14 is District 10. The district directory is the lookup; reading the number as a label is wrong.

Volumes are whole numbers in the reporting unit — barrels for liquids, MCF for gas. There are no implied decimals here, unlike the EBCDIC ledgers.

Cycle year and cycle month are separate columns; cycle_year_month is the two of them concatenated as YYYYMM and is the cheapest thing to range on.

Production is reported by lease, not by well. A lease can be one well or two hundred.

Record layout

10 columns.

`pdq_og_operator_cycle` 10 columns

Record layout for `pdq_og_operator_cycle` — 10 columns
#	Column	Type	RRC name	Meaning	Lookup
1	`operator_no` key join	text	—	The operator's six-digit RRC P-5 organization number. Join to the P-5 Organization dataset for the company's name, address and P-5 status.	—
2	`cycle_year`	text	—	Production cycle year, four digits.	—
3	`cycle_month`	text	—	Production cycle month, two digits.	—
4	`cycle_year_month` key	text	—	Production cycle as YYYYMM. This is the column to filter a date range on.	—
5	`operator_name`	text	—	Operator name as carried in this file. Names drift between filings — join on the operator number, never on the name.	—
6	`oper_oil_prod_vol`	bigint measured in bbl	—	Operator oil prod vol	—
7	`oper_gas_prod_vol`	bigint measured in MCF	—	Operator gas prod vol	—
8	`oper_cond_prod_vol`	bigint measured in bbl	—	Operator cond prod vol	—
9	`oper_csgd_prod_vol`	bigint measured in MCF	—	Operator csgd prod vol	—
10	`ingested_at`	timestamptz	—	When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against.	—

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.

PDQ Operator Production by Cycle joins to PDQ Operator Directory on Operator number — many rows here share a single row there.

totals the operator

Operator number to name and P-5 status.

pdq-operator-cycle.operator_no = pdq-operator-directory.operator_no

PDQ Operator Production by Cycle joins to P-5 Organization (ASCII) on Operator number = ID — many rows here share a single row there.

totals the organization

The same operator number against the authoritative P-5 register. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

pdq-operator-cycle.operator_no = p5-organization-ascii.id

Where this comes from

Published by

Texas Railroad Commission — the original page

Original format

CSV Comma-separated text.

RRC publishes

Updated once a month (Last Saturday each month, with the PDQ dump.)

RRC download link

GoAnywhere MFT

Record layout manual

Production Data Query Dump — User Manual

Our table

texas.pdq_og_operator_cycle

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.