AER ST37 Well Data — What It Contains and How to Use It for Business Research

Industry Overview: ST37 in the Alberta Data Stack

Alberta publishes some of the most comprehensive public oil and gas data in the world, and ST37 sits at the base of that stack. Every well drilled in the province — whether a vertical conventional well, a horizontal tight oil well, or a multi-lateral shale gas well — appears in ST37 with its identifiers, status, operator, and location. For oilfield service companies, ST37 is the single most important raw material for building prospect lists, sizing regional opportunity, and tracking the lifecycle of assets from hydraulic fracturing completions through to abandonment and reclamation.

Understanding ST37 is not just about downloading a CSV. It is about knowing what each field means, how the data is structured, and how to combine it with production, filings, and operator context so the raw export becomes a decision-support tool. This guide walks through the dataset field by field and shows the workflow that turns hundreds of thousands of rows into a focused, outreach-ready list.

ST37 vs Subsurface and Production Datasets

ST37 is the surface and regulatory well record, but it is only one of several AER datasets. Subsurface datasets such as directional surveys and well logs describe the wellbore trajectory and geology, while production datasets describe what the well has produced. ST37 does not contain production volumes; for that you turn to Petrinex and AER production records. Keeping these layers distinct prevents the common mistake of treating ST37 as a complete picture.

Reading the ST37 Status and Well-Class Codes

The status field in ST37 uses short codes that map to well conditions. Producing wells may appear as FLOW, PUMP, or GASLFT. Inactive wells use a range of holding codes. Suspended wells carry SUSP. Abandoned wells use ABD and related codes. Because these codes are not self-explanatory, the well status data guide and the well status interpretation reference decode each one. Misreading a code is a frequent source of wasted outreach.

How ST37 Links to Licence Numbers and UWIs

Each ST37 row carries both a licence number and a UWI. The licence number identifies the regulatory authorisation; the UWI identifies the physical wellbore. The well licence number guide explains how a single wellbore can carry multiple licence numbers over its life as it is transferred or recompleted. Using the correct key when joining ST37 to other datasets avoids duplicate or mismatched records.

Working With Large ST37 Exports in Code

For analysts comfortable with Python or SQL, the ST37 CSV can be loaded directly into a dataframe or database. The Alberta Open Data portal also offers an API that streams the same data, which is useful for automated refreshes. A minimal workflow: load ST37, filter to your target field centres and status codes, group by operator number, and join to Petrinex on the licence number. This is the programmatic equivalent of the spreadsheet workflow described below and scales to the full province.

Data Quality and Common ST37 Pitfalls

Three issues recur in ST37 work. First, location coordinates are missing for some older wells, so geographic filtering must fall back to township-range fields. Second, operator names are inconsistent across decades of records, so grouping by operator number is safer than grouping by name. Third, the file is a snapshot — wells change status between releases, so a research list built today may be stale within weeks. The Alberta oilfield data sources guide covers these limitations in depth.

What Is the AER ST37 Dataset

The Alberta Energy Regulator publishes a well data file known as ST37. It contains public Alberta well records, including wells with active, inactive, suspended, abandoned, and other status values. If you are doing well-related business research in Alberta, ST37 is one of the foundational datasets you will encounter.

ST37 is not a tool or a platform — it is a raw data export. It includes dozens of fields covering well identification, location fields, operator information, drilling dates, production-string details, and regulatory status. It is free to download from the AER and Alberta Open Data, and users should check the source page for the current update date.

The challenge with ST37 is not access — it is interpretation and application. The file was designed for regulatory reporting, not for business development. Making it useful for sales prospecting, market research, or opportunity identification requires understanding what each field means, how the data is structured, and what workflow you need to turn raw records into actionable insights.

Key Fields in the ST37 Dataset

The ST37 file contains many fields. The most relevant ones for business research include:

Well identification numbers — unique identifiers assigned to each well, including the Well ID and Licence Number. These are the primary keys for linking wells to other AER datasets.

Well status — the status value available in the public record, such as active, inactive, suspended, abandoned, or another classification. This is the first filter most researchers apply, but it should not be treated as a complete opportunity signal on its own.

Operator information — the company that holds the licence and is responsible for the well. Operator name and operator number allow you to group wells by ownership and assess operator activity.

Location data — the well's surface location, typically described by field centre, township, range, meridian, and latitude/longitude coordinates. Location is essential for geographic filtering and mapping.

Well type and classification — whether the well is an oil well, gas well, injection well, or other type. This affects the kinds of services the well is likely to need.

Spud date and licence dates — when the well was drilled, when the licence was issued, and key regulatory milestones. These dates help you assess well age and time since last activity.

Production-string and status fields — classification details that help interpret well type and status context. For production volumes or economics, researchers should verify against the appropriate AER production sources.

Surface and bottom hole location fields — location values that may support mapping or proximity review when coordinates are present and valid.

Where to Get ST37 Data

There are three primary sources for accessing ST37 data:

AER website — the Alberta Energy Regulator publishes ST37 files and related datasets directly. You can download current and historical versions of the file. The AER site also provides data dictionaries that explain each field.

Alberta Open Data portal — the provincial open data platform hosts ST37 as a downloadable dataset with an API option. This is often the most convenient source for bulk downloads and programmatic access.

Third-party data aggregators — some platforms re-package AER data with additional indexing, linking, or search capabilities. FracturingHub, for example, organizes a lean public-record dataset into searchable well and operator views, watchlists, and saved searches. Researchers should still verify material details against official sources.

How to Use ST37 for Business Research

The raw ST37 file is powerful but not organized for business development. Here is a practical workflow for turning ST37 data into a research asset:

Step 1: Define Your Research Question

