Chevron Q1 2026 Brief: Hess, Bakken, Permian, and State-Record Production Signals
Chevron operator intelligence brief covering Q1 2026 production, Hess/Bakken context, Permian follow-up, and state-source label discipline.
By Johnathan · Reviewed by EnergyNetWatch Research · Historical report
Historical report
This page is a historical source-record snapshot tied to a specific company update or activity event. It links back into durable operator and state workflows.
Key Takeaways
- Chevron reported 2.024 MMBOE/d of U.S. upstream production in Q1 2026, up 24% year over year.
- Hess/Bakken and acquired-label rows need source-level identity review before being used as a single operator total.
- The requestable artifact is a Chevron/Hess state-source table by label, state, county, production month, permit, and well context.
EnergyNetWatch reviewed Chevron-linked state-source records across New Mexico, Texas, North Dakota, Colorado, and California in May 2026.
Operator Signal
| Field | Current signal |
|---|---|
| Signal grade | Source review |
| Primary source-record use case | Chevron/Hess follow-through by state, with acquired-label caveats |
| Company-reported U.S. upstream production | 2.024 MMBOE/d |
| Company-reported worldwide production | 3.858 MMBOE/d |
| Main Permian source-record states | New Mexico and Texas |
| Bakken follow-up | North Dakota Hess context |
| Primary caveat | Hess, PDC, Noble, and other acquired-label rows should be reviewed before being used as public totals |
| First follow-up | Chevron/Hess state-source signal-through table |
Chevron's company report says production scale increased. The state-record work starts with label review by state, especially after Hess, PDC, Noble, and other acquired assets are folded into the corporate story.
At A Glance
| Field | Current signal |
|---|---|
| Q1 earnings | $2.2B |
| Q1 adjusted earnings | $2.8B |
| Worldwide production | 3.858 MMBOE/d |
| U.S. upstream production | 2.024 MMBOE/d |
| U.S. liquids | 1.461 MMBbl/d |
| U.S. natural gas | 3.380 Bcf/d |
| Hess production bridge context | Guyana and Bakken |
| Expected Q2 upstream downtime | 100 to 150 MBOE/d |
EnergyNetWatch public state-record signal card for Chevron-linked rows. Public articles use rounded snapshots; authenticated workflows support current tables, maps, exports, alerts, and API delivery.
What Changed Recently
| Signal | Current signal |
|---|---|
| Company update | Chevron reported lower earnings but higher production in Q1 2026. |
| Production bridge | Hess added Guyana and Bakken context; Gulf of America and Permian remained important contributors. |
| Permian signal | New Mexico and Texas are the first public-record states to inspect. |
| Bakken signal | North Dakota becomes more important after Hess. |
| Acquisition caveat | Broader Hess/PDC/Noble rollups require reviewed label handling before public totals. |
The state-source work is checking where company-scale changes show up in permits, production windows, counties, and acquired-label rows.
State-Source Snapshot
| Field | Current signal |
|---|---|
| New Mexico Chevron-linked records | Roughly 67.8M BOE over the trailing 12M window |
| Texas Chevron-linked records | Roughly 49.7M BOE over the trailing 12M window |
| Colorado Chevron-name records | Roughly 74.3M BOE over the trailing 12M window; gas-weighted DJ Basin signal |
| North Dakota Bakken sample | 43M bbl oil and 125B mcf gas in the latest rounded monthly sample |
| California Chevron-linked records | Roughly 18.2M BOE over the trailing 12M window |
| Key caveat | State-source figures are rounded public-record snapshots, not consolidated company-reported production |
New Mexico and Texas carry the clearest Permian signal-through. North Dakota is the direct public-record angle for Hess/Bakken context.
Why It Matters
| Business question | EnergyNetWatch signal |
|---|---|
| Where should Permian review start? | New Mexico and Texas Chevron-linked rows. |
| Where does Hess matter publicly? | North Dakota Bakken context, separate from Guyana offshore reporting. |
| What can go wrong? | Acquired labels can remain visible in state records after the parent-company report changes. |
| What should be requested? | A Chevron/Hess source-label table by state, county, production month, permits, wells, and source dates. |
Infrastructure And Midstream Signals
| Layer | Public page treatment | App follow-up |
|---|---|---|
| T-4 / pipeline and facility records | Not published as a free Chevron/Hess lead list in this brief. | Review operator-linked route, facility, and county records by source label before treating them as project evidence. |
| Bakken and Permian context | Infrastructure stays separate from permits, production, and acquisition labels until source rows support the tie. | Request current maps, route/facility rows, source dates, exports, alerts, and API fields. |
| Why limited here | The brief shows EnergyNetWatch can connect operator identity to infrastructure evidence without releasing the full account table. | Use the app to decide which rows are current, source-linked, and actionable. |
What To Watch Next
| Watch item | Current signal |
|---|---|
| New Mexico / Texas Permian | Do Chevron-linked source rows move with the company Permian story? |
| Hess Bakken | Does North Dakota Hess/Bakken activity show current permit, well, or production changes? |
| Colorado labels | Keep Chevron-name rows separate from broader PDC/Noble acquired-label groups until reviewed. |
| Source dates | Track state-source lag separately from company-reported quarter dates. |
| Q2 downtime | Compare company downtime guidance with state-source activity as records refresh. |
What To Request
The requestable table is:
Request the current Chevron/Hess state-source signal-through table.
The export should include source label, state, county, production month, oil, gas, BOE estimate, permit context, wells, source dates, maps, alerts, and API delivery options.
Frequently Asked Questions
What drove Chevron's Q1 2026 production growth?
Chevron's production bridge cited Hess, Gulf of America, Permian, Guyana, and Bakken contributions.
How did Hess affect the public-record workflow?
Hess adds Bakken context that can be followed through North Dakota source records. Guyana remains company-reported offshore context rather than an EnergyNetWatch state-source table.
Where does EnergyNetWatch show Chevron-linked state records?
This public snapshot references New Mexico, Texas, North Dakota, Colorado, and California source-record context.
Is the EnergyNetWatch snapshot the same as Chevron's reported production?
No. Chevron's reported production is a consolidated company metric. EnergyNetWatch uses normalized state-source records that publish on regulator cadence.
Sources
- Chevron first-quarter 2026 results
- Chevron first-quarter 2026 presentation
- Reuters Q1 earnings coverage
- EnergyNetWatch static state-source snapshot, generated May 2026
Data notes
EnergyNetWatch state-source figures are rounded public-record snapshots used for operator, state, county, permit, well, and production-month review. Company-reported production follows Chevron reporting scope. Broader acquired-label rollups are treated as follow-up identity work unless explicitly reviewed.
Recommended next pages
New Mexico Oil and Gas Production Data: OCD Records, Permits & Spuds
New Mexico OCD production data guide covering wells, operators, counties, permits, reported spuds, source dates, and current table access.
RRC Production Data Query | Texas Oil & Gas by Lease
Look up Texas RRC production data by lease, operator, and month. Lease grain, not well.
How to Track Drilling Permits by Operator Before Production Shows Up (2026)
Learn how to track drilling permits by operator, connect permits to later production signals, and avoid common state-source mistakes.
Why Oil and Gas Data Is Hard to Normalize Across States (2026)
See why oil and gas data normalization is difficult across states, source schemas, identifiers, reporting cadence, permits, and production.
Related EnergyNetWatch pages
Want the current table behind this analysis?
Public articles use selected examples. Request access if your team needs current source refreshes, exact identifiers, maps, exports, alerts, saved workflows, or API access for this market.