{"id":2978,"date":"2026-11-11T17:38:34","date_gmt":"2026-11-11T17:38:34","guid":{"rendered":"https:\/\/synmax.com\/energy\/drilling-completions\/"},"modified":"2026-11-13T22:56:19","modified_gmt":"2026-11-13T22:56:19","slug":"drilling-completions","status":"publish","type":"page","link":"https:\/\/synmax.com\/energy\/capabilities\/drilling-completions\/","title":{"rendered":"Drilling & Completion Activity"},"content":{"rendered":"\n
\"\"<\/span>
\n
<\/g><\/svg><\/div>\n\"\"\n\n
\n\n
\n\n

Capability<\/p>\n\n\n

The rig count is a survey.
The pad is a fact.<\/span><\/h1>\n\n\n

Rigs and frac crews, counted from orbit.<\/p>\n\n<\/div>\n\n

<\/div>\n\n
\n\n

Published rig counts depend on who responds, miss much of the private activity and arrive after the move has started. SynMax counts what is actually on the pad, for every operator, so a change in activity reaches you while it is still a change in activity rather than a line in next quarter\u2019s report.<\/p>\n\n\n

\n\n
Request a Demo<\/a><\/div>\n\n\n
All capabilities<\/a><\/div>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n
<\/svg>Scroll to explore<\/span><\/div>\n<\/div><\/section>\n\n\n\n
\n\n
\n\n
\"Illustrative
Same basin, two views: what a survey sees, and what is on the pad. Illustrative positions, not actual data.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

The Problem<\/p>\n\n<\/div>\n\n\n

Counts you cannot verify are counts you cannot trade.<\/h2>\n\n\n

Published rig counts are surveys. They miss private operators, lag the move, and tell you nothing about whether the crew on site is actually completing a well.<\/p>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Seen, not surveyed<\/h3>\n\n\n

Equipment on the pad is detected directly, so the count does not depend on who chose to respond.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Ahead of the filing<\/h3>\n\n\n

A crew arriving on location is visible immediately; the completion report follows much later.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Whole-basin coverage<\/h3>\n\n\n

Public and private operators are treated the same way, because the measurement does not ask permission.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Activity, not just presence<\/h3>\n\n\n

Distinguishing a rig from an active frac spread from a DUC awaiting completion is what makes the count usable.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n
\n\n
\n\n

Ahead of the Survey<\/p>\n\n<\/div>\n\n\n

See the turn before the survey does.<\/h2>\n\n\n

Activity rarely changes direction all at once. A few operators drop a crew, a few more defer completions, and the basin trend bends weeks later. Because the observed count is built pad by pad, that bend shows up as it starts, not when the next survey or filing confirms it.<\/p>\n\n\n

For a trading desk, that is time to position. For an operator or a service company, it is an early read on where the basin is heading and who is driving it.<\/p>\n\n<\/div>\n\n\n

\n\n
\"Illustrative
The observed count turns first. The survey count arrives later and misses private operators. Illustrative, not actual data.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

How It Works<\/p>\n\n<\/div>\n\n\n

Detect, classify, count.<\/h2>\n\n\n
\n\n
\n\n
\n\n
\"\"\/<\/figure>\n\n\n

01 \/ DETECT<\/p>\n\n<\/div>\n\n\n

Find the equipment<\/h3>\n\n\n
\n\n\n

High-revisit imagery across producing basins picks up rigs, frac spreads and supporting infrastructure on the pad.<\/p>\n\n<\/div>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

02 \/ CLASSIFY<\/p>\n\n<\/div>\n\n\n

Say what it is<\/h3>\n\n\n
\n\n\n

Models separate drilling from completion from idle equipment, and attribute each pad to an operator and a well.<\/p>\n\n<\/div>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

03 \/ COUNT<\/p>\n\n<\/div>\n\n\n

Track the trend<\/h3>\n\n\n
\n\n\n

Counts roll up by operator, county and basin with history attached, so a shift reads against its own baseline.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n
\n\n
\"Illustrative
Every pad across the basin, classified the same way whoever operates it, with new crews flagged as they arrive. Illustrative positions, not actual data.<\/figcaption><\/figure>\n\n<\/div>\n\n\n
\n\n
\n\n

Whole-Basin Coverage<\/p>\n\n<\/div>\n\n\n

Every pad. Every operator.<\/h2>\n\n\n

Public operators report on their own schedule. Private operators disclose far less, and their activity is often the hardest part of a basin to see.<\/p>\n\n\n

Observation does not depend on disclosure, so every pad is classified the same way: drilling, crew on location, drilled but waiting on completion, or producing. Roll it up by operator, county or basin and the history comes with it, so each change reads against its own baseline.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n

Coverage<\/p>\n\n<\/div>\n\n\n

What is in the count.<\/h2>\n\n\n

Activity observed on the pad, classified and attributed, then rolled up so a change reads against its own history.<\/p>\n\n\n

\n\n
\n\n

GRANULARITY<\/p>\n\n\n

Pad to basin<\/h3>\n\n\n

Counts roll up by operator, county and basin.<\/p>\n\n<\/div>\n\n\n

\n\n

CLASSIFICATION<\/p>\n\n\n

Rig, spread or DUC<\/h3>\n\n\n

Drilling, active completion and drilled but uncompleted wells, told apart.<\/p>\n\n<\/div>\n\n\n

\n\n

OPERATORS<\/p>\n\n\n

Public and private<\/h3>\n\n\n

Every operator is measured the same way, because the measurement does not ask permission.<\/p>\n\n<\/div>\n\n\n

\n\n

ATTRIBUTION<\/p>\n\n\n

Operator and well<\/h3>\n\n\n

Each pad is tied to the operator and the well it belongs to.<\/p>\n\n<\/div>\n\n\n

\n\n

HISTORY<\/p>\n\n\n

Against its baseline<\/h3>\n\n\n

Counts carry their history, so a shift reads against its own trend.<\/p>\n\n<\/div>\n\n\n

\n\n

DELIVERY<\/p>\n\n\n

Where you work<\/h3>\n\n\n

Platform, agents, API, Snowflake or Excel.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n

In the Platform<\/p>\n\n<\/div>\n\n\n

Activity, on one screen.<\/h2>\n\n\n

Pad status across a basin, the crew trend and the operators moving it, in one view.<\/p>\n\n\n

Start from the basin and narrow to a county or an operator, with the history attached. When a crew arrives on a pad you are watching, it shows up here before it reaches a filing.<\/p>\n\n\n

\"Illustrative
Illustrative dashboard with synthesized data.<\/figcaption><\/figure>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

Who Uses It<\/p>\n\n<\/div>\n\n\n

One count, three decisions.<\/h2>\n\n\n

The same pad-level record answers different questions depending on the desk asking.<\/p>\n\n\n

\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Upstream teams<\/h3>\n\n\n

Watch offset operators and acquisition targets as crews arrive, and check the activity claims in a data room against the pad. Alerts flag a frac crew on a location you care about before anything is filed.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Trading desks<\/h3>\n\n\n

Read the direction of supply before surveys and production data confirm it, with the operators behind each move. Completions observed today become the production you will price next.<\/p>\n\n<\/div>\n\n\n

\n\n
\"\"\/<\/figure>\n\n\n

Lenders and investors<\/h3>\n\n\n

Check that an operator is running the activity it guided to. Each finding comes with the observation behind it, so a call on a position rests on evidence rather than on the borrower\u2019s update.<\/p>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n\n
\n\n
\n\n

Use Cases<\/p>\n\n<\/div>\n\n\n

What you can ask it.<\/h2>\n\n\n
\n\n
\n\n
\"\"\/<\/figure>\n\n\n

When did a frac crew arrive on this pad?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Which basins show a change in completion activity?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

How many DUCs is this operator carrying?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Which competitor wells look delayed against public expectations?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

Is this operator running the rig count they guided to?<\/h3>\n\n<\/div>\n\n\n
\n\n
\"\"\/<\/figure>\n\n\n

How long from spud to completion on this acreage?<\/h3>\n\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n
\n\n
\n\n
\n\n

FAQ<\/p>\n\n<\/div>\n\n\n

Questions buyers ask.<\/h2>\n\n\n
\n\n
How is this different from a published rig count?<\/summary>\n

Published counts are surveys. They depend on who responds, miss private operators and lag the move. This count starts with equipment detected on the pad, so every operator is counted on the same basis.<\/p>\n<\/details>\n\n\n

What does it detect?<\/summary>\n

Rigs, frac spreads and supporting infrastructure on the pad, classified as drilling, completion or idle, with drilled but uncompleted wells tracked until a crew arrives.<\/p>\n<\/details>\n\n\n

How soon does a change show up?<\/summary>\n

A crew arriving on location is visible once it is observed. The completion report that confirms it follows much later.<\/p>\n<\/details>\n\n\n

Can I get an alert when a crew arrives?<\/summary>\n

Yes. Watch a pad, an operator or an area and get notified when a frac crew shows up.<\/p>\n<\/details>\n\n\n

How does activity connect to production?<\/summary>\n

Completions are the leading edge of supply. The activity observed here feeds the well-level forecasts in Production Monitoring.<\/p>\n<\/details>\n\n\n

How do I get the data?<\/summary>\n

In the platform, through agents, by API, in Snowflake or in Excel, so the answer arrives in the system your team already uses.<\/p>\n<\/details>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n\n\n\n

\n
<\/div>\n\n
\n\n
\n\n

Get Started<\/p>\n\n<\/div>\n\n\n

Put a crew-level count behind your call.<\/h2>\n\n\n

Tell us the basin or the operator you need watched and we will show you the observed activity count against the published one.<\/p>\n\n\n

\n\n
Request a Demo<\/a><\/div>\n\n\n
Explore Solutions<\/a><\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n","protected":false},"excerpt":{"rendered":"

The Problem Counts you cannot verify are counts you cannot trade. Published rig counts are surveys. They miss private operators, lag the move, and tell you nothing about whether the crew on site is actually completing a well. Seen, not surveyed Equipment on the pad is detected directly, so the count does not depend on […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":3070,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-2978","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/2978","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/comments?post=2978"}],"version-history":[{"count":3,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/2978\/revisions"}],"predecessor-version":[{"id":3059,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/2978\/revisions\/3059"}],"up":[{"embeddable":true,"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/pages\/3070"}],"wp:attachment":[{"href":"https:\/\/synmax.com\/energy\/wp-json\/wp\/v2\/media?parent=2978"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}