Customer
Oslo VAV (Vann- og avløpsetaten) - the City of Oslo's water and sewerage agency.
Norway · Municipal water utility
From drive-by routes to daily fresh reads.
Oslo's Water and Sewerage Agency runs 5,000+ water meters across central Oslo on Divako - wM-Bus, NB-IoT and Sensus RF in the same pipeline. The drive-by rounds are gone, legacy Sensus iPerl meters are supported alongside new Apator Ultrimis, and the billing team sees fresh readings every morning.
5,000+
water meters · wM-Bus + NB-IoT + Sensus RF
~4 yrs
helping Oslo VAV scale remote metering
Daily
automatic reads · drive-by routes retired
At a glance
The shape of the rollout
A multi-protocol pipeline that absorbs both new and legacy meters without parallel systems.
Network
wM-Bus and NB-IoT for new installs; native Sensus RF support for the legacy fleet; wired m-Bus for local SD-system reads.
Meters
Apator Ultrimis (DN25-DN32) for new installs; existing Sensus iPerl meters integrated rather than replaced.
Integrations
Direct stream to Oslo's billing and analysis tools; REST/MQTT for downstream BI; full alarm routing for leak detection.
The challenge
A working fleet, but a manual one.
Central Oslo's water network already had thousands of meters in the ground - a working mix of newer Apator Ultrimis and older Sensus iPerl units. The problem wasn't the meters; it was getting the data off them. Drive-by collection meant scheduled rounds, manual hand-offs to the billing team, and leaks that surfaced quarters after they started.
Replacing the legacy fleet wholesale wasn't viable. Whatever came next had to bring the existing meters along - including Sensus iPerl, which most platforms quietly refuse to touch.
- 5,000+ meters in DN25 to DN32 sizes across central Oslo
- Mixed fleet: new Apator Ultrimis and legacy Sensus iPerl
- Drive-by collection - slow, error-prone, hard to scale
- Wired m-Bus equipment feeding a local SD system to integrate
What we built
Three protocols, one stream.
Divako runs wM-Bus and NB-IoT for the new Apator Ultrimis installs and adds native Sensus RF parsing so legacy iPerl meters land in the same data pipeline as everything else. Wired m-Bus equipment bridges the local SD system. Every payload is decrypted, parsed, range-checked and emitted as one harmonised measurement - whether it came in this morning over NB-IoT or last week from a Sensus iPerl that pre-dates the project.
From there, readings flow straight to Oslo's billing and analysis tools. Anomalies - leaks, drift, reverse flow - surface the same hour they happen, not at the next billing cycle.
- wM-Bus + NB-IoT for new meters · Sensus RF for legacy
- Wired m-Bus integration with the local SD system
- Unified parsing, validation and alarm rules across both fleets
- Direct flow to billing - no spreadsheets between meter and invoice
- Leak and reverse-flow detection routed to email, webhook or MQTT
Outcomes
What changed for the field and the billing team
Drive-by rounds retired
Manual collection routes through central Oslo replaced by automatic daily reads. More data, less time spent collecting it, lower carbon footprint to get there.
Fresh readings in billing
The billing team works from daily data, not quarterly drive-by spreadsheets. Disputes drop; first-time-right invoicing goes up.
Legacy meters supported
Sensus iPerl meters land in the same pipeline as new Apator units. No rip-and-replace, no parallel data system for the old fleet.
Leaks caught early
Continuous monitoring flags leaks, drift and reverse flow within the hour - not at the next quarter's bill.
"Drive-by rounds are gone. More data, less time spent collecting it, and a lower carbon footprint to get there - the billing team gets fresh readings every day."
More case studies
Other rollouts on Divako
20,000+
meters · LoRaWAN + wM-Bus hybrid
Three vendors replaced by one platform across Asker Municipality. Kamstrup, Axioma and Apator on the same console, same billing pipeline.
V200
precision piston meters · LoRaWAN
An early LoRaWAN water-metering rollout that's still running effectively years on - default network for new installs.
143
housing units · sub-metered & billed
Per-apartment cost distribution for water and heat. Residents see their use; the board sees the right invoice land.
Your rollout
Same shape, your city.
Tell us your meter mix and your billing system - we'll come back with a proposal and a rough number.