BIZTRAC BETA
Plumbing installation

OSLO BÆRUM VANN & VARME AS

Org. no. 925997013 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 4,000
Equity NOK 244,000
Incorporated 2020
Share capital NOK 30,000

OSLO BÆRUM VANN & VARME AS is registered as a limited company in Bærum, Akershus with organisation number 925997013. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive rørleggervirksomhet, samt kjøp og salg av tjenester og produkter som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 4,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 4,000
Equity
NOK 244,000
Est. value
NOK 118,000

Financial health · 2024

Liquidity
1.78
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.9%
Very good
Equity as a share of total capital

Who owns OSLO BÆRUM VANN & VARME AS?

MARTIN HJELSETH
OSLO BÆRUM VANN & VARME AS
NOK 1.5m rev. · NOK 4,000 profit

OSLO BÆRUM VANN & VARME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BÆRUM VANN & VARME AS

Who owns OSLO BÆRUM VANN & VARME AS?

MARTIN HJELSETH is the largest registered owner, with 100.0%.

What is the revenue of OSLO BÆRUM VANN & VARME AS?

OSLO BÆRUM VANN & VARME AS had revenue of NOK 1.5m in 2024.

Who is the general manager of OSLO BÆRUM VANN & VARME AS?

Martin Hjelseth is registered as general manager of OSLO BÆRUM VANN & VARME AS.

Where is OSLO BÆRUM VANN & VARME AS based?

OSLO BÆRUM VANN & VARME AS has its business address in Vøyenenga.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.