Before opening the data, clarify what you are trying to find. Common research questions include: which operators have inactive wells in my service area, what wells in my target region have been inactive the longest, which operators are active enough to be worth contacting, and where are wells clustered geographically. A clear question determines which fields you filter on and how you sort the results.

Step 2: Import and Clean the Data

Download the ST37 file and open it in a spreadsheet or data tool. The file can be large — often hundreds of thousands of rows. Remove columns you do not need for your specific question. Standardize field names if you are combining ST37 with other datasets. Check for missing values in critical fields like operator name, well status, and location.

Step 3: Filter to Your Target Segment

Apply filters to narrow the dataset to your research scope. The most common initial filters are status (e.g., inactive only), location (e.g., a specific field centre or basin), operator (e.g., a set of target operators), and well type (e.g., oil wells only). The goal is to move from hundreds of thousands of records to a focused subset of hundreds or low thousands that match your criteria.

Step 4: Cross-Reference and Enrich

Raw ST37 data tells you what exists, but not always why it matters. Cross-reference your filtered list against other approved sources to add context: check operator activity in nearby areas, look for recent AER regulatory filings, review infrastructure context where available, and check whether the operator has other wells in your target region. This cross-referencing step separates a list of wells from a list of opportunities.

Step 5: Prioritize and Act

Not every well in your filtered list is equally promising. Prioritize based on operator activity, geographic convenience, well age, and service alignment. Assign each well or operator a next action: outreach call, further research, add to watchlist, or discard. Document your findings so the research is reusable.

Limitations of Raw ST37 Data

ST37 is the best single source for Alberta well data, but it has limitations that matter for business research:

No built-in search or filtering UI — you are working in a spreadsheet or writing code. There is no point-and-click interface for complex queries.

No operator context — ST37 tells you who the operator is but not whether that operator is active, what other wells they manage, or whether they are likely to commission work.

No saved searches or monitoring — every time the data updates, you need to re-run your filters to find changes.

No workspace for notes or collaboration — when you add insights to a spreadsheet, the research context lives outside the data and is hard to share.

How FracturingHub Builds on ST37

FracturingHub ingests public AER data, including ST37 records, and organizes it into a research workspace designed for oilfield business development. Instead of working through raw exports, you get:

Instant search — filter by well status, location, operator, well type, and other attributes without building spreadsheet formulas.

Operator profiles — review searchable wells, status mix, and mapped records for an operator where the public data supports that context.

Watchlists and saved searches — save research criteria for repeatable review instead of rebuilding the same filters manually.

Workspace notes — attach verification notes, tags, and next actions directly to operators and wells.

CSV export — export a clean, research-ready list for CRM import or outreach campaigns.

Best Practices for Working With ST37 Data

Always check the data dictionary — ST37 has dozens of fields. Understanding what each field means and how it is coded prevents misinterpretation.

Watch for data freshness — ST37 is updated periodically, not in real time. Always note the date of the file you are working with and verify key facts against live AER sources before outreach.

Combine with other AER datasets — ST37 is most powerful when linked to facility data, pipeline data, and regulatory filing data. Each dataset adds context that ST37 alone does not provide.

Document your filters — save the filter criteria you used so you can replicate the search later or share it with a team member.

Do not over-rely on any single field — well status, for example, does not tell the whole story. A well marked inactive might be days away from recompletion or years from any activity. Cross-reference multiple fields before drawing conclusions.

Comparison: ST37 vs Other Sources

Decision Framework: When to Use ST37

Use ST37 when you are building a list, filtering by status or location, or grouping wells by operator. Use Petrinex when you need production history. Use the Open Data API when you need automation. Use AlbertaWellFinder to verify one well. Choosing the right source for the question is the core of the data sources methodology.

Common Mistakes Checklist

• Do read the data dictionary before filtering.
• Do group by operator number, not operator name.
• Do note the file date and verify against live sources.
• Don't treat ST37 status as a complete opportunity signal.
• Don't try to analyze production from ST37 — use Petrinex.
• Don't ignore missing coordinates; fall back to township-range.

Safety and Compliance Notes

ST37 is a research tool, not a field safety document. Wells listed as suspended, abandoned, or orphan can present hazards including pressure, H2S, and degraded equipment. Before any site visit, confirm current status and operator authorization, and follow oilfield safety practice. The AER and CAPP publish the standards that govern safe wellsite conduct, and the fracturing glossary defines the technical terms used in well records.

Glossary of Key Terms

• ST37: The AER public well-record dataset covering every Alberta well.
• UWI: Unique Well Identifier, the 16-character code for the physical wellbore.
• Licence number: The AER regulatory authorisation embedded in UWI characters 12–16.
• Petrinex: The production and royalty reporting system for Alberta wells.
• SUSP: ST37 status code for a suspended well under Directive 020.
• Field centre: The named operational area a well belongs to.
• Open Data API: The programmatic access point for bulk AER datasets.
• Operator number: The stable key for grouping wells by ownership.

Summary

ST37 is the indispensable foundation of Alberta oilfield business research. Free, comprehensive, and continuously published, it gives you well identifiers, status, operator, and location for every well in the province. Used well — filtered, grouped by operator number, joined to Petrinex and filings, and verified against live sources — it becomes a repeatable engine for finding inactive wells, abandonment candidates, and reclamation backlog. Start with the data sources guide and build your workflow from there.

Related Resources

Dig deeper with the well data vs public records comparison, the UWI explained guide, the licence numbers guide, the inactive well guide, and the prospect list guide. For a methodology overview, see data sources methodology.

Quick Checklist

Download ST37 from AER or Alberta Open Data

Read the data dictionary to understand each field

Define your research question before filtering

Filter by status, location, operator, and well type

Cross-reference operator activity and nearby wells

Prioritize results and assign next actions

Document filter criteria for future replication