On any gathering or transmission system, the total gas that comes in never quite equals the total gas that goes out, and the leftover difference has a name: lost and unaccounted-for gas. Some of it is genuinely gone, some was consumed to run the system, and some is simply the accumulated error of many imperfect meters. This guide breaks down the difference between gas received and gas delivered or consumed, the real-world causes behind the gap, what counts as a reasonable LUF percentage, and how tighter SCADA measurement and balancing narrow it.
Lost and Unaccounted-For Gas (LUF) in one line: Lost and unaccounted-for gas (LUF, sometimes LAUF) is the difference between the gas a system receives and the gas it delivers or consumes over a period, expressed as a volume or a percentage of throughput. It bundles together several effects - cumulative meter error, fuel gas burned to run compressors and equipment, blowdowns and venting, leaks, and occasionally theft - into one balancing figure that operators track and work to keep small.
The LUF calculation starts as a simple mass balance across a defined system: add up everything metered into it over a period, add up everything metered out of it plus everything legitimately consumed within it, and the difference is what is lost and unaccounted for. On a gathering system, gas received is the sum of all the well and receipt-point meters feeding the system; gas delivered is what leaves at the outlet meters to a plant or transmission line; and consumed gas is the fuel burned on the system itself. Whatever remains after that accounting is the LUF.
The word unaccounted-for is doing real work in the name. Part of the gap is accounted for in the sense that it is understood and expected - the fuel gas that ran the compressors, for instance, is a known consumption. The rest is genuinely unaccounted for: it is the residual that the operator cannot pin to a specific measured stream, which is why it functions as a catch-all. A system with clean, well-calibrated metering and honest accounting of fuel and vented gas pushes as much of the gap as possible into the accounted-for column, leaving a small unexplained residual, while a poorly measured system leaves a large one.
The largest and most persistent contributor on many systems is measurement error. Every meter has uncertainty, and when a system has dozens or hundreds of receipt meters and only a few delivery meters, small biases across all those instruments accumulate into a real volume. A batch of meters reading slightly high on the inlet, or a delivery meter reading slightly low, shows up directly as apparent loss even though no molecule went missing. This is why LUF is often more a measurement problem than a physical-loss problem, and why improving metering is usually the highest-leverage way to reduce it.
Beyond measurement, there are genuine physical losses and uses. Fuel gas consumed by compressor engines and heaters is a real withdrawal that must be accounted for or it inflates apparent loss. Blowdowns and venting during maintenance, pigging, or upsets release gas that leaves the system without passing an outlet meter. Leaks from fittings, valves, and older infrastructure add a chronic background loss. And in rare cases, theft removes gas entirely off the books. A reasonable LUF depends on the system's size, age, and metering quality, so operators judge it against their own historical baseline and investigate when the figure trends upward, rather than against a single universal number.
Because so much of LUF traces back to measurement, the way to shrink it is to make the measurement tighter and to watch the balance continuously rather than reconstructing it after the month closes. Continuous SCADA measurement across the receipt and delivery meters lets an operator compute a running system balance and see the loss figure trending day by day, so an abnormal jump - a meter that started reading badly, a leak that opened up, an unmetered vent - stands out quickly instead of hiding in a monthly aggregate. Catching the change while its cause is still fresh is what makes the difference findable.
A cloud SCADA platform such as Merobix helps by bringing every well, receipt, delivery, and fuel meter on a gathering system into one live picture where the input, output, and consumption totals can be balanced in near real time. When the running LUF moves, an operator can drill into which part of the system changed - which receipt group climbed, which delivery point dropped - and prioritize a calibration check or a leak survey there. Layering this on top of disciplined balancing turns LUF from a mysterious end-of-month shrinkage figure into a monitored operating metric, and a monitored metric is one that can be steadily driven down.
The terms overlap but are not identical. LUF is the balancing difference between gas received and gas delivered plus consumed on a system, and includes measurement error. Shrinkage more specifically describes volume genuinely removed or lost, such as fuel, flare, and processing losses. In practice a large share of reported LUF is measurement error rather than physical shrinkage.
There is no single universal figure, because it depends on the system's size, age, and metering quality. Operators generally judge LUF against their own historical baseline for that system, treat a stable low percentage as healthy, and investigate when the number trends upward. A rising LUF is usually a signal to check for a failing meter, a new leak, or unaccounted venting.
Since much of LUF is measurement error, the biggest levers are keeping meters well calibrated, accounting properly for fuel and vented gas, and finding leaks. Continuous SCADA measurement helps by producing a running system balance so an operator sees the loss trending and can pinpoint which part of the system changed, turning LUF from an end-of-month surprise into a monitored, controllable metric.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.