What is the gas-to-oil ratio, and why it drives flaring

If you've sat through an operator's earnings call or read a field development plan, you've seen the GOR number buried in a table somewhere and probably skipped past it. Don't. The gas-to-oil ratio is one of the few numbers that tells you, before a single emissions report gets filed, whether a well is going to flare.
GOR is simple arithmetic: standard cubic feet of gas produced per barrel of oil, usually written as scf/bbl. A well with a GOR of 500 is oil-heavy. A well with a GOR of 15,000 is basically a gas well with some oil riding along. Most unconventional plays sit somewhere in between, and the ratio tends to climb as a well ages and reservoir pressure drops. That climb matters more than the starting number.
Why a rising GOR forces a flaring decision
Oil gets trucked or pipelined with relatively little infrastructure. Gas needs a gathering line, a compressor, and usually a buyer at the other end of that line. When a well's GOR is low, the associated gas volume is small enough that an operator can often find a home for it, or at least tolerate the cost of handling it. As GOR rises, the gas volume rises with it, and at some point the cost of building or expanding gathering capacity stops penciling out against what that gas is worth.
That's the economic cliff where flaring starts. A rising ratio crosses a threshold that makes the stranded gas economics unworkable: the pipe isn't there, the basis differential makes selling the gas a net loss after transport, or the field is remote enough that building a line for a few years of declining production never pays back. The gas gets burned off at the wellhead because burning it is cheaper than moving it.
This is why GOR trends by basin are a better early-warning signal than permit counts or production reports alone. A basin with climbing average GOR and flat gathering infrastructure is a basin where flaring volumes are about to go up, regardless of what any single operator's self-reported numbers say for the current quarter. Permian wells, for instance, are notorious for GOR creep in later life, which is part of why that basin's flaring history looks the way it does even after takeaway pipelines got built out.
Stranded gas and the self-reporting gap
"Stranded gas" is the term for associated gas that has no economic path to market at the moment it's produced, given the infrastructure and pricing in place at that time rather than for good. Getting it from the wellhead to a buyer costs more than the gas is worth once you account for the pipe, the compression, and the processing. Flaring is what operators do with stranded gas when regulations allow it and venting isn't an option.
The reporting problem is that operators self-report flare volumes, and the incentive runs toward undercounting. A flare that's lit intermittently, or one that's flaring unmeasured casinghead gas rather than metered pipeline gas, is easy to underreport and hard for a regulator or analyst sitting in an office to independently check. You're relying on the same party whose economics improved by the gas getting burned instead of measured.
That gap is exactly the problem a nightly flare count is built to close. Instead of waiting on an operator's quarterly filing, Flare Monitoring reads night-time and SWIR imagery across a monitoring area and logs which flares are lit, how big they're burning, and how that count moves week to week. It doesn't replace the self-reported data, but it gives you an independent cross-check that isn't dependent on anyone's incentive to round down. For ESG analysts trying to model emissions intensity per barrel, or regulators trying to figure out which fields are quietly burning more gas than their permits assume, a GOR trend tells you where to look and an independent flare count tells you what's actually happening there.
If you're tracking a basin where GOR is climbing and want a nightly check on what that's doing to flare counts, Flare Monitoring is built for exactly that cross-reference.