← All tables

gold_organization_registrations

The bridge between regulator-issued operator IDs (Texas P-5, New Mexico OGRID, and each region's equivalent) and our canonical company register: normally one row per (region, registration ID), carrying the name as registered, registration status, role flags (operator / gatherer / midstream), and headquarters as filed. organization_id links to gold_organizations once the operator is resolved. Where the company behind an ID was renamed, the ID carries one row per period instead (see valid_from / valid_to) so that filings made before and after the rename are attributed to the right company.

Access tier: public_aggregate Public. These rows are the public layer: aggregate series and reference records such as companies, formations and rig counts. Where a page publishes them you can read them on the website, and a free account can export the aggregate series behind a view (10 a month).
Primary key: region, registration_id, valid_from
Region codes: ab, ak, al, ar, argentina, bc, brazil, ca, co, gom, ks, la, mb, mi, mt, nm, oh, ok, pa, pacific, sk, tx, ut, wv, wy

Columns

Column	Type	Nullable	Description
region	string	no	Region code the registration belongs to (e.g. tx, nm, ab, brazil). First part of the primary key.
registration_id	string	no	The regulator's identifier for this entity in this region: TX P-5 number, NM OGRID, PA OGO number, AB AER licensee number, Brazil ANP CNPJ. Second part of the primary key. Opaque string. Do not parse.
organization_id	string	yes	Join key to the company register (gold_organizations). NULL when this registration has not yet been resolved to a canonical organization (typical for newly registered or rarely active operators); resolved coverage grows over time.
link_source	string	yes	How the organization_id link was established: 'write_initial' (resolved from name research at a bridge build), 'relink_from_mapping' (backfilled by the automatic re-link pass on a name match), 'manual_split' / 's1-verified' / 'merge_redirect' (manual adjudications: these survive rebuilds unconditionally), 'derived_window' (period row minted for a renamed company; see valid_from/valid_to), 'manual_unlink' (an adjudicated DETACHMENT: the registration's identity was ruled uncertain, so organization_id is NULL by decision; survives rebuilds and is never auto-refilled). Stable across rebuilds while the link itself is unchanged. NULL when organization_id is NULL, except an adjudicated detachment: 'manual_unlink' is the value written for one; a manual adjudication value beside a NULL organization_id reads the same way.
linked_at	date	yes	Date the organization_id link was first established. NULL when organization_id is NULL; on an adjudicated detachment it is NULL or the detachment's own stamp date. Stable. Use it to audit when a regulator ID was linked to a canonical organization.
registered_name	string	no	Entity name as filed with the regulator. May differ between regions for the same canonical organization (e.g. "APACHE CORPORATION" vs "APACHE CORP-DELAWARE LP").
status	string	yes	Regulator-side status: active = currently registered and can hold permits; inactive = registered but not active; delinquent = registered and holding property or activity, but not in good standing because a required filing lapsed: the regulator will not issue new permits until it refiles; dissolved = terminated; unknown = the source gives no readable status. Values: active · inactive · dissolved · delinquent · unknown.
status_effective_date	date	yes	When the current status took effect, when known. NULL if not provided.
is_operator	boolean	yes	Registered as an oil & gas operator in this region. NULL where the regulator's register covers more than operators and publishes no role dimension: the regulator says nothing either way, which is not the same as saying the company is not an operator.
is_gatherer	boolean	yes	Registered as a gatherer/transporter (gas or oil pipeline gathering). Not all regulators distinguish; false where the source has no signal. So, unlike is_operator, false here does not necessarily mean the regulator said no.
is_midstream	boolean	yes	Registered as a midstream company (processing, storage, transmission). Often overlaps with is_gatherer where the regulator treats them as one role.
hq_address_line1	string	yes	Headquarters street address as filed with the regulator.
hq_address_city	string	yes	Headquarters city as filed.
hq_address_state_province	string	yes	Headquarters state or province as filed.
hq_address_country	string	yes	Headquarters country (ISO code or regulator-provided string): as filed where the register carries an address; where it carries none, the licensing jurisdiction's country may be carried as a documented default.
hq_address_zip	string	yes	Headquarters postal code as filed.
delisted_date	date	yes	Date this registration was first observed absent from the regulator's register. The row is kept so its history survives the delisting. NULL = present in the latest register. Stays at the first observed absence across repeat cycles, and clears automatically if the registration reappears. When non-NULL, the as-filed fields (registered_name, status, roles, address) are a last-known snapshot as of this date: treat them as historical, not live.
valid_from	date	yes	Start of the period this registration id referred to this company. Blank means from the beginning of its observed life. Set only where the company behind the id was renamed, so that production filed before and after the rename is attributed to the right name.
valid_to	date	yes	End of the period this registration id referred to this company. Blank means up to the present. Set only where the company behind the id was renamed.

How these numbers are built is on methodology; the machine twin of this page is data-dictionary.json.