Non-revenue water is the gap between the water a utility produces and the water it actually gets paid for. Every litre treated and pumped costs money, so water that leaks away, is used without being billed, or is used but never registered on a meter is a direct drain on the utility's finances and on a scarce resource. This guide explains what non-revenue water includes, how it splits into real losses from leaks and apparent losses from metering and data problems, how the standard water balance organises the accounting, and how telemetry and metering help close the gap.
Non-Revenue Water in one line: Non-revenue water, or NRW, is the volume of water a utility puts into its distribution system that does not produce revenue, because it is lost, used without charge, or consumed but not correctly metered and billed. It is made up of real losses, water that physically escapes through leaks, bursts, and tank overflows, and apparent losses, water that reaches customers but is not billed due to meter under-registration, theft, or data errors, plus authorised uses that are legitimately unbilled. Reducing NRW recovers both water and money.
Non-revenue water is not a single thing, and treating it as one leads to the wrong fixes. The first and most physical category is real losses: water that actually escapes the system. This includes leaks and bursts on transmission mains and distribution pipes, seepage from service connections up to the customer's meter, and overflows from storage tanks. Real losses are water that never reaches a customer at all; it soaks into the ground or runs to a drain. Reducing real losses means finding and repairing leaks faster and managing pressure so pipes are stressed less.
The second category, apparent losses, is subtler because the water does reach customers, but the utility is not paid for it. Apparent losses come from customer meters that under-register and record less than the water that passed through them, from unauthorised consumption such as illegal connections and tampering, and from errors in the billing and data systems that drop or mistake consumption. A litre of apparent loss is arguably worse than a litre of real loss, because the utility incurred the full cost of treating and delivering water that a customer received and used, yet earned nothing for it. Finally, a small amount of water is authorised but unbilled, such as firefighting, main flushing, and utility operational use; this is legitimate and not a fault, but it is still non-revenue and must be counted.
To keep these categories straight, the water industry uses a standard water balance, often associated with the International Water Association, that lays out where every drop of produced water goes. It starts from the total volume put into the system and works down through authorised consumption, split into billed and unbilled, and water losses, split into apparent and real, until the boxes add up to the whole. Non-revenue water is simply the sum of the boxes that earn no revenue: unbilled authorised consumption, apparent losses, and real losses. Framing the problem this way forces a utility to name each component rather than lump all its missing water together.
The water balance is powerful because it turns a vague worry into an accountable structure. Once a utility populates the boxes with real figures, it can see whether its problem is mainly physical leakage, mainly metering and billing gaps, or a mix, and it can target its effort accordingly. The balance also exposes how much of the number is genuinely known versus estimated, which itself is a finding, since a utility that cannot measure its inputs and outputs well cannot manage its losses. Populating the balance credibly depends on good measurement of production and of consumption, and that is where instrumentation and metering come in.
Every box in the water balance rests on a measurement, and the quality of those measurements decides whether the balance is trustworthy. Production is the starting figure, and it comes from flow meters at treatment plants, wells, and imports that report their totals continuously through SCADA. If production is mis-measured, the entire balance is wrong from the top. Reliable, logged production telemetry is therefore the foundation, and having it stream into a central system means the input side of the balance is known day by day rather than reconstructed from occasional readings.
On the consumption and loss side, district metered area metering breaks the network into pieces small enough to weigh individually, so losses can be located rather than merely totalled. Continuous SCADA logging of DMA inlet flows supports night-flow analysis that separates real losses out area by area. Advanced metering infrastructure, which reads customer meters remotely and frequently, attacks apparent losses by catching under-registering meters, exposing anomalous or zero-consumption accounts, and feeding accurate consumption into billing. Together, production telemetry, DMA metering, and AMI populate both ends of the balance with measured rather than guessed numbers.
Bringing these feeds together is where a cloud SCADA platform earns its place. A hosted system such as Merobix, used across water, oil and gas, power, and other industries, can gather production and DMA telemetry into one continuously stored record that analysts reconcile against billing and AMI data to close the balance and watch it over time. With the balance updated regularly rather than once a year, a utility can see NRW moving in response to leak repairs, pressure management, and meter replacements, and it can direct its next actions to the category, real or apparent, where the losses and the recoverable revenue are largest.
Real losses are water that physically escapes the system through leaks, bursts, and tank overflows, so it never reaches any customer. Apparent losses are water that does reach customers but is not paid for, because of meter under-registration, theft, or billing and data errors. Both are non-revenue water, but real losses waste the water itself while apparent losses mean the utility delivered water and earned nothing for it.
Not entirely. A small part of non-revenue water is authorised but unbilled consumption, such as firefighting, main flushing, and the utility's own operational use, which is legitimate and expected. The concern is the rest, namely real losses from leaks and overflows and apparent losses from metering, theft, and data errors, because those represent water and revenue that could be recovered. The water balance separates the legitimate part from the recoverable part.
Utilities measure it with a water balance that compares the total water put into the system against billed and unbilled consumption and estimated losses. The input side comes from production flow meters reporting through SCADA, and the consumption side comes from customer metering, increasingly from advanced metering infrastructure. District metered areas let losses be located area by area, so the overall figure can be broken down and targeted rather than just totalled.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.